Support Featured Image (and other common WordPress functionality) · Issue #24 · snarfed/wordpress-micropub https:/
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:/
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.
Authentication Error · Issue #25 · jtsternberg/DsgnWrks-Instagram-Importer https:/
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?
UX/UI enhancement: Blank syndication links being syndicated · Issue #23 · dshanske/syndication-links
. I'm not sure if I've seen them display on other sources (in most cases I choose to use the icon versions rather than text, but could do a quick test to see if the text at least appears.) Since I'm sure there are others, I'm curious if there's a way to either fix how these show up (or not) or simply move them for POSSEd copies?
Thoughts on UX/UI:
I'm presuming that they're hooked onto the end of the_content(), which then means that they're being syndicated out as part of the body of the content. I would suggest that on most platforms, most people don't/won't care about the fact that there are syndicated copies (though for the near term of advertising the concept for the IndieWeb, keeping them may be valuable), particularly when they can view the primary source which ought to presumably have all the commentary and webmentions (by backfeed or other means).
Interestingly, I occasionally see, though not as often, the "Share This" data flow through in the same manner. In my case the share this appears _above_ the list of syndicated links: viz:
![share this](https:/
Is there some type of processing that Jetpack is doing to prevent this from syndicating as "content"?
The way I typically think about it, knowing about syndicated copies is mostly useful as a function of commenting rather than content, so that if someone comments in Facebook, for example, I go back to that silo to post a response, so their chosen platform can send notifications/emails etc about the interaction, and rely on webmentions to backport my own comment onto my site and to keep the flow of conversation on the original post rather than a separate post on my own site that points back to another. Perhaps then, the best default location for syndication links is within the comments section? This then solves the problem of syndicating out blank versions, but more closely associates the syndicated copies with the "conversation" about the post. Potentially putting them at the top of the comments section could also keep them relatively close to where they currently live as a default.
I pose most of this as ideas/potential suggestions, but I'm curious what others think in terms of what/how they use this functionality.
Returns the wrong Syndicated Link · Issue #7 · diplix/OwnYourCheckin
In using this with micropub on WordPress and the https:/
Example: http:/
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:/
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.
UI enhancement: Don't display syndication text if nothing is syndicated ·
Issue #22 · dshanske/syndication-links https:/
If there are no copies syndicated, the "syndicated to" (or other optional text) shouldn't display.
https:/
Watched Small Parts: Episode #2 - Vincent Schiavelli https:/
gRegorLove wrote a quick-reply bookmarklet for Twitter.
I wrote a quick-reply bookmarklet for Twitter. It redirects the browser to your specified URL with the tweet’s permalink as a parameter. This should work for selected tweets in your timeline, specific account’s timeline, and even the silly modal-permalinks.
Taking a break from #22 UCLA at USC at halftime to catch up on Penn State at #5 Michigan State.
General Suggestions for data and UI · Issue #29 · dshanske/indieweb-post-kinds https:/
First, I love some of the new changes in v2.2.0!
Here are some additional random thoughts for improving the layout and positioning of some of the final published look of particular posts, if they're not on your "roadmap":
Add an author URL field which could then wrap the data input into "Author/Artist Name" field. For those that want to use it, it makes for a nice way to promote the original author, particularly for properly crediting "bookmarked" items.
In the bookmark post type layout, the order and presentation of the data could be a bit more streamlined.
`Eg: Bookmarked: (Name/Title) in/from (Site Name/Publication/Album) by (Author/Artist Name)`
Currently it displays as "(Name/Title) on (Site Name/Publication/Album)" and "on" may be an awkward preposition for most cases, though it does work for Albums. Similarly the author name is currently just under the title of the post with no other data, which may be somewhat confusing. I note that some of the post formats are slightly different in how they display, but they could certainly be a bit more systematized/similar with appropriate grammar.
I haven't dug into it, but does the author photo URL have a preset size? One of my sample tests displayed a fairly large photo which was oversize compared to what I might have liked. Otherwise adding a sizing field(s) (height/width or percentage) to add to the image output would be useful for its ultimate display.
I love the idea of the featured image! I presume it will actually be output in the layout in some future release to make for more visually interesting posts?
So yesterday there were 5 hits on this post, while today there were 37. This post is currently ranked #6 on a google search for the string "Chris Aldrich Dating Naked". A Google search on "Chris Aldrich" is substantively the same as the past several months except that the profile page for the "other" Chris on VH1's site is ranked #2, while an EW.com article is ranked #8. His twitter account logs in at #15 and the next closest mention is at #69 for an US Magazine article. On Twitter, @ChrisAldrich860 currently has 139 followers.
#DatingNaked #SEOexperiment