I’ve recently started a new side project called Gay Places, a curated guide to gay bars, clubs, and queer spaces around the world.
The aim is to build something quieter, more considered, and more useful than the usual listings, especially for people exploring a city through its gay scene.
It’s early days, but I’m excited to see where it goes. I’d love to hear in the comments if you have any ideas or suggestions for where to take this!
]]>
Pi-hole is a free ad blocker for your whole home network. It works as your network’s DNS server, the service your devices use to look up websites. When a phone, laptop or smart TV tries to load an ad or a tracker, Pi-hole blocks the request before anything is downloaded. Ads disappear on every device, even inside apps, without installing anything on them.
Pi-hole was designed for the Raspberry Pi, but thanks to Docker you can run it on a Windows PC you already own.
Back in 2020 I wrote a step-by-step guide to installing Pi-hole on Windows 10. I definitely wasn’t prepared for the response! The post has had hundreds of thousands of visits, and heaps of helpful comments that helped me refine the instructions. I wrote it as a go-to guide for myself, and somehow it became one for a whole community of tinkerers. This Windows 11 version followed in 2022 when I moved to a new PC, and I keep it up to date as Pi-hole, Docker and Windows change.
Updated October 2026 for Pi-hole v6. Pi-hole v6 changed how passwords and settings work in Docker, so older instructions (including earlier versions of this guide) no longer work. If you can’t log in to Pi-hole, jump to the fix.
If you’re wondering whether it’s worth running Pi-hole on Windows, or whether you should just buy a Raspberry Pi, take a look at my review of living with Pi-hole on Windows.
Jump to: Step-by-step guide · Updating Pi-hole · Moving from an older version of this guide · Troubleshooting · FAQs
Before you start, run Windows Update so your PC is fully up to date. Then stop your PC from going to sleep. Go to Settings > System > Power & battery (just Power on some desktop PCs) and set your PC to never sleep when it’s plugged in. If your PC sleeps, so does Pi-hole, and the devices on your network won’t be able to load websites.
Docker uses the Windows Subsystem for Linux (WSL) to run Linux software, like Pi-hole, on Windows. Right-click the Start button, choose Terminal (Admin), and run:
wsl --install --no-distribution
When it’s finished, restart your PC.
Every device on your network needs to be able to find Pi-hole, so your PC needs an IP address that never changes.
ipconfig. Under your Wi-Fi or Ethernet adapter (ignore any “vEthernet” entries), make a note of your IPv4 Address, Subnet Mask and Default Gateway (this is your router’s address).192.168.1.23, use 192.168.1.200.ipconfig. The subnet mask is usually 255.255.255.0.1.1.1.1 (Cloudflare’s DNS service). This keeps your PC online if Pi-hole isn’t running.
Tip: if you’re comfortable with your router’s settings, you can reserve an IP address for your PC there instead (often called DHCP reservation or address reservation). Either approach works.
Pi-hole’s settings live in a small text file called docker-compose.yml. Docker reads this file to set up Pi-hole for you, and it makes updating Pi-hole much easier later on.
Open Terminal (you don’t need admin this time) and run these commands to create a folder for Pi-hole and a new file inside it:
mkdir C:\pihole
cd C:\pihole
notepad docker-compose.yml
Notepad will ask whether you want to create a new file. Click Yes, then copy and paste the following into Notepad:
services:
pihole:
container_name: pihole
image: pihole/pihole:latest
ports:
# DNS: how your devices talk to Pi-hole
- "53:53/tcp"
- "53:53/udp"
# Pi-hole's web dashboard
- "80:80/tcp"
- "443:443/tcp"
environment:
# Your timezone
TZ: 'Europe/London'
# The password you'll use to log in to the dashboard
FTLCONF_webserver_api_password: 'choose-a-password'
# Where Pi-hole sends the requests it doesn't block (Cloudflare)
FTLCONF_dns_upstreams: '1.1.1.1;1.0.0.1'
# Lets the other devices on your network use Pi-hole
FTLCONF_dns_listeningMode: 'ALL'
volumes:
# Keeps your settings and blocklists when you update Pi-hole
- pihole_data:/etc/pihole
cap_add:
# Lets Pi-hole keep its clock accurate and run smoothly
- SYS_TIME
- SYS_NICE
restart: unless-stopped
volumes:
pihole_data:
You will need to change:
choose-a-password: the password you’ll use to log in to Pi-hole. Keep the quotes around it, and avoid using $ or ' in your password, as they confuse Docker.Europe/London: your timezone, from this list of time zones. For example, America/New_York or Australia/Sydney.Leave the spaces at the start of each line exactly as they are, because Docker is fussy about them. Then save the file (Ctrl + S) and close Notepad.
You can leave everything else as it is. If you’d prefer a different DNS provider, you can swap the Cloudflare addresses for another one, such as Quad9 (9.9.9.9;149.112.112.112). There are also lots of other settings you can add if you want to customise Pi-hole.
Good to know: anything set in this file is locked in Pi-hole’s dashboard. To change it later, edit the file and run docker compose up -d again.
Back in Terminal, in the C:\pihole folder, run:
docker compose up -d
Docker will download Pi-hole and start it. The first time, this takes a minute or two. When it’s done, you’ll see that the pihole container has started, and it’ll also appear under Containers in Docker Desktop.
You’ll probably see a Windows Firewall pop-up for Docker Desktop Backend. Make sure Private networks is ticked and click Allow access. If you skip this, the other devices on your network won’t be able to reach Pi-hole.
Open your web browser and go to http://localhost/admin. Log in with the password you chose in Step 4. If the page doesn’t load straight away, give Pi-hole another minute to finish starting up.
From the dashboard you can see how many ads and trackers have been blocked, manage your blocklists, and allow or block individual websites. To open it from another device on your network, use your PC’s IP address instead, for example http://192.168.1.200/admin.
The final step is to tell your router to use Pi-hole as the DNS server for your network. This gives every device on your network Pi-hole’s ad blocking magic, with nothing to install.
Log in to your router’s settings page. You can usually do this by typing your Default Gateway address from Step 3 into your browser. Find the DNS server setting (often under the LAN or DHCP settings) and change it to your PC’s IP address, for example 192.168.1.200.
Every router is different, so if you get stuck, search for your router’s model name and “change DNS server”. If your router doesn’t let you change it, see the FAQs.
Devices pick up the change when they next reconnect, so restart them or turn their Wi-Fi off and on again.
Browse a few websites on your phone or laptop. Ads should be gone, and in the Pi-hole dashboard you’ll see Queries Blocked start to climb.
For a quick test, run this in Terminal, using your PC’s IP address:
nslookup doubleclick.net 192.168.1.200
If Pi-hole is working, the answer will be 0.0.0.0. That’s Pi-hole blocking one of the internet’s biggest ad servers.
Congratulations! At this point you should have a Pi-hole protected home. If something isn’t working, check the troubleshooting tips below or leave a comment.
A new version of Pi-hole comes out every month or so. You’ll see a message at the bottom of the dashboard when an update is available. To update, open Terminal and run:
cd C:\pihole
docker compose pull
docker compose up -d
Docker downloads the latest version and swaps it in. Your settings, password and blocklists are kept, because they’re stored separately from Pi-hole itself. To free up disk space afterwards, run docker image prune and type y to delete the old version.
Pi-hole’s developers recommend updating by hand rather than automatically, as occasionally an update needs extra changes. It’s worth glancing at the release notes before you update.
If you set up Pi-hole using an earlier version of this guide (or my Windows 10 guide), you’re probably running Pi-hole v5. The docker run command in those guides uses settings like WEBPASSWORD that Pi-hole v6 no longer understands. It also didn’t save your settings outside the container. The easiest way to move to v6 is to back up your settings, then start fresh:
.tar.gz file with your blocklists and your allowed and blocked domains.docker rm -f pihole in Terminal.This is usually caused by older set-up instructions. Before Pi-hole v6, you set the password with WEBPASSWORD. Pi-hole v6 ignores that setting and creates a random password instead.
To find the random password, open Docker Desktop, click Containers and then pihole, open the Logs tab, and search for “random password”. Or run this in Terminal:
docker logs pihole | findstr /i password
To choose your own password instead, run the following and follow the prompts:
docker exec -it pihole pihole setpassword
This only works if you haven’t set a password in a docker-compose.yml file. If you followed this guide, change the password in the file instead and run docker compose up -d again. If you’re still on the old set-up, I’d recommend moving to the new one.
Pi-hole needs port 53 (for DNS) and port 80 (for the dashboard) to be free on your PC.
docker-compose.yml file, change "80:80/tcp" to "8080:80/tcp", run docker compose up -d, and use http://localhost:8080/admin instead. If port 443 is the problem, you can delete the "443:443/tcp" line altogether."192.168.1.200:53:53/tcp" and "192.168.1.200:53:53/udp". Then run docker compose up -d again.This is usually Windows Firewall. Check that your network is set to Private network (Step 3). Then search the Start menu for Allow an app through Windows Firewall, click Change settings, and make sure Docker Desktop Backend is ticked under Private.
Make sure Start Docker Desktop when you sign in to your computer is turned on (Step 2). Docker Desktop only starts once you’ve signed in to Windows, so if Windows restarts on its own for an update, Pi-hole stays off until you sign in again.
To avoid this, go to Settings > Accounts > Sign-in options and turn on Use my sign-in info to automatically finish setting up after an update. Windows will then sign you back in after an update and lock the screen, which should give Docker Desktop the chance to start.
Make sure you’re in the right folder (cd C:\pihole) and that the file is called exactly docker-compose.yml. Run dir to see what’s in the folder. If the file has been saved as docker-compose.yml.txt, rename it with ren docker-compose.yml.txt docker-compose.yml.
If Docker says WSL needs updating, run wsl --update in Terminal (Admin) and then reopen Docker Desktop. If it says virtualisation isn’t supported, you’ll need to turn it on in your PC’s BIOS. It’s usually called Intel VT-x, AMD-V or SVM.
Not reliably. YouTube serves its video ads from the same servers as the videos themselves, so Pi-hole can’t block one without breaking the other. The same goes for sponsored posts on sites like Facebook and Instagram. A browser ad blocker is still the best option for those.
Yes, for personal use, education and non-commercial open source projects. It’s also free for small businesses with fewer than 250 employees and less than $10 million in annual revenue. Larger businesses need a paid subscription.
If your router only uses Pi-hole for DNS, the devices on your network won’t be able to load websites while your PC is off. Many routers let you add a second DNS server, like 1.1.1.1, which keeps the internet working when Pi-hole is down. The catch is that devices will sometimes use the backup even when Pi-hole is running, so a few ads will slip through. If you want Pi-hole to be truly always on, a Raspberry Pi is a great option.
Some routers from internet providers lock this setting. You can still use Pi-hole by setting the DNS server on each device instead. On Windows, it’s the DNS server assignment setting, next to the IP assignment setting from Step 3. Pi-hole can also act as your network’s DHCP server, but unfortunately that doesn’t work with Docker Desktop on Windows.
No. When I first set this up, my PC was connected over Wi-Fi and it worked really well. Ethernet is a little faster and more reliable though, so use it if you can.
Docker Desktop passes network traffic through to Pi-hole on your devices’ behalf, so Pi-hole usually sees every request as coming from Docker. Ad blocking still works on every device; you just won’t get a breakdown per device. If that matters to you, you’ll need to run Pi-hole on a Raspberry Pi or another Linux machine.
docker run command instead of Docker Compose?Yes. This PowerShell command sets up Pi-hole with the same settings as the file in Step 4:
docker run -d --name pihole -p 53:53/tcp -p 53:53/udp -p 80:80/tcp -p 443:443/tcp -e "TZ=Europe/London" -e "FTLCONF_webserver_api_password=choose-a-password" -e "FTLCONF_dns_upstreams=1.1.1.1;1.0.0.1" -e "FTLCONF_dns_listeningMode=ALL" -v pihole_data:/etc/pihole --cap-add SYS_TIME --cap-add SYS_NICE --restart unless-stopped pihole/pihole:latest
I’d still recommend Docker Compose though, as your settings are saved in a file, which makes updating much simpler.
Yes. On a Mac, install Docker Desktop for Mac and use the same docker-compose.yml file. On Windows 10, the Docker steps are the same, although Microsoft no longer supports Windows 10, so I’d recommend upgrading if you can.
Docker is easier to set up and maintain. With a virtual machine you need to install, configure and update Linux yourself. With Docker, Pi-hole runs in its own isolated container, and all of your settings live in one file, so you can update or rebuild it in a couple of minutes.
I’ll keep updating this guide as Pi-hole, Docker and Windows change. If you run into problems, or spot something that’s out of date, let me know in the comments!
]]>
Ever since becoming a Product Designer I’ve been on a gradual journey of realising that being open and transparent with your work is almost always better. At first working in an open and transparent fashion felt counter-intuitive.
Don’t designers need to lock themselves away in a basement and wait for inspiration to strike? In most cases this couldn’t be further from the truth. In my experience, the more (and earlier) cycles of feedback and input you get on any project almost always result in a tighter, more useful end product.
This is an article I wrote recently for The Org exploring the benefits of adopting a transparent design process.
Link - How transparency helps us become better designers (Andrew Denty on The Org Insights)
]]>
I love Audible.
It’s a fantastic way to absorb books. A few years ago I had a daily cycle commute across Copenhagen which meant I was cycling for almost an hour every day. During this time Audible helped me use this time to devour books.
However since then I’ve moved apartments and jobs. I still find Audible valuable, I just can’t get through audiobooks in the way that I used to. I’ve often found my Audible credits are building up faster than I can get through audiobooks.
Updated October 2026: Audible has changed a lot since I first wrote this post in 2020, so I’ve rewritten it. Pausing is now much easier, and Audible UK has changed how credits work.
When I first wrote this post, there was one thing I didn’t like about Audible: the dark patterns it used to keep people from leaving. In fact I’d argue they were downright nefarious. The option to pause was buried at the very end of the cancellation process, and at every step Audible’s design did its best to obscure your choices. You were repeatedly told that if you cancelled, you’d lose your valuable credits. You can see what it looked like further down.
The good news is that Audible has since moved the pause option somewhere you can actually find it. There’s now a Pause membership link on your account page, and you can pause in the Audible app too. You don’t need to go anywhere near the cancellation process.
That’s it. While your membership is paused you won’t be charged and you won’t get any new credits, but you can still spend the credits you have and listen to everything you own.
If you change your mind, you can resume at any time. On the website, select Resume membership in your account details. In the app, go to Profile, then Account, then Resume membership. Payments start again from your next billing date.
The rules vary a little from country to country, so if you’re not sure, check Audible’s help page for your country, for example Audible UK or Audible US.
This is the part that has changed the most since 2020.
In the UK, Audible credits no longer expire after 12 months. Instead, there’s a limit to how many you can save up. On the one-credit-a-month plan it’s 6 credits, or 12 if you get two credits a month. If you’re already at the limit when your next payment goes through, you lose a credit, so you end up paying for a credit you can’t keep. If your credits are piling up, that’s the perfect time to pause.
In the US and Canada, credits still expire 12 months after they’re issued, and pausing doesn’t stop the clock. If you have credits that are close to expiring, make sure you spend them.
Wherever you are, if you cancel your membership, you lose any credits you haven’t spent. Anything you’ve already bought with your credits stays in your library, even after you cancel.
If you have an annual Audible plan, you won’t be able to pause your membership. This is because you’ve effectively paid for the whole year upfront. However you can cancel your membership and you’ll still be able to keep and access any audiobooks in your library, even without a membership. Just make sure you spend your credits before you cancel, as you’ll lose any you haven’t used.
For the record, here’s what pausing Audible looked like in 2020. Please don’t follow these steps today. Use the Pause membership link instead.
Back then there was no pause link. Instead, you had to select Cancel membership and work your way through Audible’s cancellation process. The first page warned that if you cancelled, you’d lose your credits. Your credits were still perfectly safe at this point, but the page was designed to make you think twice.
Next came a survey asking why you were cancelling, with a Cancel Membership button that felt very final.
Only then, on the very last page, were you finally offered the option to pause, alongside a couple of offers to tempt you to stay.
If you have a few credits to use up and would like some book recommendations, these are some books I’ve thoroughly enjoyed on Audible:
This week as a side project I decided to recreate this year’s October Apple event invite in Figma.
Every Apple event has its own particular style with beautifully crafted graphics specific to that event. This October’s event was announced yesterday with an invite including almost luminous overlapping circles. Personally, this is one of my favourites; it reminds me of looking up into a Louis Poulsen PH5 lamp . This got me wondering what the actual inspiration was, and how it was created.
I then decided to have a go at recreating it this as one area I’d like to improve my skills is in creating illustrations. Most of my work is creating web pages and user interfaces, but rarely do I try something a little more whimsical.
Yep, I know Figma is absolutely the wrong tool to use for this task, but I really love how versatile Figma is, and I’m pretty comfortable using it as I use it for pretty much everything from flow charts to high fidelity interface mock-ups at work.
I wasn’t sure how to get started, but through the process of trial and error I’ve created a reasonably realistic knock-off of Apple’s original. Apple, please don’t sue me :-)
If you’re interested you’re more than welcome to take a look at the original in Figma. I’d love to know how it could be improved - there are certainly some areas where the lighting effects are not quite right.
View or fork the project in Figma
Let me know in the comments if you have any suggestions or tips for ways of improving it.
]]>
Here’s a lesson on designing for edge cases that I learned while travelling around Greece this summer.
We were lucky enough to be able to hike in the northern mountainous region of Zagoria and then spend some time on the island of the Milos where we mostly ate too much and sat on the beach. Either way, this post is not about my holiday, but about a usability edge case that it exposed me to…
Most of the islands and remote areas in Greece have very patchy reception. For the most part, seeing ‘3G’ on your phone essentially means no data, and ‘4G’ means slow, unreliable data. Eventually, you may be able to load a light web page, but this is mostly going to be a torturous experience.
Luckily before we travelled, I downloaded everything I would need. Mostly audiobooks, maps podcasts and music. Accessing content with limited internet connectivity has clearly been considered by most app developers. Or so I thought…
In reality, it turns out the way many app developers are approaching cached and offline content is broken.
For example, Google maps when opened in an area with crappy internet connectivity does not display the cached (or manually downloaded) map content, but instead displays a super, low-resolution version of the map. I assume this is because it is attempting to download a full resolution, up to date version of the content. While it’s good to show up to date information such as traffic, in a case where I needed to quickly glance at a map waiting for Google Maps to repeatedly attempt to access a map from Google’s servers which already exists on my device is the absolute worse experience.
In many instances, the only way I could get Google Maps to work was by switching to Flight Mode in order to force the app to use downloaded maps.
This isn’t an isolated instance. For example, Audible exhibits the same behaviour. Before playing a downloaded audiobook the app first attempts to connect to Audible - possibly to check if there’s an updated play location. If the app can’t connect to Audible it will either show an error message stating the download content is corrupt (a bug?), or simply just not play the content. Again, the only workaround seems to be to briefly enter Flight Mode and be truly offline
Obviously, not all apps are this bad at handling flaky connections. Spotify for example reliably allows access to and plays downloaded content immediately on an unreliable connection. Netflix also mostly gets this right provided you launch downloaded content from the downloads view in the iOS app.
I think many of these issues could be avoided if when designing new functionality, we as designers spend a little more time considering the edge cases. For example, offline usage, take the time to really understand all of the situations your users will be in when using your product.
In practice, this means broadening the definition of “offline” to include crappy internet connections. The reason the user downloaded is likely because they knew they would have limited internet access, or possibly wanted to reduce their data usage. In this case, prioritise offline content until a working connection can be established. If the content is downloaded, let the user use it.
]]>
Forget skeuomorphism, or even the newly coined neumorphism.
macOS Big Sur is flatter than ever.
In the last few weeks there have been a lot of suggestions that this is the start of a new “fun” era of visual design and that Apple is returning to skeuomorphism, or even a new thing called neumorphism. Neumorphism is a design trend that focuses on creating an impression of a realistic 3D environment using shadow and lighting effects.
The times may well be changing, but in my view we are not returning to an age of textured writing paper and stitched leather. This is why.
Since the unveiling of macOS Big Sur a lot has been made of its new iOS shaped icon set. Everyone seems to either love or hate the new icons.
Don’t be mislead by the icons - macOS icons have always been richer and more detailed than iOS icons. They have also used shadows and to create a sense of depth. In my view desktop interfaces are often more detailed as desktop users tend to use them for longer periods of undistracted time compared to mobile devices. Therefore adding more detail and richness is appropriate. In short, for as long as technology has allowed, macOS icons have been rich, detailed and realistic looking. Here are a selection of macOS Catalina’s icons to illustrate this:
The new icon set in Big Sur is simply a convergence of the existing highly detailed macOS icons with the consistent shape of iOS icons. During the WWDC 20 keynote, Alan Dye, Apples VP of Human Interface explained the rationale behind the new icons:
“We wanted consistency throughout the ecosystem so users can move fluidly between their Apple devices, but we also love that Mac icons have a deep history and a distinct look and feel. So we retained many of the highly crafted details and th playful elements that make Mac icons unique”
It’s also worth remembering that in many places the icons in macOS are simpler than before as Apple is porting its unified language of symbols from iOS. This means that in many places, existing detailed icons have become simple, monochrome 2D icons.
This may surprise a few people, but if you look at the user interfaces in macOS Big Sur and compare it to the current release Catalina you won’t see richer shading and detailing. Also, while macOS Big Sur uses transparency, and shadows to create the impression of layers in the UI, this isn’t a new thing for macOS.
Actually, you’ll see a lot of the detail, texture and shadows have been removed. As a whole, macOS Big Sur’s interface is cleaner and more minimalist than ever. One of the aspects I’ve noticed most is there tends to be less contrast between UI elements. Apple has also completely dropped the aluminium inspired window chromes which can be traced back to Quicktime in the 1990s.
Take for example the notes app. The faux-paper texture has finally been completely removed. The toolbar buttons no longer have containers and there is no background separator between the toolbar and writing area.
This is not a new paradigm in visual design, but a shift towards unification between platforms. There is increasingly less separation between iOS and macOS. Both in hardware with Apple’s switch to an all ARM architecture and software where iPhones and iPads can now do many of the tasks once reserved for desktop computing.
In many ways the interface changes in macOS Big Sur reflect this transition. The iOS glyph icon set, the removal of distinct buttons and increasingly rounded corners. Apple has clearly been asking why interface elements on an iPad and a Mac should look different, and come to the conclusion there’s no longer a good reason for this.
On the topic of conversion, one interesting question will be how much further this transition goes. Can we expect to see touch enabled laptops? Dual booting iPads? iPhones with docking stations?
As a designer I’ve often found the trend towards flat, minimalist design frustrating. I pretty much always have an urge to add little embellishments or extra layers to work. I then subsequently almost always end up removing them. Either due to what I’ve learned when testing the design with users, or just realising that these extra details often end up detracting from the bigger picture.
This doesn’t mean there’s no value in intricate detailing. If you are a designer and you can inject a fun details into your work in a way which delights and enriches your users lives then I implore you to do this. I just don’t think that macOS Big Sur is the signal we’ve all been waiting for to bring out those shadows, textures and bevels.
]]>
This post is an attempt to provide a visual comparison of pretty dramatic UI changes between macOS Catalina and Big Sur.
Why did I end up doing this? Well, this week I installed the developer beta of macOS Big Sur as I was curious what impact the new UI would have on the app I currently design. I wanted to make sure my team was ahead of any coming changes as we were burned by changes in last year’s release of Catalina.
I found myself taking lots of screenshots to try and track the changes and thought this might be worth sharing. I decided to carry out a quick catalogue of the UI changes as this may be helpful to other people getting ready for macOS Big Sur.
All of the screenshots below are taken on a default install of macOS and the Catalina version is always on the left. I made a conscious effort not to resize any windows or change any default settings. I haven’t captured everything, but it is a good taste of the changes so far.
At first glance macOS is a lot more colourful with, and the biggest obvious change is the bright, slightly more cartoonish iOS shaped icons. Everything is more rounded and it feels like everything has gotten a little bigger. Could this be the first hint that macOS is preparing for touch support in the future? One interesting tidbit, is that even though the icons are based around the capsule shape, many of them (like Contacts, or Preview) have elements which protrude from them giving an extra feeling of depth.
Finder sees some significant changes. Of all the places I think Apple needs to get the new UI spot on, is Finder. Overall the default size of Finder seems to be bigger in macOS Big Sur.
One thing that struck me at this point is that Finder looks a mess with many of the more advanced features enabled. The bottom screenshot shows Finder with a Path Bar, Status Bar and multiple tabs. To me, it seems like the design team have not yet been able to find a way to elegantly integrate these elements into the iOS inspired UI.
One final thing to note is that in Finder the search bar at the top right has been replaced with a search icon that expands when clicked. This change seems a little inconsistent as it’s not made it to Preview. I can guarantee this will result in fewer people discovering Finder’s Spotlight search goodness.
Preferences sees quite a lot of change in some areas. The Dock preferences pane has become “Dock and Menu Bar” and now integrates controls for the new macOS control center. It uses a nicely integrated sidebar to manage different categories.
It’s a shame that this sidebar hasn’t yet made it to other parts of the preferences UI with Network and Notifications still using a very old looking sidebar.
One aspect of preferences that has been quite controversial (on Twitter at least) is the new icons. I’m going to hold off judgement for now as they don’t yet look finished. For example, the Notifications icon does not even support retina displays.
You’ll notice that the Startup Disk pane uses apples new dialog (or sheet) UI. This is quite a departure from the existing sheet drop-down - it feels much more iOS-like.
This is one of the areas where macOS has changed the most. It’s also difficult to take decent screenshots of both of these. Control Center looks like it’s been badly photocopied and the Notification Center in Catalina has a bug whereby it renders at double it’s normal width.
What was obvious within a few minutes of use was that the Control Center is a massive improvement on Catalina’s row of scattered Menu bar icons. The updated WiFi menu is also a massive improvement, as the old list could easily be overwhelming with the number of WiFi networks displayed.
I’m less convinced that the Notification Center is easier to use though. Now it has no background, there is less to separate a list of notifications from my messy desktop!
I will try and get better screenshots for this section and update it in the near future.
The biggest news in Notes is that after years, the Skeuomorphic paper texture has finally been retired!
Music and Podcasts were brand new last year with the release of Catalina. It’s obvious that the new UI has been planned for a while as Apple Music and Podcasts are mostly indistinguishable from their initial Catalina release. For example both apps already include the new full height sidebar.
For me this illustrates a bigger point that Steven Sinofsky recently made on Twitter - that Apple is executing a meticulous multi-year strategy.
One area where changes are evident are is in preferences windows. Both apps make use of Apple’s new accent colour and new glyph icon library.
It was impossible to go into depth with every single bundled app. On the whole, the updates to Maps, Books and Mail all look solid with extensive use of the new sidebar.
Both Activity Monitor and Disk Utility have received a new style toolbar. As with Finder, there are no longer any rows meaning all elements are at the same level. On first impressions, I feel this is a little visually confusing and makes it harder to scan. The search field also loses a lot of its contrast.
Unsurprisingly Terminal is almost unchanged.
On the subject of unchanged apps, there were a number of other apps that are so far relatively unchanged.
Siri in macOS Big Sur shows no apparent changes. I think this is a little strange considering the overhaul Siri is receiving in iOS 14. There don’t even seem to be any radius changes to the borders.
The most extreme case of no change is Stickies. It’s completely identical between both releases. What’s more, I don’t think it’s changed much since MacOS 9 judging from its weird, retro controls.
Boot Camp is also practically unchanged, although this is perhaps unsurprising given Apple’s move to Apple Silicon, so presumably Boot Camp’s days are numbered. It did receive a new icon though.
Overall, the UI changes in macOS aren’t as dramatic as I was expecting. Big Sur’s new UI feels like a largely incremental set of changes to make macOS feel more coherent with iOS and iPad OS. Even if there are a few teething issues and the look is a little jarring at first, this has to be a good thing in the long-term.
Having said that, Apple still has a vast amount of work to do to perfect the new macOS UI. It unsurprising as this is the first developer beta, but there are still many rough edges.
I hope in the long term they focus on creating consistent patterns: for example for the first launch experience of apps. Right now there are several different layouts and approaches to this UI. I also hope Apple don’t leave pro users behind. Right now some of the less frequently used UI elements such as status bars and path bars look a little unloved. They don’t feel well integrated into the UI and in some cases lack visual separation.
If you’re interested in reading even more about the design changes in macOS Big Sur, Cult of Mac have a comprehensive overview of the new icons.
]]>
I’ve been running Pi-hole on my Windows 10 PC for over four months now. When I initially installed Pi-hole on my PC I wrote a short set-up guide. I did this purely so I could remember the steps I took to get it working on Windows 10, but was completely blown away by the reception. This blog which normally gets around twenty visits a week started to get thousands of visits, all to the post about installing Pi-hole on Windows 10.
It’s clear that there’s a lot of interest in this topic, so I thought it was a good time to share some of my day-to-day experiences of running Pi-hole on Windows 10 and review whether it’s actually worth it. I’ll explore some of the areas that running Pi-hole on Windows 10 excels and then go into some detail of some of the problems I encountered. It’s also worth mentioning that much of this is also applicable if you’re running Pi-hole on a Raspberry Pi, Linux PC or Mac.
There’s not really much to say about Pi-hole’s ability to block ads other than it’s utterly excellent. It just works. Web browsing with Pi-hole is a faster, less cluttered, cleaner experience. I won’t be going back.
Having said that, Ad blocking is arguably a commoditised feature at this point and this wasn’t my main reason for switching to Pi-hole. For me the biggest appeal of Pi-hole was it’s ability to bypass annoying ad blocker detection. I’d been using a browser based ad blocker, AdblockPlus for years. It was reasonably effective and did a good job of propagating across my different devices because of Google Chrome’s useful (or creepy) sync feature which ports your favourites, history and ad-ons to wherever you’re signed in. The biggest drawback however was the increase in annoying “Ad blocker detected” messages displayed on websites. While Adblock plus makes it pretty straightforward to disable the ad blocking for specific websites, it quickly becomes frustrating. Pi-hole makes this a thing of the past.
In my experience, Pi-hole is 100% effective at bypassing Ad blocker detection. I’ve seen absolutely no “Ad blocker detected” pop-ups when browsing the since switching to Pi-hole.
Below is an example of the same page when viewed using Pi-hole (left) and AdblockerPlus (right):
The other main advantage of Pi-hole over other ad blockers is it’s ability to work on all devices on your network. While Android and iOS now support ad blocking functionality through apps and ad-ons, in my experience it’s always been a clunky experience that doesn’t work everywhere. Also, with this approach you’re effectively trusting a 3rd party commercial app with all of your browsing data.
For network-wide ad blocking Pi-hole wins here hands-down as it requires no extra apps, plugins or software. It works on every single device on your network, and you own and manage your own data through the Pi-hole Admin console. This is the perfect segway to talk about what you can do with that data…
There was one unexpected benefit of using Pi-hole, it helped me identify devices and apps on my network which were invading my privacy. The Pi-hole admin dashboard provides detailed statistics of the traffic flowing through your network which makes it easy to see what is calling home on your network. If this seems like a little too much for you, you can also disable this functionality and tell Pi-hole not to do any logging.
In my case the Pi-hole admin dashboard made it clear to see that our Samsung TV was communicating almost non-stop with Samsung owned domains all day and night. This led me to investigate and it turns out Smart TVs are notorious for collecting data about what you watch with a technology called automatic content recognition, or ACR . I could find no obvious way of disabling this, and the TV itself didn’t seem to include any privacy settings, so I took the nuclear option of simply blocking its network access. We don’t use the in-built apps to watch tv, so this caused no inconvenience at all.
If you’re interested in learning more about how Smart TVs are increasingly spying on their users, Cheddar has produced a really informative video on the subject:
How does Pi-hole perform as a DNS server? It is effectively replacing your DNS server after all. Although could run a ton of benchmarks (and I may actually get round to this if there’s enough interest), I think real world, subjective experience may actually be a better judge in this case.
In my experience using the internet has honestly felt a little faster. I haven’t noticed any awkward DNS resolution hangs when loading websites. I’m talking about the kind of delay where you enter a URL, nothing happens for five seconds and then the page loads instantly. This can happen when a DNS server is slow to respond, or cannot be reached.
Overall I’ve been shocked at how well Pi-hole has functioned as a DNS server. In fact when I first set it up, I was skeptical that it was actually working because it was so fast. This even more surprising given that I run Pi-hole on a PC connected to my network via WiFi. If you’re a professional, unlike me you’ll run this on a wired connection!
What about Windows 10 performance, does running Pi-hole on docker affect my PC’s performance? In my experience, the impact on performance is very modest. My machine is a relatively low end 2017 Intel NUC with a dual core i5 and a paltry 8GB of ram. Running docker and Pi-hole it still runs smoothly and is completely useable for everything I’d normally use it for such as web browsing, designing with Figma, running a Plex server and playing a few games on Steam. The only impact I have noticed, is that running Docker at startup causes the machine to be a bit less responsive for the first few minutes after boot. This is hardly surprising however as Docker is effectively booting a second OS using Hyper-V. I suspect if you have a more powerful machine with more memory and more cores you won’t even notice this.
One of my concerns going into this process was Pi-hole on Docker would be complicated to maintain and update. I think this is partially true as there is no way of automatically updating to new versions. This biggest challenge here was working out how it is done as the process of updating to new versions of Pi-hole on docker doesn’t seem to be widely documented. However if you follow these steps documented in my guide to setting up Pi-hole on Windows 10, it’s not too complicated or time-consuming. It’s also worth pointing out that although Pi-hole is actively maintained, there haven’t been a deluge updates, so you won’t need to do this too frequently. Link How to update Pi-hole on Docker
Overall I found Pi-hole running on Windows 10 to be incredibly reliable. It worked for weeks at a time without needing any attention, however there are a few things to be aware of.
Windows 10 is infamous for its updates. Whether you think this is a good, or a bad thing, the reality is that any Windows 10 PC will restart over night on a relatively frequent basis. In this case, I’d get up in the morning and find my internet wasn’t working.
It is possible to get round this problem however as Microsoft supports a method for automatically logging on to Windows 10. The obvious trade-off with this approach is your PC is no longer secure. Anyone can effectively access your PC by simply turning it off and on again. If this wasn’t bad enough, your password is stored in the Windows registry as plain text. I haven’t enabled this and have opted to put up with the minor inconvenience of occasionally signing into your PC again. I recommend using Windows Remote Desktop to do this. This lets me sign in from whichever device I’m using at the time.
This may sound kind of obvious, but Google Shopping and any paid for link on Google will no longer work. This is also the case for services such as Google Analytics, or other B2B analytics services. Although this is exactly what I expected, I often found it surprising as I tend to forget that Pi-hole is running in the background. This can be kind of frustrating. but I have a workaround. Using a VPN service. I use a VPN (Express VPN) quite frequently as I’m a Brit living in Denmark and it’s really convenient to be able to visit UK only websites.
As I mentioned previously, I use a VPN. One thing I noticed was that if I connected to the VPN on my Windows 10 machine (the same machine which is running Pi-hole) the rest of the devices in my house partially lose internet connectivity. This is because the VPN client makes the Pi-hole DNS server unreachable to other devices on the local network. I found this a little surprising as I’d specified a backup DNS server (Cloudflare’s 1111 service) on my router, and in the case my Pi-hole DNS server is not responding, it should switch to the secondary server. I didn’t investigate this too thoroughly and found the easiest way to get round this is to stop simply stop using the VPN directly on your PC.
There are two areas where I’ve struggled to get Pi-hole on Docker to work the way I hoped it would.
The first is blocking Youtube ads. Before installing Pi-hole I’d heard rumours that it could be used to block those annoying mid-video ads in Youtube, however this doesn’t seem to be the case. Pi-hole will block the banner ads which sometimes appear in embedded ads, but is currently unable to block video ads on Youtube. If I am able to find a way of blocking these, I’ll write about it.
The second thing I’ve not managed to do with Pi-hole on docker is maintain customised whitelists or blacklists in the Pi-hole docker configuration. This is useful if there are certain websites you wish to allow. For example, I don’t mind certain adverts such as listings on Google Shopping when I’m searching for a product to purchase. Even though you can whitelist certain domains with Pi-hole, this is not advisable if you are running Pi-hole on docker as each time you update to a new version, your whitelist configuration is lost. If anyone has successfully configured whitelists in via the docker command, I’d love to hear how!
My experience over the past 4 months has completely reinforced my belief that Pi-hole is hands-down, the best ad blocker available. Its ad blocking is unrivalled, it speeds up your web browsing experience across all of your devices and doesn’t require you to install any additional software on those devices.
But, what about running Pi-hole on Docker on a Windows 10 PC? In reflection, I’d definitely recommend turning any spare PC on your network into a Pi-hole server. It makes the internet a slightly nicer place and isn’t too much of a hassle to maintain even if it does have a few niggles. It’s also a great way of evaluating whether Pi-hole is right for you (and everyone else in your household) before purchasing a Raspberry Pi.
If it works out, then I’d recommend purchasing a Raspberry Pi to run it on as you’ll have a dedicated device running your Pi-hole server, easier updates and the ability to maintain custom whitelists and blacklists. My next project will be to set up Pi-hole on a proper Raspberry Pi 4 connected via ethernet and see if the experience is any better.
If you haven’t already tried running Pi-hole on Windows 10, check out my orignal post Install Pi-hole on Windows 10 and live ad-free forever.
]]>
Update October 2026: This guide was written for Pi-hole v5, and the Docker command below no longer works properly with the current version of Pi-hole. Windows 10 has also reached the end of support. For up-to-date instructions, follow my guide to installing Pi-hole on Windows 11. The Docker steps are the same if you’re still on Windows 10.
Pi-hole is hands-down, the best ad blocker available.
That’s because it acts as a network wide ad-blocker. This means it blocks ads on every single device on your network without any browser extensions clogging up your browser. It even blocks ads inside apps.
What’s more, unlike browser based ad-blockers which just prevent ads from being displayed in your browser, Pi-hole speeds up your browsing experience as it blocks ads from being downloaded in the first place. If that wasn’t enough, it even prevents those annoying “it looks like you’re using an ad-blocker” pop-ups.
All of these benefits did come with one major drawback though. It was originally designed to run on Raspberry Pis. So, unless you had a Raspberry Pi, or a computer running Linux, you were out of luck. However, it’s now available for Docker. This means it can be installed on any device which will run Docker, such as Windows PCs or Macs.
I recently set up Pi-hole on my home network on a Windows PC and so far it’s worked flawlessly.
Anyway, here’s a step by step guide to block ads on all of our devices by installing Pi-hole on Windows 10.
A Windows 10 PC (Pro or Enterprise edition) which you’re happy to leave on all of the time. Preferably a power efficient, quiet PC. In my case I’m using an Intel NUC.
If you have a Mac, you can also install Pi-hole on MacOS using a similar process to the one described below.
Download Docker for Windows. As part of this, you will need to create a Docker account.
Install Docker, keeping “enable required Windows Features” selected as Docker needs Microsoft Hyper-V which is not enabled by default.
Avoid clicking the “Use Windows Containers” option. Pi-hole will require Linux containers which is the default.
When docker is installed the first thing you will need to do is sign in. Docker lives in the task bar notification area.
After signing in I recommend tweaking some settings in Docker. You can access docker settings from the docker menu in the task bar tray. I reduced the available Memory to 1GB. Pi-hole doesn’t actually need 2GB, so reducing it to 1GB frees up more memory for your PC. Click ‘Apply and restart’.
Update June 2020 - If you don’t see these options, just skip to step 4. Docker is releasing a new version with a technology called WSL 2. This is a new way of emulating Linux within Windows and replaces the existing Hyper-V setup. The main advantage is that WSL 2 uses less resources and dynamically uses memory instead of preassigning a chunk of your PC’s memory. This means there is now nothing to configure. You can read more about it on the Docker website.
To download the Pi-hole container, open Windows Command Prompt as an administrator and type the following command: docker pull pihole/pihole
Next, let’s ensure our PC has a static IP address. This will ensure other devices can always reach your Pi-hole server without any issues. To do this:
ipconfig in the command prompt and reuse the same values for the IP address.1.1.1.1. (this is Cloudflare’s DNS service).
Now Docker is running and Pi-hole is downloaded we can configure and start it. You will need to customise your script. Here’s a base:
docker run -d --name pihole -e ServerIP=172.16.154.130 -e WEBPASSWORD=password -e TZ=Europe/Copenhagen -e DNS1=127.17.0.1 -e DNS2=1.1.1.1 -e DNS3=1.0.0.1 -p 80:80 -p 53:53/tcp -p 53:53/udp -p 443:443 --restart=unless-stopped pihole/pihole:latest
You will need to replace:
ServerIP with your IP addressWEBPASSWORD with a password of your choosing (you’ll use this to access Pi-hole’s settings)TZ= this is optional. You can specify your timezone in the TZ formatNote: DNS1 needs to be left as 127.17.0.1 in order for Pi-hole to work. If you’re curious, 127.17.0.1 is the IP address for Localhost (or in other words this computer). You can change DNS2 and DNS3 to whatever you like.
The base script above will get you up and running, however if you want to customise how Pi-hole works, there are a number of variables you can set as part of this script.
You’ll also find more information and documentation on the Docker Pi-hole Docker Github page.
Open command prompt as an administrator again and paste in your customised command and press enter. This will create your Pi-hole Docker container and run it.
Go to your web browser and type - http://127.17.0.1/admin/ or http://localhost/admin/ you should see the Pi-hole admin console. This means you’re up and running!
The Pi-hole admin console lets you configure the advanced settings of Pi-hole, see which domains have been blocked as well as blacklisting or whitelisting new domains.
The final step is to change the DNS server on your router to point to your PC. In my case this is 172.16.154.130. This will ensure all of the devices on your network get Pi-hole’s ad blocking magic.
Congratulations! At this point, provided everything has worked you should have an ad-free home!
When I shared this post on Reddit I got lots of really useful feedback and questions, so I’ve put together a short FAQ section:
At first I thought this would be a problem, but apparently not. My setup works really well over WiFi. Because of where my PC is located in my apartment it’s pretty much impossible for it to use a wired connection. Like always ethernet is preferable though.
Yes - you absolutely can. The process is very similar. I’ve tested this on Mac OS Catalina and it works.
This could be a whole article, but in a nutshell Docker is easier to set up and maintain compared to a VM. With a VM you need to ensure your Linux installation is correctly configured and kept up to date. This takes time, and in the case where you encounter a problem, reinstalling everything takes a long time. Whereas using Docker, Pi-hole is kept in an isolated container and Docker takes care of everything else. What’s more all of the configuration settings are kept in your Docker script, so you can easily delete the container and recreate it if you run into problems.
Restarting your PC is not a problem. By default Docker for Windows is configured to run automatically when you start your PC and the --restart=unless-stopped string in the Docker script I’ve provided means your Pi-hole Docker container will automatically start up. Your internet will also continue to work if your PC is turned off as you can specify a secondary DNS server on your router. In this case your router will simply use this backup DNS server if your Pi-hole is unreachable.
Not easily. Docker for Windows relies on using Hyper-V, a virtualisation technology only included in Windows 10 Pro or Enterprise. For this reason it’s not straightforward to install Docker on Windows 10 Home. It is technically possible, but it does require you to jump through a lot of hoops. Mark Cameron wrote a guide on Installing Docker on Windows 10 Home which might help.
Occasionally you will notice in the Pi-hole admin interface that a new version is available.
With Docker you don’t update the installed version of Pi-hole, but rather delete it and reinstall it with the variables you created in your customized docker command. This is essentially has the same effect as upgrading, but ensures you have a clean, new environment each time.
In order to do this, head to the ‘Docker dashboard’. You can access the dashboard from the docker menu in the Windows notification tray. Once you’re in the Docker dashboard, click the delete icon next to your Pi-hole container. This will stop and delete the docker container.
The next step is to head to an elevated Command Prompt and type:
docker image prune -a
This command clears out the Docker cache and all unused images (i.e. the out of date version of Pi-hole).
Once this has completed, you can reinstall Pi-hole using the instructions in this article.
Essentially all you have to do is run docker pull pihole/pihole in the Command Prompt, and when it has completed downloading, run your customized docker command to restore your Pi-hole instance. Congratulations, you should now be running the latest version of Pi-hole!
See my follow up post where I share my experiences after four months Review: living with Pi-hole on Windows 10.
In the latest version of Pi-hole (version 5.0) there is a bug which can cause Pi-hole to crash meaning you’re left without an ad-blocker or DNS server. I haven’t run into this myself, and I’m running Pi-hole 5.0 on Docker with no problems. However, if you do have problems Angel-Panda Diaz has helpfully shared a workaround which may prevent this problem. This workaround increases the size of the Docker container’s shared memory (SHM) to 5 gigabytes. I haven’t attempted this workaround myself, but let me know if it helps!
If you’re experiencing crashing, try the following script:
docker run -d --name pihole -e ServerIP=172.16.154.130 -e WEBPASSWORD=password -e TZ=Europe/Copenhagen -e DNS1=127.17.0.1 -e DNS2=1.1.1.1 -e DNS3=1.0.0.1 -p 80:80 -p 53:53/tcp -p 53:53/udp -p 443:443 --shm-size="5g" --restart=unless-stopped pihole/pihole:latest
I’ll update this post when this bug is fixed.
]]>