internet category

I’m passionate about online privacy. Also posts about security, general web development and commentary.

Not included here are my archive of tweets and Delicious links. Those are in the cloud.


Unsubscribing from StackExchange pandas

Sign that says Pandas

I hate the term, but starting in 2013 I decided to be more proactive about the emails I receive. With regards to newsletters, unless it provides information not available elsewhere through RSS, Twitter or the like, I unsubscribe. Synergising my inbox paradigms.

Having clicked the unsubscribe link in a StackExchange email, I was presented with the above image, and a comment.

We couldn't find the page you requested, but we did find this sign that might help.

While technically true, I doubt sicking a panda onto my inbox will rid me of your newsletters. That is, unless it somehow overcomes its bamboo addiction and begins ingesting them on my bearhalf.

Jokes aside, having unsubscribed to dozens of newsletters so far this year, errors like this are disturbingly common, regardless of the browser or platform I use. I suppose some sites figure if they make it non-trivial to unsubscrube, you'll just stick with them.


Amazon, please check where your customers are

Merry and the gang at Karaoke!

Speaking of emails, I got this message from Amazon this morning. I'm emphatically pointing out that emphasis was added by me, for emphasis.

Dear Ruben Schade,

We thought you'd like to know that eligible songs from 2 CDs you have purchased from Amazon are being added to your Cloud Player library. [..] In addition, we're excited to announce AutoRip. Now when you buy any CD with the AutoRip logo, the MP3 version of that album will instantly be delivered to your Amazon Cloud Player library for FREE.

AutoRip is available to U.S. customers only.

Amazon, can I have a quick word with you? You seem very nice. I like your site. As you've said here, you've posted me music to my address in Australia. You've billed my Australia debit card, and a Singapore card before that.

So why, my friend, are you telling me about a US-only service?


Yay, my Twitter was breached!

Password reset form

So, I was one of the super lucky 250,000 users to have their Twitter account details leaked. While I did create my account in March 2007, my #875,971 account ID is still higher than 250,000. Maybe they only hacked earlier accounts that are still active?

UPDATE: The Guardian is saying the attack only affected Twitter accounts created in the first half of 2007. Mystery solved, if true.

Dear Twitter User:

As a precautionary security measure, we have reset your Twitter account password. Check your inbox for a separate email from Twitter with instructions on how to reset your password. If you don't see an email, you can go to this page in our Help Center to request a password reset. More information is below.

We recently detected an attack on our systems in which the attackers may have had access to limited user information - specifically, your username, email address and an encrypted/salted version of your password (not the actual letters and numbers in your password). Further information about the attack can be found in this blog post.

Since your password has been reset, your old password will not work when you try to log into Twitter. We strongly encourage you to take this opportunity to select a strong password - at least 10 (but more is better) characters and a mixture of upper and lowercase letters, numbers, and symbols - that you are not using for any other accounts or sites. Using the same password for multiple online accounts significantly increases your odds of being compromised.

For more information about making your Twitter and other Internet accounts more secure, read our Help Center documentation or the FTC's guide on passwords.

This attack was not the work of amateurs, and we do not believe it was an isolated incident. The attackers were extremely sophisticated, and we believe other companies and organizations have also been recently similarly attacked. For that reason we felt that it was important to reset your password and publicize this attack while we still gather information. We are also helping government and federal law enforcement in their effort to find and prosecute these attackers to make the Internet safer for all users.


Yahoo! Mail finally gets SSL!

Almost two years ago, I bemoaned the fact Yahoo were creating new things, but were still the only major mail provider to not offer SSL. On an unsecured wireless network, this is an open invitation for anyone to hijack your session.

Well, they finally listened!

Activating SSL adds an extra layer of security to your account. While using SSL protection is optional, we recommend it if you are on an unsecured internet connect, such as a wireless network at a cafe.

It's a step in the right direction, but it desperately needs to be enabled by default. As a developer and sysadmin I know most people don't change default settings, which means most of their users will still be unprotected.


It's Not Apple So It's Okay™

Icon from the open source Oxygen Icon Project for KDE

Also me, exactly one year ago:

Isn't it interesting that the same people who blast Apple for their uphill battle screening software for the App Store are often the ones who rush to Google's defence for not catching all fraudulent advertising? It's not double standards though, because they don't call it that, and because It's Not Apple So It's Okay™.

So much changes in a tech year, and so much doesn't.


Now I know how it feels to talk to me

London tube trains photo by Reveal on Wikipedia

From the Wikipedia London Underground 1996 Stock page:

The GTO thyristor used on 1996 stock achieves this by "chopping" the supply voltage in order to drive a sinusoidal current in the motor windings (pulse width modulation), creating the characteristic audible whine associated with the stock and with the Class 465 Networker trains that share its traction drive system. The sound changes as the pulse length changes. The noise is produced by the switching frequency current ripple and the resulting torque pulsation experienced by the rotor of the induction machine.

I'd tell you I'm an amateur train buff otherwise feeling out of his league, but my gyroscopic induction coils fail to provide the adequate capacitance ratio for me to assert I have no engineering training outside core pulsation computing apparatuses of which my home provides power through parallel transwarp modulators.

This experience has allowed me to empathise with some non-IT people who have to talk with me sometimes. When we're surrounded by computers all day, it can be hard to keep things high level and abstract when talking with people who's lives don't also revolve around IT. Or maybe that's just me.


