Last weekend was IndieWebCamp Utrecht. I went along and had a great time learning, hacking, and seeing some parts of Holland.

IndieWebCamps are brainstorming and building events where IndieWeb creators gather semi-regularly to meet in person, share ideas, and collaborate on IndieWeb design, UX, & code for their own sites. — IndieWebCamps

They’re a great way to learn more about the IndieWeb and also a great excuse to visit a new place you’ve never been before.

I travelled over on a rail and sail ticket from London -> Utrecht with an overnight ferry.  I went to IWC over the weekend, plus a day in Utrecht before, and a day in Rotterdam afterwards.

Continue reading “IWC Utrecht & a trip to Holland”

Carrying on the sporadic series (here are parts one and two), this is my next tinkering around with a means to connect a WordPress-based IndieWeb site to the Fediverse.

For my hackday project at IWC Utrecht I set up Matthias’ ActivityPub plugin that fully fedifies your WordPress site. It’s dead simple and most excellent.

Yes way!

Continue reading “Bridging the IndieWeb and the Fediverse, part 3 – WordPress ActivityPub plugin”

In part 1, I discussed why you might want to bridge your Indieweb site to the Fediverse.

In this follow up post, I’ll describe one way of doing it that I’ve been tinkering with recently.

The tl;dr: using WordPress Indieweb plugins and Bridgy Fed; it works pretty smoothly; still a few quirks at present; it’s awesome and lots of fun to mess around with.

Continue reading “Bridging the Indieweb and the Fediverse with Bridgy Fed, part 2”

I experimented recently with setting up an Indieweb WordPress site as a standalone actor on the Fediverse. Thanks to the WordPress indieweb plugins, and Bridgy Fed, it’s pretty easy to do, with a few quirks.

This post is a bit of preamble as to what this means and why you might want to do it. Part 2 will go in to the details of one way to do it that I’ve played with – via Bridgy Fed.

Continue reading “Bridging the Indieweb and the Fediverse with Bridgy Fed, part 1”

When I was younger, mid-teens to mid-twenties, I had really debilitating social anxiety disorder (https://www.nhs.uk/conditions/social-anxiety/).

To the point that I often did not want to leave my room. I found it difficult to be in a room with other people, eat in public, stand in line at the supermarket. It really affected my mental health and development of relationships.

I still have remnants of it now, in that I’m fairly quiet in social situations and not the most gregarious. But it has mostly gone away, to the point that I can go to events, even do occasional public speaking, and not really worry about it.

So I guess I wanted to say, if you currently have it, or know someone who does – you can definitely overcome it.

#SocialAnxiety #MentalHealth

UPDATE 7th Nov 2019: snarfed‘s (author of granary) preference is for people to use a different of his tools, https://twitter-atom.appspot.com/, for this use case.  (see the discussion here).  Various reasons to do so, but chief of which I would say is that using twitter-atom you use your own app key, versus everyone piling on to granary and risking it getting in to trouble with Twitter.  I’ll keep this post here, but please use that tool instead!


My online social experience is mostly through the indieweb. For following people and blogs, I use Aperture, a Microsub server, to subscribe to various social feeds. And then I read and interact with those feeds in various clients – e.g. Indigenous on Android, and Monocle on the web.

Although I don’t use Twitter anymore, lots of people I find interesting still do. So I want a way of following their posts from within my Indieweb readers.

I use granary.io to follow Twitter people in my indieweb reader. What it does is convert a Twitter feed into a feed in a format that I can subscribe to via Microsub.

Continue reading “Following Twitter peeps in an indiereader with granary.io and Microsub”

For future peoples possibly encountering this same error:

"stream_socket_client(): SSL operation failed with code 1. OpenSSL Error messages: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure stream_socket_client(): Failed to enable crypto stream_socket_client(): unable to connect to ssl://some.site:443 (Unknown error)

I was getting this on a server that was running PHP 7.1.  Upgrading to 7.3 resolved it.

(I also enabled SSL on the site that the call was being made from – a test site so it didn’t previously have any SSL – but I don’t think that made any difference.)