you really shouldn't be getting "unable to decrypt" or "waiting to receive message" problems in Matrix since ~Sept 2024. The only scenario is if you have logged out of all your devices (so the sender has no way to encrypt for you), or if network federation is so broken that messages are flowing indirectly by other servers.

▲

cowlevel 3 days ago | parent | next [-]

"shouldn't" is secondary to what actually happens in the real world.

▲

vfosnar 3 days ago | parent | prev [-]

it still happens occasionally but i think its mostly something client side as sending a few more messages usually resolves it, thats still annoyin tho

but yeah i agree this should have been Matrix i see no reason for it not to be, this is just causing unnecessary fragmentation

	▲	Arathorn 3 days ago \| parent [-]
		fwiw, i'm sure y4my4my4m has good reasons for not using Matrix (beyond unable-to-decrypt memes) - i'd be genuinely interested to know what they are. For instance, i'm wondering if this is more about wanting to avoid being constrained by using an open standard, and instead being able to freestyle rapidly on top of activitypub? After all, it's much easier to go fast if you don't have to interop with anything else. Or consciously wanting to simplify the E2EE? Or having had a bad experience with Matrix server performance/complexity in the past?