Yesterday, the Mastodon team announced it would be handing over control of its project to a new non-profit organization. The timing of this announcement is perfect given everything that’s happening with WordPress, Meta, and… well, everything else. To date, I think Eugen Rochko has done an excellent job stewarding Mastodon, but I also might have said the same thing about Matt Mullenweg a few years back. Why gamble when you can set up safeguards? Not to dwell on the WordPress, but I came across a shockingly prescient post from 2010. It lays out potential conflicts of interest between Automattic and the open source WordPress community. 1 Just about every warning from this post has come to pass in the last few months. It’s exactly these sorts of things that Mastodon looks to be trying to prevent with this new organizational structure. The re-org should also give Rochko more time to focus on product design, which sounds like a win in my book. At this point, I don’t think Mastodon will ever take over the world, but it’s a cozy place with stellar 3rd-party clients. It’s also where a large contingent of the Apple/tech cohort continue to hang out. Bluesky has really taken off, but Mastodon is still a big part of my social media diet. Yesterday also saw the launch of the Free Our Feeds campaign. I’m honestly not sure what to make of this, but I think John Gruber had a great take. The organization is requesting “$30M over three years” to launch “a new public interest foundation that puts Bluesky’s underlying technology on a pathway to become an open and healthy social media ecosystem that cannot be controlled by any single company or billionaire”. Only, that’s also Bluesky’s goal. I’ve written before about my hesitations around the protocol powering Bluesky, and I think that a competing “AppView” would be welcome — but it’s unclear if that’s what Free Our Feeds is going for. They mention wanting to build a second “relay”, though I don’t know if they’re talking about a Relay in the AT Protocol sense. Another canonical Relay would be a good start, but wouldn’t counter any issues if Bluesky started going off the rails. I wish the Free Our Feeds people all the best, but I hope they provide a more detailed plan soon. Until then, I think I’ll just continue to donating to Mastodon’s Patreon. Just watch out for the comment section. It really hasn’t aged well. ↩

Since I last wrote about WordPress, things have gone off the rails. This after a brief period when things were blissfully quiet. Matt Mullenweg stopped commenting for a while, though his company had launched WP Engine Tracker — a site for tracking WordPress-driven websites that moved away from WP Engine. I think this is a bit gauche, but it seems like fair marketing given everything that’s going on. It should be noted that many sites are leaving for Pressable — owned by Mullenweg’s company, Automattic — because of a sweetheart deal. But the drama ramped up quickly after WP Engine won a preliminary injunction against Automattic on December 10th. The injunction required that WP Engine be allowed to access WordPress.org resources, and that Automattic stop interfering with WP Engine plugins, while the trial moves forward. Ernie Smith wrote an excellent piece with more details on outcome of the injunction, including a note about Mullenweg quitting a community Slack instance with a hammy message. Mullenweg complied with the injunction, though the “loyalty test checkbox” text was changed to a still-required note about pineapple on pizza. On December 20th, Mullenweg announced that WordPress.org would be on holiday break for an unspecified amount of time. In a post on the WordPress.org blog, he again mentioned being “compelled to provide free labor and services to WP Engine thanks to the success of their expensive lawyers”. He also invited people to fund legal attacks against him by signing up for WP Engine services, and hoped “time, energy, and money to reopen all of this sometime in the new year”. This was the first time WordPress.org had ever gone on break, and it was another instance of Mullenweg using a core part of the WordPress community to send a message. WordPress.org returned to service on January 4th, but plugin and theme updates weren’t being reviewed during the holiday break. I’m all for giving volunteers breaks, but this came as a surprise to the community and there was initially no indication when the break would end. Mullenweg’s “woe is me” language around maybe, possibly, being able to find the resources to reopen a core piece of WordPress infrastructure didn’t help things. It further cemented that Matt Mullenweg’s current mood is an important function of whether or not the WordPress community operates smoothly. While WordPress.org was on break, Mullenweg also reached out to the WPDrama community on Reddit, asking what drama he should create in 2025. A couple of years ago, this sort of thing would have been some tongue-in-cheek fun from a person who’s always been a bit of a goof. These days it comes off a bit differently. Then yesterday happened. Automattic announced that it would restrict its contributions to the open source version of WordPress. The company would now only put in about 45 hours a week total — down from nearly 4,000 a week — so as to match the estimated hourly contributions of WP Engine. This action is blamed on the “the legal attacks started by WP Engine and funded by Silver Lake”, which I think is a gross mischaracterization. WP Engine definitely did not start this. Automattic noted it would focus its open source hours on “security and critical updates”. The other hours would be redirected to for-profit projects like WordPress.com. This means that the community will be expected to take up the slack if it wants WordPress to improve. I also really doubt that 45 hours a week is enough time to keep WordPress secure and bug-free. And you know what? In a normal world, that would be fine. I’d be all for it! If the community were to take control of the open source project, I think that would be ideal. The problem is that Mullenweg has final say over some very important parts of the WordPress community. He also seems recently to be acting more childishly and impulsively than usual. Another thing that came to light yesterday was that the WordPress Sustainability committee was shuttered after a core member, Thijs Buijs, stepped down. In a post on the WordPress Slack, Buijs cited the “2025 drama” post on Reddit as the reason he was leaving, and called for a change in WordPress community leadership. In response, Mullenweg responded in part with “[t]oday I learned that we have a sustainability team”, and closed the channel. The WordPress Sustainability Team had four core members, and 11 people who had contributed on GitHub. As far as I can tell, they were all community members, and none were Automattic employees. Even if it wasn’t producing amazing results, I can’t see what harm it was doing. The sin was pointing out something stupid that Mullenweg did, and having a member wanting change. The optics, especially given current world events, are definitely not great. The wildest part of this to me is that there’s video of Mullenweg — live on stage at Word Camp Europe in 2022 — requesting the creation of the Slack channel he was turning off. Guess that slipped his mind. All of this bodes poorly for the open source version of WordPress. I think it’s perfectly fair for Automattic to switch gears and focus on for-profit projects — it’s a company after all. The problem is that there’s a void being left. Automattic had, for better or worse, lead the development of both the commercial and open source pieces of the WordPress ecosystem. Now it seems like the community needs to take over, but Mullenweg still holds all the keys. In the announcement, Automattic said that WordPress.com would be updated to be more in line with the open source version of WordPress. This also makes sense to me, as WordPress.com has always been a weird version of the software. Of course, having slight differences to the core WordPress experience is the argument that Mullenweg initially used to call WP Engine a “cancer”, but who’s keeping track? I’d also like to point out again that Automattic invested in WP Engine in 2011. It also acquired Pressable in 2016, likely because it was a hosting service that offered a “real” version of WordPress, unlike WordPress.com. It’s hard to see how to move forward from here. I think the best bet would be for people to rally around a new community-driven infrastructure. This would likely require a fork of WordPress, though, and that’s going to be a messy. The current open source version of WordPress relies on the sites and services Mullenweg controls. Joost de Valk, the original creator of an extremely popular SEO plugin, wrote a blog post with some thoughts on the matter. I’m hoping that more prominent people in the community step up like this, and that some way forward can be found. In the meantime, if you’re a WordPress developer, you may want to look into some other options.

