laanwj

it's that kind of "everything must be permanent" blockchain mindset that held me back from even trying nostr for a long time
it makes sense for public declarations and publishing, but not for day to day private life social media stuff, and even less so for DMs

2024-10-24 17:42:25 UTC

- reply

neat script !
i don't see a specific reason why they'd ignore it, it looks correct to me
but i guess some relays are just really shitty about that
they'd ignore expiration tags for sure, too

2024-10-24 14:18:48 UTC

- reply

not that i know of, we should really be sending DMs with expiration tag set

2024-10-24 10:33:51 UTC

- reply

hey thats unfair some people like dicks

2024-09-29 19:30:19 UTC

- reply

thank you, followed ! 😀

2024-09-28 12:11:47 UTC

- reply

yes it would make more business sense the other way around, default is expiring, pay for the option of permanent storage

2024-09-19 13:14:40 UTC

how do those reply bots manage to reply to every post in the first place? how do they know?
can they get a feed of every single post, even on the busy relays?

2024-09-17 20:32:40 UTC

- reply

yeah, though arguably, there's so many ways a vehicle can turn dangerous when hacked, that the battery exploding wouldn't be my first concern

2024-09-11 08:10:42 UTC

Is there really no way to provide inbound liquidity to a lightning node on AlbyHub, directly from a Core Lightning node? Are Alby users always dependent on LSPs for this?
Their guide ( https://guides.getalby.com/user-guide/v/alby-account-and-browser-extension/alby-hub/node/increase-receiving-capacity ) doesn't list it as option.
We already know that the "lightning node" has no external address so there is no way to directly open a connection to it to fund a channel. But maybe an outward connection can work the other way around somehow. Or emulate a LSP.
Does anyone know the details here?
@npub1get…0nfm

2024-09-09 13:10:36 UTC

nostr version of the x0f.org "ghost bird" logo
(i'm not aware of anything that actually shows the NIP-11 relay icon… but anyway)
https://media.x0f.org/43b0d4f0b075c0d29ad0aeeff3446d00d8e6c085be7cea9b214aebb6c7786b2a.png

2024-08-31 09:57:37 UTC

- reply

an additional challenge would be gossiping addresses, as you'd effectively need to gossip URLs instead of only address/port endpoints (eg might need to extend BIP155 with a new type)

2024-08-27 15:52:17 UTC

- reply

looks like that's NIP96 (https://github.com/nostr-protocol/nips/blob/master/96.md) and it's exactly what i had in mind, thank you !
(having he relay software and clients support it is another story, but glad to see someone thought of it)

2024-08-23 11:48:22 UTC

- reply

i don't think the problem is with "unisex", but labeling the one with stand up peeing as "men" could be seen as somewhat exclusionary

2024-08-19 14:55:54 UTC

- reply

thank u that's really interesting, good to see this is only a temporary state !

2024-08-18 12:13:12 UTC

- reply

i wondered the same then found https://docs.asciidoctor.org/asciidoc/latest/asciidoc-vs-markdown/ which provides some quite reasonable argumentation, e.g. markdown is only really usable with "flavors" while asciidoc standardizes everything