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...)

Hey Lightning Wallets, you have done an amazing job integrating zaps!! 👏 Wonderful job!

What about stepping up your nostr integration?

What about allowing the user to opt-in to this integration defining his npub?

With that npub the wallet could get from nostr relays information about the user's sent and received zaps, and fetching info of the sender or receiver.

That information could be used to enrich the corresponding Lightning transactions history with the name and pfp of the sender/receiver.

What do you think?

Does it make sense?

cc: #[0] , Alby, #[1] , Stacker News , #[2] , #[3] , #[4] , #[5] , Strike(army), #[6] , etc.

It seems impossible to figure out how to get sourced on Habla.news. What does the client filter for, anything that looks like Markdown? I doubt it, but there's no apparent About or FAQ. #[5]

Self-host your own coffee machine, problem solved!

It’s not listed in the Strfry readme so I presume damus, nos.lol, and many top relays do NOT currently support it (damus used to run a different implementation).

Performance is our #1 right now and we believe there is only one implementation that can support our filter setup.

We’d like to but that’s up to Strfry to implement. Not something we can supplement in front.

We could ask Doug, but he’s a busy man and there are definitely higher priority items for us atm.

This is the first request I’ve seen so I’ve noted it.

That’s a authoring tool, I’m asking about already signed events re-broadcast.

Know any relay with Web UI for to “PushEvent” like Bitcoin’s “PushTX”?

Texas now has 28.5% of global hashrate

BOLT12 does not remove the requirement to be online in order to pay.

I think nostr users will keep using custodial LN wallets.

So whether BOLT12 or Lightning Address is used doesn’t matter that much actually.

Those who run their own LN node could use BOLT12, but that’s a minority.

Hahahah he has $45B to finish burning first

LNURL-pay was first developed for commerce/B2C.

Years later Lightning Address came along and became a success, because it allowed for an easy to write & read handle.

Soon even custodial wallets started using Lightning Address and this later lead to widespread usage on nostr.

It's a succession of events that lead to the current situation.

So as it stands now, non-custodial LN wallets are losing on walkover to custodial wallets, where you have easy access to a Lightning Address.

My Lightning Box solution tries its best to work within this framework that has been developed and gives a sound alternative to using a 100% custodial and trusted Lightning Address solution.

#[0]

Other technologies such as BOLT12, especially with "async payments", could help steer people away from Lightning address.

But it cannot fully replace it, because the primary value proposition of Lightning Address is an easy to read and write handle, which BOLT12 doesn't have.

It's possible we can do some neat "spacechain DNS with BOLT12/BOLT11 AMP" and whatnot, so I'm open to possible ideas.

No, sorry, I am not an Android user, I have no clue if there is something simliar there!

But seriously now, why LL do not want to implement bolt12 on LND? Let's have both for fuck sake and move on forward.

Nostr client support expands so fast, it’s incredible. Newest release in the App Store is Nostore which holds your keys secure to be used in various apps supporting NIP-07.

#[0]

If anyone would ever be able to verify this I would sign up for a bet:

More Lightning invoices are delivered via LNURL than not.

Puede ser, aunque no lo sé porque a nivel técnico flojeo un poco... 😅

Hablaba a nivel conceptual, ya que para combinar la adopción generalizada con la resistencia a la censura, la privacidad debería ir por defecto, desde la base.

El depender de diferentes implementaciones técnicas, empeora la UX desde mi punto de vista

Curious to see what happens to twitter when Elon gets bored of it and moves on to his next toy.