HN2new | past | comments | ask | show | jobs | submitlogin

Nice idea, and works well. The first tweet is a RT from a fellow student at RISD who I didn't even know had a Twitter. Some feedback:

The second tweet that comes up for me (Providence, RI) is one labeled "North America and Europe." I think local listings should be prioritized over broad ones.

Filters based on language/expertise. I see a lot of these tweets go into specifics already so this could probably be implemented easily.

As someone else mentioned, a link to the tweet would be good, and preservation of the hyperlinks in them so I can click directly on someone's job listing etc.

Perhaps you could also normalize the format of the locations, and group them under one heading. For example, most of the listings for Providence are Boston, and it's a list that looks like, "Boston", "Boston, MA", "Boston", "Boston", "Boston, MA", etc. A consistent format would be good for readability and having a new <h2> for each tweet is redundant.

Basically, you have a good crawler (I assume you're using one) and now you need to alter the design of your page to make it easy to explore.



Thanks, yep a lot of what is required is a better way of presenting and filterring the tweets. Working out the locations for the tweets could definately be improved, especially when it's quite vague.

thanks again.


No problem. Mind if I ask what you're using to track my location so discreetly? Chrome never asked me for permission. :P I'm also building a location-based webapp and would like to check it out.


I'm using this from google http://code.google.com/apis/loader/

Code runs in the browser then:

if (google.loader.ClientLocation != null) { loc = google.loader.ClientLocation.address.city; lat = google.loader.ClientLocation.latitude lng = google.loader.ClientLocation.longitude }

hope that helps.


Thanks!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: