Yes, the eventual consistency model works more like a blockchain. Sliding windows are only hiding this fundamental flaw of data usage. It has an advantage against censorship, but it isn’t worth it & chat is better treated as ephemeral than permanent (look at how much info is lost behind proprietary Discord communities).
You can do basically everything except multiuser encrypted calls (we use Mumble for this anyhow). But even then Jitsi (& proprietary Zoom & WhatsApp) are built atop XMPP for the backbone of their protocol using XMPP to negotiate connections before handing off for calls.
You can also choose to use technologies that aren’t such resource hogs. The eventual consistency model of Matrix alone & storage costs causud many medium-sized operations to shut their doors. Distroot.org for instance had to move to XMPP to deal with costs—& I have personally seen others.
Synapse boasts about 50,000 concurrent users on a node. Ejabberd has been tuned to 2,000,000 concurrent users which shows how efficient & scalable the setup can be. €5/mo is a lot for many folks.
The default links many folks/projects share specifically log you into Element & on Matrix.org as well which advertizes more folks to be on that centralized node. Furthermore, Matrix provides hosting for some of the other big servers as well even if they are not using matrix.org in the address.
Patch Theory operates under the premise that patches commute & order should not matter until there is a conflict. Git will throw fits if you pull in a patch at the wrong order giving you a different snapshot.
You say this but Matrix is largely centralized so it would be easy to get the biggest node to comply. Servers are quite costly to run too which is a big problem.
NixOS is a bear to set up, but it is easy to keep it running for ages since the config is declarative & irons out configuration differences better than other OS since you config will refuse to evaluate.
I am thinking of moving to SailfishOS next year if my LineageOS phone keeps acting up.
The compatibility with Git means it is ultimately shackled to the design decisions fundamental to Git which require hacky workarounds. The maker of Pijul has pointed out some of the fundamental ways it can never handle patches is the manner of Darcs/Pijul, but I am not in the position to pull some of these quotes.
I would rather see revolution over evolution, & the weird ties to Google & hosting the project Microsoft GitHub rub me wrong.
Darcs came out in 2003—Git in 2005. It was novel at the time compared to the alternatives. Darcs started as alternative to CSV & Subversion, not Git. Unlike Git it works on patches, not snapshots which has advantanges in merge conflicts.
Darcs is sort of like Pijul before Pijul. It is a little slower, but might not even affect you at your project size, but what it has instead is a longer history with more tooling & support—on the CLI, support from package managers, forge options. It ends up being my preferred option just for this reason even if Pijul has better performance, handles binary files, & the identity server is novel.
Green washed. If they cared about sustainability they wouldn’t have removed the headphone jack for longer-lived headphones—and instead started selling their own branded Bluetooth earbuds like the rest of the manufacturers.
I would like to lose the Android phone soon. Signal will not work without an Android/iOS primary device.
But also… Signal requires a phone number for signup where a lot of countries require a passport to get a SIM (unique identifier that is easy to track you). The service is centralized so there is no sort of self-hosting option. There really aren’t alternative clients (not counting mere forks) you can rely on (this helps with the double ratchet encryption of clients with XMPP & Matrix losing keys) unless you go the gateway/bridge route—where the Electron desktop client is pure ass cheeks. Historically they have a big gap in commit history—we can assume there was some sort of CIA/FBI plant. They refuse to use a self-hostable MQTT/XMPP/UnifiedPush option for notifications meaning that the notification data timestamps always flow thru Google & Apple servers. And I am still salty the mobile clients removed SMS support which made it so easy to recommend to family in the first place.
Yes, the eventual consistency model works more like a blockchain. Sliding windows are only hiding this fundamental flaw of data usage. It has an advantage against censorship, but it isn’t worth it & chat is better treated as ephemeral than permanent (look at how much info is lost behind proprietary Discord communities).