190kb? That is a lot of bandwith to you?
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
Itβs inefficient, and it all adds up over time when a lot of users are using the same relays simultaneously. You might not be aware of this, but thereβs a hard limit of 64 kb for NIP-44 encrypted payloads, so I canβt even use a signer like Amber or Nsec.app with my profile because my kind 3 events get rejected due to the data cap. My list is almost twice the size of the acceptable length even after reducing it by 1000 follows.
AFAIK, NIP 44 (DM kind4) encryption has nothing to do with kind3 events that has relay limit of 64KB.. If you want to follow more people, host your .json file externally and the point to it in a kind3 event instead of listing all the npubs in a single event, then you can use a signer like Nsec.
NIP-46 remote signers depend on NIP-44 to provide the encryption scheme. I ran into this issue trying to build an app that supported Nsec.app and it didnβt work with my follow list.
Iβm sure nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p or nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z can answer this better than I can.