There's a related issue for this: https://github.com/dshanske/indieweb-post-kinds/issues/60

Apologies, it looks like I'd miscounted on the ghost.org link, which does in fact exist and render properly. It was the plus.google.com URLs which aren't being cut down properly and displaying the G+ icon the way they should and instead appear as a generic share icon.

The other is for syndicating via email (which I imagine isn't done often?) and appears on line 205 of
https://github.com/dshanske/syndication-links/blob/52160d913fcf6d41406f468ee13323bc90a983b5/includes/class-syn-meta.php as `'mailto:' => 'mail',`
Unless I'm formatting it painfully wrong, mailto:XXX links show up with the generic share icon instead of a mail icon.

As a supplementary note, JetPack v4.5 now includes a Gravatar widget which functions a lot like the H-card Widget and pulls in data from the user's profile as well as their Gravatar account. Now, if only it had microformats...

Since the code and UI may be worth looking at: https://github.com/Automattic/jetpack/tree/master/modules/widgets

Announcement: https://jetpack.com/2017/01/17/jetpack-4-5-monetize-your-site-brand-new-videopress-and-many-many-new-shortcodes/

@aegibson73 Try viewing page source to see if the URL is properly wrapped. I know that some people have had issues with this recently and I think it was theme related: https://github.com/kylewm/KnownReactions/issues/17

The errors can sometimes be a result of which version of PHP you're running. Double check that, though I'm not sure what the minimum threshold Known requires at the moment. Usually these days v5.6 is a good sweet spot. Versions under 5.5 may cause errors like what you saw and I know my stupid host often defaults new installs to 5.4 for some reason.

You can also check to see if it's a known issue in the open or closed queues at the github repo: https://github.com/kylewm/KnownReactions/issues

Otherwise cut/paste the error(s) into the issue queue in the repo to see what what others in the community think it could be.

@Chronotope #1 Your Twitter stream makes me wish that I had a little script that would allow me to click the heart (like) on Twitter and have the link in that post be automatically "nominated" to my PressForward install.

#2 If you used something like http://noterlive.com for your tweetstorm commentary (which incidentally keeps a constant linked reply stream on Twitter), you could very easily bundle them up and repost them as a more complete blog post if you wished. (Instructions: https://github.com/kevinmarks/noterlive/wiki/Noter-Live-Instruction-Manual)

@cswordpress @webrocker I'd noticed that WP-Social quit support a while back, but didn't know why; sorry to hear it. I wrote some thoughts here [https://github.com/crowdfavorite/wp-social/issues/213] for those who need alternatives and IndieWeb tech is a great solution in my opinion.

If you go the route of API's you're on the hook for maintenance which can be troublesome at best. If you want a PESOS solution there are a few options listed on https://indieweb.org/WordPress/Plugins. I've tried Ozh's version which is pretty good. I've used DsgnWrks Instagram importer before, but not the Twitter one, so I know his code is pretty solid.

If you have a few minutes, you might find that POSSE is a better/more robust method, in which case you could set up the basic IndieWeb Plugin and use JetPack's Publicize (or SNAP or something similar) to syndicate your status updates to twitter. https://indieweb.org/Getting_Started_on_WordPress

I'd be happy to help you if you have questions. Many of the developers of these plugins spend time in the Indieweb Chat [http://indieweb.org/IRC] and are happy to help with questions, problems, or take feedback to improve the tools.

@cswordpress @redcrew Thanks for the recommendation Amanda!
I'm guessing you installed PressForward directly on your production server without using a test environment? I can tell because all of your posts are trying to redirect, but are redirecting to themselves! It's a known bug I mentioned here: http://boffosocko.com/2016/12/31/pressforward-as-an-indieweb-wordpress-based-rss-feed-reader-pocketinstapaper-replacement/#run+across+an+issue+with+the+automatic+redirect that Aram has apparently fixed in the Github repo and will push with the next update. https://github.com/PressForward/pressforward/issues/878

Until then you may want to go to the settings and set the redirect time to "0" which will prevent all of your pages from continually re-loading OR you could uninstall it from your production site and run on a test server.

I've been loving it since I installed and can't wait for the forthcoming patch. I'm curious what others think of it for the off-label use I've proposed.