Fuck these guys. I’ve spent the last ten years of my life trying to keep Google’s users safe and secure from the many diverse threats Google faces. I’ve seen armies of machines DOS-ing Google. I’ve seen worms DOS’ing Google to find vulnerabilities in other people’s software. I’ve seen criminal gangs figure out malware. I’ve seen spyware masquerading as toolbars so thick it breaks computers because it interferes with the other spyware. I’ve even seen oppressive governments use state-sponsored hacking to target dissidents … But after spending all that time helping in my tiny way to protect Google—one of the greatest things to arise from the internet—seeing this, well, it’s just a little like coming home from War with Sauron, destroying the One Ring, only to discover the NSA is on the front porch of the Shire chopping down the Party Tree and outsourcing all the hobbit farmers with half-orcs and whips.
when someone asks me a “quick favor” on friday night
And also when someone asks a sysadmin with anything office related.
So all in all the pieces are really starting to come together now and we expect to have some sessions during both GUADEC and Flock this year to try hammer out the remaining details. If you are interested in learning more or join the effort be sure to check the two conferences notice boards for time and place for the container sessions.
The best code is no code at all.
This was a interesting read…
Our focus for May and June has been to get rid of all the sporadic crashes that happen in feedly for iPhone and feedly for iPad while trying to accelerate the rendering. We have been making a lot of progress but there are two last crashes we have trouble understanding. The crashes happens deep inside WebCore. Given that it happens randomly, we are trying to understand which part of our code could result in the following low level C code.Any WebKit/WebCore expert in the feedly community? | Building Feedly
Should really write something about the Amazon CloudFront research I did last week at work.