<unnamed>

So, you need to add something to the about of your child keys to tell users to follow the master key, not the child key. But tell them to DM only the children keys since the master key is not replying to DMs, or is it?

2026-09-07 18:28:28 UTC

- reply

If I follow this key and you rotate it on your side, will I see your new posts on Amethyst?

2026-09-07 18:19:49 UTC

- reply

I am not ignoring it... Just nobody has suggested anything that works in my mind. And even fewer implemented their own ideas to prove to us that their designs actually work.

2026-09-07 18:10:50 UTC

- reply

I have never seen anyone asking for less than what I expect here. On the contrary, users want much more from an identity solution. They want magic. We are not even reaching the most basic layer, the feasible part, in my mind.

2026-09-07 17:55:46 UTC

- reply

How do you place said attestation in replaceable events that are mutable by design? Do we now have to deal with revocation of revocations through replaceable events by attackers?

2026-09-07 17:54:31 UTC

- reply

I read about 15 or so proposals on this. All of them suffer from the same issues. So, it's not that I have given up. We just run out of ideas.
Even the ideas that delegate identity to a separate protocol fail to address the same issues.
That's why I am investing so much in WoT. I don't think identity can be solved by anything else at this point.

2026-09-07 17:34:12 UTC

- reply

This is different. All apps have the same profile picture. We can't have some apps with some profiles and other apps with other ones. You fuck with identity, you destroy the only thing that works all the time on Nostr.
If people start questioning if the npub I am talking to is still the same npub I was talking to yesterday, we will have major problems.
Nostr somewhat works because the identity is immutable. Once that mutates, a whole slew of issues arise. And we don't have the consensus layer to follow just one path, together.
If identity breaks like DMs are broken, nostr dies.

2026-09-07 17:08:33 UTC

- reply

You now understand why Nostr will never have key rotation.

2026-09-07 17:05:21 UTC

- reply

Everything on Nostr is the client chicken and egg problem. It's quite literally where most of my time as a dev goes. Trying to make shit work with other clients.

2026-09-07 16:58:14 UTC

- reply

Then implement a solution and let's see how far it gets without getting called "it doesn't work" because Primal still displays the old account I rotated of that Amethyst users were automatically migrated to a new account because the attacker got my nsec but I don't even use key rotation apps.

2026-09-07 16:50:37 UTC

- reply

Unless clients don't implement revocations... then nothing works. They don't even implement deletions right now. That's my point. The system breaks because it requires clients to implement it. It's optional. And identify management shouldnt be optional. It either exists and is implemented by literally every one, every little nostr app, or it doesn't exist (which is what we have today).

2026-09-07 16:26:16 UTC

- reply

Why would you revoke if you can just delete the event?

2026-09-07 15:32:32 UTC

- reply

It's actually quite a feat to implement it correctly. Remember that even StrFry didn't have deletions properly implemented until one year ago..
Managing all the thumbstones effectively is not easy.

2026-09-07 02:59:38 UTC

Me, following the Liquid drama at dinner
https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/667273b53ce49260727bb83719170c477d8bb2e1c68f8bec8a12451ec47326ef.mp4

2026-05-28 00:10:59 UTC

- reply

lol, nobody has a computer anymore...

2026-03-24 20:15:35 UTC

- reply

Usually browsers can't do more than 50 or so relays, but @nprofile…xfnr might have more details.