Is this list accurate for outbox model support across Nostr clients? Am I missing any? Are their any inaccuracies?

Current support:

Snort

Iris

Coracle

Nostrudel

Lume

Amethyst

Future support:

Damus

Primal

Reply to this note

Please Login to reply.

Discussion

What Outbox model?

Anything built with NDK supports outbox

Is that automatic or do developers have to opt-in by using that method? Is it by default to use outbox? Can developers choose to use the legacy method?

is there an easy way to see which applications were built with NDK? i guess crawling repos on github? any particular string of text i could search for?

It does. Like nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn says, everything baes on NDK (by default) supports outbox

Thank you sir.

Did you just forgot Gossip?

see this is what happens when i try to call it the outbox model instead of the gossip model 😉

We plan to implement the outbox model, but it's such a PITA that it might take a couple more years. Who thought up this PoS anyways? 🤔

Is it adequately documented in an ELI5 way?

Damus is implementing outbox?

Will said that he would add support when speaking at #Nostrasia. Will also recently said that Notedeck will have outbox by default.

Voyage has it.

Do you know which Amethyst version introduced the outbox model? I always thought it uses static relays.

It still uses static relays

We are slowly turning the static set into a bootstrapping set of relays for the many users that still don't have their relay list set up.

If users have their relays setup for the various categories are they using the outbox model or not?

Yes, they are. But the definition of Outbox keeps growing and there is no definition on how many of these strategies a client must implement in order to be called outbox compliant.

I'd say Amethyst is 30% there.

30% is good enough for me to keep on the list. maybe ill rephrase the wording a bit.

Gossip ???

NostrDVM (other Stuff client)