Include IndieWeb Press This plugin · Issue #31 · indieweb/wordpress-indieweb
Would be useful to include the Press This plugin [https://github.com/pfefferle/wordpress-indieweb-press-this] as well, though keep in mind it requires WP v4.3

@WithKnown @ErinJo It looks like the URLs in the plugins list for Recipe and Review in the Known documentation have changed (it appears that en dashes have been substituted for em dashes). The new corrected ones should be:
https://github.com/cleverdevil/Known-Reviews
https://github.com/cleverdevil/Known-Recipes

How to find/create a URL to a status update post on LinkedIn

In addition to the manual method mentioned by Brannigan (on 7/14/15) [http://community.linkedin.com/questions/135682/url-for-a-status-update.html] one can also use a "stem" URL to which must be added a unique topic ID number corresponding to the particular post.

The two "stem" URL formats are as follows:
https://www.linkedin.com/nhome/updates?topic=XXXXX
https://www.linkedin.com/hp/update/urn:li:activity:XXXXX
Where the XXXXX indicates the topic ID number that is unique to each post.

To get this ID number:
* Find the post (either natively or on their own page by using the menubar: Profile / My Updates).
* Then highlight the word "share" in the bottom of the post and right click "Inspect" (in Chrome, though other browsers allow means of viewing source code/CSS for pages as well, see also firebug for Firefox).
* The topic ID will appear just below the <span> for the share button in the <form class="comment-box"> tag.
* Take the topic ID number and replace the XXXXX with it at the end of one of the two stem URL's above and you've now got a direct URL for your particular status update.

Example: https://www.linkedin.com/nhome/updates?topic=6103960927751651328

Naturally, it would be far better if LinkedIn would just wrap a direct anchor tag around one of the post elements so it could be more easily cut and pasted when necessary. (Facebook, Twitter, Google+, and most other social media networks do this or even provide embed code to make it easier.)

I'll also note for those with programming skills that LinkedIn provides at least limited API access for posting updates and returning the resulting URL. The opensource Known platform uses it and there's a plugin available on Github with sample code for those who might appreciate it: https://github.com/mapkyca/KnownLinkedin

"Summary" field not maintaining data · Issue #30 · dshanske/indieweb-post-kinds https://github.com/dshanske/indieweb-post-kinds/issues/30

The field "Summary" under the "Citation" tab in prior versions was constantly self-updating with details of the original website/URL and not allowing the editor to make permanent changes which then propagate to their site.

Under the changes in v2.2.0 it seems like one can finally make changes to this field manually, but after saving/publishing, the field seems to self-delete and any future updates to the post result in the "Summary" text disappearing from the final post (at least from my tests with bookmark post types.)

General Suggestions for data and UI · Issue #29 · dshanske/indieweb-post-kinds https://github.com/dshanske/indieweb-post-kinds/issues/29

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?

Sorry for the delay, but my work schedule and travel have been awfully heavy lately. It does sound like the issue I'm having is somewhat related to the discussion on https://github.com/raamdev/independent-publisher/issues/155

I've got two separate installs with the same IndieWeb plugins installed. One uses Independent Publisher and the other is a slightly older version of the Academica Theme (v1.2.3 downloadable from https://www.dropbox.com/sh/ym0c78uyzltpeu1/AAByejNd8MG83I2MVOFXOuPaa?dl=0) which is outputting the facebook likes, twitter favorites, and reposts properly (or at least as I would expect.)

For some reason Independent Publisher isn't outputting Brid.gy likes, favorites, or resahares from Twitter and Facebook out of the box the way that Academica (or even WP common themes like Twenty Fourteen or Twenty Fifteen) does. They're not showing up at all. On the site with Academica Theme, I've tried doing a "Live Preview" of the Independent Publisher theme and there, it also seems to be "eating" (not showing) these additional comments from Brid.gy while all the other traditional comments do show up.

However, while you're tracking down the issue(s), you might also consider tweaking one additional output issue with respect to these types of comments. From a UI standpoint for themes using IndieWeb, I would recommend that the comment section sort out the comments and display them somewhat differently. For simple Facebook likes and Twitter favorites, it might be best to aggregate all of them into a facepile [http://indiewebcamp.com/facepile] with a simple header ("Liked on Facebook"/"Favorited on Twitter") followed by the photo icons of the people who liked/favorited the article within those platforms. (This is similar to how most Wordpress sites handle Likes/Stars natively within WordPress.) Following this it could create a facepile of people who reposted/reshared the post. Then after this the rest of the comments should be sorted by date/time as comments traditionally are as this will allow people to more easily read/consume the actual commentary.

This post has an example of a combination of likes/favorites/reposts and actual comments that would be better sorted into a facepile section followed by a more "traditional" comments section. http://boffosocko.com/2015/07/27/algebraic-number-theory-ucla-extension/

I'm supposing that it's how Independent Publisher is rendering the output of wp_commentmeta into its comment section that causes some of these brid.gy-fed likes/favorites/reposts to disappear.

If it helps, I'll also point out a previous and possibly related issue I'd run across vis-a-vis IndieWeb and output of comments: https://github.com/pfefferle/wordpress-webmention-for-comments/issues/1. The solution was most likely the way that the Semantic Linkbacks plugin (an IndieWeb WP-specific plugin) was handling its output. Here it's likely that @dshanske or pfefferle may be of more assistance in sorting things out if necessary.

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?

I recall a few other resources in the same category as this. Here are a few links for meta-coverage on them, which may provide more beneficial than spending hours trying to delve into how to use them:
VidBolt: http://chronicle.com/blogs/profhacker/annotate-video-on-the-fly-a-review-of-vidbolt/56787
Socialbook: http://chronicle.com/blogs/profhacker/using-video-annotation-tools-to-teach-film-analysis/57171

Other tools of interest, which you'll see notes on in the comments to the two above articles:
VideoAnt: http://ant.umn.edu
ULBPodcast: https://github.com/ulbpodcast and http://ezcast.ulb.ac.be (open source code available)
Genius.com: http://boffosocko.com/2014/04/08/rap-genius/ Particularly take a look at http://lit.genius.com/ which is a great tool for classrooms to do small scale shared annotations and close reading with the benefit of full texts (in particular, try looking up the various creation stories, eg: Gilgamesh [http://genius.com/Epic-of-gilgamesh-tablet-1-the-coming-of-enkidu-annotated; Letters of Paul [http://genius.com/Laura-nasrallah-the-pauline-epistles-contents-annotated], which was part of HarvardX religious studies course and is an excellent example of using the platform for education]). There's also http://genius.com/history-genius.

#BigHistory

@raumzeit77 http://indiewebcamp.com/wordpress has some pretty great resources for implementing IndieWeb on WordPress.

If it helps, try following some of what @pfefferle and @dshanske are doing here on GitHub as they seem to be two of the foremost IndieWeb-ers in the WordPress space. They've got wealth of plugins and know far more than I, though I do my best to dabble as I have time.
#IndieWeb

+1 from me on this feature request. (It would be cool to see an awesome theme like this also support microformats v2 as well. Sempress is the only theme out there that does this already see: https://github.com/pfefferle/SemPress, so it would certainly set the theme apart.)

@raumzeit77 As a temporary fix for the IndieAuth piece, you could add a text widget to your site that helps you get compliance with some of the IndieWeb Specs. You can also repeat some of the social icons with "invisible" links so that they don't actually display on the page, but are machine readable for IndieWeb purposes. It's not the best fix/workaround as you'll need to remember that the "invisible" code is there at some later date, but it should get you over the hump. Keep in mind that not all providers work with IndieAuth, though platforms like Twitter and GitHub do.
Try putting the following into a text widget (some portions will be visible others, link tags for example, will not):

<pre><code>
&lt;div class="h-card"&gt;
&lt;link href="https://facebook.com/USERNAME" rel="me"&gt;
&lt;link href="https://twitter.com/USERNAME" rel="me"&gt;
&lt;link href="https://plus.google.com/+USERNAME1/posts" rel="me"&gt;
&lt;link href="https://www.pinterest.com/USERNAME/" rel="me"&gt;
&lt;link href="sms:+12125551212" rel="me"&gt;
&lt;link href="mailto:me@emailaddress.com" rel="me"&gt;
&lt;br/&gt;&lt;br/&gt;
&lt;img rel="me" class="u-photo" src="http://domainname.com/site_icon.png" alt="" width="200" height="200" /&gt;&lt;br/&gt;&lt;br/&gt;
email: &lt;a class="u-email" href="mailto:me@emailaddress.com"&gt;me@emailaddress.com&lt;/a&gt;&lt;br/&gt;
phone:&lt;span class="p-tel"&gt;&lt;a rel="me" href="tel:+12125551212" &gt;+12125551212&lt;/a&gt;&lt;/span&gt;&lt;br/&gt;
&lt;p class="p-note"&gt;
&lt;span class="p-job-title"&gt;President&lt;/span&gt; and &lt;span class="p-role"&gt;CEO&lt;/span&gt; at &lt;a class="p-org" href="http://domainname.com" target="blank" &gt;Company Name&lt;/a&gt;; &lt;br/&gt;
&lt;span class="p-locality"&gt;ANYWHERE, NY &lt;/span&gt;&lt;span class="p-country-name"&gt;United States&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;
</code></pre>

Some of the code will also qualify you for some additional levels within the IndieWeb identification space relating to h-card.

#IndieWeb

Except that https://github.com/idno/Known/graphs/contributors would indicate that you do code quite a lot... We can only imagine how busy you must be!

@benwerd Where exactly should one look? idno/HanShotFirst https://github.com/idno/HanShotFirst

There are two Fragmentions plugins available that might be included in the IndieWeb plugin:

Christiaan Conover:
https://wordpress.org/plugins/wp-fragmention/
https://github.com/cconover/wp-fragmention
Luis Rodriguez:
https://wordpress.org/plugins/fragmentions/
https://github.com/goblindegook/Fragmentions/

At present Conover's has 20+ installations and was written first while Luis's has 0 installs,but is more recently updated. Both seem to work on my site reasonably well, though someone more experienced than I may have an opinion on which is "better" from a coding standpoint.