4 ms·

Nice! I'd like to see an uncheck all. Or an easy way to just target one site, instead of having to uncheck all but that site. Probably the next thing would be

by mjhea0 12y ago

Nice! I'd like to see an uncheck all. Or an easy way to just target one site, instead of having to uncheck all but that site. Probably the next thing would be to pull in the Who's Hiring - https://news.ycombinator.com/item?id=8681040 https://news.ycombinator.com/item?id=8681040 - then scrape and parse it and incorporate it into the site somehow. :)

ginkgotree 12y ago
Great suggestion on targeting all the sites. Just pushed an update that un-checks every site with the "All Sites" checkbox at the top. I'll look into scraping the Who's Hiring feed next...
- mjhea0 12y ago
  I would create a new category for this since the formate will be much different than the regular HN Jobs. Scraping is easy. Trying to figure out the best way to parse/display is hard.
  - walshemj 12y ago
    well not so much the optimal browse structure for seo for job sites is fairy well understood by now - I worked on total jobs and other sites at my previous job for part of elsiveer
- mjhea0 12y ago
  Just don't worry about normalizing the data. Just grab each post and treat it as a new job. Let me know if you need help. I'm pretty good with cheerio :)
- mdaniel 12y ago
  Just as a friendly FYI, HN now has an official API designed explicitly to stop folks from doing that. For example, the whoishiring user[0] gives convenient access to every post[1] that would interest you. 0 = https://hacker-news.firebaseio.com/v0/user/whoishiring https://hacker-news.firebaseio.com/v0/user/whoishiring 1 = https://hacker-news.firebaseio.com/v0/item/8681040 https://hacker-news.firebaseio.com/v0/item/8681040