The upshot was that Google Reader was both the standard bearer and pall bearer for RSS at the same time.
While quickly discussing an issue (where native comments from others were posted as from me on micro.blog) Aaron Parecki pointed out on the #indieweb slack that the microformats markup was incomplete in that the comments were missing h-cards.
Colin Devroe wrote a thorough and thought-provoking response to my most recent musings on replies and comments. I would urge you to check it out.
He makes some very interesting and compelling points while outlining his particular answer to the question about comments.
Blogging is a particularly singular and personal act despite your posts being publicly available – the unedited voice of a person and all that.
Reading and commenting on blog posts, however, is an inherently social act carried out on a range of scales. Unfortunately, over the years, we have slipped towards the lower end of that range.
In a kind of “end of chapter 1” post over at AltPlatform, Richard McManus has been able to articulate something that I’ve been going in circles around but never quite settling on.
In the latest episode of the Core Int podcast Manton re-emphasised that micro.blog is a blogging platform rather than a social network.
It’s flexibility, however, means it can be different things to different people.
Well, yesterday’s post caused a bit of discussion (and, frankly, that was always the intention) but it was largely denied that there was any kind of existential crisis within the indieweb community.
Alex Kearney wrote about her first two years of indieweb. It makes for a very interesting read.
One thing that really came through was the confusion people feel when looking to “join the #indieweb” – it illustrates a common misconception that sites have to implement every bit of technology going.
The widespread adoption of #indieweb technologies will only happen if it is made simple, maybe even simpler than the alternatives.
This will likely only happen by stealth, by introducing it as core functionality rather than something that needs to be manually configured.
Since raising the version of the ‘Likes and Replies’ plugin to 0.9.0 and calling it a release candidate I don’t think I’ve come across any problems. It’s hard to believe that the last commit logged on GitHub was 17 days ago.
I never actually considered Twitter to be a microblogging platform, at least not for my own purposes.
At its most basic level your Twitter profile fits that brief (a reverse chronological list of short posts from a single author) but the lack of true ownership and the overarching social aspect meant I could never really see it as such.
Des asked if I was planning to release my Webmentions Directory as a plugin rather than a page template.
I hadn’t considered it but he got me thinking.
I wondered about the best way to do it and came up with creating a shortcode that can be entered on any post or page, and also in a template with the
I have been wondering recently if the name of this blog, Social Thoughts, is still relevant or valid.
When talking about ‘social’ in the context of the web we are normally referring to social networks – the mainstream players like Facebook, Twitter, Instagram – but I haven’t been writing about them very much lately.
There are times when I feel like a bit of an idiot. This is one of those times!
As you will no doubt recall, I was trying to separate out the plugin actions into various included files. The relevant code triggered correctly when posting via the REST API (I.e. from Workflow) but the action that should be run when posting natively failed.
What started as a quick update to split the plugin into parts (so that it wasn’t all one monolithic file) became quite a major one.
My original plan was to move both hooks for updating the post content to separate included files – it hasn’t quite gone according to plan.
Ten years is an eternity in internet time – we’ve come so far but, in some ways, taken backward steps so it’s easy to get nostalgic.
We can each do our bit to reclaim the spirit of the old web.
After getting the meta box working I realised that the code hooked into
save_post wasn’t being triggered when posting via the Workflow app.
The app is probably using the WordPress REST API to create the post which doesn’t behave in the same way as native posting and bypasses the hook.
Numerous tutorials exist for adding and using meta boxes; some manage to make it seem like a dark art by rushing through too much in one go without explaining exactly what is going on.
The web is broken, at least in how it rewards content and creativity. The attention economy favours extremes in the name of views and ad impressions with social platforms accused of compounding the problem. But there is a growing backlash.