Avatar
DZC
15af9e028db92e50d5462ff5837ed952d41a9bc52149fbdea45bfc0dccd7c6d9
dzcoding...

En realidad para evitar el problema del que habla Matt no hace falta protocolo tipo Monero. De hecho, las transacciones on-chain de BTC no sufren de este problema, porque no recibes *desde una IP origen*.

Matt se está quejando en concreto de LNURL y su dependencia del HTTPS.

Su solución propuesta pasa por bolt12, que está a punto de salir en distintas implementaciones de Lightning, excepto LND, curiosamente.

Bolt12 with blinded paths fixes this.

😏

Bolt12 > LNURL over nostr > LNURL over HTTPS

"South-south-west, south, south-east, east. …"

Such a meaningful book.

O M G !!

We are not used to global launches outside of the US, you know!

Thanks a lot for your work!! 🫂🤙

I have another question: where?

Are you thinking of selling the product also outside of the US?

Ok, but my real question is why are they different?

Wouldn't it be easier to use directly npubs?

Just one question:

Why do I see people 'verifying' their Nests identity?

Is it a different id? Why is it not compatible with npubs?

🤔

Thanks!! 🤙

(Sorry if there's something already explained somewhere, but I've not find it)

Some (new) kind of content-note adding some metadata to the magnet link would be nice (type, title, author, external links, ...)

- Some webs/apps could be created to put together all those content-note, allowing users to search and to react to them.

- People could validate the quality of the content, react to it (like, zaps, comment).

- A community of users could form around this.

- TBD (to be discovered...)

It wasn't accepted to even extend NIP-05 to support just a TXT DNS record due to wanting to keep it simple, so I guess that 'web3' thing won't have any place in nostr either.

It would be a nice touch to also publish it over nostr, as long-form content (NIP-23).

It would show in sites such as habla.news , and could have nostr interaction (responses, likes, zaps, etc).

👍