It is, I’ll send you the link later (AFK)

The new version uses NIP-32 labels instead of topics

Yeah, I think we need multiple services that allow users to sign in to web services where the individual events are sent from the front end app back to a signing server that holds the nsec and sign events the app requests.

At some point I realized it's actually the client's responsibility to handle deletions, not relays. And it works by not showing you data it can already access. Pretty backwards. Of course relays should also handle kind 5s, but due to the nature of Nostr it has to be handled by clients for it to "just work".

I disagree. I remember when no client showed long-form content. We implemented it blending the new post into the feed and, it took some time, but others followed. Same for custom emojis, etc.

If there is use, it helps people prioritize them. If there is no use, then no one needs to worry about it :)

There is an issue with that. Some clients dont process delete events yet. So, posts get duplicated every time they happen. :(

So you are saying the blog system of 30023 is wrong? Because this one is not any different than that.

I am considering enabling Amethyst to write a replaceable kind 1 (new kind:30111) to allow users to edit their past posts at will.

It would work in a similar way Habla News works, but using Kind 1's style of small posts instead of markdown and long-form content of kind:30023.

Of course, we could also write kind:30023 (blog posts) directly, but it would pollute most of the Blogging interfaces with short posts.

What do you all think?

- Inconsistent user experience when tagging event and user IDs in various clients. Some clients support @note ID and @npub, some nostr:note and nostr:npub, some use nevent or naddr or nprofile. You may tag a note or user in one client, and half of the other clients don’t render it.

- In several clients, there’s no way to link to other events in a note without them being rendered inline in your event. This makes for some very long notes or long form articles if you link to multiple other notes. There should be a user setting to disable or enable that in your client, or a way to simply link to another note that doesn’t generate an inline preview in your event. Imagine if every hyperlink on a webpage rendered the full page it was linking to inline in the middle of a paragraph.

- A request to DM someone should cost an amount of sats defined by the user you’re requesting to DM.

- There’s no way to transfer your existing account to a new key pair.

I don't know of any, but this looks awesome.

How long has strfry supported this?

i don't know who needs to hear this right now but read and respect the NIPs, don't blindly copy other people's code. all nostr clients need to be interoperable and the spec we agreed upon is on the NIPs. there are mistakes, bugs and leftovers from experimentation in some clients.

My user goes from 400MB to 70MB with brotli

The entire thing at once. You want to reduce duplicates (event ids, pubkeys, tag names, etc)