Admin on the slrpnk.net Lemmy instance.

He/Him or what ever you feel like.

XMPP: [email protected]

Avatar is an image of a baby octopus.

  • 13 Posts
  • 243 Comments
Joined 2 years ago
cake
Cake day: September 19th, 2022

help-circle

  • Hmm yeah, I thought this is about organisation internal discussion. Of course if it is just a mailbox for outsiders to use, you could just configure some forwarders so that multiple people get the emails and can respond from their own account if necessary.

    Selfhosting email specifically is quite hard. Not so much technically, but because of how a few large providers have cornered the market and drop most self-hosted emails reaching them with the excuse of fighting spam.

    Hosting a forum that requires login credentials (incl. 2fa etc.) is quite easy though. But I guess that wouldn’t work as a way for outsiders to contact you.


  • I am confused why you would use a single email address instead of a mailinglist.

    It is also possible to set up a private forum with mailinglist capabilities.

    Generally speaking it is better to find a trust worthy host, or host on your own hardware than trying to repurpose some public service and hope e2ee alone is sufficient.







  • Well… there has been some recent museings about something like that from the CEO of Element, but it would effectively cause a two class federation where some servers can not work independently of others (likely in reality mainly servers running on EMS infrastructure, a bit like how in Bluesky you can’t really work fully independent of their infra, and yes Bluesky was explicitly mentioned as inspiration for that idea).

    Having those two options fully independent would basically mean reimplenting xmpp in json as an incompatible alternative protocol and that would make little sense IMHO.


  • poVoq@slrpnk.nettoPrivacy@lemmy.mlOpinion on the Matrix protocol
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    30 days ago

    While Synapse isn’t great, the problem is that the Matrix protocol is over-designed for a very specific purpose (distributed rooms), that comes with a severe performance penalty but most people don’t actually need this for chat.

    Its one of these cases of a neat idea on paper, but ultimately a solution looking for a problem.

    That said, Matrix isn’t that bad overall, but there are better options like XMPP.



  • Basically Matrix is to Xmpp, what Bluesky is to ActivityPub. Which all the various issues both technically and related to VC and crypto-currency funding.

    In addition Matrix uses a federation model that is extremely inefficient, making it hard to run your own server once you have a few users that join larger rooms. And as a side effect of this inefficient federation model that replicates the database onto all participating servers, it tends to centralize all the metadata on the servers (run on AWS under UK jurisdiction) hosted by the for-profit company that is behind Matrix.

    And last but not least they rugpulled everyone very recently and made the only fully functional server implementation open-core to upsell larger servers to their proprietary hosted offering.






  • poVoq@slrpnk.nettoPrivacy@lemmy.mlEncrypted messaging recommendations.
    link
    fedilink
    arrow-up
    15
    arrow-down
    3
    ·
    edit-2
    1 month ago

    No bridges are not end 2 end encrypted. The best you can do is host the server and bridge in your own home and thus have the bridge “end” in a secure location.

    If your friends and family are not very technical, then Matrix is probably a bad idea as it tends to be quite in your face about all sorts of technical issues especially with the encryption keys and so on. It works ok usually once everything is set up though.

    XMPP is IMHO the better option as the mobile apps are easier to understand and the e2ee usually works out of the box and stays out of the way unless you specifically want to mess around with it. For a friends & family server I recommend setting up https://snikket.org/ or rent a server from them cheaply.

    There are also good bridges for XMPP, but setting them up requires more understanding of self-hosting.



  • XMPP basically uses the same end to end encyption method as Signal, but due to it not being mandatory some things are easier but come with the footgun that you can accidentially disable it (but it is enabled by default in most modern xmpp clients).

    Otherwise: since XMPP federates more servers can theoretically see some metadata, but since most servers are small and community run there isn’t a single big target like with Signal where you can siphon off all the metadata. So you can make arguments for both. XMPP: more meta data but decentralized, Signal: less metadata but all in one place.