Estudante de Engenharia Informática apaixonado pela área; algures em Portugal.

Administrador da instância lemmy.pt.


Computer Science student, passionate about the field; somewhere in Portugal.

lemmy.pt instance administrator.


https://tmpod.dev/

  • 36 Posts
  • 165 Comments
Joined 3 years ago
cake
Cake day: September 10th, 2021

help-circle




  • tmpod@lemmy.ptMtoPrivacy@lemmy.mlPrivate videoconferencing ?
    link
    fedilink
    English
    arrow-up
    0
    ·
    12 days ago

    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.







  • That’s why I love virtual card systems like MB NET. You just generate a random virtual card for every purchase (or a recurring one for each subscription vendor, for example) and move on. Your bank still knows what you’re doing, of course, but vendors can’t correlate anything. Preventing your bank from knowing where you’re spending your money is much harder, for very practical reasons: fraud detection. The only real way is to use a secure crypto coin like Monero, but very few places accept it and you still have to deal with volatility.