meichthys / foss_photo_libraries Goto Github PK

We need a description for this feature that covers underlying photo structure / photo hierarchy.

Read only access could also be included here, but maybe this is better for another feature (?)

UhuruPhotos is a third party native android app built for LibrePhotos with many features. It will also soon support backup and sync

(Disclaimer: I am the developer behind the app)

All ticks, yay! ✅

https://lomorage.com/

Based on https://www.reddit.com/r/selfhosted/comments/wp9f72/photo_manager_recommendation/ it would be useful to add PhotoStructure, and apparently being able to read / display hierarchical tags (from Digikam) as OP asked for in that link is a relatively rare feature, so it might be useful as a row as well.

I believe there is at least one library from Awesome Privacy we can add here. Here is what we have missing.

Self-hosted

• Photostructure - Self-hosted photo library that makes browsing and sharing a lifetime of memories delightful.

Third-party (they all have differing free tiers. This would be a case where the "freeness" row becomes handy)

• Crypt.ee - A private and encrypted place for all your photos, documents, notes and more.
• Ente - End-to-end encrypted storage for photos and videos. Open source clients.
• Stingle Photos - Open source solution that provides strong security, privacy and encryption to backup your photos.

Local

• DigiKam - Awesome Professional Photo Management with the Power of Open Source.
• Photok - Photok is a free Photo-Safe. It stores your photos encrypted on your device and hides them from others.
• ImageGlass - ImageGlass is a lightweight software application whose purpose is to help you view images in a clean and intuitive working environment.

Does the application support other means of authentication?

• OAuth
• LDAP
  Etc.

I would like a good comparison with other apps in the chart along with Digikam. It is a FOSS.

Home of Digikam

iOS defaults to .HEIC for photos, which a lot of apps/services don't support. For example, Photoview supports it while PiGallery2 presently does not. This would be a major factor for an iOS user.

One key feature I'm searching for is the ability to use S3 object storage as backend. Services like backblaze and other offer this kind of storage much cheaper, but not all libraries seem to support it.

Hello again,

one could add the "Semantic image search", because it's amazing. It let's user search for content in images (not limited to 1000 classes). See this nice video to show it's power.

Librephotos has it (Source) and I started working on it for Photoprism here. No other offers this feature so far (as far as I know).

Cheer
tknobi

Hi, just came across this repo and found it helpful. Just wanted to share this link which has a lot of overlap in case it helps with expanding the list:

https://docs.librephotos.com/docs/user-guide/features

The ability for guests (non-users) to upload photos to the library is quite useful and is supported by at least a few projects (nextcloud, memories, piwigo(?), others?)

Google, Samsung, and Apple all have their own version of motion photos.

Can we add if the clients support viewing each of these versions properly?

One of the cool things about Google Camera and Google Photos is that when I take a picture, I get a short video of the photo being taken, embedded in the photo. I'd want to be able to optionally see this video in my new photo library.

https://shields.io/badges/git-hub-top-language

I'm one of those people who already had 100k+ photos organized in my own folder structure, and I also like to hop around from app to app on occassion as well. To me, a major feature of a photo library is whether it can handle that existing structure without changing it or importing into it's own proprietary database. Adding db/ini/sidecar files to it is acceptable, but moving or rearranging the photos/structure is not. I don't want to duplicate my massive trove of photos, and I don't want to have to extract them from a proprietary (even if FOSS) db if the project is abandoned or something better comes along in the future.

There may be different ways to implement this, so this could be a bit subjective(?)

Chevereto is a well-known image sharing software, the project started on 2007 and it has 4 major releases already.

Current project at chevereto/chevereto (old one here: rodber/chevereto-free)

We should add the project logos under the project name

Hi, I'm the developer of Damselfly, and it would be great to get it added here. Wasn't sure if you wanted the details via issue or PR, so I thought I'd start here. 😁

