lukeonchain @lukeonchain - 2y
My contacts got nuked while using Amethyst… so I am following 0 folks. Sorry no likes from me until I restore my backup sometime. For now I’m sipping on a juice knowing my backup is safe lollll
597b4 - 2y
Just login to NostrGram and click on the Following history icon to restore your following list. Here's a video explaining how to do it: https://jonleger.com/nostr/nostrgram_following_restore.mp4
👀watching now
Broooooo +5K sats. You saved my asss painlessly (was going to run the Nostr-contact tool). Lucky for me I also learned how to query with REQ kind=3 on command line as absolute raw data backup I am familiar with lollllllllllll. Thank you man this was easy, 1 click restore. So Sick!!!!!!!!!!! No more living in NOSTR client fear 😅
🙏
Whoever does not watch your video is a fool 😄
Luigi @Luigi - 2y
This is a very useful feature. Never happened to me but it’s good know, just in case. Well done, sir! 🤙
😆 I saw so many reports of lost followings and knew how easy it was to fix the problem! I had no ethical choice but to create the tool lol
What's the trick, to post freshly signed kind=3 message to list of relays? That it
Laser ⚡☀️ @broadmode - 2y
Nostrgram.co just added a features for recovery; log in, go to profile, hit the little far-right calendar icon, then restore previous followers.
As you will see on thread, we did that. Smooth like butterrrrrrr
That's it. It just loads the Kind 3 events, lets you pick which one to restore and broadcasts a new Kind 3 from the contacts from that event (not the relays, it doesn't change that even though those are also stored on the kind 3 event). It's really simple.
I'm getting it. Just haven't dealt with event signing snippets and manually played around with JSON payloads over websocket. Cool, thanks. Kind 3 ✅ . Is there any trail suggesting which client may have been the culprit, any such client incoming metadata even.... to see where the hell the 0 came from? Or no way rather
I was on Amethyst update just scrolling, not even following only commenting on my existing follows (no immediate follow activity preceding the 0... weird)
2905f - 2y
local backup is a must
Only if the client sets a "client" tag when events are posted. If it doesn't (most don't) then there's no way to know which client is responsible I'm afraid.
💯 many unsaved JSONs in my notes lol and REQ payloads. Just everything all at once
Ok. Ty 🙇♂️
1e0da - 2y
Very, very valuable teaching👍🍻
