Installer crapped out for me, giving a gzip error. Also, I'm not wild about self-extracting and executing archives. Would you mind perhaps just posting a .tgz that can be examined before installing?
A summary here is that our main tool available right now allows the user to use a bookmarklet (we’re also working on browser extensions) to scrape the page being viewed and send it to our systems for parsing and saving. This means that any posting you find can be saved without relying on sessions, cookies, etc to keep track of it. And once it is in your saved list you have control over when it is removed, so that even if the job expires on the originating site you still have a record of it.
You can keep your positions private, or publish them to a public feed which others can then subscribe to thus getting a feed of positions you’ve found. Say you are interested in helping to support the Ruby on Rails community and you’d like to keep a list of good Rails jobs that is sharable with others. Anything you save to this queue is published to the feed and anyone can subscribe to it.
That's the quick-ish intro, we have more coming, but this is the start, and we’re hoping to get feedback and people using it.
We’ve just opened up our public beta, and while we’re very much still early in our process, I am excited to show it to everyone, get comments, and hopefully get people using it.
theoldreader seems to have died on my feed import to the best I can tell, anyone seen anything similar? It says it is still working in the background, but no update past the first 3 it imported...
http://www.sypartners.com
SY Partners is hiring Interaction and Application Developers full-time. Both are heavy javascript, with the application developer also doing Ruby and node.js work.
Bleh, left a comment and forgot about it, bad of me.
Depends on how the fields are added/removed from the page, but if they're dynamically created (I don't think they are in this case) then they wouldn't exist at the document load time which is when the manager tends to fill in fields, to my knowledge.
While I can at least see the argument of form fields possibly being intrusive, it seems like a long stretch to me in this case. Were it a multi-field form collecting data, I get it, but for a login form on a site where 99% of the activity takes place behind that login it seems damn silly to me to hide it so much.
Goodness, I hope all the people using SVN to deploy are making sure that they're taking care of the .svn directories and the resulting security issues.
Worst. idea. ever. I hate this on Twitter, it breaks the password manager and it is an additional click just to show a login. How is it so intrusive to have 2 fields on a page?