Fuck no. You shouldn't have to trust people. End-to-end encryption should be everywhere.
>If you don't know anyone who hosts a fediverse instance that you trust you can always host your own instance, no trust required.
You're still talking to people on other servers run by other people.
>Encrypting stuff comes with a lot of drawbacks ...
This isn't an argument for not having the option there if the user wants it.
>Also if you try to apply encryption to everything everywhere you end up with stupid shit like NFTs.
What? NFTs don't use encryption.
You're still talking to people on other servers run by other people.
>Encrypting stuff comes with a lot of drawbacks ...
This isn't an argument for not having the option there if the user wants it.
>Also if you try to apply encryption to everything everywhere you end up with stupid shit like NFTs.
What? NFTs don't use encryption.
How are you supposed to know that your admin's not an asshole anyway? Telepathy?
- replies
- 1
- announces
- 0
- likes
- 0
Does everyone have to have those inconveniences? What about just people who opt for it?
But to do that people can just put their details (including keys) in their bio, which I already do.
The only thing that should be implemented on the fediverse, I think, is a standard profile field for keys and clients that automatically pin said keys and notify the user when they change (or maybe just display a history or the most recent change for users you don't follow to avoid blasting you with notifications). Maybe that would entail having a "blessed" messaging application. Idk, I'm not a dev.
But to do that people can just put their details (including keys) in their bio, which I already do.
The only thing that should be implemented on the fediverse, I think, is a standard profile field for keys and clients that automatically pin said keys and notify the user when they change (or maybe just display a history or the most recent change for users you don't follow to avoid blasting you with notifications). Maybe that would entail having a "blessed" messaging application. Idk, I'm not a dev.
And those applications use onion routing? I thought the onion routing applications were Session and Briar, not Tox and Jami.
Jami uses a centralised ENS gateway to resolve names last time i checked. https://docs.jami.net/en_US/developer/name-server-protocol.html. So every time you add someone to your list, the server knows about it.
Jami uses a centralised ENS gateway to resolve names last time i checked. https://docs.jami.net/en_US/developer/name-server-protocol.html. So every time you add someone to your list, the server knows about it.
I always thought how DHTs (and P2P in general) worked was that you could see everyone interacting with everyone.