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.

@lindner Congratulations!

For extending things a bit, be sure to check out: http://docs.withknown.com/en/latest/plugins/community/ so you don't have to reinvent the wheel.

One of the things that made using my Known site much more addictive was being able to do so more easily on mobile. I wrote up a few thoughts here that you might appreciate: http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and

If you don't like the writing interface you might consider using Quill https://quill.p3k.io/ which uses micropub (already included in the core of Known). Micropub is now a W3C candidate as of yesterday. Alternate posting clients may be found at https://indieweb.org/micropub#Clients. In particular you might like OwnYourGram or OwnYourCheckin for Instagram and Foursquare if you use those.

You'll find lots of fellow devs and users of Known at https://indieweb.org/Known

Good luck and let us know if you need help!

Issue un-authenticating while moving from one site to another · Issue #29 · aaronpk/OwnYourGram https://github.com/aaronpk/OwnYourGram/issues/29

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://stream.boffosocko.com. However, I'm still getting micropub posts to the WP install at www.boffosocko.com. (Note that I would like to keep both sites listed in my Instagram profile/bio, if that makes a difference.)

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.

So it sounds like you really want is the https://wordpress.org/plugins/syndication-links/ which will give you a field under your content to show where the content was syndicated to (and properly mark the links up with rel-me).

I don't think brid.gy automatically puts the syndicated link into the field, so you'd have to do it manually. Other plugins like Social Network Auto Poster (SNAP) or using micropub with clients like OwnYourGram or OwnYourCheckin have intercompatibility with Syndication Links and those URLs will be sucked in automatically.

If you find issues like this, please file them in the github issues repositories for the appropriate plugin so that the issues are known and can potentially be fixed. (Naturally if you can code well enough, you may be able to patch them with a pull request too.)

Support Featured Image (and other common WordPress functionality) · Issue #24 · snarfed/wordpress-micropub https://github.com/snarfed/wordpress-micropub/issues/24

I'm not sure if it's something that would fit in here or quite how -- perhaps a setting toggle?, but for clients that push photos (OwnYourGram.com, https://ownyourcheckin.wirres.net/, Quill, et al), it would be nice on WordPress (especially for many modern themes) to have the (primary) photo from the client post as a "Featured Image" rather than in the main body of the post.

Other potential settings-based functionalities I can imagine being useful (based on experience with Twitter clients) include
* being able to set future posting times
* saving posts as draft, private, pending, etc. rather than automatically publishing
* allowing one to set Post Format (or if using the IndieWeb Post Kinds plugin: Post Kind)
Naturally supporting some of this would also depend on the posting client having support for these options as well.

@kraftbj already responded, but for completeness: also suggested here: http://stream.boffosocko.com/2016/this-is-hopefully-a-simple-but-useful-feature-requesti-appreciate
(This also relates to jetpack_allow_per_post_subscriptions for email and alternate posting methods to WP including via email and [micropub](https://github.com/snarfed/wordpress-micropub) with clients like [Quill](https://quill.p3k.io/)

Glad to know that JetPack is on GitHub :)

This is hopefully a simple, but useful feature request:
I appreciate that there's a filter for jetpack_allow_per_post_subscriptions, however it appears to only default to unchecked. It would be great if it could also be set (programattically or otherwise) to unchecked so that posts would always default to NOT be emailed to subscribers.

In my particular preferred use case, I'm using some advanced indiewebcamp.com related tools like micropub to allow services like Instagram (via OwnYourGram.com) and Foursquare/Swarm to post directly to my WordPress installation. In these cases, I'm posting with a remote service (perhaps similar to posting via email) and don't have access to the post interface to toggle the checkbox so that these posts don't automatically email subscribers. Conversely, when I'm using the direct posting interface, it's simple enough to toggle the checkbox manually.

To put it another way: Is there a way to add a line of code to the subscription filter [https://jetpack.com/support/subscriptions/#filters] so that the checkbox is both available AND it appears checked automatically?

For the same reason, if it doesn't already exist, it would also be nice to have the ability to toggle the checkboxes on the JetPack publicize feature as well. (If this already exists, then it's likely easy to borrow the code to accomplish the same thing for emailing subscribers).

Thanks to the entire team as always for a great product!

I'll also ping this related issue on micropub which may benefit from the apparent difference between the two similar based services either being able to provide a syndicated version or not:
https://github.com/snarfed/wordpress-micropub/issues/21

Returns the wrong Syndicated Link · Issue #7 · diplix/OwnYourCheckin

In using this with micropub on WordPress and the https://github.com/dshanske/syndication-links plugin, I notice that the syndicated link that's returned is for the actual Foursquare location rather than the technical Swarm PESOS checkin.

Example: http://boffosocko.com/2016/05/17/55672674/
The first syndicated link under the post is the one autogenerated by the micropub portion (I think) and the second one is the actual "syndicated" version which appears on Swarm (and which I copied in by hand).

Perhaps this is an odd quirk caused by the data returned by OwnYourCheckin as it dovetails with @dshanske https://github.com/dshanske/syndication-links. (I know it polls several locations to autoimport syndicated links, but I'm not sure how, or where it looks).

I notice that OwnYourGram doesn't provide an autogenerated syndication link like this (or at least it never has for me, and I've always copied it by hand), though it would be nice if it did it automatically. Perhaps this issue aaronpk/OwnYourGram#20 on OwnYourGram could be troubleshot using OwnYourCheckin, and vice versa since I'm getting a syndication link with the Checkin version, but not the Gram version.

IndieWeb and Android Mobile

@dshanske I remember you mentioning it briefly the other day and then saw something more specific this morning: http://indiewebcamp.com/irc/2016-05-03/line/1462285944410

Have you hacked around with either Bookmarklet Free or URL Forwarder apps from the Google Play store? They’re mentioned in the following two places:
https://snarfed.org/easy-indieweb-interactions-on-android
http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and

I’d gotten URL Forwarder set up and configured to make mobile sharing for my WithKnown install to make bookmarking, sharing, reposting, and a few other functionalities work incredibly quickly and well. I’ve put off doing so on WP since I have some other back-end dependencies that need tweaking so that I don’t create redundant loops with some of my other configuration. With any luck one or the other will get you pretty far without having a full micropub application.

With these you can use Android’s ubiquitous sharing icon and share to one or the other of the apps which will do the URL scraping to be able to do some of the posting types you want. Depending on the output, you may need one or two additional tweaks, but it’ll give you a reasonable template for a workflow. I’m sure some further url parameters and integration could be put in to auto checking the correct post kind and thereby making your posts fully indieweb compatible on WP. Adding Indieweb Press This https://github.com/pfefferle/wordpress-indieweb-press-this/ functionality for bookmark, share, watching, listening, et al. would complete a larger cycle of functionality.

Then, I’m sure there’s the additional functionality of API calls to Twitter/Facebook/etc. to implement the actual retweet/like on the native platform, but that could be handled later/separately (though Bridgy Publish might be able to handle this? I seem to remember a mention of it in the bookmarklet set up.)

Finally, if “Post Properties” could import the same URL and scrape the metadata, the entire process would be almost too simple and not need a “traditional” mobile app at all.

For URL Forwarder the base settings should be:
Reply: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=reply&u=@url
Like: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=like&u=@url
Repost: http://YOURSITENAME.com/wp-admin/press-this.php?v=8&type=repost&u=@url

Hopefully this gets you a few steps further on android mobile without a huge amount of work…

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?