Oddbean new post about | logout
 This tool may (or may not) be helpful.  Click on the '...' button; then 'View profile data'.  In the 'Following' section, if you have more than 1 entry (you currently have 2), I think this means you have multiple Following lists.  These lists are likely to be mostly duplicates, but any differences may be interpreted inconsistently by clients (I think).  I believe that the duplicate lists are created based on how clients choose to add Follows (maybe based on which relay they default to?)  Then when you add a Follow, it may only get added to one of your duplicate lists or the other (I think).  I have found that consistently using the same client when adding a Follow seems to do the trick (in not creating duplicate Following lists).  It's obviously not very convenient; but it's what I'm going with for now.  Presumably, this is a technical issue that will eventually be solved protocol-wide.

https://nosta.me/npub1s277u5rww60te98w9umz6p7pjcxuus96cegdsf4y978qcqvu8jtq88dsym 
 I do have two indeed. One on "primal-net" (666 follows) and another one on "wellorder-net" (665). Is there a way to delete one of them I wonder? 
 I used to have 2 or 3... the duplicates seemed to eventually go away on their own... maybe when there were finally no differences between them?... It was easier for me to get them to match at the time, though: I think I barely had double digit Follows.

It would be nice to be able to just delete one.  Not sure what that would take, though.  It seems each list is saved at a specific relay. 
 That is on the to-do list.  
 That is on the to-do list.  nostr.fmt.wiz.biz 
 If you have multiple versions of your follow list on different relays, you can now republish the one you want on Nosta. More here: https://primal.net/e/note1nytp4xafgff7cvpxu0uzye6j99m0fle23k8xuqrglah09hdt7qhsrre9nd 
 Cool!  Though, at the moment, the site appears to be broken in general: "Sorry, could not find a profile with the publicKey..." 
 Thanks for reporting, will take a look. 
 Should be fixed now. 
 Yep... looks like it's working again.  Thanks!