Can you please demonstrate how async workflows and monads resolve this issue?

Wouldn’t effect systems still be considered exceptions, but handled differently?

What does Google play do to remediate it?

Couldn’t you do that by just joining an existing server?

Does help combat censorship?

What about pushing out code anonymously to avoid lawsuits?

if enough people do it

And now will you make sure of that? As the other person mentioned, without a campaign, it’s futile. Most people won’t even hear of this

Xmpp definitely wins in privacy. What is there to privacy more than message content and metadata? Matrix definitely fails the second one, and is E2E still an issue for public groups? I don’t remember if they fixed that.

XMPP being a protocol built for extensibility means it will be hard for it not to keep up with times.

On your point of picking one or the other, I’d say pick the one you like and bridges will help you connect to the other. But XMPP came way before matrix, and I believe they fractured the community instead of building it.

There’s a good reason all the big techs built on top of xmpp (meta, Google, etc). It’s a very good protocol and satisfies modern demands very well.

Those problems you speak of about XMPP are not really a concern anymore and haven’t been for a while.

Matrix on the other hand is very difficult to implement, and currently there’s only one (maybe two?) viable implementation choices. It is way over complicated, resource intensive, and has privacy issues.

I really wish there was a system wide package manager for docker containers, which would update software in all your containers at once similar to how a typical package manager would.

I did not completely rule out docker, but I wonder if I can obtain most of its benefits without this major con with package management. I mean I know it’s possible, since its mostly kernel features, but it would be difficult to simulate and the tooling is probably lacking (maybe nsjail can get me closer).