- cross-posted to:
- technology@lemmy.ml
- cross-posted to:
- technology@lemmy.ml
Discord isn’t exactly known for generous file-sharing limits, still, the messaging app offered a 25MB limit to free users. The company has now updated its support page to reflect the upload limit for free users has been lowered to 10MB.
I moved a big group off Discord last year to Matrix chat (Element). It’s been largely pretty alright. 100mb upload limit, we have a bot that downloads tiktoks/Instagram/reddit videos and uploads them to the channel so you never have to visit the sites. Pretty nice! Open source and federated, you guys should give it a try!
Matrix is nice, but it’s still very bad UX wise.
I’ve used it on and off for years now, and about 2-4 times a month it loses my chat view encryption keys, and loses me my entire chat history. It also regularly has sync issues between devices signed into the same account, and is relatively slow sometimes to send messages.
Of course, that’s just my anecdotal experience, but I’ve tried many messaging platforms over the years, and while Matrix (and multiple of its clients, primarily Element) is the most feature-complete compared to Discord, it’s nowhere near properly usable long-term for a mass-market audience.
I agree, the security key thing is a bit of an issue. However this might a bit of a user error as well. The thing to understand is that Encryption keys are not stored on Matrix.org. If they were, then Matrix.org (or whatever homeserver you’re using) would be able to decrypt everything you can decrypt, thus making Matrix pretty useless. The solution is that keys are only stored locally on your devices. Keys are shared to other devices using the Verification process and Emoji matching thing. The problem is most users just go “Whatever!” And ignore the verification process and then have a bad experience because they don’t have Encryption keys.
The thing is, I did have encryption keys set up. The problem was that Element would repeatedly forget the very encryption keys passed by the other user, and would then have to request the keys again. Any historical message history would be permanently encrypted forever, and wouldn’t decrypt with the new view key.
After this happened about 4 times, I stopped using it, because it was impossible to maintain conversations for longer than 1-2 weeks before they’d inevitably be lost, and I’d then have to spend about an hour waiting for Element to receive the new encryption keys from the people I was contacting, even when they were already actively online.
I have no clue what was causing it, but it happened on multiple accounts, on multiple devices, all the time, and there was no conceivable fix. I’m not sure if this is fixed now, but I haven’t had a good reason to go back, especially with other encrypted messaging options out there.
I don’t know how you loose your keys all the time. But in that case you really should use a key backup.
Lose*
Would love to see the implementation!
I like bringing stuff to the fediverse by way of cobalt.tools -> catbox.moe (shoutout Catbox for so much 100% free hotlink bandwidth) (also the owner’s trying to find a CSAM content ID solution that’s not super expensive FYI y’all)
I’m using Maubot in a docker container with the Social Media Download Plugin. Here is a list of all the plugins: https://plugins.mau.bot/