Your zapper down, sir?
Good information! That explains issues I have had with Citrine being used for local NIP-46 signing at times. 😂
If using Haven behind a VPN like Tailscale as a media server, wouldn't it be the case that only those who have access through his tailnet would be able to view the media? That is, unless he is keeping copies on other Blossom servers, too.
I dunno I wasn’t considering others accessing my relay. I wanted notes I post from clients in my devices (that are in my Tailnet) to hit the relay, then Haven should blast those notes to relays on the import list.
My zaps should be working.
Ah, yes. That blastr functionality could definitely still be useful to you, even if you aren't using anything else Haven has to offer.
Hey, not sure. It's Coinos under the hood—I'm just doing some well-known/lnurlp trickery to redirect to it. I managed to zap you from the same wallet though (try again, and if it still doesn’t work, feel free to zap anthony.accioly@coinos.io or anthony.accioly@walletofsatoshi.com).
As for your second question: out of the box, yes, you're absolutely correct. There are some very clever folks doing things like syncing Haven's backup folder to a public S3 bucket and redirecting or proxying Blossom's GET /{SHA256}. So, in theory, you can expose Blossom blobs to the internet without exposing Haven itself. Having said that we don't officially support this yet (hopefully coming soon).
Very clever indeed. The draw of Haven for me is that it's an all-in-one solution for outbox model, so I probably wouldn't use it for blossom without making the relay itself accessible. I'd just run a separate blossom server in that case. Cool that it is possible, though.
