PhotoPrism VS tubearchivist

I have been using https://www.photoprism.app for a couple of years, and it works better than expected, with the latest updates it's actually quite fast and the face tagging works reasonably well.

For self-hosting, there's Photoprism[1] as well.

Ente's strength lies in end-to-end encryption[2] and its cloud[3] offering so you don't have to worry about reliability.

So if self-hosting is what you're after, Immich, Photoprism and Damselfly (TIL!) are perhaps better designed to serve your needs.

[1]: https://github.com/photoprism/photoprism

[2]: https://ente.io/architecture

[3]: https://ente.io/reliability

For quite a while I'm also in search for a solution which allows me to share galleries with my family, without having to ask them to jump through hoops in order to access them.

After some searching I'm now testing photoprism [1] which is a fantastic application, especially for self-hosting of photos. There's no mobile app for it (yet) and user-management is just starting to get implemented, but it shows alot of promise. Unfortunately not yet enough for putting it on the tablet of my granny but one can hope (and donate!)

Either way, I'm afraid that building a good mobile gallery app is an equally large task, after all the best solution would be to replace the users' native gallery-app with an equivalent that also supports custom Online-Galleries...

[1]: https://www.photoprism.app/

out of curiosity, why no sort-of-established pkg and internal dirs? What do you think of https://github.com/photoprism/photoprism structure?

Thank you!

Ente was first a piece of hardware, then a self-host-able project, but we had a hard time monetizing both, which lead to the E2EE pivot.

TIL about TagSpaces, thanks!

Our server can be open-sourced, but we're unsure of the value E2EE will provide, with services like Photoprism[1] and Immich[2] already doing a good job of serving customers who prefer to self host. In this context E2EE might become a constraint, rather than a feature.

[1]: https://github.com/photoprism/photoprism

[2]: https://github.com/immich-app/immich

Ive seen github issues like this one https://github.com/photoprism/photoprism/issues/907 in which it is implied that this is very very difficult.

Hi. I want to implement an image server similar to Photoprism using ImageAI to tag images based on objects and context. However I don't want to spend to much time working on the frontend, at first I were thinking about using Danbooru and use Flexbooru or the web interface on my phone. But it doesn't have any encryption or password protection (since the purpose of it is to be used as a public image board).

https://www.photoprism.app in Docker.

PhotoPrism[0] and some ugly plumbing[1] to semantically tag all images in the gallery.

0: https://github.com/photoprism/photoprism

holy hell I hadn't come across archivebox as of yet, I'll definitely be spinning this up this eve. Is the UI comfortable enough to use as a "bookmark manager"? just been setting up tubearchivist for essentially this purpose, wondering if ArchiveBox would essentially do the same

I'm using TubeArchivist to maintain this VERY large collection.

There appears to be a patch in Tubearchivest at https://github.com/tubearchivist/tubearchivist/issues/587

Personally, I use Tubearchivist.

There are others though.

https://github.com/tubearchivist/tubearchivist

I've been seeing TubeArchivist posted a lot recently.

It has been some time since the last release, but v0.4.0 is finally wrapped up. This brings a wide range of fixes and changes, particularly stability improvements, with our new file system naming convention, this should solve a bunch of previously unsolvable compatibility issues. I highly recommend reading the release notes carefully, as the filesystem migration could be a breaking change if you made changes manually there: https://github.com/tubearchivist/tubearchivist/releases/tag/v0.4.0

I saw this was a Django app so I dug around to look at their models. As far as I can tell this is all they have: https://github.com/tubearchivist/tubearchivist/blob/master/t... - just a `Account` model.

It looks like Django + SQLite is used for user accounts, but all other data storage happens in Elasticsearch.

It's an interesting design decision. I would have gone all-in on the database, and used SQLite FTS in place of Elasticsearch for simplicity, but that's my own personal favourite stack. Not saying their design is bad, just different.

Oh, so it is. I happen to run a TubeArchivist at home that grabs the videos and subtitles. Then I can search through the subtitle files for key phrases. I must have grabbed it while it was still public.

You probably want Tube Archivist. The only problem is that it’s naming convention doesn’t work with the Jellyfin YouTube Metadata Plugin.