Right so the relays that want to take that risk and liability would allow that kind other relays would not. Isolating themselves from compliance issues
I think if relays that don't want to deal with the regulations that come with medical data just blacklist that kind it should isolated them from that. Of course that assumes the courts and government act rationally so maybe a bad assumption.
Just unfollowed 100 pubkeys i couldnt find profiles for, If you got caught in that list someone sorry ill refollow
Get a domain name, point it to the machine that's running the node and the server. Then you can use tools like
https://github.com/niteshbalusu11/rustdress
Or
https://github.com/Dolu89/ligess
that run a lightning address server and talk to your node.
You'll have to use something like Nginx and Certbot for tls certificates and you'll see a ton of tutorials on Google for setting up that.
I like caddy find it way easier then dealing with certs myself
Get a domain name, point it to the machine that's running the node and the server. Then you can use tools like
https://github.com/niteshbalusu11/rustdress
Or
https://github.com/Dolu89/ligess
that run a lightning address server and talk to your node.
You'll have to use something like Nginx and Certbot for tls certificates and you'll see a ton of tutorials on Google for setting up that.
What mode back end does this use?
Not sure about freebsd. I'm adding an option so you can set the path in the config
Ah so what it is is the ln invoice description hash is the zap request without escape chars. But in the zap note description there are escape chars.
Think ln tip bot does it and that's in go.
https://github.com/LightningTipBot/LightningTipBot/tree/main/internal/lnurl
I've been working on a rust one. Few more issues to track down though
Yeah I was a little worried that may be an issue. It's the data directory $HOME/.local/share
Looks like still having issues with damus. But I got damus running through xcode emulator (impressed how easy it was) so should be able to debug better. Thanks for the zaps by the way
My node is and does
Is there a way to delete all unpaid invoices in cln? I accidentally created a bunch thay won't expire till 2076.
Clients could also just filter the zaps from the pubkey
This confused me a bit too. But the receiver controls the zapper so they can broadcast to whatever relays they want. But the sender does not but would want the zap to post to relays it listens to so, I think including that in the request does make sense
The clnurl server would have to stop invoice creation based on the zap note. Or the zapper could not genrate the zap note based on the pubkey in the zap request still get the sats then.
Yes thank you, checked the mutiny github don't know how i missed that.
#[0] I believe you mentioned a website on a podcast that you could use to decode things like lighting invoices its not whatamilookingat .com lol. Can't remember if you said it was public or working on it?
#[1] ?
Intresting thats what im running and broadcasted zaps you couldnt see. But thats inline with the nip so will merge thank you
... and other stuff
I think it depends. Unlike bitcoin there is no global consensus so someone spinning up a relay and posting a TB of notes has no effect on anyone else. So i think there are some interesting things that could be done on private relays that share among specific people and groups. . And i think as long as youre not spamming these events to public relays nostr is your private database with a common API.
I also wonder if it changes if you think of nostr as a communication and not a storage layer. For example maybe each hospital runs a private relay and is responsible for securing and managing access to it. But what nostr would allow is a common way to request and transmit that data enabling better sharing and transparency among medical providers. But maybe that's stretching the scope of nips and bit and should be defined elsewhere. But I think it is an interesting use case and relay set ups other then publicly available should be considered.