captjack on Nostr: In order do better nostr housekeeping and improve performance - just TRIMMED ...
In order do better nostr housekeeping and improve performance - just TRIMMED FOLLOWING list from near 1350 to 995 - no worry have back all 1350 hand picked - now I can only load 995 at a time and another profile backup set with another 995 and so soon - may be 995 if found not suitable lower it. point here about a certain number which pushed a metadata to relays it become overkill overloaded - either BREAKDOWN in chunks of 5000 npub u wanna follow and keep growing or make a FOLLOWLIST1 , 2, 3 with max of 500 to 1000 in each. problem is import n backup npub or hex from TXT to such list for now. Let see ... #nostr tip profile compact metadata management scalability
Published at
2024-10-01 16:30:13Event JSON
{
"id": "714c8d31159f242b53297804312e28a5c84f243bc6afe742d06656ee9432bc9b",
"pubkey": "5e5fc1434c928bcdcba6f801859d5238341093291980fd36e33b7416393d5a2c",
"created_at": 1727800213,
"kind": 1,
"tags": [
[
"t",
"nostr"
]
],
"content": "In order do better nostr housekeeping and improve performance - just TRIMMED FOLLOWING list from near 1350 to 995 - no worry have back all 1350 hand picked - now I can only load 995 at a time and another profile backup set with another 995 and so soon - may be 995 if found not suitable lower it. point here about a certain number which pushed a metadata to relays it become overkill overloaded - either BREAKDOWN in chunks of 5000 npub u wanna follow and keep growing or make a FOLLOWLIST1 , 2, 3 with max of 500 to 1000 in each. problem is import n backup npub or hex from TXT to such list for now. Let see ... #nostr tip profile compact metadata management scalability\n https://image.nostr.build/6d9a586b296d6a2c1e63f64a43fdb44430bf7990668168765c0bcedef5d42513.png ",
"sig": "b642ca806a861d8d831ea51cd1e0025b0bd66bc901fa065f9ae78d6a4f635fe9c439a65a749731bd5766d91803acca6fd8a6dcde0b92c3274b8ed59321a4f347"
}
