we need better censorship resistance, better/deep relay discovery, more relays, proxy services
...
then we can try to build a pure nostr/lightning ebay, step away from it and see what happens

```
INFO:root:got 138 contacts from wss://relay.nostr.vision
INFO:root:got 141 contacts from wss://relay.damus.io
INFO:root:got 137 contacts from wss://nostr-pub.wellorder.net
INFO:root:26 new follows from twitter
INFO:root:publishing 167 contacts to all relays
```
hehehe, you said zapping nips
maybe alby, lots of eyeballs on that. but not every client supports it. so, dunno. i have an encrypted copy sitting in google drive so i dont lose it
you still have 3263 Followers. so i maybe only damus shows the lower number
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
how the heck could followers be gone? maybe in damus, but for sure i saw all your posts, including old ones
a thread with 1000's of mentions and each one was getting zapped and everyone was replying with "thanks"
yes you do
protocol != ux. they're posts, that's fine.
i just drank and stayed out late last night and for the first time in weeks i don't have a headache
who knew
It's open source so we can assume that other people are looking at it and it's not too bad
But it would be nice if there was a better solution
unfortunately that solution is a systemic problem affecting the entire planet not just nostr
You're just trusting them to custody your private key correctly
most of this apps are not even storing it in the keychain
they can't because the hardware doesn't support the curve that we use and the operations needed
so even if they do stuff it in there they're going to stuff it in there as a wrapped encrypted object that they're going to unwrap and use as a raw key



?cid=2f4ce311hzucb85qhb9eyktw6b0byt6nd6b9b7u7f31yjld0&rid=giphy.gif&ct=g
