We have a huge amount of work to do in that regard. I've got NIP-46 support slated for gossip 0.10, but I don't even know of any NIP-46 providers I can use to test it as I develop. 

 I think this is it https://github.com/fiatjaf/nak
https://cdn.satellite.earth/d03578cbdfdd0a0a43b5e3fcedab43dcfcb340dc1f7517f8d1f77ff45fef0238.mp4 

 we’re building a provider for nos.social. not ready for testing yet.  

 Great to see this!!

Will you support the new oauth-like flow and NIP-89-announce it for other clients to register accounts on? 

 Nak bunker is good for testing 

 I didn't catch your talk in Tokyo so I'm listening to it now.

I agree that we need to provide powerful mechanisms for feed curation, including as communities that moderate content, as friends that flag content, etc. Feed curation gets even more complicated than just "community norms" though. I don't want to see nudity when I'm working because it is potentially distracting. But after work I'm fine with nudity. Gossip now has lists, so you can choose what kind of content you want to see right now, and switch to something else later.

Gossip has "sensitive content" warnings. Gossip has person-muting and thread-muting. Gossip has spam filtering via script too. But it needs more.

I think NIP-32 labelling is a good idea but can't be programmed against without a hard ontology. NIP-56 reporting is a good idea but has a too-simple ontology. NIP-72 moderated communities are too siloed and won't include most of the people I want to follow. So gossip doesn't do any of this yet .. I'm waiting on a better solution to be proposed first.

I don't care if we aren't growing (I don't need growth to pay the bills), as I've mentioned multiple times now, but I guess I would care if we shrunk and withered away.