Micropub Plugin work for WordPress
It will include a Media endpoint
Code for integration with the WordPress REST API
This sketch solution may be an end-around the issue of getting WordPress (or potentially other CMSes) Themes to be microformats 2 compatible, and allow a larger range of inter-compatibility for websites and communication.
The researcher’s post can webmention an aggregating website similar to the way they would pre-print their research on a server like arXiv.org. The aggregating website can then parse the original and display the title, author(s), publication date, revision date(s), abstract, and even the full paper itself. This aggregator can act as a subscription hub (with WebSub technology) to which other researchers can use to find, discover, and read the original research.
Readers of the original research can then write about, highlight, annotate, and even reply to it on their own websites to effectuate peer-review which then gets sent to the original by way of Webmention technology as well. The work of the peer-reviewers stands in the public as potential work which could be used for possible evaluation for promotion and tenure.
Readers of original research can post metadata relating to it on their own website including bookmarks, reads, likes, replies, annotations, etc. and send webmentions not only to the original but to the aggregation sites which could aggregate these responses which could also be given point values based on interaction/engagement levels (i.e. bookmarking something as “want to read” is 1 point where as indicating one has read something is 2 points, or that one has replied to something is 4 points and other publications which officially cite it provide 5 points. Such a scoring system could be used to provide a better citation measure of the overall value of of a research article in a networked world. In general, Webmention could be used to provide a two way audit-able trail for citations in general and the citation trail can be used in combination with something like the Vouch protocol to prevent gaming the system with spam.
Government institutions (like Library of Congress), universities, academic institutions, libraries, and non-profits (like the Internet Archive) can also create and maintain an archival copy of digital and/or printed copies of research for future generations. This would be necessary to guard against the death of researchers and their sites disappearing from the internet so as to provide better longevity.
In this last episode before David Shanske and I head to the Indieweb Summit in Portland, Oregon, we discuss updates to people’s Indieweb experience, little things David has hidden in plugins, web-signin vs IndieAuth, etc.
We’re both looking forward to seeing those of you who can join us in Portland.
In this episode, David Shanske and Chris Aldrich discuss how the Post Kinds plugin mapped IndieWeb types of posts to WordPress and why, the defined as opposed to implied types set up, and avatars.
While the conversation is WordPress-centric, there are a lot of discussions here relevant to a broader IndieWeb audience about adding new types of posts to your site, trying to design things flexibly (although a developer’s guide is probably needed), etc.
Running time: 1 h 16m 00s | Download (23.8 MB) | Subscribe by RSS
Summary: With the GDPR regulations coming into effect in Europe on May 25th, privacy seems to be on everyone’s mind. This week, we tackle what webmentions are, using them for backfeed, and the privacy implications.
Summary: Facebook has recently announced it will be shutting off its API access on August 1st for automating posts into its ecosystem. For a large number of users this means it will be much more difficult to crosspost or syndicate their content into the platform. As a result, this week David Shanske and I discuss the good and the bad of this move as well as some general thoughts around the ideas of syndicating content from one site to another.
David also discusses plans he’s got for changes to both the Bridgy Publish Plugin and the Syndication Links Plugin.
Summary: At long last, after about three weeks worth of work, David Shanske (along with help from Aaron Parecki) has added the ability for the IndieAuth plugin for WordPress to provide an IndieAuth endpoint for self-hosted versions of WordPress, but it also has the ability to provision and revoke tokens.
This week, David Shanske and I discuss IndieAuth and the WordPress plugin’s new functionality as well as some related micropub work David has been doing. To some extent, I alternate between acting innocent and serving as devil’s advocate as we try to tease out some of the subtleties of what IndieAuth is and what it means to the average user. As usual, David does an excellent job of navigating what can be some complicated territory.
This first half of the episode was originally recorded in March, abruptly ended, and then was not completed until April due to scheduling.
It’s been reported that Cambridge Analytica has improperly taken and used data from Facebook users in an improper manner, an event which has called into question the way that Facebook handles data. David Shanske and I discuss some of the implications from an IndieWeb perspective and where you might go if you decide to leave Facebook.
The originating articles that kicked off the Facebook/Cambridge Analytica issue:
You’ve made the decision to leave Facebook? Your next question is likely to be: to move where? Along with the links above, we’ve compiled a short list of IndieWeb-related places that might make solid options.
Micro.blog for $5/month (or bring your own web site for free)
In the future we hope to have additional broad ranging conversations and perhaps interviews with others about various IndieWeb related topics.
Part of this is also an opportunity to improve audio post presentations on our websites over time. While David posted the “original” of this post on his site, I had to debate whether or not I would technically repost it or make an original of my own. Ultimately I opted for the latter.
David, by far the more veteran podcaster, deserves the lion’s share of the credit for his audio set up and recording facilities.
I’ve wanted to create a podcast for a long time, but the effort involved just seemed like too much. So using my own website, I thought I’d see what I could come up with in under an hour in terms of creation and posting. Here’s the first “episode” of my microcast which I’ve conceived of, created, and posted in under an hour with equipment I happen to have on hand: