Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
6. Defend your opinion
This is a bit of a mix of rules 4 and 5 to help foster higher quality posts. You are expected to defend your unpopular opinion in the post body. We don't expect a whole manifesto (please, no manifestos), but you should at least provide some details as to why you hold the position you do.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
view the rest of the comments
I unfortunately can't find a link to the article from a few months ago, but reading about the protocol and its development definitely makes it look like using it for a chat server was an afterthought. IIRC the protocol was good for keeping "events" in sync across multiple servers, and that was the entire intent, there was nothing chat-specific about the protocol.
And TBH after reading that, the "move fast and half-ass things" approach explains a lot of other symptoms. Synapse server is not a memory hog like it was in 2020 anymore, but does zero cleanup, and does not have an admin panel to do so yourself. Until 2-3 years ago, there was no official admin panel, just API calls (very inconsistent at that). And some cleanup (state_groups_state table) needs to be done directly on the DB! The client was generally fine, although timely notifications and attachments were an issue for some people. Onboarding was complete garbage. I give Vector/Element credit for having a consistent web/Android/iOS app though.
But now with ElementX/2.0 "rollout", it's a mess. Synapse is now part of corporatesque "suite", where each module is de-facto required. Element "Classic" is not maintained anymore, while ElementX does not have feature parity and is much slower than Classic for me.