Anti-social media

Posted on By Mark Wilson

I’ve slowly been catching up Professor Hannah Fry‘s Secret Genius of Modern Life series. Summing up the episode on virtual assistants, Prof Hannah says:

“[…] it’s the technology that leads the way it’s and only later society asks the question of whether it’s something that we really want in our lives. And that I think is a trend that we’re going to have to deal with a lot more in future”

Professor Hannah Fry, The Secret Genius of Modern Life: S1E3 Virtual Assistants

This, very astute, observation is a concern. Virtual assistants are a branch of the technology field known as artificial intelligence. But they’re not the only examples of technology created without consideration for their impact on society.

As created, technology is neither good, nor bad. Whether it becomes one of those things is about the way we use it.

All too often, we invent something and then work out how to use it. And all to often, the techies decide the way, with society left to mop up the issues.

Social media is one such example.

Social networks come of age

This week, Facebook turned 20.

Gen-Xers like me didn’t grow up with social media but we’re heavy users of the technology. Or we were. Now, as the likes of Mark Zuckerberg and Elon Musk work out how to make money from the vast platforms, they are losing their purpose.

Once it was easy: Facebook for social sharing; Instagram for photos; YouTube for videos; WhatsApp for messaging; LinkedIn for who knows who; Twitter for brief micro-blogging; blogs for long form prose. But Google killed blogs; LinkedIn tried to be Facebook for business (small B, Facebook also tried to launch Facebook for Business); and the other platforms copied each other until they all had versions of similar features. Meanwhile, one of the world’s richest men appears to have delivered a lesson on how to destroy a social network.

Anti-social media

Modern politics – and modern media – seems to be about setting groups of people against each other.

Cyclists against motorists. Brexit or remain. Guns or no guns (in the USA). Your choice of political party (red or blue – on both sides of the Atlantic). Woke or anti-woke (whatever that means). Even whether it makes sense to park a car forwards or backwards.

Social media should have been a force for good. but everything was reduced to a soundbite. It lost the nuance, context, critical thinking. As Zoe Kleinman wrote in the tweet I embedded earlier, “at its best, it brings people together. At its worst, it destroys them.”

Where did it all go wrong?

I stopped using Facebook a while back. The Cambridge Analytica data scandal showed how the information we were giving away freely was being used by others. Not just to advertise but to target for political means. Even, some might say, to subvert democracy.

My experience of Twitter in recent years is that it has descended into a place that’s full of hate, division, bots promoting porn, and with very little genuine engagement. Instagram became very needy, with notifications trying to encourage the growth of Threads, or cross-fertilisation to other Meta properties (like Facebook).

Where next?

I’m still on LinkedIn, reluctantly, and scaling out my use professionally.

But what replaces Twitter/X (I still can’t bring myself to use the new name)? I don’t know but it’s probably not Bluesky, Post, Hue or any of those similar sites. Certainly not Mastodon. That one network where everyone came together is gone… the future looks like it will consist of small niches. Special interest groups. 

Writing last year for Wired Magazine, Jason Parham said that first-gen social media users have nowhere to go. That article is from a Millennial perspective but it resonates with Gen-X me too. Fifteen years of scrolling for news and entertainment. And fifteen years of having a platform to share, discuss and learn. What do I do now? Increasingly, I feel lost.

I’ll work out a new content strategy in 2024. We’re already a month in and I’m not sure what it is yet. One thing I do know is that you’re likely to see less from me on Twitter/X, once I work out where and how to host my history. And I’m too old to start again somewhere else.

Featured image by Daria Nepriakhina ?? on Unsplash.

Facebook’s Restricted list

Posted on By Mark Wilson
This content is 8 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Imagine the situation, a family member befriends you on Facebook and you foolishly accept, then find their replies on your posts to be inappropriate or annoying… after all, you can choose your friends but not your family, right?Well, it turns out that

Well, it turns out that Facebook has a feature for situations like this – the Restricted list.

“Putting someone on the Restricted list means that you’re still friends, but that you only share your posts with them when you choose Public as the audience, or when you tag them in the post.

For example, if you’re friends with your boss and you put them on your Restricted list, then post a photo and choose Friends as the audience, you aren’t sharing that photo with your boss, or anyone else on your Restricted list. However, if you tag your boss in the photo, or chose Public as the audience, they’ll be able to see the photo.”

May be useful to know…

Deleting large quantities of Facebook notes

Posted on By Mark Wilson
This content is 13 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few years ago, I followed the example of a “social media guru” and set Facebook up to consume my blog’s RSS feed and republish each post as a note.

