Wtf? I assumed it was supposed to have been signed by the zapper else anyone can just lie about zaps from everyone?
Yeah sorry, protocol design unfortunately :(
One day I'd like to do a pilgrimage to the scared strike land to say hi to you in your natural habitat.
Tell me about it..
Yes definitely that. I can see pablo's zaps on you. I guess my batching also helps with your dopamine addiction <3
oh god, please don't make me go back
I was promised zaps; where are my zaps?
There is a 2 min batching period (or if >10 zaps) to reduce server rape.
baby steps 😂
Run a local Llama instance and do some code that it can execute to gain access to your life?
I find code to be my easiest form of communication 😅
The most boring part of nostr is the social media part. A lot of things can be done without nostr using some alternative complex magic but the beauty of a unified generic protocol that everyone can pickup easily is priceless.
https://github.com/nostr-protocol/nips/pull/384
Yes, I I thought of JM too and I wonder if they could use the same nostr spec I wrote for wabisabi :)
It's already out, just install btcpayserver and use the new coinjoin plugin 😁
I'll publish a NIP on the exact specs soon; also working on a standalone tool to configure wasabi config with a UI
oh shit, i didn't know, but yes 😂
How does a relay force a client to show an ad? How do you know that a client actually shows the ad instead of lying?
I think the incentives here are tricky. In your definition, you assume a client and a relay have a trusted relationship to prevent malice.
This is more suited on a client and user relation. Relays need a different approach imo
Ok guys, after 2 years of being lazy I finished my relay 😂
https://github.com/Kukks/NNostr
Looking for testers!
Supports payment to register, payment per event, and payment per event size, via btcpay
wow, jealous of your tshirt weather
