Technology

The Twitter exodus has started.

When Elon Musk took over Twitter I expected some migration from those who had already planned an exit strategy but the reality was more than I could have imagined to the point that within a space of seven days there have been around 275000 new accounts created with an average of 3000-4000 new accounts created every hour.

One thing to keep in mind is that 90% of activity on twitter comes from 10% of users and to be considered part of that 10% you have to tweet at least 3 times a day. Although the numbers may not be in the millions the reality is that the impact will be big over time particularly when you look at who are introducing themselves – journalists, academics, politicians etc. the sort of ‘high value’ users that you want on your website so that you can attract the advertisers. What we’re witnessing is the slow death of Twitter and Elon Musk is going to find out the tough way that businesses don’t want to be associated with a ‘free speech free for all hellscape’ meaning all the subscribers in the world aren’t going to make up for the revenue drop off from advertisers. Just to wrap this up, here is a great interview with Nilay Patel from The Verge:

I’m back to using Chrome after giving Safari a try. I was hoping that with uBlock Origin developer creating a MV3 version of uBlock Origin (known as uBlock Origin Lite) would result in it eventually coming to Safari but it appears that as much as Apple likes to boast about it’s support for Webextensions API the reality is that there is a lot of functionality missing that uBlock Origin Lite relies on. As mentioned on a previous post, I waited until macOS 13 came out with Safari 16.1 to see whether those short comings have been addressed particularly in the area of Webextensions API support but so far it appears that just like the web standards, Apple is dragging their feet every step of the way. Although people have complained about Chrome moving to MV3 it appears that Webkit is in a much worse position when it comes to implementing the Webextension API.