Last Updated
MapAt the urging of some colleagues, I’ve started working with a professional coach to help me work through some obstacles I encountered in this last year as a WordPress focus lead. I’m fortunate in that Automattic will pay for me to receive ten coaching sessions per year.
(Since I’m also taking a…
Thinking of Homepage Mentions
One of the challenges I have been looking at has actually come because of others. Now, if you’ve been looking at my website, you might notice that, thanks to the efforts of myself, Matthias Pfefferle, and Ryan Barrett that there have been major improvements to the presentation of different types of responses on my site. I have a screenshot of the replies on a recent post.
Facepiles, the row of faces representing people who ‘liked’ or what have you, was actually the first project I tackled when I joined the Indieweb community back in 2014. I’ve learned a lot since then.
Either way, the current work not only builds on what I’ve learned, but the contributions by Ryan, who really wanted this feature available, really jumpstarted things. Now, all of these people below don’t know they commented on my site…as they commented elsewhere and I pulled it back to my site via webmention.
So, it brings me to a new problem I want to solve. Homepage mentions. What is that? So, in June, we implemented the ability to direct webmentions(which I’ve talked about before) that reference your homepage as opposed to a specific article to a designated page.
WordPress doesn’t allow the attachment of responses directly to the homepage, and david.shanske.com represents me, having a direct relationship to me on Twitter, Facebook, etc. So, any mention of my website or my username on one of those sites generates a mention that is sent to my site.
This is a problem in display. In recent weeks, I’ve had the following scenarios my website doesn’t yet deal with in a satisfactory way
- Someone referencing my website as me, effectively tagging me in their post as having been somewhere. Example: With David(david.shanske.com)
- Someone referencing my website as me in mentioning something I did. Example: David(david.shanske.com) kindly helped me.
Neither of this usages by others are displayed properly website, which is why they are not showing at all. I’m not sure how or where to display them.
Should someone mentioning me in this manner give me the option of generating a post, ala Facebook’s service of letting others post on your timeline, even if I moderate it somehow?
At the least, it should generate a message appropriate to the situation. And if it does, where should it go? Should I display recent mentions on the sidebar of my homepage? On a dedicated page?
The Indieweb declares a person tag as a tag on a post that refers to a specific person by URL and is done as a explicit action. Many of these mentions are explicit, but some are less so.
My goal is by mid January to figure out how I’m going to display these, one way or another, and write some code to do this. Perhaps as my project for Indiewebcamp Baltimore, coming up in late January.
Work on your #newwwyear Resolution to have a better website for 2018
https://github.com/dshanske/indieweb-post-kinds/issues/134
Meditations on my Grandfather
I flew to Florida on the first flight the following morning to be with my family. While it was not unexpected that my grandfather, turning 102 in April, would not live forever, there was a part of all of us who thought, due to the sort of person he was, he might just beat the odds on that.
I was set to come visit the following Monday, and it saddens me to know that I was only days away from seeing him, even if that had been the last time. I spoke to him, although he was not entirely responsive, from his hospital bed only the morning of his death.
But, that is about me. Let’s turn to my grandfather. There is a lot that people have said about him over the last few days, as not only did people fly down to Florida, family and otherwise, to call on my grandmother and provide comfort, but people in the halls, the local shops…everyone who knew him wanted to say that they had fond memories of him.
That is not uncommon after a death, but my grandfather had special skills in talking to people. I remember going into a store with him, many times in my childhood. He’d make quick friends with anyone…get their story, where they were from, make them smile a bit. And clearly, that paid off in dividends in the many people who remembered him.
I was touched by people, even those who had only heard me telling stories about him, sending me messages to say that I had painted such a vivid picture of the sort of person he was that they felt like they knew him.
It was always the skill of talking to people that I, often finding it difficult to start conversations with strangers, that I most tried to copy. He would often ask people what they did, or where they were from, or other similar questions to start a conversation.
His random question to one individual, asking them their maiden name, revealed a distant family relation with someone who had lived, unknown, in the same building as them for years.
So, one final time, I’m going to answer the question he loved to ask me. He asked so many times, I had my own unique way of responding in the Spring of 2016 when I took my current position.
I have been looking at this picture a lot in the last few days, and others. Even at over a century, and him having been in my life for longer than most have their grandparents around, no amount of time would have been enough.
My October in Review – Courtesy of Google
I have Location History with Google enabled. In October, as you may have noticed, especially if you visit my site, you may notice I was traveling around Ireland fro pleasure and business. Google sent me this email. I’ve taken some screenshots of it.
It shocks me how good Google has gotten with this over time, even going back to old dates, it has enhanced the information and cross-referenced the photos I’ve backed up to Google Photos. It has created a timeline and trip report I’d love to have a copy of. I can extract the data…but not the presentation so easily.
But this is the level of presentation I’d like to achieve someday on this website for my own trips. Not sure how I’ll get there, but being as Google has teams of engineers and I play with my website as a hobby…might be a while.
IndiewebPress: Improving Comments
Comments in WordPress were originally thought of as a way for visitors to a site to have discussions on the site. I’m going to refer to the traditional comment idea as ‘local comments‘. This is where someone fills out a comment form on a post, which adds a comment to the page, either with or without moderation.
Also built-in to WordPress are pingbacks and trackbacks. These are where another site notifies of a link to the page and this is displayed as a comment on the page. Pingbacks and trackbacks have their issues, and admittedly, WordPress, except for some minor tweaks, has left the presentation and features of these mostly unchanged, save for some security efforts. Therefore, it has become common to disable them. Webmentions are a replacement for the older pingback and trackback protocols.
There are also custom comment types used for things like logs, receipts(See mention in Trac Ticket which notes that popular plugin Easy Digital Downloads does this), etc. which are not part of the general vision of what a comment is. Of course, custom post types aren’t all traditional posts either.
Meanwhile, other areas of WordPress are getting functions to register functionality. 1n December of 2015, a ticket was opened for Custom Comment Types. This would, in theory, mirror the functionality of Custom Post Types, where a registration function would declare the functionality and behavior of a comment type.
But there are issues here beyond what is identified in the ticket. How will a theme know how to display the new comment type? There needs to be a way for this to be specified by the registration and overridden by themes that know what that comment type is. There is a possibility there may be some breaking changes in that design.
Meanwhile, comments cannot be referenced uniquely and distinctly. There is another ticket equally old, proposing comment permalinks. Whether this is just to find the comment on whatever page it is on, or allowing a comment template that emphasizes the comment by itself, it is an aspect of the comment system that needs replacing.
That addresses the structure, but not what could be done with it. Not only would this allow for webmentions as a medium to create comments(webmentions being the successor to pingbacks), but support for responses that are popularly used today such as like, emoji, annotation, etc. The Semantic Linkbacks plugin tries to create these relationships in comment meta, but it is not as robust as a supported implementation would be.
Annotations and marginalia recently have been of interest in allowing people not to just comment on a post as a whole, but on specific areas of it. This could also be a promising piece of a comment overhaul…supporting this. In my contributions to the Webmentions plugin, I started this by supporting URL fragments(see fragmentions), which would allow for a specific part of the post to be highlighted.
IndiewebPress: Connecting Your Site and Mine
In the previous article, I discussed my thoughts on the subject of comments as a structure and what comments could be capable of if that structure was improved. But, when I showed that to several people, the comment was, quite legitimately, that I didn’t explain what could be built on top of that. I had another topic in mind before covering this, but that made me want to document this as well.
Let’s start with webmentions. Webmentions builds on the idea of the two protocols that are built into WordPress: Pingbacks and Trackbacks. Trackbacks have to be discarded from WordPress. There is no verification of them…it is basically letting anyone post something on your site…moderated or not. The other site tells you they’ve linked to you(even if they haven’t) and what to make it look like on your site. And because of this…while I’ve tried to think of ways to save it, I think it needs to, over time, go on the chopping block.
Pingbacks, despite actually verifying that a URL links to where it says it does, currently don’t do anything else interesting in WordPress. The appearance and usage has stagnated. It could be improved on the display side, and I’ve tried to get interest in that…but I’m wondering as we move forward…considering the legacy design issues, the bad feelings, what I would like to see happen with comments, etc…if we should just let Pingbacks stay where they are with only some performance and other minor refinements, and develop Webmentions.
Webmentions have advantages. They support update and delete functionality if the source changes in the future. They have a standard recommended by the W3C(which the previously implemented protocols do not), as well as a dedicated community who has implemented them on their sites.
What was never realized in potential by previous protocols, but Indieweb community members are implementing is the magic. Someone links to your site with a post on their site. They use webmention to tell you that they linked to you. But what your site does at that point is controlled by you. You can parse their post and display it as a comment, or based on how their page is marked up, derive other meaning and relationships from it. You can just use it in a simple counter or stat display to note how many people linked to you. There have been some fun discussions of using it to share bibliographic data.
If you had to pick one thing, webmention is the key building block on which the Indieweb is built. By itself, it requires no trust on the part of the receiver. There is a developing extension called Vouch which allows the sender to provide proof that someone the receiver knows trusts them. And, moderation aside, presentation of this is wholly left to the receiving site. Back to the comment point in the previous article on this, one of the functional WordPress problems is that there is no way for a plugin to declare a custom comment type and tell the theme how to display it or whether to display it at all. You effectively have to hijack the comment template to do this, instead of working with it.
To the point of something like annotations, the idea of fragmentions which allow a specific part of a post to be referenced more effectively…WordPress doesn’t support inline comments of any type or marginalia. There is a trac ticket to implement the W3C’s work on annotations, but WordPress has nothing to allow for displaying this sort of work.
There is a current Webmentions plugin for WordPress that is under continual development. It was created by Matthias Pfefferle, and I have been a regular contributor to it. It handles the functional plumbing of webmentions, but not the improved display aspect. That has been delegated by its creator to a second plugin, Semantic Linkbacks, which attempts to offer the parsing of external sites and deriving information like author(name and photo), etc.
It is worth trying the combination of these. But there is more that can be done here as well. Cover more types, improve the ability to store commenter’s data, etc.
IndiewebPress: Users
In the Indieweb world, your domain is your identity. This would suggest that most WordPress sites should only have one user…representing the identity of the site. Users, however, represent roles and responsibilities within the system, not necessarily content creators.
In an update to the ‘official’ Indieweb plugin, I, with some encouragement, added the idea of designating a specific user as the ‘identity’ of the site…assuming there was one. But let’s expand that idea a bit. We have user metadata, we have the ability to define new roles and capabilities. So, what can we do with this but create new possibilities? We can better work what a role is, and add additional properties and behavior to improve the system.
There is a setting for an admin email, for which the suggestion to expand outward has been proposed for 8 years in this vein. This should be a property of any administrative account.
I have an idea I’ve long wanted to implement. It is based on a feature used by Postmatic. People who subscribed to the email service they provided would end up as users on your site. I’d like to see enhancements to the user profile. When trying to add other site profiles to user metadata, I discovered that this being left to the plugins has resulted in a complete lack of consistency.
There needs to be a consistent structure to add data to support URLs on specific other types of sites( for example, Twitter), or every plugin is going to have to retread this. This is the trouble we have with all metadata unfortunately.
That idea of using the user table for outside visitors has a lot of good potential. Commenters could create a profile on your site that could be imported from elsewhere…namely your own website. There is a certain level of trust there, because you would be displaying images and text about a person from another site…however, that is what gravatar does. Why not allow people to do it from their own site?
Gravatar itself is something that WordPress wouldn’t have put in today….a reliance on an outside service. The local avatar trac ticket is also a rather old request. It is time to look at avatars in general…to build a robust local system that is enhanced by gravatar…gravatar should not be that system. We can add in modern themeable profiles for users, as opposed to just archive pages. We can make a much better system for users.
The whole point of the ‘subscriber’ role in WordPress is for people not part of the blog to have an account they can do something with…follow the site, get updates, participate in comments…but this part of WordPress is woefully underused.
This theme is going to continue to develop and be customized, but it is now, at the least, nice enough for me to use it. What do you think so far?