mossy on nostr

Open in Damus

The Daniel 🖖 · 28w

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 eve...

Mossy Flanagan @mossy 1760463065

This approach seems a little odd, why not post discrete events to follow and unfollow instead of editing and republishing a list? Just curious why we settled on that approach at the protocol level?

4

The Daniel 🖖 · 28w

I’m not a protocol developer, so this is probably a better question for someone like nostr:nprofile1qyv8wumn8ghj76twvfhhstnjv4kxz7tn9ekxzmny9uq35amnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk6tcqyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6luf5tq or nostr:nprofile1qqsvrlrhw86l5sv06wkyjgs6rrcekskv...

Only sending updates would require the server to be able to sign the list on your behalf. The whole point of nostr is to transfer control from server to the user.

It just happened without it being seriously planned for, and now we can't change it (despite many attempts from different people) because changing would break too many things. It's not that bad, though. Well, actually the contact list event shouldn't have to be necessarily mapped to a list of peopl...

nostrich · 27w

Fetching all users followed by you would be a mess, just like, currently, fetching the list of people that follow you is a mess (and clients may get it wrong, by listing people that used to follow you but no longer do). Remember that relays have different data and no relay has all data. So if you f...