Add inactive key in nostr?

[HelpNostr]

Hey guys,

According to Twitter's `[account inactivation policy](https://help.twitter.com/en/rules-and-policies/inactive-twitter-accounts)`, it states:

"What is Twitter's inactive account policy?
We encourage people to log in and actively use Twitter when registering an account. To keep your account active, make sure you log in at least every 30 days. Accounts may be permanently removed due to prolonged inactivity."

Can we use the same Twitter account inactivity policy as an "inactive key" concept in a decentralized networking protocol like nostr?

I think it's great initially, a technical discussion on this. Also, perhaps this is possible with 'OpenTimestamps' from a technical point of view, as an event of type: 'key inactive' for nostr on login.

In this way, any relay can check the login key time, like public key and check whether the status should be idle or not. Perhaps the registered key is temporarily or always on a future date for this.

*notes*

- an idea: 'To give more security to users, if the user (you) doesn't access any nostr app like Iris, Snot etc for more than 30 days, the key becomes inactive, you lose access to your app.'

- I didn't find any NIP about it

- Since nostr is an alternative to twitter, maybe it has 'inactive key' support
- This is more of a question than a feature request or creating a NIP in nostr

- I'm a new nostr user, and I'd like to help with some ideas if it's possible to do that

- If this idea is bad, I apologize

[William Casarin]

On Sat, Jul 22, 2023 at 07:47:54PM -0700, HelpNostr wrote:
>Hey guys,

>
>"What is Twitter's inactive account policy?
>We encourage people to log in and actively use Twitter when registering an
>account. To keep your account active, make sure you log in at least every
>30 days. Accounts may be permanently removed due to prolonged inactivity."
>
>Can we use the same Twitter account inactivity policy as an "inactive key"
>concept in a decentralized networking protocol like nostr?

No, unless it's arbitrarily enforced in every client. Why would clients
ever do this? It seems pointless.

The reason twitter has this is because they have globally unique
usernames, if they used pubkeys they wouldn't need to evict any user
account. Decentralized networks that use 256-bit identifiers have no
need to evict usernames because there are none.

Will