6 ms·
Hey, I'm building that! https://photostructure.com/faq/why-photostructure/ https://photostructure.com/faq/why-photostructure/ The novel random "taste" UI make
by mceachen 4y ago
Hey, I'm building that!
https://photostructure.com/faq/why-photostructure/ https://photostructure.com/faq/why-photostructure/
The novel random "taste" UI makes navigating even very large libraries fun and serendipitous.
There are a ton of configurable image and video filters that can prevent the exif-less screenshots and other random nose from getting imported in the first place. Hop into the discord if you need any help with setup, I'm online.
(Also, know that I've open sourced a bunch of the core functionality, but this is commercial software, albeit with a very generous "free" tier).
- huimang 4y agoPersonally, with things as serious as photo libraries, proprietary software is a no-go for me. I'd rather use something with community support like Lychee than pray that e.g. photostructure will be available years later.
- mceachen 4y agoAs an open source developer for more than 20 years, I agree--using proprietary software that "locks up" your work leaves you somewhat of a hostage to that app. That's why all of PhotoStructure's metadata changes are stored using EXIF or XMP standards either within the file, or alongside in a sidecar (if you prefer). File organization is also completely customizable, and designed to work in concert with other DAMs, if desired. Details are here: https://photostructure.com/faq/system-of-record/ https://photostructure.com/faq/system-of-record/ Also: if the business ends, the code becomes open source. Details here: https://photostructure.com/faq/why-photostructure/#if-photostructure-inc-goes-away-photostructure-wont https://photostructure.com/faq/why-photostructure/#if-photos...
- huimang 4y agoThat's a fair compromise I think. Photostructure does look quite nice, so I'll give it a go.
- splitbrain 4y agoThis sounds like something I always wanted. But I can't really figure out if I understand correctly from your website. So could you please clarify: when I edit the keyword of a photo in your software, will this keyword be written back into the EXIF data of the original file? If so, you just got a new paying user.
- karolist 4y agoThis looks really nice and I think I'll try it soon in my home server. Out of interest, do you have some blog posts on the "how it's made" side of things? I see some toml files for configuration so that would point to core being written in Rust, what else? Thanks!
- mceachen 4y agoThe frontend is in Vue. Both the FE and BE are in TypeScript. Parallelism is provided by https://github.com/photostructure/batch-cluster.js/ https://github.com/photostructure/batch-cluster.js/ Metadata reads and writes are via https://github.com/photostructure/exiftool-vendored.js/ https://github.com/photostructure/exiftool-vendored.js/ Persistence is via SQLite: https://github.com/WiseLibs/better-sqlite3 https://github.com/WiseLibs/better-sqlite3 Image transforms are via Sharp: https://sharp.pixelplumbing.com/ https://sharp.pixelplumbing.com/ My more nerdier blog posts are tagged here: https://photostructure.com/tags/coding/ https://photostructure.com/tags/coding/
- karolist 4y agoThank you very much for all the links and detailed answer, I wish you all the best with this product and business.
- stackedinserter 4y agoHaha, I already built my own solution. :-)
- therealdrag0 4y agoWhat’s it do differently for you?
- stackedinserter 4y agoIDK it's just tailored for my own needs. There's nothing fancy there, standard features: importing from all our family devices, optimizing for browsers, showing date/folder trees, face recognition, showing on map, geotagging, etc.
- MitPitt 4y agono demo?