Oddbean

We must have follow lists for each kind. The kind 1 follow list is different than a blog post follow list. So, all of your options are wrong. :) Other kinds should never be rendered as root posts on kind 1 clients. But kind 1 clients must render or forward them when they are quoted into a kind 1.

"Interesting perspective! It’s always great to explore the nuances of how we categorize content. Flexibility in our approach could lead to more engaging conversations. Let’s keep the dialogue going! 🌟 #ContentDiversity"

we need follow events though, not lists but CRDTs... nip-86 isn't it? nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qg4waehxw309an8yetwwvh82arcduhx7mn99uq3qamnwvaz7tmp9ehx7uewd3hkctcpzpmhxue69uhk2tnwdaejumr0dshszrnhwden5te0dehhxtnvdakz7qgcwaehxw309a3k2mrvv9ezumn0wd68ytnhd9hx2tcpz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309aek2ctjvd5zumn0wvh8gmmyv9uj7qpq80cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwshw8uch wen can we have this relationships nip approved or what?

I have similar thoughts but I ultimately think it’s a bad idea; one of the powers of nostr is the portability of the social graph and starting from scratch on each use case breaks a lot of what’s cool about it. That said, being able to fork your follow list, or have some slight modification to your kind:3 could be very cool and depends a lot on the use case. FWIW, I don’t think it’s a per-kind follow list, but more a per-use case list, like I might be interested in someone’s thinking and want to follow them and also follow their highlights, long forms and podcasts but their music taste sucks and I want to not have them in my music follow list. Agreed on paragraph #2. I changed my opinion recently about this and I think it solves some problems.

I don't think separate follow lists are optional. I don't want to see any music recommendations or my only fans feed from you people :) A way to solve it is to create separate keys for each major kind and that breaks the graph too.

I think it depends a lot, some follow lists will have huge overlaps with your kind:3, some will have no overlap. It would suck for me to have to re-follow all the people I’m interested in reading long-forms because that’s pretty much exactly my kind:3. To be clear; it’s a different event, what I’m talking about is the tooling to make this empowering instead of detrimental to people using this.

Humans don't organize by content type. I don't need follow lists for each kind. That's terrible UX and is playing Big Tech copy cat for no reason. I don't want to manage dozens of follow lists, trust score lists, recommended handler lists, etc... I just need Communities and they solve most of that stuff as a byproduct. I open up Zapstore and can look through the eyes of the communities I want app recommendations from. Or interact with each community with their recommended apps. I open up Zapster when I arrive on a get together of my College Friends (private group) and can just launch a playlist of the music the people in that group have publicly valued. Or I just open that app when I'm alone in the car and get recommendations based on what's in my library, what I've zapped, ... Or I browse by Community. Note that I'm not following any App or Music Artist for any of this to work.