Remember WordPress' Pingbacks? The W3C wants us to use them across the whole web
'Webmentions' spec promises future linkspam outbreak
Something called Webmentions – which looks remarkably like the old WordPress pingbacks, once popular in the late 2000s – is grinding through the machinery of the mighty, and slow-moving, World Wide Web Consortium (W3C).
But don’t be deceived. Lurking behind that unassuming name lies something that might eventually offer users a way of ditching not just Facebook and Twitter but also those other massive corporations straddling the web.
Some web standards begin with little more than an idea and a healthy dose of optimism, but that's not the case with Webmentions, which was recently released as a first Public Working Draft from the W3C.
The spec itself may be at the early draft stage, but Webmentions are already being used around the web. The publication of the spec just throws some weight behind the idea and "paves the cow path," which is to say it abstracts and standardizes something that's already being used.
Paving the cow paths has given the web native video, CSS animations and half a dozen other things that were once only possible with non-standard tools such as Adobe Flash. The cow path that Webmentions hopes to pave is how to have linked, threaded conversations across the web.
The Webmentions spec grew out of the IndieWeb movement, which is a loosely joined group of developers focused on building personal websites – in its own words, "a people-focused alternative to the 'corporate web'".
One of the core ideas of the IndieWeb is that when you post something on the web, it should be yours. It should not belong – as your Tweets and Facebook posts do – to a corporation. Aside from the basic humanist principles of self-reliance, and political notions of property, much of the appeal in avoiding corporate silos is that eventually the companies go out of business and take all your data with them.
The IndieWeb solution to these problems is to run your own site, retain full control over your data and syndicate it to those corporate sites so that you can still participate in the larger conversation.
It's the larger conversation that creates some problems, though. There is, after all, a reason we've all gravitated toward hosted services such as Twitter and Facebook. It's not that users love giving their data to corporations; it's that those corporations have solved important problems – like how to aggregate, organize and display conversations. Twitter, for example, is little more than a real-time RSS feed, but it connects conversations in a way that RSS never did.
This is where the Webmentions come in: the goal is to standardize a way to link together conversations across the web. A Webmention is a simple way to notify any URL when you link to it from your site. Consider this scenario: Alice publishes a blog post. Bob writes a response to Alice's post and links to it. On the web as it is today the only real way Alice ever knows about Bob's post is if someone tells her or if she sees incoming traffic in her logs.
Webmentions is a framework for connecting these two posts such that, if Alice's site accepts Webmentions, Bob's publishing software can automatically notify Alice's server that her post has been linked to in Bob's post.
Once Alice's site is aware of Bob's post, Alice can decide if she wants to show Bob's post as a comment on her site or link to it from her post – and if she responds with another post, then the conversation can continue.
Webmentions can also help pull some of the conversation out of the corporate sites and back onto your own. The Brid.gy service takes comments, likes, re-tweets, replies and other interactions from popular sites like Twitter, Facebook, Instagram and Flickr and converts them into Webmentions. This allows developers to focus on supporting just Webmentions rather than needing to write a separate tool for each service's API. By the same token there's a service (webmention.io) to handle sending Webmentions to other sites.
The Webmentions spec doesn't have much to say about what your site should do with the content at the other end of the "mention"; rather, it specifies how the two sites communicate and make the connection in the first place.
Webmentions are already being used in the wild, and how the mentions are handled varies widely. Some people publish links to mentions – making Webmentions appear somewhat like the once-popular Pingback concept - others pull in the entire content and display it a bit like a comment. Indeed, Webmentions are similar to Pingback, but eliminate Pingback's XML-RPC format in favor of simple HTTP and x-www-urlencoded content. Even the inventor of Pingback now uses Webmentions.
So far the use of Webmentions in the wild is limited enough that spam is only beginning to happen. Eventually, though, the spam problem that haunts comment systems will inevitably come to Webmention. The spec doesn't directly address spam but services like Akismet make eliminating comment spam more manageable and would work just as well with Webmentions (there's also an additional proposal named Vouch for cutting down on spam).
The Webmentions specification is far from an actual standard. It's still in the early stages. Spec author Aaron Parecki says the next step is to get feedback.
"We need more implementations and more feedback from people who are actually using the spec," according to Parecki.
Interested developers can start building Webmention tools today. If you'd like to play around with Webmentions on your own site, there are plugins available for WordPress, Drupal and other publishing systems. If you don't yet have a site, there's Known, a service that sends and receives Webmentions. ®
Sponsored: 2016 Cyberthreat defense report