My advice would be to target the teens. They seem to switch social nets at the drop of a hat (speaking as the father of one). Get a bunch onto your network, then let them experience the fact they can still speak to their mates on another network. Then the penny might drop and you'll soon get them proselytising about the benefits of federation.
I know the protocol looks fairly simple at first glance but it takes about 2 man years to build a decent implementation, which frankly just means it's too complicated. Sending text ultimately should not be that hard. One huge point of friction I found with the protocol was the failure to just make things type-safe. You have lots of object properties that are "Sometimes a string", "Sometimes an array", etc. That makes all your models super ugly and all your marshaling super ugly.
By comparison, Nostr proved you certainly can avoid all the complexity. Nostr got it right. Nostr kept it simple. And Nostr is censorship resistant unlike the Fediverse which is full of politically motivated admins who love to maintain "block lists" to be sure no "Other Viewpoints" (that disagree with their own) are allowed to proliferate. Admins were having their entire servers blocked simply for saying something nice about some POTUS candidate for example. That just creates a very toxic environment, from all the people who of course claim they're fighting toxicity.
I believe that in order to successfully and safely move posts between nodes they need to be immutable and signed. Because you're essentially creating a new history on a new node.
Whichever way they choose to resolve this issue I think it's a major pain point for the fedi to grow.
From an end user standpoint Nostr is way too complex. If we're talking about the fedi being complex, Nostr can forget about it.
But maybe you can prove me wrong. I setup my first fedi node back in 2017 in minutes because there was a container image, people could start signing up immediately. Can you show me how to do the same in Nostr?
