To be fair, with Rust macros anything goes. There was an example where someone demoed descriping rust structs and enums nested as xml with a macro to parse it.

Signal dies something called sealed Sender. The idea is, the sender information is encrypted in the package. https://signal.org/blog/sealed-sender/

Well, unless you login and transfer all your keys every time, the client already has all the info required to fetch and decrypt all the messages.

I know that you can configure synapse to delete messages. However every federated server only operates on their own delete scedule and you as the reciever can’t see the messages then anymore. Which I think is stupid.

The messages should only be stored on the reciever device after they were delivered and deleted on the transfering server.

I think a messaging server should store messages only until they are delivered. It shouldn’t have access to who sent it, only where they are going.

Matrix keeps a massive stack of metadata on the server, because the server takes care of the protocol and it needs all that metadata.

However you can’t loose data you never aggregated.

How do you migrate everything?

Im more surprised it works at all considering it uses eac

You can limit upload size.

How do you make sure that the security flaws are patched promptly? Do you open a ticket on GitHub and simply hope it gets picked up by the devs?

No you dont expect free labour and pay them.

The way you currently say it, they tried to stop the exemption. They fought for the law, so OS gets an exemption.

Or do I understand you wrong?

We’ve got my 95 old grandma https://enna.care/ and she can use it. Instead of having to use the touch interface it works by placing cards on to an NFC reader.

What did you do about authentik always loading several seconds before login someone into a service?

One thing Torvalds enforces is not breaking userland. So it shouldn’t be kernel problems. More likely its some other lib that breaks compatibility.

Its also not the first pig cycle in the memory industry. There used to be over 20 manufacturers producing ram. These three survived because they didn’t massively ramp up production when demand increased. So they’ve collectively said, we are not really investing into production.

It’s also a lot harder to make money with open source. You would need to find something to offer on top for money. That can be hosting (nextcloud), support (redhat), consultation (hyper) or additional features(zeds AI offering).

In a side node: when building for geentoo it should be possible to build all rust libs as dylib. The compiler only offers a stable abi for the same version and all flags being equal. When building everything yourself that should work at the coat of updating the compiler requiring a complete rebuild of all libs.

Step one: Download a C or CPP repository.

Step two: Replace all semicolons with a greek comma.

Step three: ??

Step four: Poison Copilot, so that it randomly insert greek comas that the compilers totally choke on.

I don’t think chat control goes far enough! Most child buses happens in doors. We should therefore place a camera in every room so we protect the children. We should also add a screen that can’t be turned off, so we can stop the abuse faster than the police could arrive!

Just think of the children.

They can just sell their normal phone. As long as the user is able to run the installer it doesn’t really matter.

In the worst case it will just be Motorola shipping their base android version with verification and then just flashing grapheme over it. Just the way it currently works with pixels.