Flipper

I manage all my services with systems. Simple services like kanidm, that are just a single native executable run baremetal with a different user. More complex Setups like immich or anything that requires a pzthon venv runs from a docker compose file that gets managed by systemd. Each service has its own user and it's own directory.

For Facebook it doesn't matter if its e2e. They control the client on both sides. They can just let the client sent the clear text data to them.

The food, the weather and the women created a seafaring nation.

https://github.com/rust-lang/rfcs/pull/3243

Only the rfc is merged. The others need work including implementations.

Difftastic looks really cool.

I know that a lot oft options are close and make different trade offs. But as you said yourself. The fulfill most criteria not all.

At least matrix doesn't let you move your account to other server. Also it doesn't minimize metadata storage. Its is stored on every server for a room.

The other two I don't know. I'll look them.up.

The perfect messenger would be open and private.

That means open source, federated with portable account's, e2e encrypted, minimal metadata storage, discoverable contacts, easy to self host as compute, storage and knowledge.

That doesn't exist as of today. Also it's really hard.

Pretty much everything is better than WhatsApp though.

Cursive was added later or modified to clarify.

First Problem is the Server nearly everyone uses is dritten in Python. There is no real way to migrate between implementations. That at least could be fixed.

Second Problem is the massive storage space usage. That one is by design and can't be fixed.

Based in activitypub. You should be able to follow a repo with mastodon or Lemmy and then see ticket updates for example.

But it's far in the fuyure

If a service doesnt offer Oidc, just dont self host it. The SSO service can then be properly secured and even if its only a password, at least its not reused.