After too much time spent configuring my email server I decided to close it down.
I started out with my email server around 2 years ago and while it has been working fine most of the time – it does end up stealing a lot your precious time and attention. Sometimes for more than what you want it to.
To know why email can be troublesome you need to know a bit of history:
The predecessor to email was invented in the early 60s and email was we know it today was not invented until 1972. That makes it at least 44 years old. When setting up the services you sure notice that the technology is old.
To make up for this old piece of technology (and email is not going away some time soon) you have a lot of non-standard extensions such as email blacklists (RBL or Real-time Blacklist), DMARC (Domain-based Message Authentication, Reporting & Conformance) and SPF (Sender Policy Framework).
After upgrading to macOS Sierra Golden Master some programs are for some reason using any non-primary language. In my case neovim, git and other programs started to communicate with me in Swedish.
To revert it back to the old behaviour you go to
System Preferences -> Language & Region and then remove any non-primary language in the list of preferred languages.
Suggested by this article from PewResearchcenter and other articles people do want control in regard to their online presence. 59% of the people questioned in the linked article say they should have the ability so use the internet completely anonymously and 81% claim to have used something to conceal their online identities.
Let me first mention that most browsers support plugins which are similar to the ones I mention below – but for this blog post I will suggest some extensions for Mozilla Firefox because it is my primary browser. For the web to remain open in the future I believe Mozilla Firefox is the most viable alternative.
If you like me use Docker for mostly everything you may find yourself accidentally leaving your containers running after you are done with them.
In the previous part I wrote about why you should improve your web accessibility. I wrote about incorporating accessibility in your forms and labels using ARIA. In this part we will expand on ARIA and accessibility and how to apply it to buttons, navigation and dialogs. We’ll start with the buttons.