"it means nothing without broader adoption"
The way I think of it, there's only upside and absolutely no downside to using it now, regardless of whether there's broader adoption.
The reason is that you can simply create an airgapped master key now and delegate down to your current regular nostr key.
Then you just go on using your current nostr key as usual, except you make sure that your events get OTS timestamped (for example by including the inkan relay in your write relays).
So then you just use your current nostr key as usual, you don't even notice that you're using inkan. But in the background, all your events are attributed to your master identity, and if you ever switch away from your current signer key to a new one, you simply redelegate at that point to the new key, so your events will keep getting attributed to your master key.
So your identity lives in the background, even if there are no clients (other than inkan) looking at it. Maybe in five years you decide to make your own client that can see the identity, and when you do so its history and activities from the last five years will be visible in that client.
The point is that these identities have a sort of objective existence, regardless of whether there are any clients around that look at them. You or anyone else can always make an identity and its history visible later if you want to.
The way I think of it, there's only upside and absolutely no downside to using it now, regardless of whether there's broader adoption.
The reason is that you can simply create an airgapped master key now and delegate down to your current regular nostr key.
Then you just go on using your current nostr key as usual, except you make sure that your events get OTS timestamped (for example by including the inkan relay in your write relays).
So then you just use your current nostr key as usual, you don't even notice that you're using inkan. But in the background, all your events are attributed to your master identity, and if you ever switch away from your current signer key to a new one, you simply redelegate at that point to the new key, so your events will keep getting attributed to your master key.
So your identity lives in the background, even if there are no clients (other than inkan) looking at it. Maybe in five years you decide to make your own client that can see the identity, and when you do so its history and activities from the last five years will be visible in that client.
The point is that these identities have a sort of objective existence, regardless of whether there are any clients around that look at them. You or anyone else can always make an identity and its history visible later if you want to.