Not sure how Nosotros works on the back end, whether it has the outbox model implemented, etc. I expect it at least reads from your preferred write relays when looking for your follow list, which means it shouldn't have issues with erasing previous follows like Primal often does. Some clients query hard-coded indexer relays instead, though, like the purplepag.es relay.
Worth looking into.
So I had a discussion with the developer Cesar earlier today about this, and yes it uses outbound relays.
However, I've also noticed sometimes it "overwrites" my published list of relays and pre-populates with 25 of what I think are default ones... so yeah, not quite sure what's going on. Maybe it is using an indexer which was out of date.
Tagging nostr:npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c here in case this might provide a hint for him.
Yes it has outbox implemented, what signer are you using with nosotros? I recommend using a browser extension like nos2x and check all the messages the client is trying to sign in the popup (don't click "authorize kind 10002 forever"), if you are using a mobile client like damus/primal/amethyst and put your nsec on it, you have no control on what the client is signing (and possibly overwriting it), use a remove signer on mobile like amber.
Did your list was overwritten when you trying to change your relay setting or when you just tried to access some client? you will need to hunt down the client doing that.
So these days I'm using Amber as much as possible, both for desktop and mobile apps. I used to use nos2x but I admit I used to eventually allow always.
I'll have to remove some permissions from Amber and be more careful about it!
The relay list updated after I made changes to the list in nosotros. That makes sense, but the issue is moreso for some reason getting a list of 25 relays in nosotros sometimes. I didn't realise at the time, but when this default list populated, and I tried to remove some, it would of course publish this as an updated relay list.
