You can be censored on the client level. It happened to bot with the flagship Android app. Theoretically relays can do it too, although they rarely do (though early this year, I think I was the first person on Nostr to be censored by some relay operators. Also had my verification revoked.)

The bigger problem though, is that a lot of stuff is still coming in from Poast, where I’m hidden.

As long as Nostr is relying on Fedi for content, it’s subject to the same limitations in reach.

Alex can’t finish his hybrid software quickly enough. 

 > Theoretically relays can do it too, although they rarely do (though early this year, I think I was the first person on Nostr to be censored by some relay operators. Also had my verification revoked.)

That's going to be a tough obstacle to overcome. The verification component isn't being put in-place for giggles. 

 No, it’s actually not what you probably think. All verification does here is make you searchable by a unique @ rather than your key.

The way relays work, it’s not that big a deal unless a bunch of them censor you, either. 

 It seems like they'll take control of the relays if it ever catches on. I looked into it very briefly when everyone was first talking about it, so there's probably things I'm not up to speed on. 

If censored, another key-pair could be locally generated, but that would be a start from zero every time. Sure, it's doable... but it would be impossible to build any momentum if ever desired.

Hopefully they can work out the kinks. The relays look to be a much larger issue when compared to the client. 

 Who is “they?”

No one is going to take over every relay, that doesn’t make sense.