I'm curious what you've tried that you've now abandoned? I've tried a handful of methods and haven't been very happy with many of them myself.

JetPack's publicize is seemingly the simplest of the lot, but gives almost no control over the end result, so either you like it or you don't. Bridgy Publish plugin has gotten much better recently, but my theme has some quirks to it that need some work to get things there working smoothly. Most recently I've been using Social Network Auto Poster which has a huge number of POSSE targets, but also requires a lot of set up time and configuration (and also relies on other plugins like All in One SEO or Yoast to set appropriate Open Graph Protocol metadata so that versions that get sent to Twitter/Facebook display exactly what I want them to--and even then it's not always 100%. I've been tempted to try Keyring next, but I suspect it'll be much of the same convoluted dance.

If most of my readership wasn't hiding in the silos, I think I'd give up on POSSE too. I can't wait until the broader idea has completely taken over to the point that syndication is a useless function.

I'd noticed this a few days ago too as it seemed to have fixed an issue they'd had previously with the Facebook URL they displayed in the admin interface that didn't work, but was different from the URL that Syndication Links picked up. I mostly noticed because when using the SNAP buttons after initial publication they give modals showing success in posting which include the returned URLs, which for some silos can make it easier to cut and paste if necessary.

Your solution sounds like a sound one.

Your other thought recently about storing the URLs separately from SNAP's store is a good one as well because I've noticed (and generally not cared, though others surely may/will) that if one re-syndicates a post with SNAP, it overwrites the prior URL with the new one, which means that Syndication Links wouldn't have a "complete" list of all POSSE copies. This also means that Bridgy will only return replies on the most recent one for each silo this is done in. Anyone using SNAP's scheduling feature will be losing some of their backfeed as a result.

Unless they're moderating comments, it looks like there's little chance they actually saw your reply.

In some cases where others don't support webmention, if you want them to see your response, you should @mention their Twitter account directly and syndicate your reply to Twitter, and/or you can manually POSSE your response to their page directly via comments.

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

David is right, you'll have to add some code to your set up for it to happen automatically. For one workflow I've got via IFTTT.com, I do include the URL into the code so it's easy to copy and past over manually after the fact.

You could also consider using OwnYourCheckin [https://ownyourcheckin.wirres.net] and micropub, much the way you're already using OwnYourGram. I think that should send over the correct data for the POSSE version to be pulled into Syndication Links.

@rikmende Rick, I can't speak to stripping out your prior history of past posts, but I have used a quirky hack in the past to get around Facebook's save-for-later functionality which seems to be designed to keep you in Facebook 24/7. It'll work for your "saved" articles moving forward.

You can use this IFTTT recipe: https://ifttt.com/recipes/471081-read-it-later-on-facebook
To have it work, instead of bookmarking with Facebook's native interface, just repost/share the link/article you want to save to your own Facebook feed. If you don't want to share it with everyone, just mark the reshare as shared only with yourself and then only you would be able to see it. The IFTTT recipe will then strip the URL out of your shared post and push it to Pocket.

Note that if you POSSE to Facebook, you'll also see shared URLs for your own posts appear in Pocket from then on, but you can delete/mark as read all of those quickly enough. Or you can favorite them and push them to your public-facing Pocket shares (which are also subscribable) and consider them a form of POSSE to Pocket! Win-Win!

Sounds like a reasonable solution. I'd imagine that in most cases (to be safe) that if there's not a featured image, then posts to twitter would generally be just the text update as that's how most people typically use twitter.

Is it looking for photo related microformats with regard to identifying/pulling photos? I actually thought it was interesting/relatively nice that it automatically pulled the three photos and laid them out that way, but in that case I'd have done higher res photos for better clarity. The "indieweb mini-logo" is a really small icon way down in the footer of my page and I was most shocked that it popped up on the post.

I typically have been using SNAP for POSSE, but as I've been watching your work recently, I felt compelled to test out Bridgy Publish to give you some feedback about UX/UI as well as bang on things for bugs in general.

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.

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


@Petersell I'm only doing POSSE for Medium on WordPress where I tend to post my longer content. I'm primarily using Known for shorter content, checkins, and mobile use. I imagine that you could POSSE from Known to Medium by hand, but it would be hacky at best.

I'd mentioned something like this a while back at https://github.com/dshanske/syndication-links/issues/23 as I was seeing it in pop up in Woodwind.xyz and a few other places. I'm not quite sure what's causing the problem (which is sporadic and depends on who's resharing or where it's being resyndicated to.) In general it's not a problem with KnownReactions (really), but something to do with the WordPress install/configuration.

I'm hoping that @dshanske and the fix he mentioned clears it up, but if not I'll continue to look into it on the WP side, because I want to get rid of it too. This is the first time I've seen the "related", "author", and "share" this portions show up. Usually it's just the blank "Syndicated to" portions that sneak in. (I've also seen this with POSSE from WP to Tumblr as well as with Woodwind. I haven't seen it happen on many other platforms however.)