Since 2010

UniFi wireless uplinking

Sunday 8 April 2018

Ubiquiti changed wireless uplinking in UniFi Controller version 5.7.20, and are obviously still catching up on documentation updates as the steps provided in this article are out-of-date, and this one doesn’t really cover the steps needed to setup a new wireless-connected AP.

Here’s what worked for me:

  1. Adopt all access points as per normal, while they’re wired.
  2. Enable wireless uplink in the controller site configuration.
  3. Enable wireless meshing on any APs which will be islands while they’re still wired to the network. (Device configuration → Config → Wireless uplinks → “Allow meshing to another access point”. That setting should not be enabled on any APs which will remain wired.)
  4. Then disconnect and relocate the wireless APs to their final locations.

Siri sass

Tuesday 13 March 2018

Oh fuck off. The one time Siri actually understands what I said, and performs the correct action, and I get this passive-agressing shit from her:


Monday 12 March 2018

Sticking this here because I can never remember the syntax for finding any file in my home directory with a name which contains either “foo” or “bar”:

find -E ~/ -iregex ".*(foo|bar).*"
  • -E: from the man page: “Interpret regular expressions followed by -regex and -iregex primaries as extended (modern) regular expressions rather than basic regular expressions (BRE’s)”.
  • ~/: search in home directory.
  • -iregex: case-insensitive regular expression.

(macOS 10.13.3)

Granny Mac's chocolate cake

Thursday 28 December 2017

  • 4oz soft margarine
  • 5oz caster sugar
  • 4oz self raising flour
  • 1 teaspoon baking powder
  • 1 tablespoon drinking chocolate or cocoa
  • 1 tablespoon milk
  • 2 eggs

Mix all together with electric mixer at medium speed. Put in two 7" tins greased. Bake for 30 minutes at 180C.

For the filling, mix 6oz icing sugar, 1oz drinking chocolate or cocoa, 2oz margarine, and a little splash of hot water.

NAB login

Friday 22 December 2017

Here’s the personal banking login page for NAB, one of the major banks in Australia:

Simple: a bit of branding, username and password fields, plus some decoration. It’s not a single-page webapp or anything, just a bog standard HTML form that results in a regular POST.

But man is it a trainwreck behind the scenes:

  • Hitting “Login” on NAB’s homepage opens the login page in a new, full screen, toolbar-less page. Try it on a 27-inch monitor…
  • Transfers over 1.3MB, including 10 individual CSS responses and 41 JavaScript responses (accounting for 1MB of the bandwidth). Forty one! For a dumb login page!
  • Sets a kick-in-the-pants away from 100 individual cookies

Oh, and they ask permission to track your physical location. I didn’t bother to find out whether NAB were asking or one of the dozens of other domains involved.

How does this happen? And how does it not get fixed? It’s been like this for years. I’d be ashamed of delivering something like this to customers, not because it really matters, but because of the negative message it sends about the level of care NAB puts into it’s customer-facing products.