My guess is this is also related to kind 3 and your large follow count. Some relays don’t accept more than 500 tags in an event. Others 1000. Some 2000, some 5000, etc. Any relay that doesnt accept as many tags as you have follows will not accept your updated contact list event.

As such, you have a race condition where the follows list you get back can differ from each relay depending on their limit. Depending on the client implementation this could cause people you have unfollowed to appear followed again or appear in your follows timeline.

Reply to this note

Please Login to reply.

Discussion

Very interesting! Thanks 🙏 so much 🤙.

Something for paid relays especially to consider. ✋ doubt I’ll be the only ☝️ with this type of issue as this 🟣 scales 🆙

#[0]

Also saw that. Lost my follows several times trying different relays.

This was helpful:

I use the “Nostore” extension on iOS. (Works great). It stops and asks for permission when a Nostr client wants to do anything.

It’s shows the pending event as an xml page of what it’s going to do.

At one point I was following ~3500 accounts and the event to add/remove a contact was miles-long! Had to scroll for like 5 minutes to get to the bottom and approve it.

Updates to follow/following lists won’t scale. Hopefully this will get visibility in a Nip and be improved to not include all accounts list for changes.

Thanks for the 📝🫂💜🤙.

Just going with this 🟣 flow and being patient with “issues” like this 💜.

Also what makes 🏃 this 🟣 endearing at time.

Not sure if it’s at all related to the latest Damus TestFlight but the specific relay is no longer 🟢.

No rush or stress just letting you and #[3]​ know.

🙏⚡️🤙