It depends.
If tjis means to submit my private key to another third party service i woild not because the risk that this third padty would be compromised is larger than a single entity.
Discussion
Yeah, ok. That would also be a no-go for me.
huh? no, it doesn't mean that at all 🤔
Then I'd be probably fine with it 😄 self custody is king
So you would store some kind of a backup within your local installed client on your device?
What about syncing multiply devices with clients to veryfy your ownership of your NOSTR entity?
Fascinating!
If i understand this right Pablo,
this could solve an even bigger problem than a single attack on your entity.
I actually raised my point because there is a growing amount of services like verifications and online clients where you need to log in with your private key to use the service. Meaning that everytime you use a service you share your private key to an external provider outside your reach.
With a second pub key that whitlists your profile and overwrites the old key you could do a refresh and let the private key expire. This would bring the need to log in again to external services but would add the safety feature to make sure that theese services, if get corrupted one day will not mess around with your keys and conquer an army of entities at once.
This would bring much more safety and less headaches to the entire eco system.
Think the point in your discussions is that there is too many use cases for this feature.
But your messing up with the features coming at the client sides.
Would say this empowers clients to design really advanced safety features.
I like to think of it like a safersex mode to try new NOSTR clients and services without the headaches afterwards.
But why wouldn't it be possible to let the client decide about the time periode to validate?