Skip to main content
 

@Petersell I'm only doing POSSE for Medium on WordPress where I tend to post my longer content. I'm primarily using Known for shorter content, checkins, and mobile use. I imagine that you could POSSE from Known to Medium by hand, but it would be hacky at best.

 

Replied to a post on github.com :

Class entry-content div contains too much · Issue #470 · WordPress/twentysixteen https://github.com/WordPress/twentysixteen/issues/470

It appears that the <div class="entry-content"> spans more content than it should. (I'm actually a bit surprised that a modern facing theme like TwentySixteen doesn't fully support [microformats 2](http://microformats.org/wiki/microformats2) instead of the older microformats1 spec.)

Specifically I think that the entry-content div should end before the following functionalities when they're included:
<div class="sharedaddy> (Jetpack's Share This functionality),
<div id="jp-relatedposts"> (Jetpack's related posts functionality)
<div class-"author-info"> (Gravatar author information)

Essentially the semantic class "entry-content" should only contain the content written in the body of a post by the user and shouldn't really include the additional information by these other plugins.

As an example, by having entry-content include these additional pieces, users, when syndicating content semantically to other services like Tumblr, Facebook, or even RSS readers, will include this additional (often unwanted content). See also:
https://github.com/kylewm/KnownReactions/issues/11#issuecomment-224120974
https://github.com/dshanske/syndication-links/issues/23

Cross Reference: http://microformats.org/wiki/hentry

 

Replied to a post on github.com :

I'd mentioned something like this a while back at https://github.com/dshanske/syndication-links/issues/23 as I was seeing it in pop up in Woodwind.xyz and a few other places. I'm not quite sure what's causing the problem (which is sporadic and depends on who's resharing or where it's being resyndicated to.) In general it's not a problem with KnownReactions (really), but something to do with the WordPress install/configuration.

I'm hoping that @dshanske and the fix he mentioned clears it up, but if not I'll continue to look into it on the WP side, because I want to get rid of it too. This is the first time I've seen the "related", "author", and "share" this portions show up. Usually it's just the blank "Syndicated to" portions that sneak in. (I've also seen this with POSSE from WP to Tumblr as well as with Woodwind. I haven't seen it happen on many other platforms however.)

 
 
 

Replied to a post on github.com :

Excerpt not copying properly · Issue #7 · meitar/wp-crosspost https://github.com/meitar/wp-crosspost/issues/7

When I do this:
Post something on my self-hosted WP blog without anything in the "Excerpt" field

This happens:
The crosspost that appears on WordPress.com seems to have cut and pasted a portion of the body of the original along with the notice about the original post into the excerpt field.

Complicating things somewhat is that I'm using the 2016 theme which utilizes the excerpt as a magazine-like "kicker" or subtitle, so it publishes the excerpt as a teaser line between the title of the post and the traditional body of the post. With most themes this "bug" isn't as problematic as the excerpt is used as metadata, but in my case it's publishing content in a duplicative fashion.

Example:
Original post: http://boffosocko.com/2016/06/04/55673397/
Syndicated post: https://chrisaldrich.wordpress.com/2016/06/04/55673397/

As an aside, given your personal philosophy and the motivation behind this particular plugin and your tumblr crossposter, if you're not already aware of them, I thought I'd mention the [IndieWeb movement](http://indiewebcamp.com) which is firmly behind people owning their own data (as opposed to corporate silos like Facebook, Twitter, et. al. owning it) as well as their online identities. (It's also part of the reason I've been using this particular plugin). I suspect you'll appreciate their mission and potentially be able to use portions of their opensource code and related work.

 

Replied to a post on github.com :

Cannot redeclare class RelMe_Widget · Issue #36 · indieweb/wordpress-indieweb https://github.com/indieweb/wordpress-indieweb/issues/36

Just updated to the newest IndieWeb plugin and got:
Fatal error: Cannot redeclare class RelMe_Widget in /wp-content/plugins/indieweb/includes/class-relme-widget.php on line 87

I hadn't gotten a chance to do the update to Syndication Links yet. Could that be related? Do they both need to be updated simultaneously?

 
 

So it sounds like you really want is the https://wordpress.org/plugins/syndication-links/ which will give you a field under your content to show where the content was syndicated to (and properly mark the links up with rel-me).

I don't think brid.gy automatically puts the syndicated link into the field, so you'd have to do it manually. Other plugins like Social Network Auto Poster (SNAP) or using micropub with clients like OwnYourGram or OwnYourCheckin have intercompatibility with Syndication Links and those URLs will be sucked in automatically.

If you find issues like this, please file them in the github issues repositories for the appropriate plugin so that the issues are known and can potentially be fixed. (Naturally if you can code well enough, you may be able to patch them with a pull request too.)

 

@Bradamante in re: life http://etherpad.indiewebcamp.com/indieweb-life with regard to Twitter from this afternoon

I keep a primary site at www.boffosocko.com for longform and usually more substantive (whatever this means...) content while I use the Known platform through www.stream.boffosocko.com for shorter form content, checkins, status updates (Twitter), etc. Keeping my Twitter content is easier here because I don't expect any/many to subscribe to my stream site, so I'm not worried about spamming the world that may want to follow the more substantive stuff. I've tried to make using twitter with my stream as easy as possible by using a simple bookmarklet on desktop () and a simple sharing tool on mobile (http://indiewebcamp.com/Posting_from_mobile_devices)

One day, perhaps when I've over-configured my WordPress install to do things exactly the way I want them, perhaps I'll post it all to one site, but for now, it seems to work pretty well for me without being onerous for my (percieved) audience (hi mom!) :)

Fortunately there's a million ways to do all of this, you just have to find what works best for you.

 

I just finished importing all of my Instagram posts (PESOS) to www.boffosocko.com

 

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

 

B0RG, if you need it you can read some of the details I've sketched out at:
https://github.com/chrisaldrich/wordpress-indieweb/blob/ee1cfb72203f1feef05b9225c4bb465abc82e094/readme.md

Let us know if you need any additional help!

 

Replied to a post on github.com :

Embed for Tweets versus Blockquote (html/js) with Text? · Issue #10 · pfefferle/wordpress-indieweb-press-this https://github.com/pfefferle/wordpress-indieweb-press-this/issues/10

I've noticed that the IndieWeb Press This bookmarklet uses something like [embed]https://twitter.com/ChrisAldrich/status/707313378268618752 [/embed] in the main body of the content rather than the Twitter html/js embed method
(a la: <blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr"> etc... )

I suspect that WordPress is doing some processing on the back end with the [embed] short code to fetch and display the twitter card and thus isn't technically saving the actual content of the tweet the way the blockquote embed method does. In the event of a Twitter silo death, this could spell trouble for users losing the data.

Cross reference: http://techlifeweb.com/bookmarklets-for-indieweb-favorites-and-retweets/ and http://stream.boffosocko.com/2016/scott-i-love-the-concept-of-your-bookmarklets-and-how