NOSTR fix a Fediverce but ...
On a git hub of project is quite well explained why nostr came to life and why Mastodon and fedivers is broken
The problem with Mastodon and similar programs User identities are attached to domain names controlled by third-parties; Server owners can ban you, just like Twitter; Server owners can also block other servers; Migration between servers is an afterthought and can only be accomplished if servers cooperate. It doesn't work in an adversarial environment (all followers are lost); There are no clear incentives to run servers, therefore, they tend to be run by enthusiasts and people who want to have their name attached to a cool domain. Then, users are subject to the despotism of a single person, which is often worse than that of a big company like Twitter, and they can't migrate out; Since servers tend to be run amateurishly, they are often abandoned after a while โ which is effectively the same as banning everybody; It doesn't make sense to have a ton of servers if updates from every server will have to be painfully pushed (and saved!) to a ton of other servers. This point is exacerbated by the fact that servers tend to exist in huge numbers, therefore more data has to be passed to more places more often; For the specific example of video sharing, ActivityPub enthusiasts realized it would be completely impossible to transmit video from server to server the way text notes are, so they decided to keep the video hosted only from the single instance where it was posted to, which is similar to the Nostr approach.
The biggest call out that despite of all issues and bugs it is widely adopted platform. Lets go deeper to in
ActivePub
ActivityPub is a decentralized social networking protocol based on the ActivityStreams 2.0 data format. It provides a way for servers to share updates like posts, comments, and likes over HTTP, allowing for a distributed network of social media platforms that can communicate with each other. The protocol is a W3C Recommendation, meaning it has been endorsed by the World Wide Web Consortium, which oversees web standards.
Key Components:
- Actors: These are the entities that perform actions. They can be users, groups, or services.
- Objects: These are the items that actors interact with. They can be posts, images, comments, etc.
- Activities: These are the actions that actors perform on objects, like "Create," "Like," "Follow," etc.
How it Works:
- Client to Server: Users interact with their local server through a client, which sends activities to be processed.
- Server to Server: Servers can also communicate with each other to propagate activities across different nodes in the network.
Why It's Important:
- Decentralization: Unlike centralized platforms like Facebook or Twitter, ActivityPub allows for a more democratic and open web.
- Interoperability: Different platforms can interact with each other, breaking down silos.
- User Control: Users have more control over their data and how they interact with social networks.
As you can see a lot of simmularities and common features
The challenges of Fediverce
We've been investing in the ActivityPub ecosystem for years. Nostr is a better protocol, but it lacks the years of work that went into making the Fediverse usable. However, things are moving fast. This is partly because of the protocol, which is easy to implement and gives clients a lot of control. It seems like only a matter of time until it overtakes the Fediverse, and I'd rather be a part of it than get left behind. (c) soapbox
As you can see federated approch simply open a cenzorship hole and lock a user in a servers owners hands
Folks from soapbox create a bridge that allow to marry nostr and active pub mostr
Why Fedivers could be useful extension for NOSTR
I keen on video content creation and video streaming. NOSTR for now havent expanded to this type of content. We could reuse all features of Peer Tube and decentralized video hosting for a noster community. So we could use the best parts of 2 worlds that share a same values