BUD-10 Client Adoption Status
BUD-10 Client Adoption Status
BUD-10 Client Adoption Status
| Client | Platform or version | Thread status | Evidence and qualification |
|---|---|---|---|
| Amethyst | Android; version 1.20.0 explicitly reported | ✅ Working | Five independent positive reports. The final report explicitly says, “Yes. Amethyst 1.20.0.” 1 2 3 4 5 |
| Feather | Android; 1.9.0 announced | ✅ Working in 1.9.0 | An initial report said the image was not visible. Feather then announced, “Added BUD-10 support in 1.9.0!” and a user subsequently confirmed, “Yes, now I can see it.” Initial failure · Developer announcement · User confirmation |
| Nostr Vault | Web | ✅ Working according to its developer | About 4 hours 43 minutes after the initial iOS failure, Nostr Vault’s creator reported, “This is functional on Nostrvault.app now.” This is a developer statement rather than an independent rendering confirmation. Developer update |
| Nostr Vault | iOS | ⚠️ Initially failed; current status unconfirmed | The iOS app initially displayed only a link. The subsequent update was posted from an event tagged “Nostr Vault on iOS,” but its text explicitly names Nostrvault.app and does not clearly say whether the iOS app was fixed. A fresh iOS test is needed. Initial failure · Ambiguous update |
| Zap Cooking | Web | 🟡 Announced, not confirmed | The project said, “We will support this very soon in Zap Cooking.” This is an implementation commitment, not evidence that support has shipped. Announcement |
| Primal | Web in Chrome and Brave | ❌ Not working in this test | Two independent web users reported no image and raw Blossom text. Chrome report · Brave report |
| Primal | iOS | ❌ Not working in this test | A Primal iOS user explicitly reported that the image was not visible. Report |
| Wisp | Unspecified | ❌ Not working in this test | The participant saw a link and reported that it appeared to break at each query string. The event metadata says only “Wisp,” not a specific platform. Report |
| Wisp | iOS | ❌ Not working in this test | The Wisp iOS report said the reference looked like a text string and generalized the failure to every iOS client. Only Wisp iOS is counted here; later evidence showed that the generalization no longer held. Report |
| Jumble | Web | ❌ Not working in this test | A participant reported “no” while tagging Jumble’s official account. Report |
| T-Bone | Unspecified | ❌ Not working in this test | A participant associated with the client answered, “No T-Bone,” then shared its v0.5.2 release link. The release link is not itself evidence that this version supports BUD-10. Failure report · Follow-up |
| YakiHonne | Unspecified | ❌ Not working in this test | A participant reported, “Not visible on yakihonne.” Report |
| Nostur | Apple platforms; exact platform not stated | ❌ Not working in this test | A participant reported, “Not visible on nostur,” and tagged the Nostur account. Report |
| Nostrich | Unspecified | ❌ Not working in the supplied screenshot | The reply contains only a screenshot. The screenshot shows the original Blossom URI as plain text, without the referenced image rendered. Screenshot reply |
| Dark Wisp | Unknown | ❌ Not working | A participant reported that the image did not render, and the original poster subsequently confirmed that Dark Wisp is not working. Original report |
Write a comment