Content
@
0 reply
0 recast
0 reaction
🌹 zach harris 🥀
@zachharris.eth
Why aren’t channels rec’d based on a root domain added to cast? Ex. Cast + Spotify 🔗 -> /music Might be a structured approach to very simple contextual recos. WDYT?
3 replies
1 recast
10 reactions
Tony D’Addeo
@deodad
not a bad idea but channels as hashtags are lame channels are now trying to be more like group chats, you should just cast to main if you aren’t intentionally sending it to a group
1 reply
0 recast
2 reactions
🌹 zach harris 🥀
@zachharris.eth
I think we’re talking past each other. I mean at the time of actually writing a cast (before publishing) so WC client channel recs would be contextually driven by associated link in cast. Ex. AP.com -> Reco /News Spotify.com -> Rec /Podcast /Music
1 reply
0 recast
0 reaction
nyc-crypto-cabal-kid
@zinger
What @deodad said is true and is the reason this doesn’t make sense You’re assuming there is a canonical channel for news, music, podcasts, etc. but channels are specific communities now, not broad topics (“hashtags”) /untzuntz is a community for people who love house music for example Categorizing a link as music, podcast, video, etc. isn’t interesting, it’s the context that it’s shared in that matters I agree that it would be cool to have smart channel suggestions based on ones that you’re a member in but it will take time to develop “channel SEO” for an algo to understand what each channel is about and be able to effectively recommend them
1 reply
0 recast
1 reaction
🌹 zach harris 🥀
@zachharris.eth
Thanks for the clarification. Great name for house community btw. I understand more niche communities like house enthusiasts, fall lower in community taxonomy, but a topic vs community like /food with a broad following feels canonical. Somebody’s not going to unfollow and create a new one overnight. But point taken from you and @zinger on the complexities around recommendation based on that approach to categorization.
0 reply
0 recast
1 reaction
