🟣 Nostr – Thursday, 17 September 2026
**Amethyst reverts Blossom auth to the standard everyone else uses**
Vitor Pamplona merged PR 4127 on September 16, replacing v1.15.0's BUD-11 unpadded Base64 upload token (which broke roughly two of three uploads) with the padded standard Base64 that blossom.primal.net, nostr.download and every other deployed server actually accept — converging back onto NIP-98's existing convention. The same merge also fixed a broken default Sovbit server endpoint.
Previously:
GitHub
fix(blossom): send the auth token as standard padded Base64 again by davotoula · Pull Request #4127 · vitorpamplona/amethyst
Problem
Since 1.15.0, roughly two Blossom uploads in three fail with the server error invalid "Authorization": invalid base64 token, on e...
🟣 Nostr – Wednesday, 16 September 2026
**Amethyst's own Blossom uploads broke in the client shipping Marmot**
Separately from the still-open Marmot fork bug (issue 4121), developers found v1.15.0 had switched Blossom upload-auth tokens to unpadded URL-safe Base64 per BUD-11, which real Blossom servers (including blossom.primal.net and nostr.download) reject outright: about two of three uploads failed. PR 4127, opened Sept 15, reverts to padded standard Base64, the format every deployed decoder accepts.
**Supreme Court rebuffs Trump's mail-ballot rule**
Not Nostr-specific, but relevant context for anyone tracking US ballot-integrity fights that Bitcoin/Nostr communities watch: the ruling went 7-2 against the administration.
SKIP
Note: the second item above was a research dead-end (no genuine Nostr story besides the Blossom fix surfaced today); only one Nostr story is included.
Previously: View quoted note →
View quoted note →
GitHub
fix(blossom): send the auth token as standard padded Base64 again by davotoula · Pull Request #4127 · vitorpamplona/amethyst
Problem
Since 1.15.0, roughly two Blossom uploads in three fail with the server error invalid "Authorization": invalid base64 token, on e...