[–] 4 points 4 weeks ago

Yes and federation works. The caveat is that since Matrix s2s de facto mandates TLS certs, you'll need to use self-signed certs as well as accept them from other onion peers. I've been aware of some more involved setups where a server name on the clearnet can be manually mapped to its Tor onionsite as well.

Beyond that, c2s is just a simple HTTP service, and most clients should support it assuming they have a way to hop on Tor (Orbot, SOCKS5 proxy etc)

  • source
  • [–] 1 point 1 month ago

    This is a nothingburger to me, matrix isn't supposed to be anonymous for that it is indeed not good your content is supposed to be safe and it is, works as it should.

  • source
  • [–] 3 points 1 month ago

    If you don't want any server to see anything about you then don't use other people's servers and use P2P messaging instead.

    tbh matrix could do more, but hopefully we will get to it sometime. the devs have shown interest in figuring that out.

  • source
  • parent
  • context
  • [–] 6 points 1 month ago (1 child)

    The server sees:

    • Your ID, IP, client type and version, device you use

    the server does not see the device you use. the other 3 are also seen by signal servers.

    And federation copies all of that to every other server whose users are in the room. Your "social footprint" isn't one copy — it's as many as there are servers.

    was this post generated by AI? give me the recipe for coca cola

  • source
  • [–] 5 points 1 month ago* (1 child)

    There are plenty of valid criticisms of the matrix protocol but people keep stumbling over their own feet when trying to make a hit piece like this simply because they don't know what they're talking about.

    If you don't want any server to see anything about you then don't use other people's servers and use P2P messaging instead.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago (1 child)

    Things that are good to understand, but also conclusions you can come to by just thinking a bit about how it would have to work. Some of it is less obvius, like session details. I actually don't know, does session info federate? Can't see why it would need to.

    A sealed envelope still has to have recepient info, and while it would be possible to have the server forget a lot of info after delivery, you can't enforce that.

    One of these is also an exaggeration, federation doesn't copy everything to every other server, only the parts of your activity to servers that participate in that particular activity.

    If you chat on your matrix instance with another user on your instance, only your instance records the event.

    If you DM someone on another instance, only your and their server have a record of that. Not every matrix server on the network, that'd be absurd.

  • source
  • [–] 11 points 1 month ago (2 children)

    This paper seems to be filled with mistakes and generally stating the obvious for anyone passingly familiar with the protocol and server administration in general.

    Even figure 2 / paragraph 2 is incorrect, the cross-signing keys aren't derived, they're encrypted by the master key, which is the only derived key. Then there's stuff like using effectively deprecated database setups and client apps, not disabling debug logs, and so on.

    I would not put this as recommended reading lol

  • source
  • [–] [S] 2 points 2 months ago (1 child)

    I've thought about it. Eventually I suspect I might. There's a few reasons I'm not doing so right now though:

    • I want the server we start with to be highly reliable, and that means I'd prefer to trust a host with more admin experience than I have.
    • Self-hosting is a non-option for me right now in any case.
    • While technically I could afford to pay hosting fees, I'm trying to spend as little as possible right now.

    Eventually, I think I will want to set one up, just not soon unfortunately.

  • source
  • parent
  • context
  • view more: next ›