Ask HN: Personal photo library recommendations? Open source, browser-based
I'd like to move away from Apples Photo.app to open-source, self-hosted, and browser-based application that may run on a NAS or Linux server.
There seem to be lots of alternatives out there (Nextcloud, Piwigo, ...) but I'd love to hear about recommendations and experiences.
120 comments
[ 3.1 ms ] story [ 192 ms ] threadOne feature I'm missing at the moment is raw conversion support. It would be great if thumbnails and previews of raw photos could be automatically generated. I've solved this via generating previews with ImageMagick, but native raw support in Piwigo would be better.
I just went through and renamed all my pictures by the exif create date, adding any unique names to exif UserComment.
I'm working on scripting all of this, but it works for me and I can pull data from anything into the directory. Everyone in the house can access it via samba and view the pictures.
It was way ahead of it's time, and actually worked!
Best of all, it did everything locally... not cloud based and thus retained privacy of your personal photo collection.
Doesn't help much for privacy, however.
It took multiple disparate photo directories and presented everything in a timeline of folders. And because everything was local, that happened quickly, rather than waiting for your browser to get the next 100 photo results from a javascript call or whatever.
Are there any photo clients for windows that present multiple folders as a single coherent timeline? And can manage tens of thousands of pictures? I've got stuff going back to the late 1990s and would love to be able to find all those old cat pictures or whatever.
PhotoStructure does this (and I believe is the only software that does robust time zone inference, as well). (I've posted elsewhere here with more details).
I'd love to have you try out the beta and have you share feedback!
One question though - if you end up feeling it's unsustainable to continue developing PhotoStructure down the line do you have a plan? Obviously we would rather not be burned by it either, you you consider at that point making it open source so existing users can continue and make improvements?
Certainly I hope it never comes to it but it's nice to have a little reassurance.
1) There's a corporate mandate to open-source PhotoStructure for Desktop in the event of business closure.
2) Your library consists of industry-standard files. If you choose to do so, your originals are copied into a standard YYYY/YYYY-mm-dd/ folder hierarchy. XMP sidecars are added to hold inferred or novel metadata and store nondestructive edits, like rotation. A SQLite db (with commented schema! it's pretty, honest!) holds asset-file-tag relationships, albums, and other non-file metadata.
3) It's just me, and I love open source, so if I can get to the point where my licensing stream pays for food and shelter, I can open source then.
It's really the killer-feature that made Picassa so great - find all the photos over several years of a family member or friend.
Sadly, I've needed this feature for funeral photo albums lately and could really use the old Picassa!
Sorry if I missed it, but is it possible (API or directly) to control Photostructure via python?
That way we could extend the features in many interesting ways - including our own face/object detection.
Nextcloud photos is not a photo application. It's basically a shared gallery with thumbnails. There's no metadata support or editing. No true multiuser access other than granting sharing through Nextcloud like Dropbox. The only good part is you can autoupload from your phone.
I've looked at several webapps, like Piwigo. Most of them feel like a single user application or have limited upload and metadata support.
The closest I have found is Digikam using external SQL, but this requires a local application carefully configured with a DB and a fileshare.
Piwigo definitely supports having multiple users. What kind of metadata do you mean? It supports tagging and reads and displays EXIF data. It has extensions/plugins for adding capabilities.
It looks pretty good, has multi-user capability, metadata editing, etc. It would be nice if it had some geotagging integration and ability to group albums into sets.
I filed a bug report and the developers/maintainers fixed it very quickly.
[1] https://github.com/LycheeOrg/Lychee
http://owl.phy.queensu.ca/~phil/exiftool/
PhotoStructure can read iPhoto libraries (and LR XMPs), and will coalesce both "sidecar" dupes (like JPG/RAW pairs), as well as images that were downsampled from other photo services (like Google Photos). It can leave your originals where they are, or copy them into a single time-stamped folder hierarchy (yes, you can edit the format of the timestamp if you don't like the LR standard). Files with the same SHA are not copied, but referenced in your library db.
Your library's metadata is kept both on disk (in XMP sidecars) as well as a sqlite db for fast access, and you can run queries on the db to do anything more exotic.
https://github.com/hooram/ownphotos
Have not had that weekend to try these options myself.
(I did take a brief look at it, it's fairly normal json)
http://koken.me/
(EDIT: clarified that the issue is the license; the source is readable)
[0] https://mediagoblin.org/
Agreed. I guess I could've been more specific in my original comment, easy of installation/maintenance are the things I wish they'd have worked on before worrying about federation. At this point I'm thinking about what will e the least painful way to migrate from mediagoblin to something else.
https://photonix.org/
Installation is fairly simple with Docker, frontend is web-based (React), backend is Python with a sprinkling of Tensorflow. So far auto-tagging of photos by location, object detection and colour is fairly decent. UI is progressing and is useable on most devices, though quite minimal.
Please feel free to check out the demo site and the GitHub issues. I'd really appreciate feedback and help. Thanks.
The UI for metadata is a bit unintuitive at the moment but you can scroll down to see it when you're viewing the fullscreen photos.
I've been struggling to find a tool that handles that handles the duplicates problem within a web interface. I've been experimenting with some approaches including perceptual hashes and was wondering if that's something you'll include?
Is there any way to use metadata from Lightroom Catalogs, or enable people tagging in your current implementation?
I don't have any experience of Lightroom but I can have a go at reading the files if you think it's useful.
https://github.com/jonathankoren/photo-autorganize
The thinking behind GraphQL was to allow for advanced filtering, supporting all the attributes we store without a lot of extra API work. The GraphiQL web interface makes it quite nice to explore the data and is bundled in and accessible at /graphql . GraphQL also has "subscriptions" which allows for pushing data from the server. The Apollo JS library I used also provides built-in extras like caching.
I'm looking at the docker-compose.yml and wanted to give it a go, but not allow it any way of deleting anything :)
I have checked this out, running the docker-compose method, and kudos for your work. Looks great.
One issue I ran into was regarding videos (tried with a couple of MOV and MP4) - it doesn't generate a thumbnail and in fact throws an error along the lines of: File "/srv/photonix/photos/models.py", line 84, in base_image_path AttributeError: 'NoneType' object has no attribute 'base_image_path'
Happy to open a gitHub issue, but thought I'd drop you a line here to see if it was your intention to support videos (which would be cool!)
Cheers,
https://perkeep.org/doc/
Which is a shame because I really like Perkeep/Camlistore as a concept.
-- Edit --
Actually on checking, it doesn't seem like Perkeep is at all dead. I'm seeing several updates in the last month...
Which seems to me fairly definite about it no longer being actively maintained. There haven't been any updates to that posted on the @perkeeporg Twitter at least.
I'm actually going to check out perkeep when I get a chance and see if I can't help out some.
It was/is very good. But patching it and PHP became a chore and I eventually migrated away to a messy matrix of Dropbox, Flickr, Google Photos and Apple Photo...
I should look into consolidating them all. Always tempted to write my own, aimed at photo albums for non-photographers... but it will probably not move beyond a readme.md...
[1] https://coppermine-gallery.net/
https://www.photosync-app.com/home.html
easy to set up, looks decent, even shows exif data like exposure time, lens used etc.
For example, I've gone back to Shantsel's UX research several times over the course of thinking through app designs, eg:
* http://shnatsel.blogspot.com/2012/08/irc-client-new-tab-mock...
* http://shnatsel.blogspot.com/2012/03/true-app-center.html
https://github.com/davidbanham/photobomb
I’ve used Lightroom and CaptureOne to manage my photo library but ended up using digiKam in the end because I can just mount a volume and use it from any desktop.
I can still take pics on the phone which will be synced via Dropbox and Shotwell picks them up immediately. The sync is faster than I’m used to on iCloud and finally I just have files that I can tag, again.
Shotwell is also super fast, has a similar UI to photos.app (automatic events for example), but it also had hierarchical tags which it can even write to the files itself. So it’s very simple and yet portable without lock-in. Couldn’t be happier. Of course ymmv.
Good luck!