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

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.

Display Text toggle not working · Issue #25 · dshanske/syndication-links https://github.com/dshanske/syndication-links/issues/25

I've updated to the most recent and everything works properly (I've toggled through most, but not necessarily all of the various combinations).

The one that doesn't seem to be working is the "Display Text", which as I recall swapped between the icons only view and the actual text (eg. "Facebook"). It doesn't seem to matter whether the "Display Text" is checked or not, it only displays the icons.

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...

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.

Congrats! That sounds awesome. I hope when you've got the Bridgy Publish tweaks fixed up, you'll try to push them back into the original as I know David is still working on them and they sound pretty useful.

I've recently been using "SNAP" https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/ to syndicate out to most social networks (previously I'd been using a combination of Jetpack and manual). It adds a lot more fine tune ability about the where, when, and how of syndicating as well as allowing for re-syndicating. The Syndication Links plugin you mentioned also automatically sucks in the syndicated URL for display also.

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


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:
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.

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.

IndieWeb and Android Mobile

@dshanske I remember you mentioning it briefly the other day and then saw something more specific this morning: http://indiewebcamp.com/irc/2016-05-03/line/1462285944410

Have you hacked around with either Bookmarklet Free or URL Forwarder apps from the Google Play store? They’re mentioned in the following two places:
https://snarfed.org/easy-indieweb-interactions-on-android
http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and

I’d gotten URL Forwarder set up and configured to make mobile sharing for my WithKnown install to make bookmarking, sharing, reposting, and a few other functionalities work incredibly quickly and well. I’ve put off doing so on WP since I have some other back-end dependencies that need tweaking so that I don’t create redundant loops with some of my other configuration. With any luck one or the other will get you pretty far without having a full micropub application.

With these you can use Android’s ubiquitous sharing icon and share to one or the other of the apps which will do the URL scraping to be able to do some of the posting types you want. Depending on the output, you may need one or two additional tweaks, but it’ll give you a reasonable template for a workflow. I’m sure some further url parameters and integration could be put in to auto checking the correct post kind and thereby making your posts fully indieweb compatible on WP. Adding Indieweb Press This https://github.com/pfefferle/wordpress-indieweb-press-this/ functionality for bookmark, share, watching, listening, et al. would complete a larger cycle of functionality.

Then, I’m sure there’s the additional functionality of API calls to Twitter/Facebook/etc. to implement the actual retweet/like on the native platform, but that could be handled later/separately (though Bridgy Publish might be able to handle this? I seem to remember a mention of it in the bookmarklet set up.)

Finally, if “Post Properties” could import the same URL and scrape the metadata, the entire process would be almost too simple and not need a “traditional” mobile app at all.

For URL Forwarder the base settings should be:
Reply: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=reply&u=@url
Like: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=like&u=@url
Repost: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=repost&u=@url

Hopefully this gets you a few steps further on android mobile without a huge amount of work…

It looks like no one is maintaining this actively and the last patch was in 2014. Just keeping up with Twitter and Facebook API changes can be painful.

You might find similar functionality using a group of IndieWeb related plugins https://wordpress.org/plugins/indieweb/ much of which is in active development on GitHub as well. Documentation and additional information can be found at http://indiewebcamp.com/wordpress.

Some of the rest of the autoposting portions can be had through JetPack's Sharing functionality or alternately through NextScript's SNAP plugin: https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/

@veganstraightedge The facebook event for #indieweb LA 2016 got deleted somehow? https://www.facebook.com/events/590941321087314