News for hackers. Stuff that matters.
Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by mceachen on Tuesday March 03, 2020 @12:49PM (#22476851)
I've made a bunch of design decisions to address long-term storage concerns (after being personally burned by more than a handful of abandoned photo apps):

File storage (if you opt for PhotoStructure doing automatic organization) is configurable (with a default of $library/yyyy/yyyy-mm-dd/$original-filename).

All metadata extracted or changed is saved in standard-format sidecars next to the original, or in the image itself. The sidecar format and whether to use sidecars for edits are both configurable.

The database is a SQLite DB with a straightforward schema (although as I add features, each version has had db migrations).

If you try PhotoStructure out, and you find or think of anything else I can do to set things up to be more friendly to long-term storage, I'd love to hear your ideas.

(Sharing is coming in a future release, both via any hierarchical tag, or by manually-selected images).

Re:How Retroactive makes Aperture, iPhoto, and iTunes work a... by jwr on Wednesday March 04, 2020 @05:16AM (#22482561)
Everything you wrote is very intriguing and largely aligned with my goals. I'd like to take a closer look at what you are building.

There is still the issue of control: I am worried about the lack of a "Pricing" page, not because I do not want to pay (quite the opposite), but because I am worried about the sustainability of your business. And about what will happen when you sell it to Google, or otherwise abandon it.