Wyoming LLC's are great for this sort of crap.
cc: #[4]
Is there a way for users to manage their nip-05 id and add relay info for their given npub?
See thread.
For sure for sure. Just noticed that the following URL request returns no info (indicating no relays set for your npub)
May also want to add to your nostr.json file the "relays" parameter, then login to new clients with your nip-05 id so that it can point them to relays with your info on it.
Wish I could run it in a FreeBSD Jail 😢, otherwise I would totally host my own.
In terms of protecting IP address of user downloading images. Can use COIL-compose and configure the ImageLoader to use a separate OkHttp client (which can be instantiated with Tor SOCKS5 proxy).
In terms of reducing mobile data, I think COIL resizes it on the fly based on the composable view size that it'll be loaded into. Still might be downloading the entire size though. IMO, imgproxy would be the best way to go.
Jeeeeeesus, lmao
Did you set blaster as your write only relay? Because it has a que to "blast" events, so there is a delay
GM 🌞 ⚡
Shit cracks me up every time, lmao
Yeah they have it behind a webserver which serves only the query params requested.
I was confused because I thought a parameterless request returned all names, but I guess not?
Maybe a core lightning plugin???
Cc: #[1]
Idea:
Nip-05 registry info delivery upon receiving payment is DM'd to npub registrant.
Cc:
#[0]
#[1]
Idea:
A client you can run on your node that you can DM with a lightning invoice and it will pay it for you.
Will only accept DMs from a specified pubkey (yours)
Can "Uncle Jim" friends and family and set spending conditions for their Nostr pubkeys.
100%
Would love a setting client side that will require confirmation.
Cc: #[2]
Example (Android using KiwiBrowser + #[3] extension + snort.social)
Not having the same relays from client to client. New relay has no info, and so it updates other relays and wipes followers.
Blastr fixes this.
Set as your only write relay. All other relays set to read only.