How many comments does it take to ruin a joke?

Mount Lofty Cafe in the Adelaide Hills

A few weeks ago, Georgina on Twitter gave me some moral support for disabling Rubenerd.com's comment system in June 2012. So far, so good!

Spam

When I first turned comments off, I stated the primary reason was spam. I was getting hundreds of spam messages a day, and the law of diminishing returns started kicking in. Sure, I could comb through these and perhaps uncover a legitimate comment, but the time it took to do so was increasingly hard to justify.

Details, details, details

I'll admit, that was only part of the story. In his typical style which I now miss dearly, John Siracusa pointed this out which rang bells:

The main point is that you're supposed to be communicating something, and if you successfully communicate that idea, it doesn't matter so much about how you said it. That's the details. It's better to be better at communication without being strictly correct or formal or whatever than the reverse when you're correct and formal but don't communicate your idea.

Someone in the real world professed to reading my blog once, but claimed what I wrote was often wrong. When quizzed about what they meant, it was because I'd often fail to mention certain details, or that my definitions weren't entirely accurate.

And therein lies the issue. Unless you define every term in legalese with hundreds of footnotes, caveats and painstakingly outlined definitions for what "security" and "is" means, there will always, ALWAYS be ways to pick apart posts. After a while, it became tiring arguing over tiny, insignificant points when the broader issues I was hoping to foster conversations about went ignored.

In Siracsa's words, I was communicating an idea, but rather than commenting on that, some people just revelled in being picky. More power to them, their choice! Another way to put it is this joke currently spreading:

How many geeks does it take to ruin a joke?

Okay, first of all you mean nerds, not geeks. And it's not a joke, it's a riddle. Proceed.

I have a bone to pick with your humerus

The third problem is humour. While I spent my formative years living in Asia, my mum was Scottish Australian and my dad is German. Both these cultures, much like the Brits where a large part of Aussie culture derives, value self deprecating, dry and deadpan senses of humour that are lost on some people. Chalk it up to cultural differences, but I'd say something I think is clearly a joke, and there'd be people who'd misunderstand or get offended.

This doesn't happen as much on App.net or Twitter, because people on those networks presumably follow me because they like what I tweet, my sense of humour makes sense to them, and I pay them large sums of money. In a blog, people often found my posts through search engines, would read a bit, misunderstand, get angry, and post away.

So the question I set out to answer in this post: was it a good idea to turn off blog comments? Most definitely. I've noticed a drastically improved quality of life since doing this, and I have no intention of re-enabling them any time soon. John Gruber and Dave Winer were onto something.

That said, I've decided to look into alternative ways to allow people to contact me for feedback, maybe a disposable email address with the year in it or something.

Photo by me, at a café in Mount Lofty in Adelaide.


Well hello, @yaakov_h!

@yaakov_h's avatar on Twitter

@yaakov_h, earlier this evening:

@Rubenerd_Blog Hello Mr. Blog

And in response, from @hanezawakirika:

How short is that post? XDDD [..]

This short!


Minor site tweaks of doom

Netscape Navigator!

Taking a quick break from writing a development proposal, I made some minor tweaks on the site today. On the site? To the site?

  • The layout is now centred, not to the left. I preferred it the old way, but the number of tweets and emails from well meaning people asking me if my CSS was broken got to be too much. Actually, I did this a few days ago.

  • Lines from the header have been removed.

  • After two years of CSS3 rounded corners, I've got rid of those too. They looked okay, but they were inconsistent with the rest of the design. Or at least, I thought so.

I've also done some other CSS tweaks in preparation for the unveiling of something much bigger soon. Or should I say, someone much bigger. And no, it's not Netscape Navigator Gold 2.02 support.


Soon we can download an archive of our tweets

Morning coffee, free wifi, Twitter

This is huge news. Monstrously huge news. Eliza Kern at GigaOm:

Several Twitter users began noticing Sunday that they now have the ability to download their full archive of tweets, a capability that users have asked for since Twitter’s early days, but which looks like is rolling out to users now.

Photo by me in 2007, at the Coffee Bean and Tea Leaf in Tanglin Mall. Cue nostalgia!

Only took them half a decade

Back when we all started using Twitter in the early days, we just assumed our archive of tweets would be accessible, just as our blog posts are. After we hit the invisible ~3000 tweet ceiling, we realised some of them weren't easily accessible unless we had the original URL. As far as I know, it's not accessible in their API for third party clients, either. If you use Twitter as a IM client that's probably acceptable, but for those of us who tried using it as a microblog, that was a horribly limiting factor.

Prior to their recent policy changes for third party clients, I kept a backup of all my tweets in a pseudo-hidden category here. Still, there are a lot of gaps, and I have almost none of my tweets from 2007 to 2009. I'd been considering going through various caches in home folder backups to see if I could reconstruct a timeline that way, but given the sheer number of clients I've used over the years (Twitteriffic, Snitter, Twirl, Tweetie, TweetDeck, TweetBot, Polly... and that's just on the desktop) I knew I had my work cut out for me.

It'll be like downloading six years of my life

ASASP, I'll be downloading my own archive. First thing I'll do: import it right here into my same pseudo-category. Second thing: figure out how to backup tweets more reliably going forward.

I wonder what format it'll be in. JSON? CSV? An SQLite database? Hey, that'd be schweet.