the only client that lets me specify a relay is nos social. would be interesting to see an implementation that instead of directly choosing a relay from my main list, it presents it as post as “topic” and thats a relay isn’t held in metadata, or at least not the main list, so I don’t submit notes that are off topic when I use any other client that doesn’t allow per post granularity.
Discussion
Amethyst now has the option for you to select which relays you want to post to as well. i'm not sure if it's used very extensively and but the option exists.
I think for topic relays to gain traction the clients need to do more hand holding, and not pulling from main relay list, so the relay op requires a bit less moderation of irrelevancy, for it to work and be worth it to set up a topic specific relay. Would be nice to see a relay implementation that would let me set up multiple topics using the same resource.
I think I understand the concept of filtering a feed to read based on relay, but what about writing?
For this to be useful wouldn’t it require clients to support the ability to choose which relay you’re publishing to when you write a note? Otherwise aren’t topical relays going to be full of notes unrelated to the topic?
Some apps, line mine nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch do support choosing which relays to publish to.
I think we could have relays that only host a part of a users posts, say those in a community / group / connected to a list / or with hashtags.
Also we’re building a viewer which shows who’s using and what content is on a relay. Hence I wanted to see what topical relays / content focused ones exist to test it out.
Yes, for now you have to use keywords.. eg. You could tell everyone the keywords and hashtags that get collected.. and then in addition you can further curate off topic spam.. relay.tools does this.
Coracle