Repo: https://github.com/Webreaper/Damselfly
Github Stars: 682
Active Contributors: 1
Source Language: C# / .Net
Licence: GPL 3.0
Automatic Mobile Update: ❌
Cross platform access to photos: ✅8️⃣
LivePhotos Support: ❌
Mobile App: ❌ (planned mobile support here: Webreaper/Damselfly#40)
Photo Sharing: ❌
Docker Installation: ✅8️⃣
Object/Face Recognition: ✅8️⃣
Basic Editing: ❌ (planning to add crop/hue/saturation/rotate/etc later this year)
EXIF data viewing: ✅9️⃣
Multiple User Support: ✅7️⃣ (adding folder-based permissions later this year)

Other key features you don't call out in your table:
EXIF data editing: ✅9️⃣
Background Thumbnail gen and indexing (i.e., no need to manually update): ✅9️⃣
Comprehensive Search including free-text on EXIF metadata and various other search types: ✅9️⃣
Desktop App: ✅7️⃣ (provides sync to local laptop)
Export with watermarking and different resolutions: ✅7️⃣

This would be anything that 'curates' photos for the user.

Nextcloud photos now supports album sharing and collaboration

The app immich has added a new External Libraries feature with v1.79.0 which replaces the now deprecated read only gallery.

It may be worth re-evaluating the Existing Folders score.

I wouldn't want to end up with an unmaintained application like is the case with Photonix, so adding the year or month of last change would seem prudent, depending on the maintenance overhead this would be.

Maybe there are also automatic badges for something like this.

As the number of software and feature grows, the table is becoming too wide and long.

I suggest splitting the table into multiple ones like Comparison tables in Wikipedia

For example, divide the features into categories like General Information/App or client support/Format support/Functionalities etc, where different softwares are listed as rows.

Adding a row that describes whether or not the software allows you to make a directory structure or if it does its own thing that you cannot control would be nice. I personally prefer a directory hierarchy as compared to dumping everything in one folder and letting the program arbitrarily control it. That makes it hard to pull your images out of it and retain your organization. If I'm being unclear, paperless-ngx has a section describing what I'm talking about.

#6 is relatively close, but considering #20, I assume they are not talking about the same thing. If you think they should fall under #6, then please close this issue.

Hi,

For me, recognizing objects and recognizing faces are two completely different things. While objects are simply recognized, faces have to be detected, a person has to be recognized, suggested, labeled, filtered, clustered, ....

So should this be split?

Cheers
tknobi

https://photoview.github.io/

Keep old versions of photos when modifying photo.

We should add a short description of each feature and notes related to those features.

Hi

I think that having a shuffle/random photo feature is also important for a gallery app.

Some libraries like Photoview work with a read-only photo library, which is pretty important to someone like me where all uploading, editing and restructuring is done by other means.

https://github.com/xemle/home-gallery

Nextcloud memories moved their demo to a new URL: https://demo.memories.gallery/apps/memories/

See pulsejet/memories#702 for details.

Wonder if memories belongs here; could use some better visibility. Basically we've have feature parity with Nextcloud Photos now, except a couple of minor things.

Consider adding photofield to this list:
https://github.com/SmilyOrg/photofield

Hi,

I am not sure how easy it is to compare these as it obviously depends on the amount of data. But perhaps it would be possible to give an indication per product how much the minimum CPU and RAM requirements are.

Cheers

Application is free, and has no paid subscription.
People when choosing NAS are actually considering DIY build with Photoprism as an alternative to Synology Photos.
I think comparison of features and limitations of Synology Photos with competitors would be very useful.

"Tags", "keywords", whatever you call them, they're pretty much my killer feature.

"Batch tagging" (applying the same tag to multiple images at once) would be even better, but that's probably too niche. :)

It seems odd to put and "x" when even the issue linked shows that it clearly has some support. Especially since timestamp data is probably the most important, this should probably be bumped to a checkmark with at least a low number like 1 or 2 or something.