TFW you put OpenCode in build mode and tell it to proceed with your well-constructed plan:

There's only one way to find them all. ;) While we're at it, I'd like to add LDAP auth to blossom-server soon, so that the people who can write to our strfry relay can also upload to our Blossom server. (I know it sounds a bit weird, but LDAP is actually great at being a highly available user directory service, and we standardized a `nostrKey` attribute, analog to `gpgKey`.) So the question is: for any auth methods more complex than a simple whitelist, do you have a preferred architecture/layout in mind? I haven't really looked at the codebase in depth yet. Maybe you already thought about the topic in general?

Yes, that fixed it. Thanks. 👍

By the way, Applesauce is awesome! Going to share what I'm currently building with it soon. And Blossom is also playing a role. Thank you for both! 🙏

Hey there. My blossom-server returns http:// URLs instead https. It's running behind nginx and both the nginx config and blossom-server config seem to have all the relevant headers and config keys set. Wondering if I'm the first person to run into this issue...

Oh, interesting! How do you handle the queue and approvals? I'm planning to do exactly this for a new use-case-specific relay I'm spinning up soon.

Yay, now I can replace a few little bash scripts with bunker profiles!

Running Blossom for media attachments now. Here, have a sheep:

I don't know. There's a NIP with a number, so there should be at least a couple implementations, no?

Nostr devs: what's the most popular photo-centric app using NIP-68?