First of all this isn't backwards compatible (because indexes, relay message validation and other things have to be changed), so if you're going to break Nostr entirely then it's better to make a new protocol that also tries to address other suboptimal parts of Nostr, like is doing with Mosaic. But then at the same time you lose all the (small, but significant) network effect we have here, which to me isn't worth doing. Second, you create the need for these "disavowing" events to be reliably published (which cannot ever be guaranteed in Nostr) and they become the central part of Nostr, and you can't have that work reliably without a centralized sequencer (i.e. either a blockchain or a trusted operator), see for just a brief example of one of the many half-broken issues that can happen (I'm not sure this specifically applies to your idea, but I'm sure we can think of many variants). Now even if by miracle these disavowing events become reliably distributed then there is still the problem that now all clients and all relays have to store them and then check all incoming events that come with a locally valid attestation to see if their pubkey has been previously disavowed, forever. (I just came up with these issues now, later I can revise my opinion to either add more or retract these.) The other solution is to go the NIP-26 way and treat each key as independent, soft-linking them with attestations. That is more elegant in my opinion, but in practice it breaks too, because of issues like those described in this comment by : https://github.com/nostr-protocol/nips/issues/1810#issuecomment-2685163334 Maybe you'll want to see also although I don't remember what I wrote there.

I get it, but any subkey proposal creates enormous burden on clients and relays and ensures nothing cool can ever be built again on Nostr. Also bunkers -- hosted frost multisig, self-hosted, running on your phone, running on trusted hosted hardware, running on a physical device in your home -- are the solution to not having to post your nsec everywhere.

I think https://github.com/nostr-protocol/nips/blob/pf7z-nip41/41.md is still the best idea for saving identities from catastrophic key loss situations.

A better URL to accompany my comment from 43 days ago: https://ngit.dev/grasp/

No, that does not work at all unfortunately.

This is what great normie UX looks like.

Discord requires a phone number to create an account now.

Apparently I have free access to Primal Studio and I had no idea. I'm feeling like an influencer now. I'm influencing so much. Look at these crazy influence numbers:

I believe Yakihonne is there.

See also:

Some form of "moderation" is absolutely necessary if you want any open space to remain usable by good people. And shared blocklists are a completely inefficient solution, it belongs more to the domain of "p2p-like ideas that are very cool but do not work at scale". The only solution I can see is to do it with smart relays that the users choose to act on their behalf, relays with clear policies, reputation and name-recognition, community relays etc -- all interchangeable, of course, and easily swappable on the client side. Muting people or hiding posts from people outside of your WoT can good solutions to catch anything that slipped through relays, but they cannot work in an actually adversarial environment without destroying the experience in multiple different ways.

Just made a website which tracks nostr projects I've created that are approximately useful: https://stuff.fiatjaf.com/ Maybe they will be approximately useful to you too. This is only a little bit inspired by:

Wow, so Blazepoint was going to be an app? I always assumed it was just a generic protocol. Is it also the name of a weird type of boat?

Important message: See my comment for more nuance if you like nuance.

Maybe following people is overrated. It's totally doable to use Nostr by just following relays instead. You can get a very nice and well-curated feed today by just browsing wss://nostr.wine or wss://pyramid.fiatjaf.com -- and this is because basically no one even knows or is aware of this mode of doing things and we don't have the relay infrastructure necessary to enable such flows, so it has a lot to improve. Maybe we should really only be following at most 50 people each, only the people we want to ensure we will not lose sight of, and people who have been banned or inhabit a different ecosystem (of relays) than the one we frequent the most. Aside from that just following a bunch of relays, either grouped together or in different tabs.

Kind 3 was probably a mistake, following could have been local or private by default, and assigning public "trust" to people could have been taken a more intentional form, with more structure to it rather than "whoever I want to see posts from I put in this list and now that person gets an endorsement from me". But following people is still a good thing. I do think the focus on following people should be drastically reduced (no one can really "follow" more than 100 people) and that we need more opinionated relays like wss://theforest.nostr1.com/ and more tools for browsing relays, recommending relays, publishing to specific relays. It shouldn't be necessary for a new user to click on a follow button hundreds of times in order to get a feed. Clients shouldn't be required to send many hundreds of REQs (most of which will be about pubkeys that haven't posted anything for months) to a bunch of relays in order to build a default feed. That number can be cut drastically and Nostr can still work fine, in fact much better.

By the way, it would be really nice to get some other Grasp server implementation in another language (except JavaScript) just to ensure the interoperability stuff is holding up well. Also another web app for browsing repositories, browsing issues, merging patches and so on, just in case.

We were so young.

Spotify is successful. Spotify does forced face scans and ID checks. Therefore, forced face scans and ID checks are the core traits of a successful UX. We must add that to Nostr apps if we want Nostr to be successful. The market has decided.