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
What Outbox model?
nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt does Highlighter support outbox?
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?
Give this a try: https://github.com/search?q=%40nostr-dev-kit%2Fndk+path%3A**%2Fpackage.json&type=code
nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszymhwden5te0wp6hyurvv4cxzeewv4ej7qgnwaehxw309aex2mrp0yhxvdm69e5k7tcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuetcd96zuur4vghszynhwden5te0wfjkccte9e6x7mmvwvhsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qy88wumn8ghj7mn0wvhxcmmv9uqzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jdfe3e9 your strategy worked. NDK is used in 412 packages on github. Respect for your long-term vision.
But it still depends on 2051 packages, so it's losing by 1639.
Perfect. Thank you.
It does. Like @hodlbod says, everything baes on NDK (by default) supports outbox
Thank you sir.
Did you just forgot Gossip?
LMAO sorry @Mike Dilger
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? 🤔
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
Support started to be added in 0.87.0. nostr:nevent1qqsgvvfykevjxk2fgwtvy2u307wj2xk39tp3kz0298szvh3upzxwn7qpzemhxue69uhkzat5dqhxummnw3erztnrdakj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqzvd9lx3
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.
NostrDVM (other Stuff client)
You're missing https://github.com/mikedilger/gossip, https://nostrrr.com/, https://github.com/dluvian/voyage, https://github.com/nostur-com/nostur-ios-public (future). Also Amethyst is future as far as I know.
I believe it's on by default
Thanks.
Thanks.