But how do you handle the aggregation, syncing and re-writing of events? I noticed that a lot of things *eventually* end up on nos.lol or one of the nostr.band relays one way or another, which is kinda interesting. Also, caching servers like Primal will just lump all events from all relays together into one big mass.

I like the idea of topic-oriented or community-focused relays a lot (because it would make it easier to "get rid" of some topics) but right now, Nostr is very small and surprisingly interconnected - indirectly, through syncs and rewrites.

So rather than making relays "enforce" a topic, what if we took more advantage of tags? For instance, instead of just a regular hashtag, we could add a literal Topic tag, allowing the post to have a soft-heading. Future clients could allow you to then not just follow that user, but maybe just show events related to a topic. You shouldn't have too many topics, naturally, but if you use the same npub for updates of your app and your personal thoughts... you have two clear topics. Now a user might chose to only see your app updates, but not your personal thoughts - whilst another user wants to see both.

This approach would allow the syncing and rewriting to continue as it is right now, be backwards compatible (since it is just an extra tag) to older clients but still offer clients to implement this feature just fine - and it would also still be optional.

Unfortunately... that is the best I ever came up with in regards to this :/ It feels a little underwhelming but... yeah, that's what I got. o.o