Get rid of the lists. They're an attempt to create tables in an event store and they're an inevitable hot mess.
Lists should be created out of similar or related events, not saved in list format.
#devs
Discussion
Lists are an anti-pattern.
Well, okay, lists are not an antipattern, but they're only appropriate for some collection that is relatively short (under 1000 entries) and quite static.
Totally inappropriate for something that is constantly being fiddled with and/or steadily grows in length, like a follow list or bookmarks.
This is causing "event bloat", where relays have to allow for larger and larger event size.
This makes so much sense.
Right?
At the moment, the plan is to maybe split long lists into chunks, but it's like
ADMIT YOU MADE A l MISTAKE AND CHOOSE A DIFFERENT DATA STRUCTURE, PLEASE.
Can't we just use this for every follow?
https://github.com/vitorpamplona/nips/blob/relationship-status/81.md
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q is there a reason that would be silly?
that's what i see it eventually doing, yeah i was looking at it a couple weeks back, i posted an asknostr what it was and someone directed me to it
It's like a contacts card, basically, is how I'm interpreting it. "This person is interesting enough, that I want to keep a private note about them." and then you could categorize each one, according to why they are interesting and how much you want to see of them, instead of having 500+ follows because reasons you can't remember, and all of their notes flooding the timeline indiscriminately, so that you're forced to make lists of "follows I actually _really_ want to follow", to cut down on the noise. 😅
Would also solve for most mutes, as you could have a category "quiet", where they can @ you or reply to your notes, and you can go to their profile and see what they've written, but you don't see everything they post to main.
Could even have another category "loud", where everything they post stays at the top of your feed until you've seen it, or something.
maybe you want to start putting together a reasonable minimal common set of categories as well with their semantics
I was hoping that they'd merge it, soon, so that I could do that in a PR. But everything just rots over there, fr.
It's still in draft even though two (or three?) clients already produce the events.
Maybe I should just wiki it and add it to my events list and then I can edit the wiki and submit the new events list to the NIP repo. Vitor can't take his own event kind hostage, like that. 😅
I like it.
But if they're not lists, what do you call them in the UI?
I used "Profile Lists" before and somehow "Categories" or "Labels" has a weird feel to it for people. Although that's obviously what you're doing: categorizing npubs with labels.
They are a "list" in the UI. The client gathers the events together and builds a list for the display, just as it does with your followers, but with much less inconsistency because you regularly write to the same relays.
"followers" is a mess because the event is wherever _they_ write to, and you might not be reading from there.
I mean, you could actually keep all of these events on a private relay or use the private version of the events.
So like this'd be fine?
(I don't like lying 🙈 )
I like it. It's more intuitive because you could probably click on "271 Profiles" and see a list. You can't "see" a category. That's a descriptor, not a thing.
What this UI does is use your categories to produce lists at runtime. The categories can also be used to do completely other things, but here it's just building lists.
KWIM? Like, if you go here, you see the list of my followers. You do not see the "category" followers.
You categorize the npubs, in order to determine what will be included in the list displayed.
You also can do other things with the categorization, like batch-DM or batch-invite everyone under "best frens" or "community ABC", or have your personal algo shuffle the order of categories you see in your feed, or prioritize the order or change the formatting, according to category, or create custom feed DVMs, or etc.
Follow is binary follow/unfollow, whereas categories are circa 2000 possibilities, limited only by the size of the category event, and most clients will probably have some defaults, like "following" or "friends" or "contacts" or "must read" or "expert" or...
