That would be someone like nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr or nostr:npub1e8wj749dylsew4pkm9ufz97hvrtk63wfy0cfq2c9gv4973q25hds8e6dq0 for #Primal and nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr for #noStrudel.

It seems likely that they aren't seeing your updated profile note (kind 0), which suggests it is saved on a relay that they aren't looking at, or in Primal's case that their caching relay isn't pulling data from. Something you could do to try and ensure they see it is to update your write relays on a client that shows the correct information to include a couple major relays, like relay.primal.net and relay.damus.io, then make some small change to your profile, like updating something in the bio.

Primal could take a bit to pull that new profile info into their caching relay, but you should be able to verify that it has been updated on noStrudel pretty quickly. Then you can set your relays back to your preference.