pull down to refresh

deleted after seen

deleted by author

reply

deleted after seen

reply

You can also send a 1 sat message attached to his LN address or nodeID (if you know it) as keysend. That could be another secret way to communicate this stuff...

Just a tip.

reply

deleted by author

reply

I wasn't talking about SN address. I know that is not supporting yet LUD12.
Hear that @k00b ?

  • when SN lndhub account
  • when support for LUD12 and 18 ?
reply

LUD18 doesn't seem to be quite as widely adopted from a wallet perspective[1]. It shouldn't be too hard to implement from a receiver side, but if not many wallets support sending it, it's probably lower on the priority list to support, if I had to guess.

  1. https://github.com/lnurl/luds/tree/luds

reply

Be the example... don't wait for other to be for you.
Few implemented because they do not know the power of it.

reply

Good point, re-reading the spec I see some of the potential usefulness of it aside from associated arbitrary identity data on the invoice. Good looking out, Darth!

deleted by author

reply

LUD12 was merged last night, to be deployed soon™️

reply

wow, then we would have a new fun way to "PM".

😂😂😂

deleted by author

deleted by author

reply

ssshhh don't spoil all the SN secrets

reply

the new art of talking in public? haha

reply

deleted by author