I would be SoL if I didn't have one of my original sessions upon making the account years ago still
key backups are a thing: element tries to make you save the recovery phrase. if you lost your recovery phrase and all sessions, you can still rotate keys and recover the account, just no encrypted history. it seems you're not familiar with matrix, not that the system is flawed
99% of rooms aren't encrypted so are completely and totally insecure anyway
if this is true, you wouldn't even be SoL if you lost your session: just rotate keys. very big rooms are unencrypted: what value does e2ee provide when the other end is 10k+ people? any of these may ne untrustworthy, you're just paying extra infra cost. also, if 99% of your rooms are unencrypted, how do you keep seeing encryption issues?
these statements seem excessively dramatic and in opposition with each other
you mention neochat and fluffychat. i explicitly said element, and element x on mobile
im rather upset at the fact that we have basically no choice: dendrite is getting left behind, construct is abandoned, conduit is weird and conduwuit is not super reassuring. on the clientside, fluffy mostly works but uses old crypto, cinny is slow and lacks a ton of stuff, nheko is a mess, fractal is really underfeatured and i don't even know what neochat is. using matrix basically boils down to "synapse+element(x)" or "lmao have fun fixing stuff"
it seems from your replies you lack understanding of how things work and are nonetheless choosing community clients rather than the stuff element does. super valid, i encourage you to do so, just maybe cast your judgment on the actual stuff you're using and not the whole project itself
i'd like to close saying that your anectodal experience is not of much value here: you are having issues? i'm not, and neither is all those i'm communicating with. what gives? it's instead observable that newer developments address the issues you're mentioning: transparent encryption and simplified sliding sync
element is entitled, ignoring feedback and constantly playing the victim. its practices with the protocol are despicable.
the protocol, however, works
your statement is so extreme it gets nonsensical too.
compilers will usually produce higher optimized asm than writing it yourself, but there is room to improve usually. it's not impossible that deepseek team obtained some performance gains hand-writing some hot sections directly in assembly. llvm must "play it safe" because doesn't know your use case, you do and can avoid all safety checks (stack canaries, overflow checks) or cleanups (eg, make memory arenas rather than realloc). you can tell LLVM to not do those, but it may happen in the whole binary and not be desirable
claiming c# gets faster than C because of jit is just ridicolous: you need yo compile just in time! the runtime cost of jitting + the resulting code would be faster than something plainly compiled? even if c# could obtain same optimization levels (and it can't: oop and .net runtime) you still pay the jit cost, which plainly compiled code doesn't pay. also what are you on with PGO, as if this buzzword suddenly makes everything as fast as C?? the example they give is "devirtualization" of interfaces. seems like C just doesn't have interfaces and can just do direct calls? how would optimizing up to C level make it faster than C?
you just come off as a bit entitled and captured in MS bullshit claims