• 0 Posts
  • 4 Comments
Joined 1 year ago
cake
Cake day: April 9th, 2024

help-circle
  • taking care of bad servers is instance admin business, you’re conflating the user concerns with the instance owner concerns

    generally this thread and previous ones have such bad takes on fedi structure: a federated and decentralized system must delegate responsibility and trust

    if you’re concerned about spam, that’s mostly instance owner business. it’s like that with every service: even signal has spam, and signal staff deals with it, not you. you’re delegating trust

    if you want privacy, on signal you need to delegate privacy to software. on fedi to server owners too, but that’s the only extra trust you need to pay

    sending private messages is up to you. if i send a note and address it only to you, i’m delegating trust to you to not leak it, to the software to keep it confidential, and to the server owner to not snoop on it. on signal you still need to trust the software and the recipient

    this whole “nothing is private on fedi” is a bad black/white answer to a gray issue. nothing is private ever, how can you trust AES and RSA? do you know every computer passing your packet is safe from side chain attacks to break your encryption? you claimed to work in security in another thread, i would expect you to know the concept of “threat modeling”



  • it’s not unrealistic to keep trust at the server level. following your rationale, you can’t trust my reply, or any, because any server could modify the content in transit. or hide posts. or make up posts from actors to make them look bad.

    if you assume the network is badly behaved, fedi breaks down. it makes no sense to me that everything is taken for granted, except privacy.

    servers will deliver, not modify, not make up stuff, not dos stuff, not spam you, but apparently obviously will leak your content?

    fedi models trust at the server level, not user. i dont need to trust you, i need to trust just your server admin, and if i dont i defederate