Open Thinkering

Menu

Tag: Facebook

Kettled by Big Tech?

Yesterday on Mastodon, I shared with dismay Facebook’s decision to impose ‘login via Facebook account’ on the Oculus range of products. If, like me, you have an Oculus VR headset, but don’t want a Facebook account, then your device is going to become pretty useless to you.

The subsequent discussion included a request not to share links to the Oculus blog due to the number of Facebook trackers on the page. Others replied talking about the need to visit such sites using Firefox multi-account containers, as well as ensuring you have adblockers and other privacy extensions installed. One person likened it to needing an “internet condom” because “it’s a red light district out there”.

I struggle to explain the need for privacy and my anti-Facebook stance to those who can’t just see the associated problems. Sexualised metaphors such as the above are illustrative but not helpful in this regard.

Perhaps a police tactic to contain and disperse protesters might serve as a better analogy?

Kettling (also known as containment or corralling) is a police tactic for controlling large crowds during demonstrations or protests. It involves the formation of large cordons of police officers who then move to contain a crowd within a limited area. Protesters either leave through an exit controlled by the police or are contained, prevented from leaving, and arrested.

Wikipedia

The analogy might seem a little strained. Who are the protesters? Do the police represent Big Tech? What’s a ‘demonstration’ in this context?

However, let’s go one step further…

[K]ettling is sometimes described as “corralling,” likening the tactic to the enclosure of livestock. Although large groups are difficult to control, this can be done by concentrations of police. The tactic prevents the large group breaking into smaller splinters that have to be individually chased down, thus requiring the policing to break into multiple groups. Once the kettle has been formed, the cordon is tightened, which may include the use of baton charges to restrict the territory occupied by the protesters.

Wikipedia

In this situation, the analogy is perhaps a little easier to see. Protesters, who in this case would be privacy advocates and anti-surveillance protesters, are ‘kettled’ by monopolistic practices that effectively force them to get with the program.

Whether it’s Facebook buying Oculus and forcing their data collections practices on users, or websites ‘breaking’ when privacy extensions are active, it all gets a bit tiring.

Which brings us back to kettling. The whole point of this tactic is to wear down protesters:

Peter Waddington, a sociologist and former police officer who helped develop the theory behind kettling, wrote: “I remain firmly of the view that containment succeeds in restoring order by using boredom as its principle weapon, rather than fear as people flee from on-rushing police wielding batons.

Wikipedia

It’s a difficult fight to win, but an important one. We do so through continuing to protests, but also through encouraging one another, communicating, and pushing for changes in laws around monopolies and surveillance.


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

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

On the difference between people-centric and resource-centric social networks

Something Tom Murdock said recently resonated enough with me that I felt the need to write it down in a place that I can reference. Here is as good a place as any!

I’m leading Project MoodleNet, which is currently described as “a new open social media platform for educators, focused on professional development and open content”. Tom mentioned that he saw an important difference between ‘people-centric’ and ‘resource-centric’ social networks.

(Note: it’s been a couple of weeks since that conversation, so anything witty or clever I say in the next few paragraphs should be attributed to him, and anything confusing or stupid should be attributed to me)

I should also point out that I blog about things I’m thinking about here, whereas the official project blog can be found at blog.moodle.net.

What is a resource-centric social network?

A people-centric social network is something like Facebook or LinkedIn. Users have a single identity and want to follow or connect with you as a person. A resource-centric social network is something like Pinterest or Thingiverse where people interact and engage with you through the resources you’re sharing.

I think most people reading this will understand how Facebook and LinkedIn work. Imagine them towards one end of the spectrum, and Pinterest and Thingiverse towards the other. Twitter is an interesting case here, as users can have multiple accounts and follow non-human accounts. I suppose it would probably be somewhere in the middle of the spectrum.

A quick tour of Thingiverse

I think Project MoodleNet is more of a resource-centric social network. To illustrate that, I want to explore Thingiverse, a wonderful site I came across recently after acquiring a 3D printer. Here’s what the About page says:

MakerBot’s Thingiverse is a thriving design community for discovering, making, and sharing 3D printable things. As the world’s largest 3D printing community, we believe that everyone should be encouraged to create and remix 3D things, no matter their technical expertise or previous experience. In the spirit of maintaining an open platform, all designs are encouraged to be licensed under a Creative Commons license, meaning that anyone can use or alter any design.

So it’s:

  1. A registered trademark
  2. Owned by a company
  3. Focused on makers
  4. Allows the sharing of open content
  5. Encourages remixing

In that sense, it’s a very interesting model for Project MoodleNet.

Let’s look a little more closely. Below you can see the home page. The site is obviously curated by real human beings, as they’ve featured particular designs, and created collections which include designs from different users. There’s a feed of latest activity, the calls to action in the top menu bar make it obvious that this is a living community full of creative people.

Thingiverse home page

The next thing you notice when you click through onto a particular design is that there’s a lot of information here to help orient you. There’s a clear call-to-action below ‘DOWNLOAD ALL FILES’ but also we can see how many times it’s been liked, watched, commented upon, and remixed.

Thingiverse design

Click on the remix button and you get to see those who have remixed the original design in some way. If the design you’re looking at is itself a remix, it also allows you to look at the original, too.

Naturally, you want to know a little bit about the person who created it. Perhaps they’ve created some other things you’d like? Clicking on the user name reveals their Thingiverse profile.

Thingiverse profile

There’s lots of information about the person here: their username, location, Twitter profile, website, short biography. However, the focus is still on their resources. What have they designed? What have they shared?

The last thing to highlight is how Thingiverse deals with openly-licensed resources. When you click to download the files, the first thing that pops up is a windows that tells you in no uncertain terms about the license under which this resource has been made available.

Thingiverse CC licensing

In addition, it encourages you to ‘show some love’ to the designer. You can tip them using money via PayPal, and you can take a photo to ‘document’ your 3D print of their design, and you.

Final thoughts

I’m very impressed with the thought that’s been put into Thingiverse. I don’t know the history of the community, but it feels like something that has responded to users. In turn, I should imagine that when those who are regular users of Thingiverse come to purchase their next 3D printer, Makerbot will be top of their list. It’s a virtuous circle.

So there’s a lot to learn from here that we can apply to Project MoodleNet. I like the way that they make it easy for people new to the community. I love the ease by which you can use the fork-remix-share approach that developers are used to on GitHub, but many educators are still yet to discover. And I adore the way that they encourage users to ‘show some love’ to original resource creators, educating them on how to use openly-licensed content appropriately.

css.php