Open Thinkering

Menu

Tag: blog

Practice what you preach

I spend a lot of time looking at screens and interacting with other people in a mediated way through digital technologies. That’s why it’s important to continually review the means by which I communicate with others, either synchronously (e.g. through a chat app or video conference software) or asynchronously (e.g. via email or this blog).

When I started following a bunch of people who are using the #100DaysToOffload hashtag, some of them followed me back:



@dajbelshaw you have a really beautiful site that doesn't open for me. First it's not compatible with LibreJs and then uMatrix block Cloudflare's ajax and you'll not get further than loading screen.

I know that some people are quite hardcore about not loading JavaScript for privacy reasons, but I didn’t know what ‘LibreJs’ was. Although uMatrix rang a bell, I thought it would be a good opportunity to find out more.


It turns out LibreJS is a browser extension maintained by the GNU project:

GNU LibreJS aims to address the JavaScript problem described in Richard Stallman’s article The JavaScript Trap. LibreJS is a free add-on for GNU IceCat and other Mozilla-based browsers. It blocks nonfree nontrivial JavaScript while allowing JavaScript that is free and/or trivial.

Meanwhile uMatrix seems to be another browser extension that adds a kind of ‘firewall’ to page loading:

Point & click to forbid/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.

Meanwhile, the extensions that I use when browsing the web to maintain some semblance of privacy, and to block annoying advertising, are:


So just running the tools I use on my own site leads to the following:

Privacy Badger found 18 potential trackers on dougbelshaw.com:

web.archive.org
ajax.cloudflare.com
assets.digitalclimatestrike.net
www.google-analytics.com
docs.google.com
play.google.com
lh3.googleusercontent.com
lh4.googleusercontent.com
lh5.googleusercontent.com
lh6.googleusercontent.com
licensebuttons.net
www.loom.com
public-api.wordpress.com
pixel.wp.com
s0.wp.com
s1.wp.com
stats.wp.com
widgets.wp.com

Disconnect produced a graph which shows the scale of the problem:

Graph produced by Disconnect showing trackers for dougbelshwa.com

This was the output from uBlock Origin:

Output from uBlock Origin for dougbelshaw.com

It’s entirely possible to make a blog that involves no JavaScript or trackers. It’s just that, to also make it look nice, you have to do some additional work.

I’m going to start the process of removing as many of these trackers as I can from my blog. It’s really is insidious how additional functionality and ease-of-use for blog owners adds to the tracking burden for those reading their output.

Recently, I embedded a Google Slides deck in a weeknote I wrote. I’m genuinely shocked at how many trackers just including that embed added to my blog: 84! Suffice to say that I’ve replaced it with an archive.org embed.

I was surprised to see the Privacy Badger was reporting tracking by Facebook and Pinterest. I’m particularly hostile to Facebook services, and don’t use any of them (including WhatsApp and Instagram). Upon further investigation, it turns out that even if you have ‘share to X’ buttons turned off, Jetpack still allows social networks to phone home. So that’s gone, too.


There’s still work to be done here, including a new theme that doesn’t include Google Fonts. I’m also a bit baffled by what’s using Google Analytics, and I’ll need to stop using Cloudflare as a CDN.

But, as ever, it’s a work in progress and, as Antoine de Saint-Exupéry famously said, “Perfection is achieved when there is nothing left to take away.”


This post is day two of my #100DaysToOffload challenge. Want to get involved? Find out more at 100daystooffload.com


Header image by Gordon Johnson

New blog: Doug, uncensored

TL;DR: Head to uncensored.dougbelshaw.com or bit.ly/doug-uncensored for my new blog about freedom and decentralised technologies.


One of the great things about the internet, and one of the things I think we’re losing is the ability to experiment. I like to experiment with my technologies, my identity, and my belief systems. This flies in the face of services like Facebook that insist on a single ‘real’ identity while slowly deskill their users.

I’ve been messing about with ZeroNet, which is something I’ve mentioned before, and which gets close to something I’ve wanted now for quite some time: an ‘untakedownable’ website. Whether it’s DDoS attacks, DNS censorship, or malicious code injection, I want a platform that, no matter what I choose to say, will stay up.

To access sites via ZeroNet, you have to be running the ZeroNet service. By default, you view a clone of the site you want to visit on your own machine, accessed in the web browser. That means it’s fast. When the site creator updates the site/blog/wiki/whatever, that’s then sent to peers to distribute. It’s all lightning-quick, and built on Bittorrent technlogy and Bitcoin cryptography.

