Either way is fine. Just be sure to modify the WordPress.org flow (if necessary) as the WebMentions plugin, which I imagine the majority of users would be using unless they decide to roll their own, is now apparently adding the endpoint directly and will cause the potential conflict we've seen.
I'm guessing it searches for the endpoint and only directs users to add it if it's not found, so you're likely fine.
I've got all the services enabled, "icons only", sharing label: "Share this:"; all four options on "Show buttons on" are checked; likes are "turned on per post"; "Disable CSS and JS" is unchecked.
As an additional test (for possible recreation and comparison/contrast) I'm also using a plugin called Syndication links [https:/
(As an aside, functionality like Syndication Links would be a cool feature for Jetpack to add/acquire, particularly if the "Publicize" functionality could hook into it and automatically pull in the links where the content was shared.)
Thanks @jeherve!
Thanks @snarfed, brilliant find as I wouldn't have thought of it. I took out the first one which I'd had hiding in a widget and moved into my header for clarity a few months back.
I vaguely recall putting the others in many months ago, but honestly I can't remember for the life of me where they came from (probably IWC) or which portion of my WordPress is actually generating them now. I also don't seem to recall where I was hiding my code that injects my rel="icon" photos (primarily for shortcut buttons on iOS and Android), though I'm guessing they're in the same place. Any suggestions on where a clever guy who's too sleep deprived to find them right now may have hidden them? None of the IndieWeb plugin sub-plugins would be generating them quietly could they?!
The quirky part is that all three lines have been in there a while and (to my knowledge) haven't been causing problems until about a week ago.
The 6 or so outstanding webmentions went right through without any issue, so I'll mark this as closed for now unless problems continue.
Syndicating WP content to Tumblr includes sharedaddy div · Issue #4399 · Automattic/jetpack https:/
<!-- 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:/
#### 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:/
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&post_id=0&origin=boffosocko.com&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:/
- 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:/
-->
Webmentions failing sporadically · Issue #682 · snarfed/bridgy https:/
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:/
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.
David, This is some excellent code for adding some microformats to @WordPress. Thanks @dshanske! https:/
For those with less technical expertise, could I pose a few questions which you may or may not cover in part 2?
If I recall, there's microformats version 1 and a more recent, updated microformats2. Most of what you're adding here is the mf2 spec and not backwards compatible mf1 mark up, right?
When you say that a theme shouldn't "style" hfeed or hentry, you mean that the CSS shouldn't include these classes as they're used only for semantic mark up and not meant to be used for CSS at all?
If hfeed is already added into a theme, do you recommend removing it from the theme code directly with search and replace (particularly if it wasn't added in the correct place) and then adding it with the snippet you provided, or is it best to leave it in the theme and remove it from the code? If we remove it from the code you provided, which line(s) should we omit? What happens if it is duplicated (ie, what will the output look like, or what happens to parsers that read the code)?
What exactly are the post, body and comment class functions? What do they look like and where would one find them in a particular theme?
How is the code you've provided different from what the WordPress plugin uf2 does? Is it more or less extensive?
In the end, this is also just a stop-gap measure to quickly add a small, but high level subset of microformats to current themes that don't support it? Ideally we would hope more modern themes will add a more full version of microformats natively?
As someone who uses <a href="http://www.boffosocko.com">my own WordPress site</a> as a research notebook/tool and commonplace book (as well as for owning all of my own data and social posts), I'm <a href="http://boffosocko.com/2016/06/17/hypothes-is-and-the-indieweb/">already loving</a> this plugin and can see some tremendous potential for improvements on both it and on the hypothes.is platform in the future.
While I've played around with other platforms like Genius.com as well, Hypothes.is seems to have a more focused approach to how I prefer to use annotations, highlights, and marginalia on the web. It also has a growing API and related suite of tools which portend more flexibility and growth for the future.
Still, one must be cognizant for how these sometimes "hidden" tools can be used for abuse and bullying on the web: <a href="http://boffosocko.com/2016/04/07/webmentions-for-improving-annotation-and-preventing-bullying-on-the-web/">Webmentions for improving annotation and preventing bullying on the web</a>[http:/
@RikMende There's now a WordPress plugin for my WP install. You'd have to do it manually for Known at present.
Issue un-authenticating while moving from one site to another · Issue #29 · aaronpk/OwnYourGram https:/
I was moving my Instagram posting target from a WordPress install to a Known install.
For my WP install, on IG I revoked access from OYG and then reauthenticated for my Known site at http:/
Is there something else I need to do to deactivate ownyourgram from publishing to my WordPress install?
Is it possible that OwnYourGram holds the same authentication for two separate sites using the same Instagram account? This could mean that one would need an "off" switch through the ownyourgram interface to deauthorize one site. It could also separately be the case that Instagram didn't flush a cache which allowed my last IG post to the WP site to slip through.
Andreas, I'm pretty sure my experiment with OwnYourGram was well after I updated to 0.9.2. I never worked on it further to get brid.gy to push the comments/likes back to my Known install, but did spend some time to get OwnYourGram to work with WordPress and eventually have brid.gy backfeed the comments/likes from Instagram.
Ultimately I decided for data portability reasons that it was far easier (and prettier) to import all of my old instagram posts into my WordPress install where I know the code base a bit better. I just finished importing all of my instagram activity to my main site over the weekend, but it'll take some more work to get them to display the way I want them to along with the correct microformats2 markup.
For Instagram/Known, if I recall, you have to correctly specify either http or https properly to make sure the two link up properly, which was an early problem I had. I also had issues with trying to use two sites simultaneously, but apparently putting the URLS of your sites into your bio on instagram works just fine for authentication.
I don't think I went so far as to register my instagram account for known with brid.gy, but I could dig back into it if you need some help. I need to document some of the process for some user manual work I've promised to do for Known.
You could also try the #indieweb IRC channel: https:/