Avatar
DETERMINISTIC OPTIMISM ๐ŸŒž
e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411
-... .. - -.-. --- .. -. strong opinions, loosely held.

Turns out the delete button puts the 0 in Kind0

Delete information. Not create a note and broadcast a kind0 note.

Canned cod liver pate is pretty good.

/No seedoil option found./

LOOONG list episode of #[0] with

#[1], #[2] and #[3]

Sparrow, COLDCARD, Nunchuk, Keeper, Breez LSP and lost more.

Enjoy

https://bitcoin.review/podcast/episode-26/

To be fair, It does make you type "DELETE". Maybe extra confirm with a full red screen LOL.

But I'm not sure I like the idea of an app authoring a event in my name like that, specially not being a NIP or documented. I think a NIP to handle "account self deletion" to comply with GDPR might be worth doing, if anything because it could describe how to un-delete the account.

All these will be very client/relay specific on how it gets enforced, so would be nice to have a way to unlock yourself out of this hole.

Just in case you need, here is my confirmation of the npub remaining the same.

https://twitter.com/nvk/status/1631351106038120448

## What happened? @#[0]

The original DERP; I accidentally took the Damus "Delete Account" as sign out (ie Delete Private Key). Which I do have a backup so was not very concerned and did the deed.

(IIRC that's where the sign-out button use to be)

Damus to comply with Apple Store has to have a "delete account" method.

So how does Damus do it? AFAIK, it authors an empty (zeroing) of the Kind0 (profile data), clients rendered it as "nobody" and adds a "deleted account" flag. This means that until this is cleared from all relays and cache you can't login into the Damus app. But this zeroing out of the meta data does seem to cause relays and other clients confused. The contact list (follow/followers) seems to also have been zeroed in some relays.

- The followers seem to be all gone, which is not a big deal ppl who want just go and refollow me.

- For the following list, I just need to go look at an old contact list event and manually refollow ppl.

Because this is not documented as a NIP it's hard to know which relays or clients are honouring the Flag.

I think once the Kind0 of the profile is fully propagated the Damus should let me login again. Maybe there is a bug or IP block on Damus too, can't login with other "non-deleted" keys even after re-installing the app (TestFlight version)

...and then Client/Relays confusion should end.

Going to take a walk... BRB

#[1] pushed a updated kind0 to as far as I could, I think most relays have seen it. Still can't login. Odd enough can't login even from unrelated pk. Some server cashing IPs or device ID? (using latest from TestFlight)

thx. still no luck logging into Damus.