hodlbod

@vitorpamplona interesting, the additional complexity of avoiding memory limits (on both server and client, along with any attacks that deliberately craft huge payloads to crash implementations) makes the low limit...

> Nostr, as a protocol, shouldn’t stop me from encrypting a payload of whatever size I want from my own client to my own relay. Limitations of popular Nostr software,...

Ok, that makes sense, you've convinced me.

Any solution that overloads a event kind's payload with a differently encryption scheme (whether v3 or fiatjaf's hack) will result in unsupporting clients failing to read the data, and potentially...

Best thing would be to open a PR and point to any implementations. Once there are two clients that implement the changes, we can merge.

Yeah, I don't think we'll ever get rid of kind 3. I included the whole nip 51 table for completeness, but this is mostly useful for kind 3 and 10000....

Yes, but how is that different from what already happens today? Edit: For example, every time I update a list in coracle I attempt to re-load the latest version: https://github.com/coracle-social/welshman/blob/master/packages/app/src/commands.ts#L120

> Not sure if I'm missing something, but how would this allow a consistent ordering of items in the list? You're right, I don't think there would be a way...

> Looks good, but we really need to stop calling this "plain text". I thought about introducing the term "nostr flavored markdown" but I think that communicates the wrong thing....

Humans copy/paste urls, they can copy/paste `nevent1`s too (and they do). They're all the same thing — a URL, i.e. a _reference_. base64 encoded images and nembeds are _content_, and...