Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #25664

D

Doug Ross

Personal blog · directorblue.blogspot.compoliticssecurity

Doug Ross's personal blog at directorblue.blogspot.com covers politics and security. Since 2009, 3 different Hacker News readers have linked it 3 times. It is still writing: the last post was on 2026-11-02, and you can follow it by feed.

Visit the blog
3mentions?
3HN people?
2009–2011first – last linked?
Links on Hacker News per year · peak 1 in 2009

Too few sampled comments (3) to say how often HN recommends it.?

Why HN links it

HN commenters link Doug Ross's blog as a reference on private ocean exploration, a summary of the 2009 Climategate emails, and how BlueCoat SSL proxies intercept HTTPS traffic. Comments cite it without judging it.

Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

75% snark-free diatribes on politics, technology & security

What Hacker News says?

  1. We've had plenty of forays into the ocean by private oil companies: http://directorblue.blogspot.com/2008/11/mile-and-half-deep-... This is much more inspiring, though.

    Comment linking /2008/11/mile-and-half-deep-submersible.html

    on “Richard Branson Announces Virgin Oceanic Submarine ”
  2. Pretty good summary. I would add that there's a summary and references of some of the emails here: http://directorblue.blogspot.com/2009/11/climategate-executi... For point #3 - there is speculation that the emails were leaked (and not "illegally hacked") not only because it would seem a correspondent saw a number of the emails prior to their release to the general public but because it only contained emails that wo…

    Comment linking /2009/11/climategate-executive-summary-of-cru.html

    on “Climate change cover-up? You better believe it”
  3. BlueCoat documents this fairly well here: http://directorblue.blogspot.com/2006/07/think-your-ssl-traf... When the SSL Proxy intercepts an SSL connection, it presents an emulated server certificate to the client browser. The client browser issues a security pop-up to the end-user because the browser does not trust the issuer used by the ProxySG. This pop-up does not occur if the issuer certificate used by SSL Proxy…

    Comment linking /2006/07/think-your-ssl-traffic-is-secure-if.html

    on “Ask HN: Anyone know how bluecoat mess up with https?”

Search all of HN for directorblue.blogspot.com