Never knew about prelockd, seems like a pretty neat and useful idea, thanks!
Adding onto what's already on the thread, you can try look at the newer Element Call, which is an implementation of Matrix's native calls.
I've been using it a bit recently, since Jitsi seems to have stopped working reliably for me (to be frank, I've not put much effort into debugging it yet). It works well, but it's still early stage, lacking some features Jitsi has. If that one works for you, I recommend you stick to it.
Not exactly. Matrix 2.0 relates to the protocol (Matrix) version, which has its major number incremented due to a bunch of, well, major changes/updates to make it much better. OIDC, sliding sync and native calls are some of the new things that comprise the 2.0 update.
The server implementations are somewhat orthogonal to this. Synapse (the original Python server) is still the main implementation, and is Matrix 2.0 ready.
As far as I know, modern cards don't just send your CC info to terminals, they do some form of a cryptographic handshake (probably a pubkey signature or similar) which gets confirmed by your bank. I believe Caveman was talking more about online shopping, where you have to enter your card number, expiration date, CVC and often your name too.
Very useful, even for someone who has been using Linux for many years. Sometimes you just forget or need that tool you rarely use.
tldr
can be much handier than parsing a man page when you're in a pinch.I use the tealdeer implementation, but any is fine really.