There is no doubt that the recent coronation of King Charles III was a massive event in the UK. Wether you’re in favour of the monarchy or not, there is no doubt that the coronation event is a big taking point. This was certainly the case on Mastodon – my preferred microblogging platform of choice.
By focusing on posts which mention the hashtag #Coronation over a severn day period (3rd May – 10th May) a total of 4,269 posts were made across 1,997 users, 396 instances and featuring a total of 2,295 alternative hashtags. As shown in the timeline plot below, activity peaked around 6th May – the day of the coronation.
Across all 1,997 users that posted about the coronation, around 16.52% of which originated the mastodon.social instance – the largest instance of them all. Other notable mentions include mastodonapp.uk, mstdn.social and mastodon.online. The rest are recored below.
To explore this space further, I built a user-hashtag network to consider the role of other, co-occurring hashtags. Building user-hashtag networks is something I have done in many previous posts (e.g. , , ). As shown in the figure bellow, the network is a little messy but, in order to reduce the network down to a more manageable size, I focused on the top 25 hashtags and users.
Among all the hashtags, the is a significant presence of anti-monarchy hashtags – a few of which include #notmyking #abolishthemonarchy and #republic. The remainder are fairly genetic.
One of the benefits of using bipartite graphs is that we can project nodes based upon mutual connections (as shown in a previous post). This means that we can connect hashtags together if they have at least one mutual user in common. The results are shown below.
With a large enough dataset, the projected graph could be used to perform some very basic topic modelling to see if there are any themes within the content. In our case, given the size, all of the hashtags are grouped together except for #charliesausagefingersgoldenhatparade. That one cracked me up.
If you have any creative ideas on how I could better use this data. Let me know what you think. I’m always open to suggestions.