3 ms·
Here's a similar link collecting service I've been developing, e.g. for #nodejs http://tagwalk.com/tag/nodejs http://tagwalk.com/tag/nodejs
by timhastings 16y ago
Here's a similar link collecting service I've been developing,
e.g. for #nodejs http://tagwalk.com/tag/nodejs http://tagwalk.com/tag/nodejs
- adrianwaj 16y agoNice, didn't know about it. The black background, small writing and grey text kills me. But I've got a new link on Twitya for any username to tagwalk. Thanks.
- timhastings 16y agoCool, thanks for the link. Sorry if the colour scheme made your eyes bleed - I'm still experimenting with that. :-)
- iampims 16y agoThat's really interesting. I started firetweets by tracking only node.js links. I really like the data driven approach you've taken. Do you plan on expanding to other topics? edit: You already do track other topics. That's really cool!
- timhastings 16y agoThank you. It already works for any hashtags or usernames that it encounters, here's #sundaybaconclub http://tagwalk.com/tag/sundaybaconclub http://tagwalk.com/tag/sundaybaconclub
- iampims 16y agoI'm impressed. From what I've read on your blog, you have gathered a massive amount of data. How do you fight spam?
- timhastings 16y agoIt's many pronged approach. User timelines are loaded for "reputable" users, (see blog for computing reputation) and search input is used with primative bayesian filtering. In my experience, I have found Tweet source (web, Tweetdeck, API etc.) to be one of the most effective quality/authenticity indicators.
- iampims 16y agoUsing the tweet source is such a smart idea! So far I rely on username filtering / patterns. Toughest is to get rid of job postings ! Good luck with Tagwalk ! You've got a new user ;)
- timhastings 16y agoNice one, thanks, and good luck with Firetweets! There is tons of job tweets, but most have "job" in the username and/or app source. Also any app source that contains "bot" or "feed" is most likely safe to ignore.