All posts by Bjørn

Apple made a watch (and told you it was a revolution)

So Apple decided they needed to jump on the wearable tech bandwagon, and revealed the Apple Watch at their recent keynote. I guess iWatch would be a misleading name? As a tech blogger and rehabilitated fanboy, I feel obliged to write about this. They also released two new phones. They’re bigger, and can now be turned sideways for landscape mode. Such innovation. There, I’ve covered the new phones.

Completely scrambled RGB data
Apple Watch, according to their own press photo

I’m a good law abiding guy, so instead of just taking some picture from Google, I went to the source and downloaded the second official press image. When I tried to open it in an image viewer, it wouldn’t even let me. I tried opening it in a document viewer, and what you see above is the output. Thinking the download had become corrupted, I tried again, with the same result. I’m on Linux, so I figured this was some proprietary Apple format silliness, and spent a few minutes trying to figure it out. Then I ran another test, downloading a press photo for their Magic Trackpad, and I could open that just fine. Their keynote was completely botched as it was, and now this. Wow.

This is the Watch
This is the Watch

There, that’s better. That’s a jpeg file, copied from the same site as the tiff. It’s lower res, and I didn’t agree to their Image User Agreement to get it, because of course they have one. It’s not unreasonable though, just says I can’t edit it or use it to sell stuff. Shown in that image is both what I see as their biggest innovation and biggest mistake.

It’s a square watch.

Come on, Apple, you can do better. Nobody wants a square watch. It’s got your logo on it, so it’ll sell, but seriously, come on. You went and made a new homescreen implementation, that wonderful app cloud, perfect for a round display, but then you just went and made it square anyway. This is the opposite of what Motorola did with their Moto 360, which is that they made a beautiful round watch, but some of the UI is obviously tuned for a square display. With this you might as well have stuck with the app grid we’re used to.

Aside from that, there are a few things I’d like to mention. I’m not a big fan of this release, and I didn’t expect I’d be, but somewhere deep inside I keep hoping that Apple will become revolutionary once more. Instead they settle for telling us how revolutionary they are. They take great pride in their seriously brand new super innovative digital crown you guys this thing is the shit. It’s supposed to make their touchscreen almost unnecessary, only it doesn’t. You can use it to scroll, zoom, and for input, but when demonstrated the guy just kept tapping the screen, using the crown mostly to set the clock, which, in fairness, is what it’s supposed to do.

Oh my God you guys we make the best chargers ever! The Watch charger is magical, you just put the charger on the back and it snaps into place, just like magsafe! Only it uses induction charging! So innovative.

It’s a charger. It hopefully works. We’ve got induction chargers for the other smartwatches already, and they’re on the market. You know what would make this innovative? If you actually shipped when you announced it, you know, like you used to?

Holy hell, you won’t believe how clever we’ve been with the hardware! It’s a quantum leap in technology,  nobody has ever done anything like this before. We can’t even put in words how amazingly we’ve packaged our hardware. Everything is in one module. This is insane, an industry first!

It’s just that we’ve got that. We’ve had it for a long time. There’s System on Chip, or SoC, which puts a lot of sensors and radios and stuff on one piece of silicon. We’ve got System in package, or SIP, which packages chips inside modules to deliver supercompact working systems. How is this not that? How is this innovation and an industry first, guys? You can’t just say you’re the first to do something when you aren’t, there are laws against that kind of ting, I think. Don’t believe me? This is a direct quote from

Configuring an entire computer system on a single chip is an industry first and represents a singular feat of engineering and miniaturization.

I sincerely hope that wearables take off in a big way, and I hope that Apple will help achieve that, but this is not the revolution we’re waiting for. This is another subpar watch, touted as the most brilliant thing we’ll ever see until Apple makes The New Apple Watch. There’s more to the Watch than the things I’ve mentioned, but I only write about things that get me excited, and there’s nothing else. This Apple Watch is mostly boring.

Yes, you can quote me on that.
All of it.

Configuring a linux firewall

