how would you advertise that in regards to nip65?

I remember fiatjaf mentioning the idea of single location specific relays as well. It's a long way off but it's neat to think about concert or conference venue relays that you could connect to while there or if you have to miss it, you could still see what's going on. It sent me thinking for a long time about what a marketable idea it would be to connect relay access to ticket sales & have a simple app to download that goes along with it. Then, if you're already using nostr, use what lever app you want but if you're not, you'd have a simple, clean, fun introduction.

Genius. Why not start taking advantage of the unique #freedomtech features we already have in #nostr

and then some clicks...

I like this and I'd like some guidance on how to implement this.

For more clarity on why I want to silo posts: (1) some people have unfollowed me who I think probably wouldn't have if they knew they would never hear me talk about that topic again, and (2) I can't stomach the political posts from Howard Chu on ActivityPub so I stopped following him, even though I really do want to still want to see anything he posts that is technical. So I'm looking at the problem from both sides.

Please consider powmem for deterministic content and spam redistribution.

I would've written a NIP, but I lack the experience and time to do it alone.

The relay explorer alpha can read and post from a single relay. It's fun to read the streams on smaller or topic specific relays, it's more of a community feel. Example explorer:

https://relay.tools/posts?relay=nrelay1qqw8wumn8ghj76r0w3exjemgw3hx7aewdehhxarjxyhxxmmd64ack9

There is also a directory for discovering new relays of any types.

Given that relays don't get scraped and rebroadcasted this could provide a bit of soloing your posts without having to run 10x the pubkeys just to have an opinion on 10 things.

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

hi

Isn't there a comminties nostr app/function already ?

I do agree with this. If I select interest in a specific topic I should be automatically connected to any relay dedicated to that topic.

I was just thinking this yesterday. I think hashtags could work like subreddits, which people could follow and even sort and build algorithms around.

Those communities might get large enough where a few relays basically handle that traffic and maybe relevant topics/hashtags/communities.

Is there a NIP for metadata tags on notes? AI could assign tags if and when the compute power is there.

What do you think of adding an optional "relays" tag to kind 1 notes such that other relays can refuse these notes?

"oh, this note was intended to only these other relays, so I won't bother storing them"

These would probably also fix the problem of the Japanese chatter that happens in some relays in a constant stream of responses without any tags and gets propagated to other relays totally out of context.

Would topical relays really solve this problem, cause the notes can still be broadcasted back to regular relays, and his regular followers can still see them.

Probably a dumb idea but sharing it either way.

Idk, I am not knowlegeable on the protocol or coding in general, but what you said sounded to me that it would centralize specific content in specific relays (?). Now gov could go after/blacklist at the IP level one "specialized" relay and an entire topic would be "disappeared" from the internet, provided the relay is niche enough.

Below is prob some dumb overview how to maybe do it?

New NIP where the Nostr protocol starts support a new post category that we can call Off topic (or anything else), and that can act as an unbrella for different tags/Topics.

Clients decide how best to implement it: Not at all, all posts from an nPub are shown even those tagged as off topic; full support, clients allow users the granularity to pic and mix what topics they'd like to follow, and allow them to tag their posts and manage tags in the client should they want to...

Either way, from a user POV, this is how I would like to handle the situation:

What Mike would do:

* Create a new tag Israel/Palestine, assign it to Off topic.

* Tag his new post with it (or Off topic if he don't wanna bother subdivide it) and post it.

What people who want to see his thoughts on the issue do:

* Either ensure they follow his Off topic posts, which would follow ALL tags he assigns to it. Or individually follow some tags inside of Off topic.

* Consider changing the default behavior of their client to follow an nPub's Off topic post by default when following someone. Or set it to ask everytime.

What would people who don't want to see his comments on the issue do:

* If they don't follow his Off topic posts, nothing.

* If they follow his Off topic posts or a specific tag inside of it, then tell their client to not show them anymore.

* Consider changing the default behavior of their client to not follow an nPub's Off topic post by default when following someone. Or set it to ask everytime.

What if you don't give a damn about any of this?

* Just keep using Nostr as usual and you won't even know it's a thing.

Everybody is happy, except for maybe Nostr devs who'd have to add this to the protocol/clients somehow...