Skip to main content
 

Scott Kingery's post on techlifeweb.com: Quick update. Own your gram is working as expected with likes/comments flowing back to my site so it look like everything is set up correctly.

 

I actually have some extra goodies for you that should now allow your blog to import likes and comments from instagram. There's also a way to set things up so that when you do instagrams they automatically post to your blog directly too. You'll have to call me to set part of it up... We should also catch up about the latest draft this week too -- I just got back from a vacation trip.

 

Another thing to try (temporarily) is to change themes to something like SemPress or Independent Publisher to see if the comments show up properly. You can preview it on your site without actually activating it.

 

Scott, in case you don't get the webmention/comment from http://stream.boffosocko.com/2016/semantic-linkbacks-plugin-is-for-showing-comments-like-this-on

Semantic linkbacks plugin is for showing comments like this on your site. Separately there are also syndication links which show you where you syndicated your posts to (Facebook, Twitter, et al.)

Do you have brid.gy set up properly? Also sometimes comments can be caught up in your spam/Akismet filter. Occasionally (but not usually -- I've only seen one case) some comments.php sections can be wonky and webmentions won't show up in your comments at all.

I know I sent you a webmention to one of your posts the other day. I'm presuming now that you didn't see it...

 

Replied to a post on github.com :

Updated and works wonderfully! Thanks. (I was worried it would be worse as I've heard from colleagues that IG has been pulling developer API access recently.)

Given the philosophy behind this plugin and your Twitter plugin, I thought I'd take a moment to mention http://www.indiewebcamp.com which is a developer movement to assist people in owning all of their own content/data rather than relying on corporate silos/walled gardens. Your plugins sit squarely in this philosophical area.

There is a suite of related plugins (see http://indiewebcamp.com/wordpress, http://indiewebcamp.com/WordPress/Plugins, and http://indiewebcamp.com/Getting_Started_on_WordPress) that do additional types of similar data import and improved functionality. One particular function you (and your users) may appreciate is some of the plugins in combination with a service at http://brid.gy allow one to backport comments and likes from instagram, twitter, facebook, and google+ onto one's associated post on WordPress. As an example see the comments on: http://boffosocko.com/2016/05/24/55672775/. The combination of the your plugin and some of these allow users to own all of their instagram activity outright.

If you're interested and free this weekend, they're streaming a big annual meeting from Portland http://indiewebcamp.com/2016.

 

Description and FAQ for IndieWeb WordPress Plugin

5 min read

I just wrote up a quick description for the IndieWeb plugin for WordPress. As a native IndieWebber, I thought I'd PESOS it from GitHub and share it out for those who might be interested. It's also a somewhat self-contained description why one should join the movement and points to some great resources.

Description

The IndieWeb Plugin for Wordpress is a bundled installer for a core set of IndieWeb-related plugins. It's meant to be a one-stop shop to help WordPress users quickly and easily join the growing IndieWeb movement (see below). Some of these sub-plugins are required while others are optional.

Some of these plugins allow you to:

  • send and receive comments, likes, reposts, and other kinds of post responses using your own site
  • allow comments on others' sites to show up as comments on your posts
  • help make IndieWeb comments and mentions look better on your site
  • allow support for threaded comments and webmentions
  • more easily syndicate your content to other sites to take advantage of network effects and other communities while still owning all of your original content
  • link to syndicated versions of a post so that comments on your content in silos like Facebook, Twitter, Instagram, Google+ can come back to your original post as comments there
  • allow you to add bookmarklets to easily respond/comment on other sites with one click
  • set up a MicroPub Server to use other posting interfaces. (You could potentially use services like Instagram, Foursquare, and others to post to your WordPress site.)
  • set up a personal URL shortener
  • log into your WordPress site with services like Twitter, GitHub, SMS, or even email using IndieAuth.

The IndieWeb

The IndieWeb is a people-focused alternative to the ‘corporate web’ that allows you to be the humb of your own web presence. It's been written about in Wired, The Atlantic, Slate, and Gigaom amongst others.

The IndieWeb, like WordPress, feels that your content is yours

When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.

The IndieWeb is here to help you be better connected

Your articles and status messages can be syndicated to all services, not just one, allowing you to engage with everyone in your social network/social graph. Even replies and likes on other services can come back to your site so they’re all in one place.

Interested in connecting your WordPress site to the IndieWeb? Let us help you get started.

Frequently Asked Questions

How do I get Started?

IndieWeb for WordPress includes a plugin installer program. A Getting Started Guide can be found under Plugins->IndieWeb.

Where can I find help? Can I contribute?

A group of web developers (including those knowledgeable about WordPress, among many other web technologies) can be found discussing and working on IndieWeb related technologies in the wiki at IndieWebCamp.com or in the IRC on Freenode. WordPress specific portions of the IndieWeb camp can be found at WordPress, Getting Started on WordPress, Examples, and other plugins.

If you need additional assistance, feel free to reach out to any of the WordPress Outreach Club members via the website, our individual websites, or our social media presences -- we're happy to help!

Why IndieWeb?

Find more information and details for the motivations for joining the IndieWeb at http://indiewebcamp.com/Why

What about plugin XYZ?

If you think we missed a plugin reference, please file an issue on Github.

What plugins are included in this package? Can I install them separately?

  • Webmention (Required) - allows you to send and receive by adding webmention support to WordPress. Mentions show up as comments on your site.
  • Semantic Linkbacks (Required) - makes IndieWeb comments and mentions look better on your site.
  • Webmention for (Threaded) Comments - Adds support for threaded comments for webmentions.
  • Webactions - Adds webaction markups to WordPress elements.
  • Post Kinds - Allows you to reply/like/RSVP etc to another site from your own, by adding support for kinds of posts to WordPress.
  • Syndication Links - Adds fields to a post to allow manual entry of syndication links as well as automatically from a supported syndication plugin. Fully supports Social, partial support for NextScripts: Social Networks Auto-Poster (aka SNAP).
  • MicroPub - A MicroPub Server
  • IndieWeb Press-This - Adds IndieWeb markup to the WordPress Press-This bookmarkets to allow you to respond on your site with one-click.
  • Hum URL Shortener - A personal URL shortener.
  • Indieauth - The plugin lets you login to the WordPress backend via IndieAuth. It uses the URL from the profile page to identify the blog user.

One could certainly download, install, and activate some or all of these plugins separately, but it is much quicker and easier to utilize the interface provided by this IndieWeb plugin to install and activate them. Note that some of these plugins may only be available on GitHub and are not yet on WordPress.org.

 

Also posted to GitHub:

wordpress-indieweb/readme.md at ee1cfb72203f1feef05b9225c4bb465abc82e094 · chrisaldrich/wordpress-indieweb https://github.com/chrisaldrich/wordpress-indieweb/blob/ee1cfb72203f1feef05b9225c4bb465abc82e094/readme.md

 

Congrats @raamdev for supporting microformats2 & better comments in @WordPress Independent Publisher theme https://github.com/raamdev/independent-publisher

 

Is it just me or has @sciencemagazine quit showing/allowing comments on articles? Perhaps a response to http://stream.boffosocko.com/2016/indieweb-raison-detre-55-freedom-of-the-press-trumps-atrocious

 

Replied to a post on github.com :

UX/UI enhancement: Blank syndication links being syndicated · Issue #23 · dshanske/syndication-links

![woodwind](https://cloud.githubusercontent.com/assets/5882943/15369012/8beee060-1ce5-11e6-90f1-df8f8d6a4ec5.PNG)

I've seen blank versions of syndicated links appear on various platforms, the one above is a capture from the reader Woodwind.xyz. I've also noticed it when syndicating to tumblr.com and Facebook (though I've removed it programatically since). I'm not sure if I've seen them display on other sources (in most cases I choose to use the icon versions rather than text, but could do a quick test to see if the text at least appears.) Since I'm sure there are others, I'm curious if there's a way to either fix how these show up (or not) or simply move them for POSSEd copies?

Thoughts on UX/UI:
I'm presuming that they're hooked onto the end of the_content(), which then means that they're being syndicated out as part of the body of the content. I would suggest that on most platforms, most people don't/won't care about the fact that there are syndicated copies (though for the near term of advertising the concept for the IndieWeb, keeping them may be valuable), particularly when they can view the primary source which ought to presumably have all the commentary and webmentions (by backfeed or other means).

Interestingly, I occasionally see, though not as often, the "Share This" data flow through in the same manner. In my case the share this appears _above_ the list of syndicated links: viz:
![share this](https://cloud.githubusercontent.com/assets/5882943/15369752/deb86c00-1ce8-11e6-9182-f0014f3a2938.PNG)
Is there some type of processing that Jetpack is doing to prevent this from syndicating as "content"?

The way I typically think about it, knowing about syndicated copies is mostly useful as a function of commenting rather than content, so that if someone comments in Facebook, for example, I go back to that silo to post a response, so their chosen platform can send notifications/emails etc about the interaction, and rely on webmentions to backport my own comment onto my site and to keep the flow of conversation on the original post rather than a separate post on my own site that points back to another. Perhaps then, the best default location for syndication links is within the comments section? This then solves the problem of syndicating out blank versions, but more closely associates the syndicated copies with the "conversation" about the post. Potentially putting them at the top of the comments section could also keep them relatively close to where they currently live as a default.

I pose most of this as ideas/potential suggestions, but I'm curious what others think in terms of what/how they use this functionality.

 

Congratulations! If you're not using the SemPress theme, you might also enjoy https://github.com/pfefferle/wordpress-uf2 which will do some of the mf2 material (as best it can) without remarking up your theme by hand. I've used a handful of WP themes with IndieWeb and not had problems sending/receiving webmentions (to my knowledge) or using other indiewebcamp.com goodness.

You might also appreciate the Independent Publisher theme, which is not only beautiful, but has some custom code for displaying comments, pingbacks/trackbacks, and even webmentions and will shortly have additional mf2 mark up as well (or should, in it's next release which is right around the corner.) The Github code is ahead of the official release on WordPress.org if you want to test it out.

 

I'm now trying out https://ownyourgram.com/ on WithKnown and it seems to work fairly well so far: http://stream.boffosocko.com/2016/ceiling-with-great-lighting-hardware

We'll see if we can't get the comments from Instagram to flow back as well.

 

Replied to a post on github.com :

Not receiving webmentions via Instagram on WP.org #671

I notice I'm not receiving likes/comments from Instagram via Bridgy (and apparently never have.)

I'm using OwnYourGram to PESOS Instagram photos into a WordPress (.org) site, which are then marked has having been syndicated using the Syndication Links WP plugin. The Instagram post naturally doesn't have a link to my web site's post, but my sites's post does have rel-syndication and u-syndication like so: `<a title="Instagram" class="u-syndication" href="https://www.instagram.com/p/BFcP4knxC6m/" rel="syndication"> </a>`

Is there some other smaller fine point I'm missing from the Brid.gy about page and support? Has anyone else seen this with WP (.org)?

Cross reference:
https://brid.gy/instagram/chrisaldrich#
https://www.instagram.com/chrisaldrich/
with post https://www.instagram.com/p/BFcP4knxC6m/ "syndicated" from http://boffosocko.com/2016/05/15/55672649/

 

Replied to a post on github.com :

You could start with http://indiewebcamp.com/Getting_Started_on_WordPress which will walk you through most of the process. You should start with the Webmention Plugin and Semantic Linkbacks to send/receive webmention support and to help comments look better respectively. Brid.gy connects your blog to responses from sites such as Facebook, Twitter, et al.

Keep in mind that some of the other plugins you'll run across may have small bugs or quirks as they're being actively developed. Most of the plugins in the WordPress.org repository are usually more stable than some you'll run across on GitHub, but those also are dated in terms of development work, so you'll have a better idea how current they are. You can usually find one or more of us via IRC, or in social media if you need help.

 
 

Replied to a post on github.com :

I played around with it a bit tonight. In general I like the fact that the webmentions are simple/short one liners listed last with the commenter's name (linked) along with whether they like, reposted, or mentioned the article and where.

Eventually at some point for very popular articles the list can get incredibly long at which point doing either a facepile (or even a simple list) would probably be preferable. Example
Liked by: John Smith, Bob Jones, Jane Chen, Larry Sommers, Charlie Brown
Reposted by: comma separated list of names
Mentioned by: list of names (wrapped with URL pointing to the mention)

In the end, some of this type of UI will depend on the site (perhaps it's an option in the theme? for n>some integer cutoff), but as it stands, the current solution you've given @raamdev is probably workable for the larger number of potential users.

Kudos on being one of the first themes to split this type of functionality out in your comments!!