So you’ve got your Linux server going, it’s configured the way you want it , and everything is coming up roses. You try to ping it, but the server doesn’t seem to exist. You’ve been blocked by some of the best/most insane firewall in the galaxy: iptables. A firewall’s job is to block unwanted traffic, and iptables takes its job seriously. By default, it. drops. everything. Got a http request incoming? Psh, drop that packet. I don’t care if you’ve got apache running. FTP request? Same story. Mysql? Nope.

A cat shoving things off a desk
This is iptables

Ssh is usually fine though, so we can log in and edit the rules. Iptables rules are added to rule chains. The only chain we’re interested in is the INPUT chain for now; We want to be able to receive http requests to our server, ssh connections, and nothing else. We’ll also want to allow existing connections to persist. These are the switches we’ll be using (you can find all these in the manpages, of course, but some are in the iptables-extensions manpage).

  • -F flushes the rulechains. This means exactly what you’d think.
  • -A [chain] adds a rule to the specified chain.
  • -I [chain] [number] same as -A but inserts rule at a given point in the chain.
  • -i [interface] specifies the interface the rule will act on. If you don’t specify this, the rule will act on all interfaces, including loopback (more on this later).
  • -p [protocol] specifies whether the rule is for tcp, udp, or whathaveyou.
  • --dport [port] further narrows down the packets to look at by checking which port they’re headed for.
  • -m [match] this is an extension that looks at the type of traffic the packet belongs to. We use it with:
  • --state [state], which asks a different module called conntrack whether the connection is INVALID, NEW, ESTABLISHED, RELATED, or UNTRACKED. This is magic, I have only a vague understanding of how it works.
  • -j [policy] says whether to accept or drop the packet.

Alright, let’s get to it. You can think of iptables as a sieve, where every rule along the way checks out a packet and decides whether to keep it or discard it. If the rule doesn’t match the packet, it moves further down the sieve to be checked by other rules. Therefore, at the end of it, if the packet doesn’t match any of our rules, we will just discard it. A good policy for internet traffic is that if you don’t know what it is, don’t touch it. Every rule we add gets added last in the chain/sieve.

A script demonstrating the use of iptables

And that’s it. We’ve configured our firewall. It will reset every time you reboot your server, but that isn’t often. I just keep a script like the one above to reconfigure it. You can get NetworkManager to configure it for you on boot, but I don’t really see the point unless you reboot your server all the time, which, I mean, why would you do such a thing?

Plugin rot and how to do regex replaces in mysql

I’ve spent a few hours over the past week restoring my old blog, which can now be reached at  This will be the final chapter in that saga.

My old blog is sort of old. It started out on MySpace, moved to Google’s BlogSpot platform, then moved to Tumblr for a while because I got some new authors on board. Finally we moved to a WordPress solution.  From there on BRBcoffee has been on WordPress, but it’s moved around hosts like an alcoholic goes from bar to bar trying to get his fix. I’ve employed a bunch of plugins to do various things for me, from importing and exporting posts to providing language switching capabilities to advanced caching to image scaling to… you get the picture. This is all fine and dandy, but it does pose a few problems when you move around like I do.

  1. The image scaling edits your wp_posts database table, naturally. When you move, the scaled images don’t necessarily come with, resulting in a lot of broken links.
  2. The translation plugin just has it’s own tags in that same database table, and keeps two posts in one field. When the plugin isn’t there anymore, or isn’t compatible with your WordPress version, the tags become visible on the site, and you get two languages at once.
  3. Plugins are often developed by lone wolf devs, and they are never up to date when you check up on them years later.

So, we need to clean up the mess they’ve created, and we don’t install Yet Another Plugin™ to try to fix the problem. We need to dig into our database and fix things ourselves. There’s only one problem: Mysql is made for storing, finding, updating, removing, etc. It isn’t the tool for the job when you need to do complex things like searching for a pattern and replacing only the part of the string that matches that pattern. It can be done, I’m sure, but why would you do it when there are better tools for the job? Here’s how I do it:

  1. Export the table you need to edit with
    mysqldump -u USER -p DATABASE TABLE > dumpfile.sql
  2. Do work on the dumpfile with specialized tools like sed, awk, or even vim when in a pinch.
  3. Empty the table before reimporting the modified dump with
    mysql -u USER -p DATABASE -e "delete from TABLE;"
  4. Finally reimport the table with
    mysql -u USER -p DATABASE < dumpfile.sql

