Fediverse

A few weeks ago I was completely opposed to Threads being connected and accepted by the Fediverse because I hated the idea of 100 million users flooding a social network with 10 million users. Now that threads has imploded I feel differently.

Now that Threads is the same size as the Frediverse, or at least closer to being the same size, the impact of the two joining up would be diminished. Now is the time when, theoretically, the impact of Threads and the Fediverse merging would be less dramatic.

Someone asked Is decentralization the future of social media? and I’d take an extra leap. I believe that the Fediverse, made possible by ActivityPub, and the other one, made possible by the Authenticated Transfer Protocol both point to a different future

Playing With WordPress, ClassicPress and Firefish

As we play with the fediverse, and we experiment with WordPress, ClassicPress and Firefish, among other instances or communities one thing becomes clear. The social media age could be over, replaced by something akin to the blogrings of the 90s. What I mean by this is that the fediverse is a gigantic web portal. We add photos via pixelfed, video via peertube, conversations by mastodon, notes via Firefish, and blog posts via WordPress and ClassicPress, among others. The point is we’re on niche platforms, talking with other niche platforms without logging in and out constantly. Log in, in one place, and we’re connected to everything within the fediverse. We’re on a community of communities.

After my first post about playing with ClassicPress and the Fediverse it was suggested that I try the nightly build of ClassicPress so I did. The result can be seen here.

Mastodon and Firefish

I have tested integration with the fediverse via Mastodon.social but also firefish.social and mastodon.social is faster, but mastodon.social eventually catches up. I tried posting a blog post, and commenting on blog posts and it works although not instantly. You need to wait for the changes to be propagated to where they are needed.

Although I didn’t achieve what I set out to achieve I have been experimenting with ClassicPress and the Fediverse, but rather than do it from my main blog I have decided to experiment within a subdomain and so far I have achieved much. I see that activitypub and webfinger can be installed on ClassicPress.

I checked that a webfinger was created and displayed correctly but this took trial and error. The biggest error is that to create a webfinger that is valid you must come from an https hyperlink. If it is not secure you get a “socket not secure error”. I found a solution, by creating classicpress.main-vision.com for the sake of testing.

Yesterday I experimented with migrating my blog from WordPress to ClassicPress to see whether ClassicPress plays nicely with the fediverse. It does but there is room for improvement.

If you want instructions on how to migrate from wordpress you can find the instructions here. Summarised, you download the switch to ClassicPress plugin, you run it, it checks that you’re ready to migrate, you fix what needs to be fixed, and when ClassicPress sees that you’re ready it will allow you to start the migration. The migration takes a second or two. It felt almost instant in my case. You know it has succeeded because you see the “ClassicPress” message at the bottom of the admin section.

I started writing a post, but felt that it was too negative so I stopped, and now I’m writing this one. I want to explore the way in which Facebook, Instagram, YouTube, Twitter and Reddit are still front and foremost on The Guardian Website, as well as many others.

As I write this Twitter has become x.com. Reddit has had several weeks of protests and Facebook reached over three billion users. The paradox, with Facebook is that it’s the most unpleasant “social network” I know. I find Facebook and Instagram deeply unpleasant to use.

With the change in name from Twitter to X, and with the destruction of a recognisable brand mentioned in tens of thousands of podcasts, podcasts, episodes and millions of web pages I was curious to see how Twitter was, with the new logo. It took more than 24 hours to change the favicon, and whilst x.com does redirect to Twitter, it does not do anything else than redirect to Twitter.com. You can’t see your x posts there.

Yesterday Twitter decided to re-brand as X. X.com redirects to Twitter.com. Within the next few days, weeks, months twitter will change its name and brand, and the URLs will be wrong. All twitter links, all embedded tweets, everything will become dead links. When we look for something on Twitter, we will be redirected to X.

The Podcast Legacy

Every single website, every single CMS, every Static Website, everything, will have to be re-written to point to the new domain name. Plenty of content will not be updated and will be a reminder of the past.

The Fediverse is great because people are experimenting and trying new idea. It’s also great because we can be there through every step of the process. This is also why things could be better. I am now writing my blog in Hugo first, and then moving the content over to Wordpress at the moment. I could just replace my Wordpress blog with Hugo but I don’t for two reasons. The first reason is that I’m experimenting, and if I change my mind about something, I can, without affecting Quality of Service. The second reason is that I believe that the production server should be in fine working order with as little downtime for users as possible. With one or two projects on the fediverse this isn’t the case. Downtime can be for hours, or even days at a time.

Over a period of a few days I have turned my WordPress blog into a fediverse instance. The process took some trial and error. In the end it was quit easy and there are three steps.

Step One: Have a WordPress Instance

The first step is to have a WordPress blog/CMS. You can start with an existing website, that you are willing to have on the fediverse, or you can install the WordPress CMS in another director and use that as a dedicated Fediverse CMS.