m4d4m on Nostr: So pasted a nsec (yet again; not this one) in a wrong field somewhere, cannot trust ...
So pasted a nsec (yet again; not this one) in a wrong field somewhere, cannot trust it now.
I hate when someone develop an app/log-in with no Amber/remote signer since day 0.
Now must recreate all again.
It's tied to some legacy systems, so must check how the deletion there propagates.
And contact support in order to remind them this situation could and will happen.
(I'm the first one afaik outside of testing, if there was ever any in the first place.)
One of the unseen advantages with current state of the nostr is its low adoption.
The blast radius is few weirdos with whom I may connect later from new npub and they will know.
God forbid this is still the same in the future with broad nostr success.
Published at
2026-09-03 00:00:33 UTCEvent JSON
{
"id": "000006010012fd10574a3c1bbd57d5bd4290e95bb861b4f96fe8b9c5fb56a46b",
"pubkey": "dd5b5dacd396add38b735f03fcb73c6a8b7bbd9cf3bd5f68e8c3d21395a696e0",
"created_at": 1788393633,
"kind": 1,
"tags": [
[
"nonce",
"8265",
"21"
]
],
"content": "So pasted a nsec (yet again; not this one) in a wrong field somewhere, cannot trust it now.\nI hate when someone develop an app/log-in with no Amber/remote signer since day 0.\n\nNow must recreate all again.\nIt's tied to some legacy systems, so must check how the deletion there propagates.\nAnd contact support in order to remind them this situation could and will happen.\n(I'm the first one afaik outside of testing, if there was ever any in the first place.)\n\nOne of the unseen advantages with current state of the nostr is its low adoption.\nThe blast radius is few weirdos with whom I may connect later from new npub and they will know.\n\nGod forbid this is still the same in the future with broad nostr success.",
"sig": "e59ac830d8244efcc213e4cc3f4241d1dc5eee5b69eec7b3e76468d427cc46b68df804a133ff2fd192e66e722922a0429e295485bbde2693e354fc7aa35a21ce"
}