nprincigalli

Kudos to the Waterbear author! Loved to see it done with JS, HTML5 and CSS3. One less thing in my list of "things that I want to see in the world but may have to build it myself". Watching the repo already! :)

  > a camera I had stolen in Peru

  a camera stolen from me in Peru

IMHO, saying things like

  Microsoft’s Internet Explorer and its email programs
  Outlook and Outlook Express are very difficult for even
  professionals to secure. Furthermore, adversaries tend to
  attack more popular platforms and applications.

  every single user action, no matter how trivial, 
  generates a jquery, which goes directly to the 
  master database.

Hemingway: Manuel drank his brandy. He felt sleepy himself. It was too hot to go out into the town. Besides there was nothing to do. He wanted to see Zurito. He would go to sleep while he waited.

Faulkner: He did not feel weak, he was merely luxuriating in that supremely gutful lassitude of convalescence in which time, hurry, doing, did not exist, the accumulating seconds and minutes and hours to which it its well state the body is slave both waking and sleeping, now reversed and time now the lip-server and mendicant to the body's pleasure instead of the body thrall to time's headlong course.

And I bet the poster (ig1) is not the site's admin.

Just so you know, for anything that works over a socks proxy you can already do that easily with ssh (using the -D switch, check the manpage). You then need to configure your client app to use it (e.g. if doing ssh -D locally, in google's chrome, go to tools -> preferences -> under the hood -> proxy settings -> manual, then fill with localhost and the port number)

  And nobody never notified me of any security flaws in my key exchange,

  And nobody ever found any security flaws in my key exchange,

Regarding SSHuttle itself, I really liked it! (coming from someone who does all his browsing with ssh -D)

  > During the years we worked on Viaweb I read a lot of job descriptions. A
  > new competitor seemed to emerge out of the woodwork every month or so. The
  > first thing I would do, after checking to see if they had a live online
  > demo, was look at their job listings.  After a couple years of this I could
  > tell which companies to worry about and which not to. The more of an IT
  > flavor the job descriptions had, the less dangerous the company was. The
  > safest kind were the ones that wanted Oracle experience. You never had to
  > worry about those. You were also safe if they said they wanted C++ or Java
  > developers. If they wanted Perl or Python programmers, that would be a bit
  > frightening-- that's starting to sound like a company where the technical
  > side, at least, is run by real hackers. If I had ever seen a job posting
  > looking for Lisp hackers, I would have been really worried.

We're also fiddling a bit with Google's App Inventor, which uses http://education.mit.edu/drupal/openblocks jut like Scratch.

On the other end, if you have a bad posture, no matter what you wear, man, you'll still look crappy. Only it'll be "designer crappy".

I've got some good stuff from Hautelook, Gilt and Ideeli, for me and my wife (strategically omitting the "el cheapo" part of the story, heh). You'll find a lot of minor brands there, then every once in a while a big-name-brand sale with stuff straight out of vogue or harper's bazaar.

Some of these are invite-only, but getting invites is not difficult, you just have to search around blogs and twitter. Here's a bunch of invitation links in case anyone wants to give them a spin (and just so you know, I'll get a referral bonus if anyone uses them + buys something there):

http://www.hautelook.com/invite/nprincigali762

http://www.ideeli.com/invite/nuba

http://www.gilt.com/invite/nuba

I'd even say it's not about being hardened by rejection, but rather standing up for yourself. Speak up. Dare to ask something. Dare to want something. Then learning that taking risks increase your chances of getting a "yes". The famous "you lose 100% of the shots you don't make" :)

If you've been through the entire piece of work already, it helps you wrap it up. If not, they're good to help you decide whether to dive in or not. Just like when you'd read a long paper's abstract + conclusion sections before committing your time to it.

Summarizing a long text into "key ideas and phrases" can also help the author see the structures and the patterns of his output, which is important for his own development, and critical if you want to generalize, go meta, and bring it onto other areas :)

http://bit.ly/bFuh7x

(source http://jobs.perl.org/about/stats)

  ;; move along, nothing to see here :P
  ;; the beef is in ~/.vimrc and under ~/.vim/ ;)

Posted this one to see what'll happen when it's a tweet from the bigwigs :)

I once worked as sysadmin in a brazilian university, and it was quite common to stumble on unmaintained and hacked boxes serving warez or movies via FTP with dir hierarchies like /path/to/ftp/root/--==tagged-by-this-group==--/--==uploaded-by-that-group==--/warez/.

This becomes a bit of a gray area when every other webapp now comes with some social feature.