Zebedee integration with nostr makes so much sense.

Thank you very much, #[4] ! 🫂

Good job!!

Thank you very much, sir!

🫂

The Lightning protocol allows to set the invoice expiration time as you want, but afaik wallets don't allow the user to set this and just use a default value.

None that I knew off. 😞

Afaict, you need a CLN node with some 'experimental' feature on.

Eclair and LDK also working to support it, but nothing standardized or finalized yet.

Bolt12 ftw!

#[0]

Agree.

Ideally a client should connect to the needed relays depending of the information it wants to get or send, not to a fixed list.

In a social client that will depend on the follows list, and the follows' preferred relays.

The 'gossip model', they call it.

Fair enough!

😊🫂

Well, 10002 events are not for storing configuration settings:

"The primary purpose of this relay list is to advertise to others, not for configuring one's client."

https://github.com/nostr-protocol/nips/blob/master/65.md

I reckon storing client settings should be done in a specific "list" (maybe a private list) as defined in NIP-51 (still a PR).

👀

Is this zap-spam, zapam, szapm??

🤔

strike.army servers seem to be down.

If you want some note to be ephemeral or replaceable, the protocol supports notifying that:

https://github.com/nostr-protocol/nips/blob/master/16.md

But nobody can be 100% sure that every relay or client would follow the protocol.

Is it required to set a NIP-05, or is it enough to set the npub?

🫂

It's alive!!

#[0]

KISS

#[0]

También estaría bien la opción de poner nuestro npub y poder filtrar contenido (long form content) de nuestros follows.

Se podría usar por defecto nuestra lista de follows de micro-social (kind-3), o incluso gestionar nuestra lista personalizada de creadores de long form content y guardarla en una lista específica (NIP-51), diferente a la que usamos en clientes micro-sociales (kind3).

Troll definition:

#[0]

The best way out is separating the Contact List and the Relay List.

Not storing them in kind-3 event at the same time, imo.

They are available NIP-65 and NIP-51 (not merged yet) to create and publish different lists.

I see you have set in your profile a Lightning Address from Alby.

Afaik, they don't support receiving zaps (NIP-57) yet.

You can still normal Lightning payments and tips, though.

Congrats #[3] !! 👏