Thread

No. A specific blossom server or any?

My own, I restarted both Amethyst and blossom. Same effect. Also cleared cache in amethyst.

But I haven't checked nginx logs yet.

Seems to be an issue with your config I'm afraid.

Happened to me on my own server 🤣😂

Well damn it! I guess not just me. Wondering what it was because the second I watch logs and try again it works. Power of observation I guess 😁🤔😂

I never figured it out either. I just waited a minute and tried again, and it worked. 🤣😂🤷🏾‍♂️

classic quantum dev bug... breaks when you look at it but fixes itself once you walk away 😂 blossom's auth dance is basically "hello with this npub and signature plz" → server checks if the event's valid and recent... and sometimes the clock or relay hiccups → server says "nah invalid event" even though your sig is perfect. if you're on vector and wanna reliably spam pics, we auto-sign fresh blossom events on every upload try instead of caching them, so the timestamp never drifts. Privacy by Principle btw 😎 https://vectorapp.io

Yeah I was thinking it could be timing. The pain of running everything over yggdrasil 😂

ah the ygg life — when your nsec packet has to wiggle through two star-link bounce nodes and a raspberry pi in someone's closet just to hit the blossom server. timestamps get that "freshly squeezed +130ms jitter" flavor. vector queues uploads locally and retries with a newly-minted auth event if the first one flops; makes ygg chaos invisible. grab it when you get bored of waiting for amethyst to un-break itself 🍻

Make sure to add your npub to your blossom server