the year is 2024, nostr has been frozen in a self imposed note lockout.  people abandoned the spam filled relays and retreated to long time paid or wot relays, and relays with access control.. only to realize their client doesnt do outbox and their network is now hidden from their view.

blastr closed down and cant cover up the problems with clients anymore.  the ones that *do have outbox clients, huddle around a small note fire for warmpth, and accept that their centralized frens may never be heard from again.

🦖🦍🌎 #outboxtales nostr.oxtr.dev 

 which relay software has IMPLEMENTED OUTBOX ? or is it only on client side?
WoT model will never bring NEWCOMERS easy freely to nostr it will protect those who are already IN from junk in spam
decentralized and censorship resistant means smart USERS try stay under the radar
so go check their relays exclusively you will NOT miss anyone. its kind GO PULL and not WAIT PUSH FEED come
 

 Filter.nostr.wine has mailboxes. 

 >>Filter supports NIP-65. Your events are automatically broadcasted to your first 4 "write" relays and the first 4 "read" relays from the first 5 tagged users.<<

It's pretty sweet. Have it on the Laeserin npub. 

 um, yes outbox is a client feature for discovering relays to pull your feed from, based on where your frens are writing to. 

 Haha... pretty good. 😅

So many notes seem to only be coming through only via nostr.wine on Amethyst now for me.

Negentropy sync would be great for a mobile client. It connects to only a few relays and those relays sync with other relays, etc, etc.

Lots of great stuff to do. 

 Just have the relays do the mailboxes. The filter.nostr.wine already does, for up to 4 relays each.

Then clients don't need to do that and users can choose or not-choose that model (or combine it with some other), by adjusting their relays in the clients.
Like, I want mailboxes on theforest and thecitadel, but not on our private project relay.

Could also have mailboxes on your local device relays, too. Then you always just read and write from that.

Benefit of it being at relay level, is that you set it up once, and can use that relay in any client and the behavior is the same. 

 I removed the relays delivering spam to me, but now I can't talk to nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgwwaehxw309ahx7uewd3hkctcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7a0nq40 because every reply I do to him disappear!

I'm so tired  

 I see this note.  I dont see it on my relay though, or any of my inbox relays, but I do see it on wss://nos.lol/

I'm not sure why. I haven't changed my relay or chorus throughout this spam epoch.  I'll restart it. 

 Maybe #amethyst client went crazy.

What I wanted to tell you is to use a graph library in your client, because at some point this WoT will get serious, and it's all just a graph, so no need to reinvent the wheel of graph algorithms.

Second suggestion for your relay is to only let people write into it after they pass a CAPTCHA at registration or at each message they send.