3 ms·
I've been wondering if segmentation might be the way to go. Have the chatbot look at all the items, cluster them into a few buckets of its choosing, then throw
by flir 2y ago
I've been wondering if segmentation might be the way to go. Have the chatbot look at all the items, cluster them into a few buckets of its choosing, then throw each new item into the most appropriate bucket.
(I've been thinking about this not just in terms of HN, but treating all my RSS feeds as one undifferentiated stream and just having a chatbot sort incoming items into whatever bucket it deems most appropriate).
What's stopping me is that it might work, and I doubt making the internet even stickier is good for me long term.
- 8organicbits 2y agoI've been thinking about that at length recently. RSS feeds often don't have category elements specified and there isn't a widely used taxonomy of category names. I'd prefer not to use AI to solve the problem, although encouraging the use of RSS categories will be slow work. https://alexsci.com/blog/rss-categories/ https://alexsci.com/blog/rss-categories/
- flir 2y agoThanks for the link. It's interesting, and I hope you find a way forward with that, it would undoubtedly be a useful addition to the ecosystem. But my gut feeling is that there's not enough interest in RSS right now to drive widespread adoption of a new version of the spec. My approach would be to focus on improved UX over existing feeds, rather than speculatively expanding the spec to make feeds richer. The main advantage of my approach, I think, is that it adapts to the individual end user's needs. If all my subscribed feeds are tech-focused and I use a generic published taxonomy, I'm going to end up with 60% of my items in "Technology" and 30% in "Computing". If I use a chatbot to dynamically bucket stuff, I'll get "Micro PCs", "Graph theory", "Golang", etc etc.
- 8organicbits 2y agoOne nit, RSS categories have long been part of the spec, but I've found people don't add them consistently.