Now with Olas, I am even more convinced a single follow list for all apps is idiotic.
Discussion
*clapping*
If Olas worked with lists it would be a big help, eh?
true, different people produce different content depending on the medium. kind of nice to have some reasonable default that follows you around though.
I think every type of client will need some form of "onboarding" where you can pick people from your kind3 list.
yeah maybe it can detect kind20 notes from your kind3 pubkeys and suggest those
Should we go back to calling kind3 a contact list and not a follow list? :)
I've always called it a contact list, maybe I didn't get the memo.
you could also detect when someone on your contact list "joins" a kind20 app by noticing if they post a kind 20. then the app could suggest: "hey, looks like one of your contacts is posting photos, you want to follow them on your kind20 follow list?"
Yeah, that's what nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0ekucf3 is trying to do on Zapstore. So, you will know which apps to install based on what your friends are using.
Either that or we will have different nsecs for different apps.
The latter is what I do with "instagram". I occasionally repost myself if the pictures might be interesting to my main account followers.
That said, after 20 years or so on social media I still haven't found the right balance between multiple accounts for different aspects of my life vs sanity.
I’m currently working on a project that uses Nostr for its communication layer, and yeah, I was planning on implementing my own list feature using a special kind number specifically because it wouldn’t make sense for the list to overlap with your regular follows.
It is.
Honestly I been thinking that. There should def be different contact lists.
Follows on Olas will be a different kind, like a user list with a k 20 and a k for horizontal videos.
Consider the relationship status event. In that way, we avoid putting stuff on mega lists again :)
https://github.com/vitorpamplona/nips/blob/relationship-status/81.md
I'm not sure why it was a single event at the start, it seems simple but turns out to be more complex.
An event for each follow makes a lot more sense and avoids conflicts between clients that can overwrite a follow list. Gossip is the only client that I know that has dealt with it well, by giving options to merge. However, all of that is not needed if each follow is a single event.
Furthermore, if each follow is an event, it can be private or public. It can also be an identity confirmation and include more information to record the name and other kind 0 meta that will help security.
I'm single. You can follow me.
What about nip51? Should be enough to create categorized lists for anything
Every kind should have it own follow list; and every 'type of thing' should have its own kind as much as possible; every kind should have its own app(sort of).
Follow lists should not be different because of the app, but because of the difference in kind. I.e. it being 'another type of thing'
This way, you get the flexibility, both in the type of feed, and in whatever app you decide to use.
Make it optional, like a buffet of apps for the prospective content maker.
Okay i get your point