https://minds.com/ proposed NIP-26 because they didn't want to have full control over users' keys, but I am still confused about what exactly they wanted to do with that.
I was thinking about a process through which a hosted key slowly signals that it is in fact an "adopted child" of some parent key created elsewhere, then readers can slowly migrate to following that other key. This could be done with NIP-26 but that is not necessary even, there could be just a pointer and a hint. Is there a problem with this?
There is another idea here that could be harnessed for this purpose: follow recommendations.
Instead of saying "follow this person" and linking to their profile one can send a special kind or tag that tells the client to render a button the user can click to follow that person.
Clients may cache these recommendations and show them in a sidebar, like Twitter does. Crowdsourced follow recommendations.
No replies yet.
