So, I’m listening to @Mike Dilger on @BitcoinReview discussing inbox/outbox relays, and I’m starting to realize, I have no idea how @damus handles this. All my relays are just “relays”.
Is the in/out handled under the hood? Are my particular relays “both”, or does it not matter if I’m mostly sending and requesting Kind 1 notes?
I believe I’ve seen them sorted into inbox and outbox in Amethyst, maybe in Gossip, too.
Time to learn 🫡
#asknostr
Cc @jb55
i started building nostrdb so that I could do outbox in a safer way without worrying about rogue relays. its a slow WIP but its coming. we're calling it relay autopilot.
🔥🔥 that’ll be a good name 🤝
Gossip considers those relays as both write(outbox) and read(inbox) for you. I don't know what NDK does or what other outbox-model clients do.
I expect to see middleware that handles the outbox model relay fanout issue.... what I am calling a 'client proxy'. You would have to trust such a service. And Damus would be a good client to use such a service.
Oddbean new post about login | logout