Once I’d got my Raspberry Pi back up and running, one of the things I was desperate to try out was Pi-Hole, a DNS sinkhole capable of running even on my extremely old Pi. DNS sinkholes make it possible to block ads, trackers and malware at source, speeding up browsing and improving privacy. The particular advantage of a Pi-Hole is that it cannot operate at the network level, blocking ads automatically on every device that connects to a WiFi network. Well, it’s got to be worth a go, right?Continue reading Installing Pi-Hole
As documented a long, long time ago, I’ve got an old Raspberry Pi (B 1.2) kicking around. I wanted to try to teach it some new tricks, but once again my first challenge was getting it set up. This time, I don’t even have a TV I can plug its composite output into and I couldn’t be bothered to get HDMI working. I’m going to have to do this completely blind. Continue reading Raspberry Pi revisited
A few months ago bought a new computer, and, in the midst of all the swapping around hard disks, realised it would be an opportune moment to enable full-disk encryption.
I’m doing quite a lot of research at the moment into the history of Uganda (1890 to present). Unfortunately it is not always easy to find primary sources and documents online. This is my running list, published here in case it helps anyone else:
- Buganda Agreement (1900)
- Memorandum on Constitutional Development and Reform in Buganda, 17 March 1953
- Correspondence between Mutesa II and Sir Andrew Cohen (1953)
- Submissions to the Namirembe Conference (1954)
- Hancock Report (Cmd. 9320) (1954)
- Buganda Agreement (1955) [alternative OCR version]
- Report of the Constitutional Committee (the “Wild Report”) (1959)
- Buganda Agreement (October 1961)
The Uganda (Independence) Order in Council, 1962 and The Constitution of Uganda (excluding Schedules 1 to 6) (as in force, 31 December 1963)
- The Constitution of Uganda (1967)
- “Myths and Realities“, letter from Obote to a British newspaper (November 1968)
- Constitution (Amendment) Act 2005
- Constitution (Amendment) (No. 2) Act 2005
Unless something has gone horribly wrong, you’re reading this on a secure ‘https’ (SSL) connection — the content of the website is encrypted on its way to (and from) your PC.
Until even a couple of years ago, moving from an insecure ‘http’ to an ‘https’ connection would have involved considerable difficulty and at least some expense given I’m on a shared hosting platform (HostPresto). But today, it took me about fifteen minutes. Continue reading Moving to https
The first SSD I installed was into my laptop, back in April 2014. But since then I’ve shuffled them around, and I was back to having an old HDD. This was just about tolerable, but with the 240GB OCZ Trion 100 (a ‘meh’ quality SSD) available for under £40, and Windows 10 upgrades nagging, I thought I’d rectify the situation. Unfortunately, it didn’t exactly go well.
And so it came to pass that the Nexus 4, which was already a year old when I bought two years ago, started getting slow. I was hopefully initially that Android M (marshmallow), Google’s latest version of the operating system, would help: it apparently has a lower RAM footprint than L (lollipop). But unlike in the case of my Nexus 5 (which has already received the update) Google does not intend to ship M to Nexus 4s. Thus I had three three options: slug it out; hack a version of Android M onto it; or install a maintained fork that would (eventually) pick up the benefits of M. I chose the latter, going with the most popular fork: CyanogenMod, version 12.1 (a stable version 13 – i.e. one based on M – is expected around the New Year).
Installing CyanogenMod is not a walk in the park, even following the detailed instructions available on the CyanogenMod website and working out of Ubuntu. The following commands were useful (gapps.zip is an OpenGApps package and TWRP is, well, TWRP).
sudo apt-get install android-tools-adb android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery ~/Desktop/twrp.img
adb push ~/Desktop/cm.zip /sdcard/
adb push ~/Desktop/gapps.zip /sdcard/
Unfortunately the “stock” OpenGApps package doesn’t seem to fit in the system partition of a Nexus 4 (and hence use of Advanced Options is advisable). To ascertain how many Google Apps needed excluding, and to effect that change, the following commands were useful:
adb pull /sdcard/open_gapps_log.txt
adb push ~/Desktop/gapps-config.txt /sdcard/
As I mentioned in my previous blogpost, I am now the proud owner of a Pebble Time. This week I took the plunge and decided to make my own watchface in honour of xkcd #247 (“Factoring the time”). Pebble watchfaces have historically been written in the programming language C, although (given the relative unpopularity of C) the team there have also built a JavaScipt API, PebbleJS. I mean, I’ve never written any C before, but there’s no time like the present eh?
C turns out to be a particularly intensive language to work in, especially without the benefit of large utility libraries. For example, its array handling is poor, lacking push/pop functions, an accurate count function or indeed join/implode. The other thing I struggled with was performance enhancement. The major challenge when developing a watchface is battery conservation. Although Pebble provides some guidance covering this aspect, it remains vague (and difficult to even deduce through trial and error. For example, my initial design factorises the time afresh every minute using a blunt force recursive technique (given the maximum target is 2359, this is not too inefficient). But equally, I could store the pre-computed factorisations in a file. Would this be better or worse for battery conservation? Who knows.
The full code to the Factorise watchface is available from Github under the MIT licence.
About a fortnight ago I added at Pebble Time to my collection of gadgetry. It’s one of the more basic second gen smartwatches, with a 64-colour e-ink screen rather than a touchscreen, as well as a microphone. Most of its functionality is derived from a bluetooth connection to a mobile phone. To buy one in the shops will set you back around £200. Continue reading Pebble Time: First Thoughts
This week’s task was move by existing my old SSD from my laptop to my gaming desktop, which I’ve had since September and am otherwise very happy with — certainly, the AMD FX-6300 Six Core CPU + Radeon R9 270X can handle most things thrown at them, with the unusual exception of The Sims 3 (no idea why the Sims is an exception; maybe something to do with the age of the game). Continue reading SSD transfer (again)