It dawns on me that I haven’t used JetPack’s Publicize or social sharing functionalities in ages (particularly with the coming death of Google+), so I’ve gone in and finally turned them off. I’m still surprised they don’t return the URLs of where the content got shared for showing on the page with plugins like Syndication Links.
David Shanske has recently updated the Syndication Links plugin for WordPress that now allows users to add custom syndication endpoints to their websites so they can actually syndicate their content to external sites.
In particular, this now includes syndication endpoints like IndieWeb News and indieweb.xyz subs. Configuring the plugin with a syndication name, UID, and the appropriate URL will create additional endpoint checkboxes in the “Syndicate To” metabox. (The UID is simply a unique identifier that the plugin uses in conjunction with Micropub clients, and the URL is the appropriate full URL to the appropriate syndication target.)
If one wishes to test syndication out, I might suggest using the test endpoint provided by indieweb.xyz. The appropriate entries in the custom provider section at
/wp-admin/admin.php?page=syndication_links would be:
For convenience, the settings page also allows the user to disable (via checkbox) endpoints they don’t use or don’t want to appear in their administrative meta boxes.
Use with Micropub Clients
The update to the Syndication Links plugin also means that Micropub clients with appropriate support (like Quill, for example) will know about which syndication endpoints your site supports and will be able to include them in its checkbox list for auto-syndicating via Micropub.
Naturally, people using these methods should be very careful about how they’re using them so that they aren’t abusing or spamming these channels. Those abusing these channels will certainly find their sites blocked from posting. Keep in mind that some of the syndication endpoints shown here are examples and that other endpoints exist or can be created on sites like indieweb.xyz.
Bridgy for WordPress
I’ll also note in passing that the syndication functionality to Twitter, Flickr, and GitHub that the Bridgy for WordPress Plugin provides is now also available within the Syndication Links plugin, so those who already have Brid.gy set up with their websites can easily and safely deactivate and uninstall that plugin. Doing this will prevent the duplication of meta boxes in one’s admin UI. Given the migration of some of its functionality, it is certainly possible in the future that this plugin may be deprecated or the Brid.gy set up portion of its functionality may be merged into another plugin like the IndieWeb plugin.
With the most recent update I’m noticing a few small edge case quirks that seem to have popped up:
For syndication to indieweb.xyz the displayed result (set for icon only) is giving a relatively interesting “info” icon,which is a reasonable proxy, but sadly the hover text is also “info” instead of a more useful or expected “indieweb.xyz”.
For syndications to reading.am (which I’m guessing still doesn’t have a service specific icon) instead of giving the old default image of a globe icon, it’s not displaying anything at all. I haven’t tested specifically, but are unmapped urls still given that old default icon?
I’m still seeing issues with my chrisaldrich.wordpress.com URL. Previously it displayed a blank space (presumably not able to understand the inpub), but the newer version is displaying the word “WordPress” even when I’m using icons only. (Example: https://boffosocko.com/2019/02/14/a-sketch-for-an-indieweb-bullet-journal/#Syndicated%20copies) My initial inclination is that the two instances of “WordPress” at https://github.com/dshanske/syndication-links/blob/057733d921b485cf8f0eb98b28b104ccb708bd21/includes/class-syn-meta.php#L333 are both CamelCase when all the other examples around/near that segment of code are all lower case.
Today, from my hotel room in Berlin, Germany, where I am preparing to attend Indiewebcamp Berlin, my first European Indiewebcamp, I released Syndication Links 4.0.0. The major version number change is because in this version, Syndication Links takes on a new role. As promised previously, I’ve buil...
Yet another update from the unstoppable David Shanske! I can’t wait to try this out.
I’ve seen a bunch of new folks coming into the IndieWeb community recently who are a bit overwhelmed with the somewhat steep learning curve of both new jargon as well as new ideas and philosophies of what it means to have one’s own domain and presence on the internet.
While parts of the IndieWeb’s overall idea are quite simple, where the actual rubber meets the road things can be a bit overwhelming, and more so if you’re a non-technical person. This doesn’t have to be the case. Generally I’d recommend to people to begin attending local Homebrew Website Clubs or, even better, to attend an IndieWebCamp in person to get a one day crash course followed by a day of building and help. Sadly, life can intervene making these not as quick and immediate a reality as one might otherwise like.
So toward the end of making the crash course to explain in relatively broad terms some of the basic terminology as well as some of the bigger individual pieces and what’s happening when using an IndieWeb site with most of the major new functionality built in, I’ve made a short pencast of what is going on. Naturally there’s still a tremendous amount to learn and do, and a million things which could always be better or improved, but if you’re setting up a site using WordPress this overview will hopefully get you a lot further a lot faster. (It may also be useful for those setting up Known or even something for micro.blog, though those will have different plugins and other small quirks that aren’t covered here.)
What is a Pencast?
Pencast?! What is that? It’s a technology that has been around for a while courtesy of Livescribe.com digital pens which not only record an audio file of what is being said, but also record penstroke by penstroke what is being written. Even better the audio and the penstrokes are crosslinked, so you can more easily jump around within a lecture or talk.
To do this you should download the version of the notes in Livescribe’s custom Pencast .pdf format. This seems like a standard .pdf file but it’s a bit larger in size because it has an embedded audio file in it that is playable with the free Adobe Reader X (or above) installed. With this version of the notes, you should be able to toggle the settings in the file (see below) to read and listen to the notes almost as if you were sitting with me in person and I was drawing it out in front of you as I spoke. You can also use your mouse to jump around within the pencast by touching/mousing to particular areas or by jumping forward and back by means of the audio bar. If you need to, also feel free to zoom in on the page to have a closer look.
Viewing and Playing a Pencast PDF
Pencast PDF is a new format of notes and audio that can play in Adobe Reader X or above.
You can open a Pencast PDF as you would other PDF files in Adobe Reader X. The main difference is that a Pencast PDF can contain ink that has associated audio—called “active ink”. Click active ink to play its audio. This is just like playing a Pencast from Livescribe Online or in Livescribe Desktop. When you first view a notebook page, active ink appears in green type. When you click active ink, it turns gray and the audio starts playing. As audio playback continues, the gray ink turns green in synchronization with the audio. Non-active ink (ink without audio) is black and does not change appearance.
Audio Control Bar
Pencast PDFs have an audio control bar for playing, pausing, and stopping audio playback. The control bar also has jump controls, bookmarks (stars), and an audio timeline control.
Active Ink View Button
There is also an active ink view button. Click this button to toggle the “unwritten” color of active ink from gray to invisible. In the default (gray) setting, the gray words turn green as the audio plays. In the invisible setting, green words seem to write themselves on blank paper as the audio plays.
If you have comments or feedback, I’m thrilled to receive it. Feel free to comment below, or if you’ve already IndieWebified your site, write your comment there and send it to me via webmention, or add your permalink to the box below. Ideally this version of the pencast is a first draft and I’ll put something more polished together at a later date, but I wanted to get this out there to have a few people test-drive it to get some feedback.
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):
I noticed that Kartik has an an original-of page at https://kartikprabhu.com/original-of which may have inspired the original-of URL functionality for use in Syndication Links.
For improved UI, is there a code snippet that could be created (or which already exists?) that could be added to a custom page to allow the creation for a simple search for such things the way Kartik has done? I’m thinking of something along the lines of
<?php get_search_form(); ?> which can be added to 404 page templates to allow the addition of a search box on such a page to get the user moving in the right direction.
This type of
original-of search functionality could also be added to a simple widget as well so that one doesn’t need an entire page for it. Suggested verbiage: “Have a social media permalink for a piece of content? Use it here to search for the original version on this site.”
I’m verifying, for the tape since I know you don’t use Mastodon Autopost, that this works as expected now.