This morning I read a 404 Media article about Instagram showing people ads with AI-generated images of themselves. I thought this take from Sam Biddle was very good: Never in my career have I seen such a giant gulf between What Companies Think Is the Most Important Thing in the World and What Normal People Have Absolutely Any Interest in Whatsoever Meta has always been a taste-free zone, so this sort of promotion isn’t surprising to me. Apple, who have always tried to embody taste, are also tripping over themselves to squeeze AI into everything. I think some of their ideas are reasonable, but not all of them. Most recently their AI summarization feature has tripped up a second time while editing notifications from the BBC. I think LLMs and generative AI are interesting and useful pieces of technology. I also think they’re massively overhyped and their current capabilities are poorly understood. Some people compare the LLM craze to the crypto/blockchain boom, and I think that’s unfair. Blockchains are slow, expensive databases masquerading as a social revolution while functionally being a get-rich-quick scheme. LLMs have been useful for years, and are only getting more useful with time. Still, that doesn’t mean they should be shoved into every corner of every product. There’s a group of the population that is disgusted by anything related to LLMs or generative AI. Part of this is because LLMs come with a massive ethical issue built-in. Training them requires feeding a statistical model as much content as possible. The makeup of the big LLM training datasets is proprietary, but a conservative bet is that at least 50% of any model’s training set is unlicensed copyrighted content. The companies doing the training say that using this copyrighted content is OK because it’s transformative. Some of them go so far as to say that any content on the web is free. There’s a deep sense of unfairness at play. OpenAI, for example, slurps up content which doesn’t belong to them, uses it to get billions in funding, and announces a $200/month subscription plan. Meanwhile, regular folks regularly get smacked around by lawyers for doing similarly transformative stuff. Heck, the Internet Archive isn’t even allowed to lend books, which I think is a very reasonable use of copyrighted material! 1 Because of this, even useful features that have a hint of “AI” get crapped on. Earlier this week I saw several posts on Bluesky linking to an article on The Register about an Apple Photos feature which detects landmarks, and which arrived in October. Many were upset about being automatically opted into something AI related. To me, this feature seems legitimately useful and it also seems like Apple has been more than responsible in terms of preserving privacy. It seemed to be a big deal because there’s “AI” at play. Only, according to the research paper, it’s actually using more traditional machine learning and not LLMs. I can maybe see an argument for having the feature to have been opt-in, but I also think it’s unreasonable for Apple to have a checkbox for every new feature in every point release. Meanwhile, what The Register is accusing Apple of is actually the sort of thing that Google does at every opportunity. My point here is that, like a lot of things these days, there seems to be a weird divide. Companies like Apple are currently trying to “AI” everything. Sometimes this makes sense to me, often it doesn’t. Meanwhile, there’s a chunk of the public that’s angrily opposed to anything vaguely AI-flavoured. There was a great discussion about this on Upgrade this week, which I recommend. Jason and Myke made a great case that Apple needs to be held more accountable when it screws up, and that it’s currently being graded on a curve because “LLMs make mistakes”. Apple seems to be pressured to play catch-up on AI technology, and I feel like this is being driven by activist shareholders instead of people who are focused on products. Apple has previously been a company to take their time and do things right. Their current AI strategy seems to be announce everything way too early and release some things before they’re ready. From the outside it feels like there was a dictate from on-high that everyone needs to drop what they’re doing and sprinkle AI everywhere. Like I said above, I think that generative AI is useful and interesting. I’m also someone who’s very interested in product design. Building a product that starts from a technology instead of a user need is ass-backwards. I really hope Apple is a bit more mindful as it continues to roll out future AI features. For whatever it’s worth, I square this circle personally because I believe that fair use of copyrighted material should be more permissive in general. The fact that large corporations can get away with copyright uses which most citizens can’t is an issue with our current implementation of capitalism, and needs to be addressed from the ground up. Companies like OpenAI are playing the game by the current set of rules, and boycotting their services won’t end that. ↩

