Update to the Syndication Links plugin for WordPress for Custom Endpoints

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:

  • Name: xyz hottubs
  • UID: xyz-hottubs
  • URL:  https://indieweb.xyz/en/hottubs/
Settings for configuring custom syndication endpoints in the Syndication Links plugin

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.

An example of the meta box that appears in the administrative interface when creating new posts. To syndicate your content to the desired sites using Webmention, just click the appropriate 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.

Example Quill micropub interface with syndication endpoints configured within Syndication Links plugin

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.


👤  Chris McLeodJoe Jennett, and Khürt Williams may appreciate this the most for use with indieweb.xyz. It may be a minute too late for Brad Enslen however.

11 thoughts on “Update to the Syndication Links plugin for WordPress for Custom Endpoints”

  1. Thank you for writing this up Chris. As much as I subscribe to the various Github repositories and the IndieWeb Podcast, I always seem to miss the addition of new functions. The ability to add your own endpoints makes me wonder about the possibility of syndicating posts from my main site to this te?

    1. Khürt, I’ve been using WordPress Crossposter almost since it came out and have never had any major problems with it. (I’ll note that I’m also using the Classic Editor instead of Gutenberg, so mileage may vary with that particular variable.) I think the developer still actively uses it and is open to fixing bugs/issues, but other than a few known quirks (which are usually issues with WP.com only supporting a subset of what WP.org is capable of) I suspect it’s fairly solid. Are you having particular issues with it?

      Syndication via POSSE from .org to .com using Syndication Links is doable, but would require some reasonable amount of coding as a plugin/sub-plugin to enable Syndication Links to handle it. If you wanted, you could register an issue on the Syndication Links GitHub repo to start a discussion with others or potentially attempt to hack on it yourself. I’m not sure it would rank high on David Shanske’s to do list since I don’t think he has or mirrors content to a .com site and there are other means for doing it.

      Another option I’m aware of is the Social Network Auto Poster (SNAP) which I think also does syndication to WP.com websites, though I’ve never tried it personally. I suspect there are likely other methods/plugins, but haven’t had the need to try to use them.

      Another basic fallback is using any number of RSS plugins which could be put on a .com site to pull in content from a .org-based site.

      I’ll also mention that though I do this sort of syndication myself, I’m honestly not sure how valuable it really is in the grand scheme of things, and have been recently evaluating if I’m going to continue doing it. Have you gotten more readers/reach or experienced positive benefits in doing it yourself?

      1. Thanks, Chris. I’m more concerned that’s it’s abandoned software and hence not likely to get a response should security issues arise. The SNAP seems like so much bloat to use to do this one thing. Syndication to WordPess.com was more about backup than reaching an audience. My website already shows up in WordPress.com Discovery which has a larger and more diverse audience than micro.blog or mastodon. I know some have taken a radical approach of shunning any syndication to social media, but I noticed a significant drop in viewership and responses when I did that. Discovery is nigh impossible without participation in the larger conversations.

Mentions

  • Beko Pharm
  • Kicks Condor
  • Bryan Ruby | socPub
  • Chris McLeod
  • Brad Enslen

Leave a Reply

Your email address will not be published. Required fields are marked *