Embed for Tweets versus Blockquote (html/js) with Text? · Issue #10 · pfefferle/wordpress-indieweb-press-this https://github.com/pfefferle/wordpress-indieweb-press-this/issues/10

I've noticed that the IndieWeb Press This bookmarklet uses something like [embed]https://twitter.com/ChrisAldrich/status/707313378268618752 [/embed] in the main body of the content rather than the Twitter html/js embed method
(a la: <blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr"> etc... )

I suspect that WordPress is doing some processing on the back end with the [embed] short code to fetch and display the twitter card and thus isn't technically saving the actual content of the tweet the way the blockquote embed method does. In the event of a Twitter silo death, this could spell trouble for users losing the data.

Cross reference: http://techlifeweb.com/bookmarklets-for-indieweb-favorites-and-retweets/ and http://stream.boffosocko.com/2016/scott-i-love-the-concept-of-your-bookmarklets-and-how

Rich Embeds for silos like Twitter might actually be somewhat useful when using post kinds "like" and "repost" as the Twitter card would then display in the post in a nice visual fashion. The tougher question, however, is: Is the actual content of the Tweet being copied over as a blockquote with the full text (similar to what one would cut/paste from Twitter when clicking on their "embed" option within a Tweet) or is it using something like [embed]https://twitter.com/ChrisAldrich/status/707313378268618752 [/embed] which happens with the [IndieWeb Press This](https://github.com/pfefferle/wordpress-indieweb-press-this) plugin? If this is the case, then I imagine that if Twitter experienced a site-death then the proverbial "backup copy" of the plain text of the original liked/reposted tweet would be gone and the [embed] portion would be utterly useless thereafter, no?

Cross reference: http://techlifeweb.com/bookmarklets-for-indieweb-favorites-and-retweets/ and http://stream.boffosocko.com/2016/scott-i-love-the-concept-of-your-bookmarklets-and-how

Scott, I love the concept of your bookmarklets and how they work!! I particularly like the way that WP blockquotes the original and copies over the actual text of the tweet. Sadly after configuring it for use, when I cut and paste I don't get the actual tweet, but end up with a blockquote that literally reads "+document.title+" instead of the text of the tweet. I'm also using it in Chrome, but not sure what is going wrong that I'm seeing this quoted text instead of the actual tweet. Is there something else I need to configure?

I like the way your bookmarklet works compared to the https://github.com/pfefferle/wordpress-indieweb-press-this bookmarklets which work fine, but rather than do a full embed of the actual text in blockquote style, it puts in something like `[embed]https://twitter.com/ChrisAldrich/status/707313378268618752[/embed]` which WordPress then processes to display the tweet. I'd worry that if Twitter experienced a site death, that the content on my site would no longer show the original content of the tweet!

The third potential method of doing all this could be to use David Shanske's Post Kinds plugin https://github.com/dshanske/indieweb-post-kinds which provides the ability to create a bookmarklet that supports URL parameters using the URL http://www.YOURSITE.com/wp-admin/post-new.php?kind=like&kindurl=@url or http://www.YOURSITE.com/wp-admin/post-new.php?kind=repost&kindurl=@url where the variable "@url" is the permalink of the tweet. The post kind is then set appropriately as well as the referenced URL which then does the embed, but I suspect it's using the [embed] method, which again doesn't seem like it will work sustainably in a possible post-Twitter world.

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.

If supported it could also be used to push tags (example "private") that are apparently being built into plugins like JetPack to act as a "switch" to prevent JetPack from publicizing/emailing subscribers on particular posts. See also: https://github.com/automattic/jetpack/issues/7#issuecomment-220964940 which is apparently on track to become a feature soon.

@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 :)

Authentication Error · Issue #25 · jtsternberg/DsgnWrks-Instagram-Importer https://github.com/jtsternberg/DsgnWrks-Instagram-Importer/issues/25

When I try to "Create a User" and "Secure Authentication with Instagram" I get the error message "There was an authorization error. Try again?"

Last week sometime I had tried setting up the importer on a fresh WP install and didn't have any problem importing about 85 past posts. Now on my live site, I'm unable to get past authentication.

I've tried going into Instagram and deauthorizing DsgnWrks Instagram Importer in case that was the issue, but it doesn't seem to be the cause.

The plugin seems to authorize properly and redirects to the set up page for the plugin, but throws the error. (Authenticated apps within Instagram indicates that the plugin was properly authorized.) I've also tried using a different Instagram account, but that didn't work either.

Thoughts?

I'd put the issue into the <a href="https://github.com/pfefferle/wordpress-uf2/issues/15">log on GitHub for uf2</a> and got the following back from David Shanske which confirms my suspicion:

<blockquote>It is the fact that the theme styles hentry</blockquote>

hentry is a microformat and shouldn't be used as a theming class: http://microformats.org/wiki/hentry

Jay, I don't think the author David spends much time in the fora here, and I know he's been diligently developing several other plugins in the https://wordpress.org/plugins/indieweb/ suite. If you're still interested, the base code for Bridgy Publish is is on GitHub https://github.com/dshanske/bridgy-publish, where you'll also find code for most other things IndieWeb too.

If you have questions or need help, you can find him on IRC via http://www.indiewebcamp.com. He and others there are more than happy to help!

Congratulations! If you're not using the SemPress theme, you might also enjoy https://github.com/pfefferle/wordpress-uf2 which will do some of the mf2 material (as best it can) without remarking up your theme by hand. I've used a handful of WP themes with IndieWeb and not had problems sending/receiving webmentions (to my knowledge) or using other indiewebcamp.com goodness.

You might also appreciate the Independent Publisher theme, which is not only beautiful, but has some custom code for displaying comments, pingbacks/trackbacks, and even webmentions and will shortly have additional mf2 mark up as well (or should, in it's next release which is right around the corner.) The Github code is ahead of the official release on WordPress.org if you want to test it out.

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.

rel-feed support for Bridgy and Instagram #40
While I'm thinking about Bridgy/Instagram support and mf2, I thought I'd cross post this issue https://github.com/snarfed/bridgy/issues/671#issuecomment-219580229 snarfed/bridgy#671 (comment) here as it doesn't look like SemPress supports this out of the box.