At the end of last year, I wrote about wanting to focus on the web in 2024. How did that shake out? Top level stats I considered 2023 the first year that I honestly tried getting back into blogging. My goal then was to post something every month, and I managed that with 14 posts in total. This year I wanted to post something at least once a week, and I also met that goal with 79 posts (including this post). Overall I wrote 36,515 words on this site in 2024. My top five posts by traffic were: Maybe Bluesky has “won” Why isn’t the <html> element 100% supported on CanIUse.com? ACF has been hijacked Get yourself a /dev/lunch The hidden WordPress license Looking back on blog posts over the year January was a slower month for me, work-wise, and I was able to spend some time thinking about this site. I wrote a few things, and I’m still quite happy with Just write, you dolt and The library is a superpower, but February was when things really kicked off. I wrote a piece about a weird quirk of the Can I Use… website where no element (including html) was ever 100% supported. This got a large amount of traffic, and was the top post on Hacker News for a few hours. The rest of February though April were quieter. I experimented with posting some smaller items, but I couldn’t get that to stick. I’m still happy to have learned about the goofy Katamari Damacy patent images because of a copyright date oddity, as well as some TikTok ban thoughts that I still think hold up. May was another highlight for this site. I decided to participate in Weblog Posting Month at the last minute, having already posted something the day before. This was a fun experiment and I took away some lessons. I’ll likely give this another go this year, but I’ll give myself more leeway to post smaller things. June through the beginning of September were light, having somewhat burned myself out on posting in May. I didn’t post anything in August, which I still feel bad about. It was an extremely busy month for me, but I also feel like I fell off the wagon. Later in September and through October things kicked off again as I covered the still-ongoing WordPress vs. WP Engine drama. Several of the posts in this series got a lot of traffic, with ACF has been hijacked going viral. I’d been writing about Bluesky since mid-2023, and went from deep skepticism to begrudging support. In November, I wrote about how my feelings changed about the service in Maybe Bluesky has “won”. This turned out to be my biggest post by traffic ever. I also wrote about creating a small toy site to experiment with the Bluesky firehose. December was fairly low-key with a few small posts as I got some down time during the holidays. I used my iPad to post the last three pieces, which was a surprisingly pleasant experience. What’s next for 2025? As I’ve written before, the default publishing flow using Jekyll and GitHub Pages has become a headache. I plan to replatform, and I’m almost certainly going to use Eleventy for that. There are many things I’d like to improve on the site, and I don’t really want to build them on a creaky foundation. I plan to write more about this process as it moves forward. I also plan to do some incremental design tweaks. I’ve been using the same design since 2012 and have only slightly changed it over time. I don’t think I need a major redesign, but there are some additional things I’d like to add. Primarily, better archive navigation and adding post categories. I also want to add smaller posts more often, rather than having those thoughts live on someone else’s service first. I’m happy to use Mastodon and Bluesky for socializing and discussion, but I’d rather have links and small posts living on my own site. Finally, I want to build more small sites and projects. I used to do this a lot more, and I have no idea why I stopped. Building the Bluesky Filter was a fun afternoon project, and I was recently inspired by Robb Knight’s Mean Girls curio. I think I may have over-focused on the blogging part in 2024, and I want to correct that. Overall, I think this was a successful year in terms of upping my indie-web game. I hope to keep the momentum going next year.

Earlier this year, I looked into why Mastodon didn’t include referer headers. As someone who enjoys following web analytics, it seemed a shame that Mastodon appeared never to send any traffic. I knew this wasn’t the case, but that lack of traffic data certainly wasn’t doing Mastodon any favours in terms of marketing. Yesterday I saw this Mastodon post from Terence Eden. I haven’t been keeping tabs on social media and RSS sources as much over the last few weeks, so I missed his original blog post about this. Turns out, Mastoson servers now have an option to enable referer headers! This is enabled for everyone using Mastodon.social, as Terence and I both am. I think this is a great option, and I hope it’s something that other large servers enable. I don’t think it’ll affect things dramatically, but I appreciate anything that helps spread the word about Mastodon.