Outbox in Write: nostr.wine
Are your followers supposed to connect with Cellar to download your posts? If so, then add cellar.nostr.wine to the "write" part of the NIP-65 list. If not, if this is just for you, then this needs to be in an internal list in the client you use.
inbox.nostr.wine put it on the DM Relay List only.
Where do you want other clients to send all events that are mentioning (p-tagging) you, like zaps, replies, likes, streams where you are hosting, etc? That goes in the NIP-65 list with the "read" option. I don't think the "wine" company has a good option for that. So, your users might not be seeing replies without other relays.
The setting of "I want to read notes from x and y" doesn't have a place. Because no one else needs to know how you are reading your posts. It should be an local list somewhere in each client.
Your replies should go to whatever relay that author is using as public inbox. I don't think it's good for Nostr to send replies everywhere, indiscriminately.
My replies do go to the authors public inbox (though they also may end up on other relays).
So there is no way for me to use nos.lol as my public inbox on amethyst but only read events from filter.nostr.wine and never connect to nos.lol to fetch replies, correct?
Thats my predicament.
Currently, you can put filter.nostr.wine in the "General Relay" section so that the app uses that to pull posts to the phone. But that section will go away soon because of the outbox.
You can add nos.lol to the Public Inbox relays on Amethyst. That means that all users will send you information there. But Amethyst will connect to nos.lol as well :( to download your notifications.
youre gonna need a way to specify relays as "spam safe" like gossip does. that way it knows not to pull comment spam..
I was thinking in the opposite. Specifying which relays should be blocked and never connect. Does Gossip also has NIP-51 blocks? nostr:nprofile1qqsq0aun5tp6z7csek0ghr0n0leh7guq8wr57xtuxtgysv4e87gt9rgpz9mhxue69uhkummnw3ezuamfdejj77p470u?
Gossip client does not currently have NIP-51 blocked relays (10006). I'll open an issue for it.
"Spam safe" basically stops it from loading replies & mentions from strangers from ALL relays, and then you have to whitelist the relays you trust.
blocking is not a substitute for spam safe flags. since i still gotta connect to dirty relays of my damus follows and such.
Thread collapsed
Is the whitelist a nostr event as well? I noticed that NIP051 has 10012 for "Favorite Relays"... whatever that means...
I don't know what that means. I guess for recommending them to other people?
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
you should give gossip a spin. it might help you see what good gossiping does. (i recommend unstable branch)
Thread collapsed
Thread collapsed
Thread collapsed
Yeah that’s my main problem. I can feel all of nostr moving to a model where I’ll need to simply build my own client. It’ll probably eventually happen 😂
Anyway - thanks for pointing that out to me. I’ll fix the inbox part from the main list. It’s weird because I think Damus still uses the 10002 for their static relay list, so if I remove inbox from it I won’t connect to that relay anymore.
I think nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0 is the only one that lets me truly do that I want with our aggregator. Both app only lists and optional outbox relay crawling. Thanks nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe !
Also, I think you should separate DMs from Zaps and the other stuff in the Inbox relay.
Otherwise people will put in the Public Inbox and clients will build big filters to download zaps, replies, likes etc. And the relay will just reject the REQ because it includes kinds that it doesn't allow.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
