Fedi doesn't have any centralized server, it's more of a combination of the middle and right.

Nostr and Fedi actually have a very similar architecture, with the main difference being that on the Fedi you are reliant on 1 server which manages both your account and aggregating your follows/notification/ect on your behalf, while on Nostr you manage your account and all your follows ect, and you can use as many different relays as you want at the same time.

This should hopefully take the power of censorship away from the hands of the relay operators and give the end user the final say in what they do or don't see.

Reply to this note

Please Login to reply.

Discussion

I still don’t understand how nostr really works, like if relays talk to each other for example.

I think sometimes they broadcast to each other, but usually no, they don't.

Honestly, the best thing to do would be to start reading the NIPs. #[8] & co. have done a really good job making them readable (not boring like the ActivityPub specs).

https://github.com/nostr-protocol/nips

Ok. Will do.

I need to read about it more too, but my basic understanding is that you use cryptographic keys to prove that you are the person making your posts/changes to your account, in a way similar to how crypto currency uses them to prove you are the person who made the transaction.

How that info gets from my computer to someone else's is still a bit of a mystery though.

After skimming through the NIPs, I didn't actually see any explicit wording for how relays talk to each other.

I imagine (again, having not done any actual coding on Nostr yet) that a relay could just act as a client to another relay and send/receive a bunch of messages that have already been signed by completed unrelated entities.

A message is just a message that I can pass around, whether I'm the one who created and signed it, or if it was created and signed by someone else. As long as the message ID checks out, then it's a valid message.

See https://github.com/nostr-protocol/nips/blob/master/01.md#events-and-signatures

Got it. Thx.