Are there any clients that allow you to specify which relays a note will post to on a note by note basis?

Suppose I have a private fren relay where I want to post my spicy notes, but only allow like 10 npubs to read from it?

Would this work?

Reply to this note

Please Login to reply.

Discussion

Damus actually had this at one point but I removed it since it seemed niche and confusing at the time. May bring it back.

I would really like this feature, so only you and a few other frens can view my nudes

I can see its use case. Just yesterday, we were planning to have a relay for our existing friend circle. So even if Nostr grows rapidly, we will still have our current Nostr friend circle.

Yes private relay sets should have proper support. Will just take time before that’s ready. Has many ui considerations so that’s its not too confusing.

I can understand, please take your time πŸ€œπŸ€›

I can also see a good use case for this. If a user wants to support paid subscriptions to their notes/long form articles, they can post to a specific relay that only allowed paid subscribers to read from.

Ideally you could have this be in a form where the author also gets paid. It works for one author per relay but to scale to one relay to many authors, something like delegated 3rd party caveats in macaroons could work. You could also use nostr to not just get the content, but leave the content encrypted and then users could only read it once the relay gets a decryption key from the author after a confirmed payment.

Yeah I mean that encryption key idea is similar to the Bitcoin 2019 hackathon idea you did right?

Heh, yep exactly. That used blockstack's distributed storage protocol on top of their blockchain. But this could probably be done just as well with nostr.

Yes that would work

I believe nos can do this

This would be a great feature to expand the use of topical relays.

I would use this.

#devstr #devstrClients #DevstrRelays https://devstr.org

A small ux thing which would work wonders for topical discussions would just to gather all the seen hashtags, and during post composition suggest to implicitly tag the post with popular ones or ones you’ve saved, and the ability to follow hashtags.

Technically the client I am working on can only post to one relay rn lol it’s Damus relay but the concept can apply all the same, you don’t need to use relay pools

You can do something like this in Coracle, although you do have to unselect your default relays first one by one. After that you can search by text for the one relay you wish to select I think...

I'm not sure how the settings are saved for the next post.

u use another npub that simple example

1 npub -> main captjack

2 npub -> privatejack (storing in localDB relay)

3 npub -> subscribe to paidcontent perview/weekly/daily depends

4 npub -> publishing

5 npub -> specificgroup

Yep basically just thinking this, I will have dankutxo and regular utxo

also fact that if publishing - cooking - science - technology - medical - economic - comedy --- audience will hate to see it posted from one npub

many people just focus on certain topics in their timeline - depends on mood

u can RESTRICT access by npub LIST RW for private / paid / contentbased relay - must run multiple instance of relays in same of multiple hosts

Better off finding another app/client or finding another device entirely.

I've not found a client that can do this on a note by note basis.