The trouble, of course, comes when someone who isn’t yet running ZeroNet wants to visit a site. Thankfully, there’s a way around that using a ‘proxy’ or bridge. This is ZeroNet running on a public server for everyone to use. There’s several of these, but I’ve set up my own using this guide.

I encourage you to download and experiment with ZeroNet but, even if you don’t, please check out my new blog. You can access it via uncensored.dougbelshaw.com or bit.ly/doug-uncensored — the rather long and unwieldy actual IP address of the server running the public-facing copy is 165.227.167.16/1PsNi4TAkn6vtKA6n1Se9y7gmVjF4GU3uF.

Finally, if you’re thinking, “What is this?! It’ll never catch on…” then I’d like to remind  you about technologies that people didn’t ‘get’ at first (e.g. Twitter in 2007) as well as that famous Wayne Gretszky quotation, “I skate to where the puck is going to be, not where it has been”.

Tools to help you with your blog post

This is part of a series. In the following, I cover some tools you might want to use when planning, writing, and editing your blog post.


If there’s one thing I’ve learned from watch other people write, and reading what people have written about how they write, it’s that everyone writes differently.

Bloggers rock

One way of thinking about this is through rock formation. Bear with me. Remember at school you learned there were (broadly) three different types of rock?

  • Igneous — formed when volcanic lava cools
  • Sedimentary — formed from the repeated deposits of sediments
  • Metamorphic — formed by transforming existing rock through heat and pressure

Writing can be a bit like this too. Some writers sit down in a burst of frenzied activity and their writing is the result of that volcanic eruption.

Volcano gif

Others lay down words day after day after day to get to a point where they’re happy. Still others have existing stuff that they’ve worked on, but after a burst of inspiration it turns into something else.

While all writers can write in different ways at different times, it’s good to know what kind of blogger you tend to me. I, for example, tend to be an ‘igneous’ blogger. I like getting everything down in one go — as I’m doing now with this post. That doesn’t mean things are stream-of-consciousness, as often the post has been rattling inside my brain for a while.

Choosing your tools

The reason this discussion about blogging styles is important is that it has an impact on the tools you use and the ways you use them.

The three tools I recommend most often to people are:

There’s a whole list of blogging tools on the Buffer blog.

Interestingly, although I recommend these three, the only one I actually use on a sporadic basis is Hemingway. It’s a great way to spot things your high school English teacher pointed out, such as when you over-use the passive voice.

The other two tools help in-line with your blog post punctuation, grammar, and spelling (Grammarly) and planning (Workflowy).

When it comes down to it, though, the tools you need for writing a blog post are either in your blogging platform or are ones you probably use every day. You need a version history: that’s built-in to WordPress as well as into tools such as Google Docs (and Draft). You need a spellchecker, that’s built into web browsers and word processors. You’ve got pretty much everything you need already!

Getting graphical

What people often miss when putting together their blog post is the importance of showing rather than telling. If a picture paints a thousand words, then a labelled screenshot is worth even more — and what about a two-minute YouTube video?

It’s easy to default to words when you’re comfortable in that medium and can type quickly. Put yourself in your reader’s shoes, however, and think about what’s the quickest line from what’s inside your head to what you want to be inside theirs.

Three tools/resources that can help up the graphical content of your blog post are:

These are examples of types of applications that should be in your toolkit.

For example, I’ve included Unsplash because you don’t have to credit the author of the photo you use to illustrate your post, although they make it easy to do so. You can discover many more Creative Commons-licensed images here.

Although I’ve long been a fan of the Awesome Screenshot browser extension, the latest versions of Firefox have a new screenshotting tool which is incredible. Try it!

Firefox Screenshots

Finally, the weirdly-named LICEcap allows you to create animated GIFs of areas of your screen. Once you start doing this you’ll begin to realise how incredibly useful it can be. I’m sharing this in the knowledge that most people who read this post will use Windows or macOS. If you’re on Linux, like me, try Peek.

Conclusion

Use blogging as an opportunity to experiment with different tools and approaches. Your focus should always be to convey something to the reader, and experimentation will help you with ways of doing that!


Photo by WOCinTech Chat used under a Creative Commons Attribution license.

css.php