> This conversation has led me to believe that we should proactively share the Nostr story, positioning it as the future of social networking. It's the future of social networking if the only thing you want to talk about is Bitcoin or Nostr. The technology isn't the problem: it's the lack of any discussion here about anything other than these two topics. This needs fixing before anything else. > This approach will also help us differentiate from platforms like Threads, Pixelfed, Mastodon, and Bluesky. While these platforms are based on open protocols, they operate as single-app, vertical silos. Mastodon is not single-app, nor is it a vertical silo. The interop with Pixelfed is excellent - it's the same underlying protocol - and there are hundreds of apps out there for it and thousands of servers running ActivityPub. What's the deal with pretending otherwise?
It didn't use to be that you could even seen content from mastodon to pixelfed and vice versa... I guess they fixed that... but clearly the fediverse model is confusing people: https://www.reddit.com/r/fediverse/comments/uj1kpj/i_cant_login_pixelfed_or_peertube_using_my/
"the fediverse model is confusing people" is a far cry from "it's a single app on a vertical platform", as you say in your original post. Meanwhile, I only see content from the Nostr relays I'm using, and not others. Surely, this is *much* more confusing - I have one username that works everywhere on Nostr, but if people aren't subscribed to the same relays as I am, they won't see my messages. This is "the future"?
That's not how nostr works. People can see content from you though they are not subscribed to te same relays.
mastodon is nice in theory- i would not consider it open- its been manipulated to be controlled by a few- anyone can cancel ur instance from the "fediverse" through a centralized block list- its total bs imho- worse than a company adhering to a TOS🤔😉✌️
There isn't a centralised blocklist. Each instance can choose whatever it wants to block. The closest to a centralised blocklist is that admins can choose to share a blocklist with others if they wish. I'm an admin of a Mastodon server. There's the option to "import" a blocklist as a CSV, but no more defined method of blocking instances exists in Mastodon.