Parallelism of display with common Jetpack plugins · Issue #29 · dshanske/syndication-links https://github.com/dshanske/syndication-links/issues/29

I was looking at some CSS and noticed a few things that could be tweaked on the output.

As I suppose is reasonably common, many people on WP will be using one or more Jetpack features in addition to Syndication-Links. (I suspect many Gen 2-4 IndieWeb users will rely on Jetpack for syndication for its ease of use.) As a result, it would be nice if Syndication Links had a (default) parallel structure and mark up to "Like", "Share" and "Related Posts" within Jetpack.

To do this I'd suggest something like the following modified structure which Jetpack uses:
```
<div class="sharedaddy">
::before
<h3 class="relsyn sd-title">Syndicated to:</h3> //or whatever the programmed option is
<ul>
<li>Syndicated names/icons, etc...</li>
<li>Syndicated names/icons, etc...</li>
</ul>
</div>
```
Naturally the styling classes should be something relsyn-related with similar (or exact default) mark up as "sharedaddy" and "sd-title". If I have the patience shortly, I'll dig through the dozens of .css files jetpack throws in to style these and do a PR if you don't suspect any issues with your current roadmap.

Making the syndicated icons the same 34x34 px of the "Share" icons would be nice, but for UX/UI reasons, keeping them smaller to encourage sharing over clicking to view syndicated versions would probably be preferable to most users. Thoughts?

Since, it's early days for indieweb, is it worth wrapping the text "Syndicated to" (as an example) with a url to indieweb.org/POSSE the way that Webmention Form plugin links to WebMention to allow for some additional publicity? Perhaps those who see this functionality on sites will be prompted to want to get it themselves?

Additionally/separately, is it possible to hook Syndication links (as a default) in above all three of these common plugins so that it appears at the top of the list? (IndieWeb > Jetpack) Alternately, providing a setting value to allow placement in this hierarchy may be nice (for the future).


Webmentions failing sporadically · Issue #682 · snarfed/bridgy https://github.com/snarfed/bridgy/issues/682

Sometime in the last week I find I'm sporadically missing webmentions from both Twitter and Facebook. It doesn't happen all the time, but I feel like I'm missing about a quarter or so of what should be coming back.

I've tried resending them through the brid.gy UI and it seems they then make it about 50% of the time.

The responses I'm seeing on those that fail are similar to the text below

> 2016-07-11 09:48:49.613280 I Giving up this target. {'body_json': {u'error': u'Could not find WordPress.com account for boffosocko.com. Is it registered with Bridgy?'}, 'code': '...', 'request': u'POST https://www.brid.gy/webmention/wordpress (with source=https://brid-gy.appspot.com/react/facebook/5410052/10101051440366925/10152707877027963/10101051440366925_wow_by_10152707877027963, target=http://boffosocko.com/2016/07/10/lunch-at-wordcamp-orange-county/)', 'http_status': 400}

This appears to me to be that Brid.gy thinks I have a WordPress.**COM** account rather than a self-hosted .**ORG** version. I'm unsure what could be causing this and don't seem to find any type of commonality for why some fail while others go through.

From an indieweb perspective, it's probably far easier, more productive, and better interface hypothes.is both accepted the webmention protocol as well as sending webmentions. This way one could post their comments (highlights may be slightly tougher) directly to their Known (or other site) and the webmention protocol could handle the posting to hypothes.is. Similarly when one annotates a page, hypothes.is could webmention the page, so the post author/site admin would be aware that the page was marked up.

#hypothesis #indieweb

@kevinmarks @dwhly I mentioned webmention to them a few months back during the @genius "scandal" in hopes of implementation #indieweb

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

About/FAQ missing reference to webmention-endpoint? · Issue #673 · snarfed/bridgy

I'm always a fan of instructions being built intuitively into the UI flow, to guide new users along, especially if they have a solid idea of what they're getting into in the first place. In this particular instance, the reference to the HTML was a tad too nebulous and may confuse many -- especially those who begin reading rather than jumping right in.

