Chrome display issue in Refreshed CSS · Issue #12 · indieweb/chat.indieweb.org https://github.com/indieweb/chat.indieweb.org/issues/12

Per our conversation here's a screenshot of what's happening:

Essentially the bar on the left is covering up most of the chat commentary, which needs to be shifted over. Doesn't seem to be happening on any of the other browsers I tested -- only chrome.

WhisperFollow still supported? · Issue #2 · acegiak/WhisperFollow https://github.com/acegiak/WhisperFollow/issues/2

Ashton, I'd recently installed the version from the WordPress.org repository and didn't get the result I would have expected. I'm running the WordPress 4.5.3 and noticed that the plugin says it's supported up to 3.5. Perhaps this is the issue? I'm not getting any error codes or anything, just no output with what I expect is the proper set up per the instructions.

I notice that there is some new code here on Github since then which I haven't tried yet, but thought I'd ask first to see what the status of the project is. The concept of an indiereader inside WordPress is _very_ compelling and is one of the pieces that's really missing to fill out the other end of the WordPress product.

Let me know if I can provide any additional information.

Nope, Twitter links work like they should (as do most others I've run across on https).

I do remember @petermolnar having a possibly related issue back in March. It had something to do with his server supporting SSLv3. See also:
https://github.com/idno/Known/issues/1360
and if necessary https://github.com/kylewm/KnownReactions/issues/8

UX: Bridgy to Twitter makes some unfortunate default photo choices · Issue #10 · dshanske/bridgy-publish https://github.com/dshanske/bridgy-publish/issues/10

Surely I should have put in a featured image, but otherwise it's grabbing multiple low res photos on the same page (in widgets, footer, or from gravatar author block) which don't correspond well with the content :

Maybe default to none if not a featured image or appearing within the_content()?

sslv3 handshake failure · Issue #16 · kylewm/KnownReactions https://github.com/kylewm/KnownReactions/issues/16

## While trying to do this:
Like a [post ](http://www.rmendes.net/2016/notifications-slavery-versus-attention-ecology) on @rikmendes Known site

## I encountered this error:

## Some other notes:
I have a sneaking suspicion that this is being caused by Rick having recently switched to httpS on his site, but just in case.... I'll ping him separately to see if he knows something on his end.

I like that even with the SSL failure that the plugin gives a description field to fill in manually.

Syndication to Medium · Issue #33 · dshanske/syndication-links https://github.com/dshanske/syndication-links/issues/33

Now that Medium's API now supports posting and in addition to their "import post" functionality (POSSE), their [bulk POSSE method](https://help.medium.com/hc/en-us/articles/218572107-How-to-move-to-Medium), as well as their [WordPress Plugin](https://wordpress.org/plugins/medium/), it would be great if Syndication Links could programatically grab the URL from the plugin for inclusion. (I don't think any of the other methods provide data, but I could be wrong.)

For reference the WordPress Medium Plugin is storing the data in postmeta in meta_key named "medium_post"

Here's an example from something that I posted recently from that field:
`O:11:"Medium_Post":11:{s:16:"author_image_url";s:69:"https://cdn-images-1.medium.com/fit/c/200/200/0*ici7OvT6gSngj2t9.jpeg (14KB) ";s:10:"author_url";s:32:"https://medium.com/@chrisaldrich";s:11:"byline_name";N;s:12:"byline_email";N;s:10:"cross_link";s:2:"no";s:2:"id";s:12:"4335e2d72369";s:21:"follower_notification";s:3:"yes";s:7:"license";s:19:"all-rights-reserved";s:14:"publication_id";s:12:"12b80d28f892";s:6:"status";s:6:"public";s:3:"url";s:73:"https://medium.com/@chrisaldrich/wordcamp-orange-county-2016-4335e2d72369";}`

It's obviously the final URL in the array that you'd want to scrape.

I've added mf2 classes to WordPress's [recipe] shortcode at: https://github.com/chrisaldrich/jetpack/pull/1/commits/f914ebe3bd573d1d6d42c5b7752bf26c41448a3b

I've also opened an issue for the JetPack repository to see if they'll include it moving forward.

[Recipe] shortcode: add additional microformats support (v1 and v2) · Issue #4470 · Automattic/jetpack https://github.com/Automattic/jetpack/issues/4470

#### Steps to reproduce the issue
The current [recipe] shortcode appears to _only_ support the '[hrecipe](http://microformats.org/wiki/hRecipe)'; class in microformats1

#### What I expected
I would have expected the additional dozen or so classes in hrecipe to be supported, or better yet, that it would have also supported the newer microformats2 [h-recipe](http://microformats.org/wiki/h-recipe) spec in parallel.

I'm anything but a github expert, but I took a crack at adding the additional classes (for both mf1 and mf2) on a forked branch, which also includes some additional detail:
https://github.com/chrisaldrich/jetpack/pull/1/commits/f914ebe3bd573d1d6d42c5b7752bf26c41448a3b

I've got a copy of this patch running on a site with a recipe at: http://boffosocko.com/2016/07/17/chili-prep-for-dinner-tonight/

Support Post Kind: Recipe · Issue #57 · dshanske/indieweb-post-kinds https://github.com/dshanske/indieweb-post-kinds/issues/57

I've been playing around with food recipes lately and thought this might be another worthwhile/relatively common post type (https://indieweb.org/recipe) to add/have in the future along with food and drink.

I'll also note that WordPress (via JetPack) just updated their recipe shortcode: https://en.support.wordpress.com/recipes/ which
gives some additional front end support (as well as mf1 mark up for hrecipe, though I'll see what I can do to inject mf2 as well)

Potential icons:
Fontawesome: &lt;i class="fa fa-cutlery" aria-hidden="true"></i>
Genericon: ??

Use case example: http://boffosocko.com/2016/07/17/chili-prep-for-dinner-tonight/

Syndicated copies to silos include "Syndicated to:" text · Issue #32 · dshanske/syndication-links https://github.com/dshanske/syndication-links/issues/32

Similar to this issue with Jetpack: https://github.com/Automattic/jetpack/issues/4399

The text output from Syndication Links (the default text "Syndicated to:" ) shows up in the syndicated copies (and I'd generally think that most wouldn't want it from a UI/UX perspective). I've tried syndicating to most of the major platforms and Facebook and Tumblr appear to be the primary offenders.

Example:
Original: http://boffosocko.com/2016/07/16/the-indieweb-ified-library/
Syndicated Tumblr Copy: http://chrisaldrich.tumblr.com/post/147515812392/the-indieweb-ified-library
Syndicated FB Copy: https://www.facebook.com/ChrisAldrich/posts/10101055831666725?pnref=story

Perhaps the checks and the patch mentioned in https://github.com/Automattic/jetpack/issues/4399 could provide a solution?

UI suggestion: Sort M/F or F/M · Issue #11 · lynnandtonic/hollywood-age-gap https://github.com/lynnandtonic/hollywood-age-gap/issues/11

Given the prevalence of older men with younger women and the fact that currently the largest gap is actually a MUCH older woman and a younger man, it would be interesting if the sort could be done on a gender basis with the +# indicating one direction and a -# indicating the reverse. This way one could more easily emphasize the larger M/F gap and the way in which it skews. It would also more easily highlight the far fewer cases in which women exceed men in age.

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:
```
&lt;div class="sharedaddy">
::before
&lt;h3 class="relsyn sd-title">Syndicated to:&lt;/h3> //or whatever the programmed option is
&lt;ul>
&lt;li>Syndicated names/icons, etc...&lt;/li>
&lt;li>Syndicated names/icons, etc...&lt;/li>
&lt;/ul>
&lt;/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).


Syndicating WP content to Tumblr includes sharedaddy div · Issue #4399 · Automattic/jetpack https://github.com/Automattic/jetpack/issues/4399

<!-- Thanks for contributing to Jetpack! Pick a clear title ("Sharing: add new Facebook button") and proceed. -->

#### Steps to reproduce the issue
I'm using Social Network Auto-Poster [https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/] (rather than Jetpack's Publicize because it includes more control over post types and additional platforms) to syndicate my WP content to my Tumblr. I'm using their standard "Text Post" option with the text set to include `<p><img src='%IMG%'/></p><p>%FULLTEXT%</p>`

#### What I expected
The copy on Tumblr should simply transfer only the user's input in the post from WP into the Tumblr post.

#### What happened instead
I get the content of the post, but I'm also getting a div with all the class=sharedaddy etc. (see below) appended to the bottom of the post which generates the Like prompt/button/functionality and the word "Loading...". (Example: See bottom of http://chrisaldrich.tumblr.com/post/142661877457/a-new-view-of-the-tree-of-life which was syndicated from http://boffosocko.com/2016/04/11/a-new-view-of-the-tree-of-life/)

Here's the HTML that's being copied over and displaying unnecessarily.
`<div class="sharedaddy sd-block sd-like jetpack-likes-widget-wrapper jetpack-likes-widget-unloaded" id="like-post-wrapper-67433065-0-570c56a68fcae" data-src="//widgets.wp.com/likes/#blog_id=67433065&amp;post_id=0&amp;origin=boffosocko.com&amp;obj_id=67433065-0-570c56a68fcae" data-name="like-post-frame-67433065-0-570c56a68fcae"><h3 class="sd-title">Like this:</h3><div class="likes-widget-placeholder post-likes-widget-placeholder" style="height:55px"><span class="button"><span>Like</span></span> <span class="loading">Loading...</span></div><span class="sd-text-color"></span><a class="sd-link-color"></a></div></div>
`

Generally, this doesn't happen when syndicating content like this into other platforms (though this could be because other platforms, Facebook for example, may be stripping out all other html and thus precluding this). Additionally, for example, it's not copying over Jetpack's "Share This" or "Related" posts content which also sit inside the main `<div class="e-content">` which I suspect is the general section being copied over.

In short: Why is the "Like" functionality being copied over while "Sharing" and "Related" aren't?

<!--
PLEASE NOTE
- These comments won't show up when you submit the issue.
- Everything is optional, but try to add as many details as possible.
- If requesting a new feature, explain why you'd like to see it added.
- This issue tracker is not for support. If you have questions about Jetpack, you can [start a new thread in the Jetpack support forums](http://wordpress.org/support/plugin/jetpack#postform), or [send us an email](http://jetpack.com/contact-support/).
- Do not report potential security vulnerabilities here. For responsible disclosure of security issues and to be eligible for our bug bounty program, please submit your report via [the HackerOne portal](https://hackerone.com/automattic).
-->