I don’t see why we can’t just have an on-boarding experience where people select a few topics they care about or don’t care about. If they unselect Bitcoin, it can just filter out the 3-4 variants of it being mentioned.

Another good example is to filter #NSFW, or perhaps content warning events.

They can always go to filters and change them in future.

The only UX weird part is it’s kind of reversing today.. you select topics you don’t want to see.. normally you select what you want to see.

We don’t need this at the relay level - at least ignoring data consumption.

I’m still surprised we don’t have more universal in-client regex filtering of Event content. We likely need an encoding we can share them with too.

Thanks #[4]​ for the flow. One feedback we got from new users is that they get confused when you show them public/private keys and they scramble to copy or write it down. So we took that away. Just pick a username and you are inside. Then there is a task for you at the top to show where the keys are and if you want to back it up…!