Mysql also comes with a tool called mysqlimport, but I had a problem with it, so I just used the standard mysql command in the end.  So what do those switches mean?

  • -p means this user has a password, ask me for it before doing anything
  • -u USER means use this username. Pretty obvious.
  • -e means execute. Execute the following quoted code.

The only weird thing is that -u takes an argument, but -p doesn’t. It looks like DATABASE should be the argument to -p, but it isn’t. DATABASE is simply the database you want to do work on. In my case, it was called “archive,” while yours might be “blog,” “sales_records,” or even “naughty_movies.” That’s commandline switches for you. In my opinion, a single dash should be reserved for switches, double for arguments, like so:

  • -p [ask me for a password]
  • --user <name> [I'm logging in as name, how quaint]

Oh well, you get used to it. That’s how you should do many complex updates on a migrated database. This isn’t for when you want do do one small change on a live system. The 3rd step removes all records from the specified table. Your system will practically be offline until you’ve reimported the changed data.

If you wish this were simpler, you’re not alone. Behavior like this has been a feature request in mysql since 2007. Go there and click affects me, and maybe in another 7 years we’ll have it built in. Till then, use the method described above, and for heaven’s sake, don’t let the plugin rot get your blog too. If you can do it without a plugin, do it without a plugin.

And the archive is restored!

I did it! I partially restored the dead disk, and I did the necessary doctoring on the old WordPress database dump. Sadly, my OffTopic blog wasn’t in the backup tarball, so that’s gone forever. It only had a handful of posts anyway, so no big loss.

Anyway, has everything dating back to february 2009. I was 18 when I wrote that stuff. Don’t judge. Some of the images are gone, as is the nature of the internet. Sorry about that.


Phoenix blog

Here follows an account of how almost a decade of blogging got lost in the æther:

  1. The power supply for my old netbook broke.
  2. I moved.
  3. I moved from Amazon AWS to DigitalOcean.
  4. I moved from Ubuntu to Fedora (DigitalOcean used to support Arch, but doesn’t anymore. This annoys me).
  5. I didn’t update the blog for a long time.
  6. I retrieved all the data from my netbook hard drive’s ext4 partition that looked interesting.
  7. I turned the old hard drive into a backup disk.
  8. I wrote a new partition table to my backup disk.
  9. I added an NTFS partition to my backup disk’s partition table.
  10. I discovered that my website was down.
  11. I discovered that I had failed to retrieve the backup of the blog from the old hard drive.
  12. I discovered that I only had that one backup.
  13. I wept.

Now, I’ve tried to run some basic data recovery. It’s easy enough to retrieve data from a deleted ext4 partition, but getting data from a partition that has been deleted, whose partition table no longer exists, and that has been overwritten by a non-compatible partition type, that’s a completely different story. There are very few vectors left to me at this point. They are:

    • Find a backup disk that has my blog on it.
      • Number of possible disks: 1.
      • Probability that any of them have my blog: 0.2.
    • Download everything has on me. Write a program to retrieve all the blog posts, in order, with metadata.

Things I’ve learned from this:

    1. Your offsite backup is only as reliable as your offsite hardware.
    2. Your offsite hardware is only as reliable as your offsite hardware maintainer.
    3. Don’t be your own offsite hardware maintainer.
    4. I don’t really care what I blogged about in high school.

So, that’s where I’m at. As soon as I have a few minutes to spare I’ll decide whether or not it’s worth it to mine through the internet wayback machine for my teenage musings. I’m guessing I’ll end up doing it for the challenge, and hey, I could even write a blog series about how I did it! But even if I do this thing, and succeed, I won’t import the old blog into this one. BRBcoffee is reborn today, free of the past. Brace for impact.

Bjørn out.