Except, I don't gave to just care about whether the client I prefer has implemented it. I also have to care about whether the clients those who follow me have implemented it. If they have not, then my posts on the derived key will not show up in their feed, since their client will treat my derived key as a completely separate identity that they are not following, right?
Login to reply
Replies (1)
Correct. Rotation changes the key you post from, so followers on clients without lineage support won’t see those posts as coming from you. That’s expected.
This is why rotation is optional and timed to ecosystem readiness. You don’t rotate when a single client implements it. You rotate when the clients used by your audience support lineage. It’s the same adoption pattern as every new NIP feature: creators only switch once their readers can see the result.
This isn’t a flaw. It’s how optional, backwards compatible features roll out.
Nothing forces early adoption, and nothing breaks for existing followers as long as you wait for their clients to add support. Rotation just becomes a better operational model once the ecosystem is ready.