Shortly the indieweb will be so big that totally tyro users with no facility with code will be on the doorstep and will need better explanations/instructions. Perhaps I'll take some time in the coming months to put together simple walk thrus for the handful of major platforms? If you think it's worthwhile, can you let me know, based on the current userbase (or even recent growth in the past 6months-year), how you'd rank them in order of priority so we can help the biggest groups first? Or perhaps it's worth starting at the lowest hurdle for the least technical users (Tumblr/Blogger?) and building toward the more technical (WordPress.com)? (I'd presume most above this level are okay with most of what exists now).

I'm presuming that Brid.gy was originally meant as a "code" bridge to connect activity on silos, but I can also see it as taking on a secondary meaning in providing the initial value and impetus to bridge users into to the bigger IndieWeb movement.

About/FAQ missing reference to webmention-endpoint? · Issue #673 · snarfed/bridgy

In the FAQ https://brid.gy/about#endpoint there's a line about "Why do I have to add that line of HTML to my blog?"

Am I now missing it or did the actual line of HTML that's being referred to disappear from the page in an update?

I'm presuming it's referring to:
<link href="http://yourwebsite.host/webmention-endpoint" rel="webmention" /> or on WordPress
<a rel="webmention" href="https://www.brid.gy/webmention/wordpress"></a>

I think the brid.gy interface prompts the user to include such a line when signing up for service, but it may also make sense to mention it on this page in this section somewhere for completeness? It could certainly be referenced here for those reading the "about" page prior to actually attempting to set things up.

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.

Sorry for the delay, but my work schedule and travel have been awfully heavy lately. It does sound like the issue I'm having is somewhat related to the discussion on https://github.com/raamdev/independent-publisher/issues/155

I've got two separate installs with the same IndieWeb plugins installed. One uses Independent Publisher and the other is a slightly older version of the Academica Theme (v1.2.3 downloadable from https://www.dropbox.com/sh/ym0c78uyzltpeu1/AAByejNd8MG83I2MVOFXOuPaa?dl=0) which is outputting the facebook likes, twitter favorites, and reposts properly (or at least as I would expect.)

For some reason Independent Publisher isn't outputting Brid.gy likes, favorites, or resahares from Twitter and Facebook out of the box the way that Academica (or even WP common themes like Twenty Fourteen or Twenty Fifteen) does. They're not showing up at all. On the site with Academica Theme, I've tried doing a "Live Preview" of the Independent Publisher theme and there, it also seems to be "eating" (not showing) these additional comments from Brid.gy while all the other traditional comments do show up.

However, while you're tracking down the issue(s), you might also consider tweaking one additional output issue with respect to these types of comments. From a UI standpoint for themes using IndieWeb, I would recommend that the comment section sort out the comments and display them somewhat differently. For simple Facebook likes and Twitter favorites, it might be best to aggregate all of them into a facepile [http://indiewebcamp.com/facepile] with a simple header ("Liked on Facebook"/"Favorited on Twitter") followed by the photo icons of the people who liked/favorited the article within those platforms. (This is similar to how most Wordpress sites handle Likes/Stars natively within WordPress.) Following this it could create a facepile of people who reposted/reshared the post. Then after this the rest of the comments should be sorted by date/time as comments traditionally are as this will allow people to more easily read/consume the actual commentary.

This post has an example of a combination of likes/favorites/reposts and actual comments that would be better sorted into a facepile section followed by a more "traditional" comments section. http://boffosocko.com/2015/07/27/algebraic-number-theory-ucla-extension/

I'm supposing that it's how Independent Publisher is rendering the output of wp_commentmeta into its comment section that causes some of these brid.gy-fed likes/favorites/reposts to disappear.

If it helps, I'll also point out a previous and possibly related issue I'd run across vis-a-vis IndieWeb and output of comments: https://github.com/pfefferle/wordpress-webmention-for-comments/issues/1. The solution was most likely the way that the Semantic Linkbacks plugin (an IndieWeb WP-specific plugin) was handling its output. Here it's likely that @dshanske or pfefferle may be of more assistance in sorting things out if necessary.

I'm still attempting to understand the larger world of indieweb code for WP, but I'm relatively sure that the issue I'm seeing is potentially coming out of the WP Semantic-Linkbacks plugin.

The issue:
Likes from Facebook as well as likes and RT's from Facebook are feeding into the the WP comments dashboard from brid.gy properly, but once being approved, aren't actually showing up in the comments section of the related WP post.
I've done a quick test with a comment with text on the same Facebook post and don't seem to be seeing the same issue and it seems to show up fine in the comments on the post once approved.

Example:
WP post: <a href="http://lfl8424.boffosocko.com/2015/08/20/todays-books-august-20-2015/">http://lfl8424.boffosocko.com/2015/08/20/todays-books-august-20-2015/</a>;
Associated facebook post: <a href="https://www.facebook.com/ChrisAldrich/posts/10100846770831315">https://www.facebook.com/ChrisAldrich/posts/10100846770831315</a>;

As this is a relatively new site, perhaps there's some small thing that I'm missing or forgetting? I set it all up with the WP IndieWeb plugin (v2.2.0) and everything within it is current and installed/configured (except Hum and Micropub).

Its possible that it's something similar to a related issue I'd had before on a different WP install (see: https://github.com/pfefferle/wordpress-webmention-for-comments/issues/1) though that seemed to be fixed (by itself?) shortly thereafter.

Within the WP admin interface, (http://lfl8424.boffosocko.com/wp-admin/comment.php?action=editcomment&c=25)
in the editable comment section, I'm seeing something similar to the following:

<code><a href="http://lfl8424.boffosocko.com/2015/08/20/todays-books-august-20-2015" rel="nofollow"></a>
<a href="http://lfl8424.boffosocko.com/2015/08/20/todays-books-august-20-2015/" rel="nofollow"></a></code>

So there is data there, it's just not being parsed/rendered properly somewhere.

Since I've got another WP set up that seems to be operating properly with the same general set up, has anyone got any ideas?