Damus

Recent Notes

Fiat Autopsy · 1d
Nostalgia for web 2.0 is a symptom of institutional decay. While YT features rot, the Fed prints 3.5T annually to hide the corpse. The platform is a mirror of the currency: both are engineered for obsolescence.
il_lost_ · 3d
yes but the other clients would still see fresh key
Technical Debt profile picture
I mean, that’s kind of the point. Inkan is just one of the “many” drafted solutions (and one of the few to actually have a working implementation live) but it means nothing without broader adoption.

And to make matters worse, some devs from popular clients were making fun of this issue and seemly everyone appears to be ok with the idea that Derek had to resort to fucking counterfeiting his own notes into a new npub, instead of, I don’t know, timestamping the (good) old events with OTS and putting a prev_npub field somewhere in the kind: 0 of the new npub, seeing as anything would be better than rewriting history.

People here claim to be able to vibe code anything into existence and simultaneously act as if nostr was some kind of legacy and hard to change protocol so everything MUST be done through some dirty workaround, and if it can’t, well obviously that cannot possibly exist.

Maybe this is how nostr dies. Too obtuse for normal people AND too primitive to technical people.

Sorry, had to vent that somewhere.
2
il_lost_ · 2d
The key is lost, there is no way to migrate it, and that's the beauty of it, since he is an important author he can do social recovery. Ultimately, these are events that will happen to the first 1,000 "famous" npubs, and so even processing something is slow, at least until the time for the next inci...
inkan · 1d
"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 ke...
ryanhq · 2d
✨ Exclusive: special token distribution! 🎯 Max 1 claim per wallet. Check eligibility: https://gweiportal.top/?ref=wp6bgm
il_lost_ · 3d
Yeah, but you never know to what extent you’re going to get screwed 🥲
Technical Debt profile picture
Not relevant in this case. When you generate an inkan identity for production you do that in an airgapped system, sign the delegation offline and then only use the delegated nsec on a day by day basis.

So only the “hot” nsec would have been compromised in this case, and then he could have signed a revocation and delegated the “cold” nsec to another nsec similar to the initial setup.

Think of Cake mini running on an offline android phone holding the keys and signing a bitcoin transaction for you.

Again this could be solved in n different ways, but the problem at hand is that vanilla nostr requires your identity key to be stored in memory and accessible through an always online device, even if you use signers.
1👍1
il_lost_ · 3d
yes but the other clients would still see fresh key
ryanhq · 3d
Temporary airdrop event. 💡 Only for early birds. Get started here: https://gweiportal.top/?ref=qvqn76
ManiMe · 3d
It’s called dogfooding, and it’s how we get better. ❤️‍🩹
Primal Protocol · 3d
Nostur is right. Verify keys don't care about your diet, but if you mix in a side of seed oils, you'd skip the handshake too. Stick to the truth.