toastal

Not open? Wat

Privacy is one part. The cost of joining & maintaining a server on the network is the other. Many servers have shut their doors due to expensive hosting. If you are lenient on how many messages need to actually be stored on the server for archives, self-hosting is now much more accessible which leads to a healthier, more decentralized network since more nodes can afford to join.

You can still creating your own archives in your clients or on your specific server via s2s communications, but Matrix has this as a network requirement for eventual consistency. You can’t have the “search all messages in the last 5 years” feature without eventual consistency—but this is the point I am trying to make: copying the Slack/Telegram/Discord model makes this a requirement to have in a decentralized sense which costs way too much. Step back & reassess if copying this model is the right call. We were fine last decade without this.

Drag can archive it locally just fine or on Drag’s own server if using a different protocol. Is it worth storing hundreds of thousands of messages & attachments that price out self-hosting & low-spec hosters & medium-sized communities on a budget? These storage costs add up quickly & without lots of nodes, the network is no longer federated but held by a few mega hosts like Matrix.org & a sprinkling of single-user hosts. I have seen many servers shut down due to costs. This tradeoff just isn’t worth it for a triving, decentralized platform (Mastodon suffers similar duplication issues).

Libraries are clearly communist… or anarchist… either way, I hate it!

It is a standard, starting at RFC 6120. Everyone can use it today. 😃

Since we are on a decentralized platform & many of us care about federation, do yourself a service & read this little history lesson: How to Kill a Decentralised Network (such as the Fediverse) (archived)

Same reason it is weird to want a FOSS copy of the UX of Slack/Telegram/Discord in Matrix instead of realizing you don’t need or want the chat history to persist for eternity. Good thing you can choose a different protocol/service in these cases.

Does the job

Well, we start be organizing the folks of Lemmy to understand the values of the old protocols instead of trying to chase the shiny new ones. “Ain’t broke, don’t fix it”

The web client is serviceable.

There are advantages, but I think a lot of folks are tracing trends in this space (including trying to copy Slack/Telegram/Discord rather than be better or strip the bad parts out). Newer ≠ better.

ｌｅｖｅｒａｇｅ