The offshoot threads on this post are super interesting
This is what my Nostr contact list with over 2600 pubkeys looks like, and an example of why you should consider reducing your follow count. This 190kb file has to be updated and saved to my relays every time I follow or unfollow someone.
It’s why I built nostr:npub1pvz2c9z4pau26xdwfya24d0qhn6ne8zp9vwjuyxw629wkj9vh5lsrrsd4h and why I’m building more tools to help reduce my (and your) bandwidth footprint.
Discussion
Could we make a list of lists and only update the section that would contain the newly added or removed follow? Then more data could be static and less of the data needed to be changed when updating. Idk seems like some kind of intermediate step could reduce this overhead.
There's 100 better ways to handle it than the way it seems to work. What you described is oddly pretty close to how I handle folders in Bloom lol.
That's how I'm dealing with watch history in nostr:nprofile1qqsgjw33lfdxfqfftwmkagka340vwpjqumn26wvwv4rawu0gy440z8cpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpfemhxue69uhhyetvv9uj2v3sy5crqmrfwd6z2v3sy5crqar0y5erqffsxpjxjumrdamx2u39xgcz2vpsw35x2ffjxqjnqvr4wdjhyfmny5erqffsxp3k7mn5v4h8gtcppemhxue69uhkummn9ekx7mp0pluls5
I'm creating a new list every month to create a dated and paginated series of searchable private lists with note events for the videos watched. Seems to work so far.