Maybe these days it’s “hackernews’d”.
Some kind person posted a link to this article, which resulted in an email alert from Linode about outgoing traffic at midnight this evening.
This blog runs on a single wee Linode instance, but fortunately it’s over-engineered for its usual traffic volume, and served by nginx, php-fpm and the WordPress totalcache plugin.
It seemed to weather the storm really comfortably with load hovering around 0.2.
Unticking a box might seem like a small thing, but consider the following:
- The number of Flash Player and Java updates are frequent due to security issues and staying up to date is very important.
- Updating Java or the Flash Player is anything but a frictionless process as it is. For Flash, upon clicking the update prompt I am taken to a download page, where I must untick the box for whatever crapware is on offer, click download, open downloads, launch the download, close web browsers (and possibly other applications), click retry, finish. Java is a little better, but not much.
- Many people have multiple devices to update which magnifies the annoyance factor.
We are not in the 90s any more. Apple, Microsoft and Google have all managed to make updates a 1 touch process (or less), and this is the expectation of your users.
So stop being precious about distribution, but in the very least, stop abusing the update process as a marketing opportunity. It is irresponsible and annoying to millions of people every day.
Flagship smart-phones have been getting progressively larger. My first high-end Android device was a Samsung/Google Nexus S, which was comparable to an iPhone 3GS in dimensions. By modern standards it is chunky, yet it remains a good tradeoff between screen size, pocketability, and handling.
The two phones I’ve owned since the Nexus S have had progressively larger screens – I went to a Galaxy SII, and then a Galaxy SIII. But I never wanted a larger device than the Nexus S, just a faster one.
E.g. “ssl poodle attack”, referring, obviously, to the recently disclosed security vulnerability in SSL. Which, you know, basically broke the internet.
DuckDuckGo thinks I’m looking for a vicious canine:
Google on the other hand, knows exactly what’s going on:
Update – Since this was posted, Max Allan and Damion Yates have investigated further and found that BT are intercepting DNS queries and replying with doctored DNS results, which I didn’t notice when originally researching this article. The title is therefore not entirely accurate, and BT are most probably doing this without any special treatment from Google, but the point that Google is facilitating this (by performing http redirects) stands. Please keep this in mind as you read :)
As I’m currently in temporary accommodation I have found myself without a permanent internet connection. 3G service in the area is pretty spotty, so I bit the bullet and ended up purchasing a single month BT Wifi pass, effectively piggy-backing a neighbours connection. I’m guessing they see very little of the £39 I paid.
It is well-known that BT has filtering in place, supposedly for the protection of children, as required by the UK government. I don’t agree with this policy, but accept that many do.
However when it starts to affect privacy, I feel that BT’s meddling of my internet connection has gone too far.
Case in point, when using Google on BT Wifi I happened to notice a new message on the side:
SSL search is off
This network has turned off SSL search, so you cannot see personalised results.
The security features of SSL search are not available. Content filtering may be in place.
Learn More | Dismiss
After digging into it, I’ve found that statement to be demonstrably false. In actual fact what it should say is; “We have disabled SSL search on behalf of your network provider.”
To which I say, thank you for giving me another reason to use duckduckgo.
This article was also posted on the Gumtree devteam blog
If there was one golden rule when working with redis in production, it would be
“Don’t use KEYS”
The reason for this is that it blocks the redis event loop until it completes, i.e. while it’s busy scanning its entire keyspace, it can’t serve any other clients.
Recently, we had a situation where code was storing keys in redis without setting an expiry time, with the result that our keyspace started to grow:
This blog has just moved from a Rackspace Cloud host to Linode, which offers a lot more specification for the pound (quadruple the ram for one).
At the same time I’ve migrated from CentOS + Apache to an nginx + php-fpm setup, which is not exactly easy for WordPress, but it feels good to be in the modern era!
Let me know if you notice any problems :)
Yesterday I noticed something odd when I made a commit:
/Library/Ruby/Site/facter/util/resolution.rb:27: warning: Insecure world writable dir /Users in PATH, mode 040777
Tube strikes are unfortunately a fairly regular fact of life in London, and so far I’ve been unaware of the reasons the RMT (National Union of Rail, Maritime and Transport workers) feels strike action is necessary. So with the recent announcement of more strikes, I decided to educate myself this time around so I could either support the RMT and accept the inconvenience, happier in the knowledge that it’s for a good cause, or support TFL and just be angry.
Unfortunately, I’m just angry.
Nostalgia is a wonderful experience. Visiting an old city, seeing old friends, visiting old bars, shops, and reliving the moments is an experience to be treasured. With Christchurch, we have been deprived.
I visited a full 3 years after the most devastating quake (February 22nd, 2011). In that time, much of the rubble has been cleared, and the city is starting to rebuild. But it was shocking just how much of the condemned old city remains, so long after the event.