frame VS PhotoPrism

Regarding your earlier comments on Frame, did you try the AppImage? At least on the x86 side of things, the AppImage just works, and I don't think I've ever seen an AppImage that didn't "just work". The arm64 version can be seen on their releases page here: https://github.com/floating/frame/releases/tag/v0.6.6

Using frame.sh instead of metamask helps. It isn't connected to a single chain at a time, but all of the chains you've added. For example you can use dapps on multiple chains at the same time but never go through the step of switching networks. Also sounds like what you're really complaining about is delay period for fraud proofs, that should not be abstracted away because bridging without waiting is likely costing you more than you're making in returns if you bridge too often.

MetaMask provides an extension to add a wallet feature to your browser so that you can interact with dapps. This was the first project to provide this feature back in the day, but it's now quite outdated; A much better alternative would be Frame. A wallet needs an RPC node to talk to, and a new user doesn't want to have to worry about this, so MetaMask uses Infura as their default. But you can go into settings and change it, either to your own node or to a node hosted by someone else.

As your next step, I'd suggest trying alternative apps for accessing and managing your account(s). I'd personally suggest Frame (https://frame.sh/), but most use MetaMask (which is available as a browser extension).

gotcha, maybe check out frame (https://frame.sh) — you can import any wallets, hardware, seeds, private keys, etc. If you want to use it with any defi, there’s a companion browser extension.

I work on Frame (frame.sh) and used MEW to get a keystore file for testing our import keystore flow. The file I got was a different version (v4) and format from the expected v3, and our import flow does not support it at all. Digging deeper, we use `ethereumjs-wallet` to parse the keystore files - this library does not have a fromV4 method, and the existing fromV3 does not work at all with the MEW file.

Just wanted to install frame.sh as a new web3 wallet. It tells me to add "frame companion" to Edge, it warns me about:

So try MetaMask, or my personal favourite for stuff like this is: http://frame.sh and play around with derivation paths.

Frame Wallet does a few things Rabby doesn't and also supports hardware wallets but lacks the contact security check.

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