People continued working on it. Everything you need using W3C standards like Webmention, Microformats2…give it a try? https://IndieWeb.org/WordPress/Plugins
I suspect that @chrismessina could do it quickly, but for those who’d like to leave Twitter for #WordPress with similar functionality (but greater flexibility and independence), I recorded a 2 hour video for an #IndieWeb set up/walk through with some high level discussion a few months back. If you can do the 5 minute install, hopefully most of the rest is downhill with some basic plugin installation and minor configuration. The end of the walk through includes a live demonstration of a conversation between a WordPress site on one domain and a WithKnown site running on another domain.
Post Kinds plugin (for better delineating articles, status updates (notes), replies, favorites, likes, etc. with appropriate microformats markup)
Aperture Plugin (allows you to sign into a variety of Microsub readers which also act as your stream and allow you to reply to others directly from your reading interface. This part is still a bit experimental, but the kinks are being worked out presently for a richer experience.)
For those watching this carefully, you’ll notice that I’ve replied to David Shanske’s post on his website using my own website and sent him a webmention which will allow him to display my reply (if he chooses). I’ve also automatically syndicated my response to the copy of his reply on Twitter which includes others who are following the conversation there. Both he and I have full copies of the conversation on our own site and originated our responses from our own websites. If you like, retweet, or comment on the copy of this post on Twitter, through the magic of Brid.gy and the Webmention spec, it will come back to the comment section on my original post (after moderation).
Hooray for web standards! And hooray for everyone in the IndieWeb who are helping to make this type of social interaction easier and simpler with every passing day.
Micropub Plugin work for WordPress
It will include a Media endpoint
Code for integration with the WordPress REST API
This sketch solution may be an end-around the issue of getting WordPress (or potentially other CMSes) Themes to be microformats 2 compatible, and allow a larger range of inter-compatibility for websites and communication.
Instead of 'eliminating' divisions, or 'blowing up' silos....let's use metaphors about bridging, connecting, unifying, transcending, collaborating across borders.... connecting all of the groups within an organization in a coherent way so that they all work seemlessly together.
As any kindergartner can tell you, “It’s difficult to play ball when the local bully owns the ball and wants to make up their own rules or leave in a huff.”
One of the things I love about IndieWeb is that we’re all trying to create a way for balls to be roughly standardized and mass manufactured so that everyone can play regardless of what the bully wants to do or what equipment people bring to the game.1
And as Nikhil Sonnad has reminded us very recently, we also need more than just connections, we need actual caring and thinking human interaction.2
My friend Alan Jacobs, a key inspiration in my return (such as it is, so far) to blogging and RSS and a generally pre-Twitter/Facebook outlook on the scholarly internet, is pondering the relationship between blogging and other forms of academic writing in thinking about his next project. Perhaps needless to say, this is something I’m considering as well, and I’m right there with him in most regards.
But there are a few spots where I’m not, entirely, and I’m not sure whether it’s a different perspective or a different set of experiences, or perhaps the latter having led to the former.
I really like where you’re coming from on so many fronts here (and on your site in general). Thanks for such a great post on a Friday afternoon. A lot of what you’re saying echos the ideas of many old school bloggers who use their blogs as “thought spaces“. They write, take comments, iterate, hone, and eventually come up with stronger thoughts and theses. Because of the place in which they’re writing, the ideas slowly percolate and grow over a continuum of time rather than spring full-formed seemingly from the head of Zeus the way many books would typically appear to the untrained eye. I’ve not quite seen a finely coalesced version of this idea though I’ve seen many dance around it obliquely. The most common name I’ve seen is that of a “thought space” or sometimes the phrase “thinking out loud”, which I notice you’ve done at least once. In some sense, due to its public nature, it seems like an ever-evolving conversation in a public commons. Your broader idea and blogging experience really make a natural progression for using a website to slowly brew a book.
My favorite incarnation of the idea is that blogs or personal websites are a digital and public shared commonplace book. Commonplaces go back to the 15th century and even certainly earlier, but I like to think of websites as very tech-forward versions of the commonplaces kept by our forebears.
There’s also a growing movement, primarily in higher education, known as A Domain of One’s Own or in shortened versions as either “Domains” or even #DoOO which is a digital take on the Virgina Woolf quote “Give her a room of her own and five hundred a year, let her speak her mind and leave out half that she now puts in, and she will write a better book one of these days.”
There are a growing number of educators, researchers, and technologists reshaping how the web is used which makes keeping an online commonplace much easier. In particular, we’re all chasing a lot of what you’re after as well:
Part of what I’m after is consolidating my presence online as much as possible, especially onto platforms that I can control.
To me, this sounds like one of the major pillars of the IndieWeb movement which is taking control of the web back from corporate social media giants like Facebook, Twitter, Instagram, et. al. Through odd serendipity, I came across your micro.blog account this morning which led me to your website. A lot of the underpinnings of micro.blog are informed by the IndieWeb movement. In many subtle ways, I might suspect the two had a lot of influence on your particular choice of WordPress theme.
Tonight I’ve also seen your reply to Dan Cohen’s question:
Has anyone set up WordPress so that “standard” post types continue to show up on your blog, but “status” (or “aside”) post types feed into social media platforms such as Twitter or https://t.co/kisv1mbGgT?
No worries! Replies/notifications stay within their own domains, for better or for worse. The good news is that the original post can reach people where they are; the bad news is that the conversation around it is increasingly diffuse.
Interestingly, your presumption that the replies/notifications stay within their own domains isn’t necessarily fait accompli, at least not any more. There’s a new web specification in the past few years called Webmention that allows notifications and replies to cross website boundaries unlike Twitter @mentions which are permanently stuck within Twitter. Interestingly, because of the way you’ve set up your WordPress website to dovetail with micro.blog you’re almost 90 percent of the way to supporting it easily. If you add and slightly configure the Webmention and Semantic Linkbacks plugins, the asides and other content you’re syndicating into micro.blog will automatically collect the related conversation around them back to your own posts thus allowing you to have a copy of your content on your own website as well as the surrounding conversation, which is no longer as diffuse as you imagined it needed to be. Here’s an example from earlier this evening where I posted to my site and your response (and another) on micro.blog came back to me. (Sadly there’s a Gravatar glitch preventing the avatars from displaying properly, but hopefully I’ll solve that shortly.)
This same sort of thing can be done with Twitter including native threading and @mentions, if done properly, by leveraging the free Brid.gy service to force Twitter to send your site webmentions on your behalf. (Of course this means you might need to syndicate your content to Twitter in a slightly different manner than having micro.blog do on your behalf, but there are multiple ways of doing this.)
I also notice that you’ve taken to posting copies of your tweeted versions at the top of your comments sections. There’s a related IndieWeb plugin called Syndication Links that is made specifically to keep a running list of the places to which you’ve syndicated your content. This plugin may solve a specific need for you in addition to the fact that it dovetails well with Brid.gy to make sure your posts get the appropriate comments back via webmention.
I’m happy to help walk you through setting up some of the additional IndieWeb tech for your WordPress website if you’re interested. I suspect that having the ability to use your website as a true online hub in addition to doing cross website conversations is what you’ve been dreaming about, possibly without knowing it. Pretty soon you’ll be aggregating and owning all of your digital breadcrumbs to compile at a later date into posts and eventually articles, monographs, and books.
In any case, thanks for sharing your work and your thoughts with the world. I wish more academics were doing what you are doing online–we’d all be so much richer for it. I know this has been long and is a potential rabbithole you may disappear into, so thank you for the generosity of your attention.
For a post today, I wrote on my own site and syndicated it to Twitter and got a reply back via webmention through Brid.gy. This process happens for me almost every day, and this all by itself feels magical. The real magic however, and I don’t think I’ve done this before or seen it done, was that I replied to the backfed comment on my site inline and manually syndicated to Twitter using a permalink of the form http://www.example.com/standard-permalink-structure/?replytocom=57527#respond, where 57527 is the particular comment ID for my inline comment. (This comment ID can typically be found by hovering over the “Reply” or “Comment” button on one’s WordPress website in most browsers.)
I’ve now got a nested copy of the conversation on my site that is identical to the one on Twitter.
I suspect that by carefully choosing the URL structure you syndicate to Twitter, you’ll allow yourself more control over how backfed comments from Brid.gy nest (or don’t) in your response section on your site.
Perhaps even more powerfully, non-WordPress-based websites could also use these permalinks structures for composing their replies to WordPress sites to have their replies nest properly too. I think I’ve seen Aaron Parecki do this in the wild.
Since the WordPress Webmention plugin now includes functionality for sending webmentions directly from the comments section, I’ll have to double check that the microformats on my comments are properly marked up to see if I can start leveraging Brid.gy publish functionality to send threaded replies to Twitter automatically. Or perhaps work on something that will allow automatic replies via Twitter API. Hmmm…
Despite the fact that this could all be a bit more automated, the fact that one can easily do threaded replies between WordPress and Twitter makes me quite happy.
I announced recently that Bridgy Publish for Facebook would shut down soon. Facebook’s moves to restrict its API to improve privacy and security are laudable, and arguably ...
This is so disappointing. Facebook is literally killing itself for me. So much for their “connecting everyone” philosophy.
Brid.gy was the last thing really keeping me connected to Facebook at all. Now that Facebook is shutting down its most useful functionality from my perspective, perhaps it’s time to deactivate it and move toward shutting it all down?
Summary: Facebook has recently announced it will be shutting off its API access on August 1st for automating posts into its ecosystem. For a large number of users this means it will be much more difficult to crosspost or syndicate their content into the platform. As a result, this week David Shanske and I discuss the good and the bad of this move as well as some general thoughts around the ideas of syndicating content from one site to another.
David also discusses plans he’s got for changes to both the Bridgy Publish Plugin and the Syndication Links Plugin.
I’ve decided to take a different direction for the Bridgy plugin for WordPress. I’ve never quite been able to explain to people it doesn’t actually do anything. It’s a user interface for the Bridgy service. I’ve decided that the best thing to do is to is to change the approach radically.
I have some functionality in the Bridgy app that allows someone to register for Bridgy for various services. I'm thinking of moving this functionality into the Indieweb plugin. All it is is a series of links that redirect you to the Bridgy site and redirect back when done.
That seems like Indieweb plugin territory.
I think there’s certainly a case to be made that it may make sense to include it in the IndieWeb plugin, particularly as it’s often a one time set up operation.
I also think that it might make a lot of sense to put that piece into the Syndication Links plugin as well since that’s a piece that directly relates to something Brid.gy is looking for to do backfeed. Doing this may also make even more sense if Syndication Links becomes a tool for POSSE as well. It would be nice to have a definitive one-stop-shop for syndication and backfeed related functionality.
As a “throw-away” aside, if you’re looking for a good name for such a thing, perhaps Boomerang? Throw your content out there and all the responses return back to your site?
I spent some time this morning doing a dry run through setting up a suite of IndieWeb plugins on a fresh WordPress installation. Going off of a scant outline I talked for almost two hours describing IndieWeb functionality as I set it all up. Hopefully it will provide a useful guide to newcomers to the space until I can write up a more solid outline and take a more polished approach. Apologies in advance for the roughness of the audio, lack of quality, and even live mistakes. Hopefully folks won’t mind suffering through until we can come up with some better tutorials.
As prerequisites, I assume you’ve already got your own domain and have installed WordPress on a server or other host. I actually finish setting up the WordPress install as I start the video and then sign in for the first time as we begin.
While many of the core plugins are straightforward, there is a huge amount of leeway in how folks can choose (or not) to syndicate to sites like Twitter, Facebook, and others. Here I make the choice to use the Bridgy Publish plugin and only demonstrate it with Twitter. With one example shown, hopefully other silos can be set up with Brid.gy as well. The IndieWeb wiki details other options for those who want other methods.
At the end I walk through creating and syndicating a post to Twitter. Then I demonstrate commenting on that post using another CMS (WithKnown) from a separate domain.
I do my best to provide verbal descriptions and visual examples, but these can certainly be supplemented with further detail on the IndieWeb wiki. I hope to come back and add some diagrams at a later date, but this will have to suffice for now.
For those who would like an audio only version of this talk, you can listen here (.mp3):
...holy crap this stuff [IndieWeb] is great. When I started getting webmentions from social media using Bridgy I flipped. It's like we're in the future!!!
I remember the early days of Twitter when people were excited about what it was and what it could do. Even then I don’t think people were as excited as Chris Beckstrom was when he made what is certainly the IndieWeb quote of the week this morning.
This week, using the magic of open web standards, I was able to write an issue post on my own website, automatically syndicate a copy of it to GitHub, and later automatically receive a reply to the copy on GitHub back to my original post as a comment there. This gives my personal website a means of doing two way communication with GitHub.
This functionality is another in a long line of content types my website is able to support so that I’m able to own my own content, yet still be able to interact with people on other websites and social media services. Given the number of social sites I’ve seen disappear over the years (often taking my content with them), this functionality gives me a tremendously larger amount of control and ownership over my web presence and identity while still allowing me to easily communicate with others.
In this post I wanted to briefly sketch what I’ve done to enable this functionality, so others who are so inclined can follow along to do the same thing.
Setting up WordPress to syndicate to GitHub
I’ll presume as a first step that one has both a GitHub account and a self-hosted WordPress website, though the details will also broadly apply to just about any content management system out there that supports the web standards mentioned.
Register your GitHub account and your website with Bridgy
Ryan Barrett runs a fantastic free open sourced service called Bridgy. To use it you’ll need the microformat rel=“me” links on both your GitHub account and your website’s homepage that point at each other. GitHub will do most of the work on its side for you simply by adding the URL of your website to the URL field for your GitHub account at https://github.com/settings/profile. Next on your website’s homepage, you’ll want to add a corresponding rel=“me” link from your website to your GitHub account.
In my case, I have a simple widget on my homepage with roughly the following link: <a href="https://github.com/username">GitHub</a>
in which I’ve replaced ‘username’ with my own GitHub username. There are a variety of other ways to add a rel=“me” link to your webpage, some of which are documented on the IndieWeb wiki.
Now you can go to Brid.gy and under “Connect your accounts” click on the GitHub button. This will prompt you to sign into GitHub via oAuth if you’re not already logged into the site. If you are already signed in, Brid.gy will check that the rel=“me” links on both your site and your GitHub account reciprocally point at each other and allow you to begin using the service to pull replies to your posts on GitHub back to your website.
To allow Brid.gy to publish to GitHub on your behalf (via webmention, which we’ll set up shortly), click on the “Publish” button.
Install the Webmention Plugin
The underlying technology that allows the Bridgy service to both publish on one’s behalf as well as for the replies from GitHub to come back to one’s site is an open web standard known as Webmention. WordPress can quickly and easily support this standard with the simple Webmention plugin that can be downloaded and activated on one’s site without any additional configuration.
For replies coming back from GitHub to one’s site it’s also recommended that one also install and activate the Semantic Linkbacks Plugin which also doesn’t require any configuration. This plugin provides better integration and UI features in the comments section of one’s website.
Install Post Kinds Plugin
The Post Kinds Plugin is somewhat similar to WordPress’s Post Formats core functionality, it just goes the extra mile to support a broader array of post types with the appropriate meta data and semantic markup for interacting with Bridgy, other web parsers, and readers.
Download the plugin, activate it, and in the plugin’s settings page enable the “Issue” kind. For more details on using it, I’ve written about this plugin in relative detail in the past.
Install Bridgy Publish Plugin
One can just as easily install the Bridgy Publish Plugin for WordPress and activate it. This will add a meta box to one’s publishing dashboard that, after a quick configuration of which social media silos one wishes to support, will allow one to click a quick checkbox to automatically syndicate their posts.
Install the Syndication Links Plugin
The Syndication Links plugin is also a quick install and activate process. You can modify the settings to allow a variety of ways to display your syndication links (or not) on your website if you wish.
This plugin will provide the Bridgy Publish Plugin a place to indicate the permalink of where your syndicated content lives on GitHub. The Bridgy service will use this permalink to match up the original content on your website and the copy on GitHub so that when there are replies, it will know which post to send those replies to as comments which will then live on your own website.
You should now be ready to write your first issue on your website, cross post it to GitHub (a process known in IndieWeb parlance as POSSE), and receive any replies to your GitHub issue as comments back to your own website.
Create a new post.
In the “Kinds” meta box, choose the “Issue” option.
Type in a title for the issue in the “Title” field.
In the “Response Properties” meta box, put the permalink URL of the Github repopository for which you’re creating an issue. The plugin should automatically process the URL and import the repository name and details.
In the primary editor, type up any details for the issue as you would on GitHub in their comment box. You can include a relatively wide variety of custom symbols and raw html including
and with code samples which will cross-post and render properly.
In the GitHub meta box, select the GitHub option. You can optionally select other boxes if you’re also syndicating your content to other services as well. See the documentation for Bridgy and the plugin for how to do this.
Optionally set any additional metadata for your post (tags, categories, etc.) as necessary.
Publish your post.
On publication, your issue should be automatically filed to the issue queue of the appropriate GitHub repo and include a link back to your original (if selected). Your post should receive the syndicated permalink of the issue on GitHub and be displayed (depending on your settings) at the bottom of your post.
When Bridgy detects future interactions with the copy of your post on GitHub, it will copy them and send them to your original post as a webmention so that they can be displayed as comments there.
If you frequently create issues on GitHub like this you might want a slightly faster way of posting. Toward that end, I’ve previously sketched out how to create browser bookmarklets that will allow you one click post creation from a particular GitHub repo to speed things along. Be sure to change the base URL of your website and include the correct bookmarklet type of “issue” in the code.
The Post Kinds plugin will also conveniently provide you with an archive of all your past Issue posts at the URL http://example.com/kind/issue/, where you can replace example.com with your own website. Adding feed/ to the end of that URL provides an RSS feed link as well. Post Kinds will also let you choose the “Reply” option instead of “Issue” to create and own your own replies to GitHub issues while still syndicating them in a similar manner and receive replies back.
Given the general set up of the variety of IndieWeb-based tools, there are a multitude of other ways one can also accomplish this workflow (both on WordPress as well as with an infinity of other CMSes). The outline I’ve provided here is one of the quickest methods for beginners that will allow a relatively high level of automation and almost no manual work.
One doesn’t necessarily need to use the Post Kinds Plugin, but could manually insert all the requisite HTML into their post editor to accomplish the post side of things via webmention. (One also has the option to manually syndicate the content to GitHub by cutting and pasting it as well.) If doing things manually this way is desired, then one will need to also manually provide a link to the syndicated post on GitHub into their original so that Bridgy can match up the copy and the original to send the replies via webmention.
If you’ve followed many of these broad steps, you’ve given already given yourself an incredibly strong IndieWeb-based WordPress installation. With a minimal amount of small modifications you can also use it to dovetail your website with other social services like Twitter, Facebook, Flickr, Instagram, Google+ and many others. Why not take a quick look around on the IndieWeb wiki to see what other magic you can perform with your website!
I’ve documented many of my experiments, including this one, in a collection of posts for reference.
If you have questions or problems, feel free to comment below or via webmention using your own website. You can also find a broad array of help with these plugins, services, and many other pieces of IndieWeb technology in their online chat rooms.