Beware the barrenness of a busy life.
- Socrates (from my quotes file)

Today, we're going to learn how to be a 10x anything. We're going to do that by putting slack on mute. But not the simple way. That works, but don't expect 10x results. Also, this guide assumes that the most distraction during worktime comes from Slack. If that's not the case for you, you might end up with ~4.5x results (scientific).

What we'll essentially be doing is:

  • Set up Pi-hole on our home network. Pi-hole is a DNS based ad blocker which sinks requests if they're for ad network.
  • Use Pomodoro app on KDE to trigger scripts when the focus session starts and ends. If you haven't heard about Pomodoro technique, read up more here: https://en.wikipedia.org/wiki/Pomodoro_Technique.
  • The scripts themselves will block any website / app that you don't want distracting you when the focus time is on.

Pi-hole

Pi-hole is amazing! No, seriously. It blocks all ads and tracking, has a very good interface which supports custom rules for each device, groups and more. All of this is free, open source and pure. Did you star the repository already?

Pi hole can not only block DNS queries for ads/tracking networks, but also anything you ask it to. We'll use it to block Slack on our network.

Raspberry Pi

We need something to run the Pi-hole, so grab a Pi zero or a normal Raspberry Pi. A virtual machine / docker would work but then you need that thing running 24/7.

Pomodoro app that supports scripts

I'm sure your operating system of choice has a Pomodoro app made for it. The trick here is to find one that supports executing scripts on certain events like focus time start and end.

As you can see, Fokus on the KDE store supports this functionality and is perfect for me since I'm already on KDE.

Router with custom DNS setting

We need to change the DNS settings in our router and point it to our Raspberry Pi's IP address. As a backup, we still keep 1.1.1.1. Most routers support this setting. If for some reason you're not able to do it at the router level, you can still set custom DNS on each of your device, which is a bit more work.

Ability to not overthink

Given how futile this whole exercise is, if you start questioning yourself why am I even doing any of this when you could just mute Slack?, this exercise (or this blog) is not for you.

Tutorial (kinda)

The initial setup is very standard. Install Pi-hole on your Raspberry pi by following their official guide. Get the Pomodoro app up and running.

Once that's done, we create a directory on our computer and create two files in it: focus-start.sh and focus-end.sh and mark them executable 

$ mkdir hackerman && cd hackerman
$ touch focus-start.sh focus-end.sh
$ chmod +x focus-start.sh focus-end.sh

As the file names suggest, the focus-start.sh will execute when our focus time starts and focus-end.sh executes when our focus time ends. It should look like this in Fokus, our pomodoro app.

So now that this is configured, we need to enable passwordless ssh access to our Raspberry Pi. I followed this guide here. What that enables is just typing ssh pi@raspberrypi.local will log us into the Pi without a password.

Next, we open our files and add the commands to enable and disable Slack's domain using a wildcard blacklist/whitelist entry. 

# focus-start.sh
ssh pi@raspberrypi.local "pihole --wild 'slack.com'"

# focus-start.sh
ssh pi@raspberrypi.local "pihole --wild 'slack.com' -d"

The focus-end.sh command is only different in that has the -d flag, which removes the wildcard domain from the blacklist. We can even try running that command on the terminal and verifying if it creates an entry in Pi-hole. Remember to substitute raspberrypi.local with your Raspberry Pi's hostname / IP address.


That's it. The other command works as expected too, removing the slack.com's wildcard entry at our discretion.

So, how does it (not) work?

Theoretically, we're sinking any DNS query for slack.com and any of its subdomain meaning the APIs won't work once the blacklist entry has been created. But there are a couple of problems with our approach.

One, Slack's messages are transferred over Websocket and once that's established (when you open the website / app), it doesn't need DNS to work (resolve) for sending and receiving messages.

Even if it did, DNS queries are cached (by a variety of entities like browsers, operating systems etc), so it isn't like this is fool proof and starts working the second it is turned on.

Third, many apps use their own DNS and have little regard for your home DNS. For example, I tried to block Whatsapp this way (using this list) and it just doesn't work, at least on Android.

A complete fail then?

Not exactly. You can still block websites that you open in browsers, like reddit.com and youtube.com if you spend too much time on those like me. In any case, it is a fun way to learn about how web apps, DNS and ad blocking work and involves a lot of trial and error to get things to work. Oh and yes, we do have a network wide ad blocker which is what Pi-hole does best, so there's also that.

That's it for this one. Thank you for reading.