Though this has been resolved, is being "decentralised" the root cause of why follows get nuked for having done nothing to cause it?
This probably shouldn't be happening. Or is the community going to continue to come up with 5 temporary solutions for every issue?
Which new apps did you try recently?
Hmm, White Noise
We knew about white noise rugging relay lists: https://github.com/nostrability/nostrability/issues/212
Just recorded your white noise contact list rug: https://github.com/nostrability/nostrability/issues/219
It’s probably white noise. It also nukes relays. I tested it with a throwaway nsec. This doesn’t happen with stable apps like Damus, Nostur, Amethyst
I read about the bugs so ive just downloaded the app but i didnt sign in to use it. Waiting for few more weeks.
I like trying new things.
recommend doing that with an alternate npub, so if anything happens, you're alright
that, or get used to backing up your account
Do you hop about on platforms. I rarely go off #Amethyst and have never lost my follows list. I also use #Citrine where I can and do back up data. It also has a recover follows option
I thought the beauty of decentralised is being able to app hop and "it'd be seamless, they said".
I dare say it would normalize when the relays get synchronized again.
You did mention not have done anything, but to one or more of the relays you may have been flagged as idle user.
My guess is that the client did not properly fetch your current follows list before broadcasting a new one. This would essentially replace your follows list with an empty or mostly empty one. This is probably due to unsafe process or lack of robustness in individual clients. They should probably fetch before saving a new follow list.
