Interesting. I’m exact opposite. Never used lists. Only pay attention to one timeline unless I search for something.
Discussion
Exactly, different use cases. I have a list of meme-posting accounts that I don't want cluttering up my main feed. Same with SW. I think all that goes back to when I used TweetDeck (before it got bought up by the bird app), and used to have at least 4 or 5 columns of different interests - like one just for Nascar news and commentary, as I was a fan at the time. Lists and feeds come pretty naturally to me, but they wouldn't come as naturally to someone used to a single timeline of everything.
I created a mute list today, with my blocked accounts from Onyx on it, since I don't think they save anywhere else. Some other client created that list for me, but I deleted it. Now I added it back. Nice to have a record for when I switch clients, or when clients start using lists to handle muting/blocking.
Also created relay lists of my paid and free relays. Just playing with Highlighter.com, and making sure I have my current state saved pretty well.
Feel free to drop my npub in a client that supports lists. Nothing to hide (that isn't hidden and encrypted by my nsec).
Yup. That’s the goal. Saw your lists.
And it’s easily to switch between the different feeds, to have a focused view about a group of users or topics.
Idea for kiwi or anyone else implementing lists - would be very nice to be able to set a certain relay configuration to a list of profiles, at least for receiving notes to the client. Like I might want my sw list to grab posts frim adult relays, my rss list to grab from rsslay, my meme list from everything except nsfw, and my follows list from my paid de-spammed relays.
Since Pablo at least has separate list types for relays and profiles (not sure if these are separate events?), that could even be leveraged to relate one or more relay lists with a profile list.
I don't think I'm the first to have this idea, but happy to help test it out!
That could be possible. Will need to balance between customisation and user experience. Making it as easy as possible, and also performance.
Absolutely, and I would assume it may take a few passes at it before getting the right balance and feature set.
Not sure where I would prioritize it either. NIP-07 and NIP-46 for all clients are more important to me right now. Relay controls of some kind would be close behind it, though, for those clients that really don't support it. I admit I do also like and frequently use the Primal model, which scraps relays altogether and basically just runs its client on top of its own relay, as I understand it. Maybe there it would be even more important to implement lists, as well as external mute/block lists.