“Wishing that I could hide entries without comments (as opposed to likes or comments).”
June 20 at 1:50 pm
- Link
peter huesken liked this
But what about the slipperyslopeness of this? Maybe I'm just being too hippy'ish here, but if everyone did that, there'd be no comments. It's basically, a "No, you first." "No, you!" standoff. It's admittedly a tough balance with Friendfeed (and beyond), eh? 1) Show the user specifically what they request. 2) Show the user what they actually want. 3) Show the user stuff that will help enrich the community (e.g. surface less-popular stuff). Tough to manage all three! - Adam Lasnik
My use case is that I'm subscribed to (for example) Jeremy Zawodny's blog in Reader, and I already see/read his posts there. I only want to see his posts here if they have comments, otherwise it's just wasted space. - Mihai Parparita
I think there are plenty of people who will "go first", either because they just like more volume, or because they feel closer to the feed in question (they know the poster in real life, or care more about the topic, or whatever). I think the only real balance is with UI simplicity, I don't think there's any need to force-feed people anything they don't want just to jumpstart comments. Super-Hide could easily be a giant dialog box (I also want "eliminate all FOAF last.fm entries", for example). - ⓞnor
FF has three pages for a user. Using Mihai as an example - http://friendfeed.com/mihai, http://friendfeed.com/mihai/li... and http://friendfeed.com/mihai/co.... What Mihai is asking for is http://friendfeed.com/mihai/ot.... - Atul Arora
I do this in Friendfork (http://friendfork.appspot.com) for Reader shared items (it actually creates duplicates for both likes and comments right now, but I'm going to change it to comments only). I want to do this for blog posts too, but I need to either implement feed discovery myself (not sure how well that will work with appengine timeouts) or have the FF api return feed urls in addition to html urls. - Ben Darnell