

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.


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.
No. They drink animal (deer i think) blood. It makes them weaker and gives them golden eyes, instead oft the red eyes. Its a whole plot point in one of the later books.
Well a shell script that can only run with Nash should include !# bin bash in the header.
Linux users: Everything needs to be dynamically linker. Otherwise it uses to mich space.
Also Linux users: Lets just ship a whole operating system AS a container so the dependencies are always the same.


For this generation we changed nothing. Except for the motherboard. K, thanks, bye.
Here is 25 Minutes about a bike tire is produced from dandelions. Though it’s only in German. But that also means there are no jokes.


You know how at some point ww1 was just called world war? Get ready for Cuban missile crisis 1 & 2.


A lot of German banks don’t want to deal with the hassle of a us dual citizen. Don’t know if it’s the same with french banks. But that could be another reason to give it up.


We wouldn’t even need to ban them outright. Just ban the usage for important things like windscreenwipers and climate control.
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.