Right now, images are stored as uploaded blobs. This has a few downsides:
- I don't quite understand how they work. My initial solution was base64 encoding, and AI suggested file blobs, and I went with it.
- They don't persist across refresh.
- They don't export and re-import with the Markdown file, so you have to manually re-upload the images as you go along.
Potential solution could be to dump all images to a CDN and reference them there, or to fight more with local image storage to get a better UX.
Update, 28 October:
After doing some research, I think Cloudinary is a good move, especially if we can script periodic cleanup of old assets via API. Their free tier is generous enough to work for now. We could also store images as attachments in PouchDB (https://pouchdb.com/) and reconstitute them as blobs. I generally bias away from extra services and towards local storage, but I need to think more about this.
Right now, images are stored as uploaded blobs. This has a few downsides:
Potential solution could be to dump all images to a CDN and reference them there, or to fight more with local image storage to get a better UX.
Update, 28 October:
After doing some research, I think Cloudinary is a good move, especially if we can script periodic cleanup of old assets via API. Their free tier is generous enough to work for now. We could also store images as attachments in PouchDB (https://pouchdb.com/) and reconstitute them as blobs. I generally bias away from extra services and towards local storage, but I need to think more about this.