This was A Bad Thing for a number of reasons, not least:

  1. Copyright – I’m sure that when I upload anything to Facebook, I give them some rights over it (which is why my images are still on Flickr).
  2. Traffic – reproducing content on Facebook might get eyeballs, but it takes that traffic away from your own website and only Facebook gains any revenue. This may be OK if you are selling goods/services that can be monetised via Facebook links but my revenue is from ads: ads on my site = revenue for me; ads on a Facebook copy = revenue for Facebook.
  3. Layout – invariably, despite my best efforts to write good XHTML, the blog posts look better on my site than when scraped into Facebook as notes.

I turned off the feed but deleting the notes was far from trivial. There is no bulk delete option that I can find, and that meant opening each note, scrolling down, clicking delete, etc. In a word, tedious.

I forgot about the notes until last week, when I switched over to timeline view. Arghh. Yes. Must delete those…

…and then I found another method – much quicker – using the iOS Facebook app.

By opening the Notes section of the Facebook app on my iPad, a quick swipe and press was all it took to delete each note. Still tedious, but a lot quicker to get through…

Designing a private cloud infrastructure

Posted on By Mark Wilson
This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A couple of months ago, Facebook released a whole load of information about its servers and datacentres in a programme it calls the Open Compute Project. At around about the same time, I was sitting in a presentation at Microsoft, where I was introduced to some of the concepts behind their datacentres.  These are not small operations – Facebook’s platform currently serves around 600 million users and Microsoft’s various cloud properties account for a good chunk of the Internet, with the Windows Azure appliance concept under development for partners including Dell, HP, Fujitsu and eBay.

It’s been a few years since I was involved in any datacentre operations and it’s interesting to hear how times have changed. Whereas I knew about redundant uninterruptible power sources and rack-optimised servers, the model is now about containers of redundant servers and the unit of scale has shifted.  An appliance used to be a 1U (pizza box) server with a dedicated purpose but these days it’s a shipping container full of equipment!

There’s also been a shift from keeping the lights on at all costs, towards efficiency. Hardly surprising, given that the IT industry now accounts for around 3% of the world’s carbon emissions and we need to reduce the environmental impact.  Google’s datacentre design best practices are all concerned with efficiency: measuring power usage effectiveness; measuring managing airflow; running warmer datacentres; using “free” cooling; and optimising power distribution.

So how do Microsoft (and, presumably others like Amazon too) design their datacentres? And how can we learn from them when developing our own private cloud operations?

Some of the fundamental principles include:

  1. Perception of infinite capacity.
  2. Perception of continuous availability.
  3. Drive predictability.
  4. Taking a service provider approach to delivering infrastructure.
  5. Resilience over redundancy mindset.
  6. Minimising human involvement.
  7. Optimising resource usage.
  8. Incentivising the desired resource consumption behaviour.

In addition, the following concepts need to be adopted to support the fundamental principles:

  • Cost transparency.
  • Homogenisation of physical infrastructure (aggressive standardisation).
  • Pooling compute resource.
  • Fabric management.
  • Consumption-based pricing.
  • Virtualised infrastructure.
  • Service classification.
  • Holistic approach to availability.
  • Computer resource decay.
  • Elastic infrastructure.
  • Partitioning of shared services.

In short, provisioning the private cloud is about taking the same architectural patterns that Microsoft, Amazon, et al use for the public cloud and implementing them inside your own data centre(s). Thinking service, not server to develop an internal infrastructure as a service (IaaS) proposition.

I won’t expand on all of the concepts here (many are self-explanitory), but some of the key ones are:

  • Create a fabric with resource pools of compute, storage and network, aggregated into logical building blocks.
  • Introduced predictability by defining units of scale and planning activity based on predictable actions (e.g. certain rates of growth).
  • Design across fault domains – understand what tends to fail first (e.g. the power in a rack) and make sure that services span these fault domains.
  • Plan upgrade domains (think about how to upgrade services and move between versions so service levels can be maintained as new infrastructure is rolled out).
  • Consider resource decay – what happens when things break?  Think about component failure in terms of service delivery and design for that. In the same way that a hard disk has a number of spare sectors that are used when others are marked bad (and eventually too many fail, so the disk is replaced), take a unit of infrastructure and leave faulty components in place (but disabled) until a threshold is crossed, after which the unit is considered faulty and is replaced or refurbished.

A smaller company, with a small datacentre may still think in terms of server components – larger organisations may be dealing with shipping containers.  Regardless of the size of the operation, the key to success is thinking in terms of services, not servers; and designing public cloud principles into private cloud implementations.