Think I've been using it longer then that but could be wrong, tough to keep track moves to quick

https://github.com/mikedilger/gossip

It's a client. Depends how you define new I guess

Its in rust it has to be

Great, I got it working with a CLN plugin. But the easier solutions like you mentioned will be much better for wider adoption.

It's pretty cool being able to zap with just a click from my own node. Looking forward to see what you got, so hopefully more people can start doing that instead of zaps just going back and forth between wos and alby.

But if the node is expecting to validate it as well, it can't unless it's included in the request. Is node side validation unnecessary and core lighting shouldn't enforce it?

What do you think of adding the invoice description to the pay request json as zap invoices only have the hash? Cln deprecated paying invoices without knowing the description. Though they rolled back enforcing it as it broke everything

Definitely need to look at the async my zapper does. Think it gets backed up waiting for the zap before to broadcast.

⚡

Guess we'll find out how my nip47 plugin holds up

Just don't coinjoin right from Gemini. They'll close your exchange account and card.

Get up there and tell them about nostr spaces

Whirlpool?

Definitely would like to see some more discussion on nip47 before i really recommend using it. But it is much better UX then having to leave the app to zap.

https://github.com/thesimplekid/cln-nostr-connect

Enforcing it was rolled back but it is still depreciated. I think you're right that they wont be able to enforce it for awhile, or maybe ever, as it would break everything. However, a tag could be added to nip47 with the description, future proofing it a bit. I don't see a down side to this? At least in the case of zaps the client knows the description and has a method of sending it to CLN. That isn't the case for all use cases so would much harder for them to support.

The reasoning here makes sense to me which is why i think it makes sense to add it especially as its low/no cost to nip47

https://github.com/ElementsProject/lightning/pull/6092#issue-1622210179

So much nicer then having to leave the app. From my node to yours. Wish I got it working a few hours ago for the #zappathon

https://nostr.build/av/nostr.build_9fd29a4f0ee83653cb4bc382e431ae157afea113c66d0de18e9e504c330040b5.mp4

Reminds me of the apple app store logo

#[2] #[3] #[4]

Do you have an opinion on this as I think (draft) NIP 47 would have to be updated to include the description?

Thank you, intresting will have to look into the reasoning

Warner not Warren

Yeah I took a snapshot so it's back up already. Unless youre on a client that cares about cors as I still haven't fixed that with caddy.

I thought I had it on a different vps and the vps I deleted wasn't running anything

Thanks, this fixed it. #[0] looks like we're back up, got myself an account to test it out

hmm same for me. At least our channel balance is the same, guess thats something lol

This is the channel that should be up

https://amboss.space/edge/851102264369283072

Did 23.02 solve your issue? that is what i am on

hmm CLI is showing 2 channels

#[0] Our channel seems to be always down. I can connect to your node manualy but if i look away it disconnects. Any idea if its you or me my other channels seem fine, but looking at amboss your other channels seem fine too. Okay with closing but would like to avoid a force closing if possible but have been trying to get it back up for a few days with no luck

But that's sort of a different question. Could you have made more if you bought a block yes. Do you need to have made more? I would argue no if you have all you needs met.

thanks saw the NIP from alby. Was looking for the discussion, guess thats why i cant find it

Worked

Would be cool if you made you invisible though

Is the hash of the description tag the same as the hash of the invoice description. I ran into this issue as well I don't think amethyst checks this but Snort and Dmaus do.

If the event has proof of work.