June, 2020 | Chris Aldrich

Syndicating my IndieWeb Wiki edits to my personal website

I don’t have a specific “Edit” post kind on my website (yet!), but I’ve set things up–using a prior recipe–so that edits I make to the IndieWeb wiki are syndicated (via PESOS) to the Micropub endpoint on my website to create draft posts on my personal website!

Presently they were easiest to map to my website as bookmarks until I can create the UI to indicate edits, but changing the UI piece, and retroactively modifying some data for posts, should be fairly simple and straightforward for me.

I’m not sure I’ll keep the entire diff content in the future, but may just keep the direct text added depending on the edit and the potential context. We’ll play around and see what comes of it. It’s reasonably sure that I may not post everything publicly either, but keep it as either a draft or private post on my website. In some cases, I may just add the edit syndication link on an original bookmark, read, watch, or other post type, a pattern which I’ve done in the past for articles I’ve read/bookmarked in the past and simply syndicated manually to the wiki.

I’ll also need to tinker with how to save edits I make directly in the chat channels via Loqi, though I think that is straightforward as well, now that the “easy” part has been done.

I only wish I had thought to do this before I made the thousands of edits to the wiki earlier this week. Both IndieWebCamp West 2020 and the edits for part of organizing that were the inspiration for finally getting around to doing this.

This isn’t as slick as the process Angelo Gladding recently did a demo of and is doing to syndicate his edits to the wiki from his website using a POSSE syndication workflow, but I’ll guarantee my method was way less work!

Also, since my edits to the wiki are made as CC0 contributions, the POSSE/PESOS flow doesn’t make as much difference to me as it might on other social silos.

I don’t edit Wikipedia incredibly often, but perhaps I set that functionality up shortly too.

Here’s the first example (public) post: https://boffosocko.com/2020/06/30/55772818/

I’ll get around to fixing the remainder of the presentation and UI shortly, but it’s not a horrific first pass. It’s at least allowing me to own copies of the data I’m putting out on the Internet.

Replied to Hovercards by

Joseph Dickson (linuxbookpro.com)

A Hovercard also known as a h-card is a bit of content that’s shared about you on your website kinda like a visual/interactive business card. Implementation looks like Gravitar. It can contain far more information and is self-hosted.

Joseph, I thought I caught you say it during the demos, but wasn’t 100% sure. Reading this, confirms it. You’re conflating two different but very similar ideas.

h-card is a microformat class around the mark up of data about identity elements like names, addresses, cities, countries, and often including an avatar or photo. Hovercard is a UI element that creates a visual card when one hovers over a name or similar element that would contain h-card details.

Gravatar serves some of these functions for WordPress from a centralized perspective. The data you would imput there would be wrapped with the h-card class, while Jetpack would give you the ability to display Gravatars as hovercards, so that when you hover over an avatar it will display more detail about the person in a small card-like UI.

For your experimentation purposes, you should be able to use just one post to test against my site. Once you’ve modified your theme, you can simply resend the webmention to my site and that will automatically update your original post. You don’t need to create new posts each time to test it out.

If you haven’t gotten it cleared up, do join us in the IndieWeb #WordPress channel, or catch us at an upcoming HWC event.

@@ Line 94: / Line 94: @@
 | published = 2020-06-29
 | archiveurl = http://web.archive.org/web/20200629215208/https://paulopinto.org/2020/06/indiewebcamp-west-2020/
 }}
 * {{addyourself}}