Last Updated

Map

Post Types, Post Formats, Post Kinds

In my recent development of the Post Kinds plugin, I’ve felt the need to try to explain what exactly a Post Kind does. I needed a way to distinguish the custom taxonomy I’d created. So let’s define the competition for the terms…

  • A Post Format is a piece of meta information that can be used by a theme to customize its presentation of a post. Confusingly, the slug for post formats is ‘type’.
  • A Custom Post Type is a single item of what is generally called a post, although post is also a specific post type. It is more a custom content type.
  • A Taxonomy is a grouping mechanism for some posts.
  • A Post Kind is a taxonomy that allows posts to be classified according to the kind of post it is.

So, not so much of an invention as a necessity to distinguish from similar concepts

They have gone through some changes. But, at the moment, they are designed as a drop-in replacement for post formats. There are actually many good reasons why the WordPress developers decided a set of standardized formats would make sense…most notably the ability to change themes without losing your customization. Fewer and fewer people are using post formats, however.

Indieweb Post Kinds are designed the same way. The two can exist simultaneously, but you are better off disabling formats in favor of a single solution.

As more and more sites incorporate concepts like “Like’, ‘Favorite’, and so on, one’s own site should support these.  This allows for that.

The plugin supports sending webmentions via the WordPress Webmentions plugin, to send notices to other sites you might be ‘liking’, replying to a post on, etc…assuming the other site supports it. But more and more indieweb sites are doing so.

Download

Updated Response Display

Screenshot from 2015-01-04 14:48:04On the 23rd of December, I completed a major update to this site, as part of a commitment to do so by 2015. I often forget to document these changes.

I redesigned and updated the portion of the post that shows what a post is in response to(for those that are in response).

Unlike the previous, this blends in with the background of the post itself, and adds in support for an author and profile picture.

I’ve captured two examples of that in this post for posterity.

More coming, but feedback is appreciated.

 

Screenshot from 2015-01-04 14:48:13

Indieweb 2014 End of Year Summary

I found out about Indiewebcamp in March of 2014, so I have not yet been involved with it for a complete calendar year. But, I’ve decided, with the end of 2014 approaching, to take stock on how I’m doing, and can reassess next year.

As part of this evaluation, I am using the Indiemark system, a set of metrics for measuring the indieweb-ness of a site, and a step-by-step approach to incrementally adopting indieweb features.

Identity

Level 2

I own my own domain, and I post h-card contact info and an icon on`my page.

I have given much thought to people-focused communications, which falls under this category. Need to develop this more.

 Authentication

Level 1

I have set up Indieauth, which allows me to authenticate to sites using my domain name. But this exposed a bug in one of the libraries indieauth runs on, which has gone up the chain for repair. There is currently no level 2, but a level 2 may include two factor authentication, which I am trialing as a security measure…

Posts

Level 3

My Post Kinds/Taxonomy plugin supports different kinds of content. And while I support the following types, I am actually planning to limit myself due overlap.

  • note
  • article – longer form content
  • reply
  • like or favorite, depending on your preference – I have the hardest time with deciding
  • photo – post where the primary content is an image
  • repost – this is a complete reposting of the original, haven’t really done those
  • rsvp – only used once. I really need to go more places.

Syndication

Level 2

I syndicate(POSSE) my posts to applicable silos(Facebook, Twitter, Google Plus). I am not currently linking back to the originals, as I previously did, unless relevant, as I haven’t gotten my syndication working the way I’d like.

 

Posting UI

Level 3

It’s hard to say where I am with this. I have a UI for posting, the WordPress interface, one I created for adding context information for replies, but I’m still not happy with the UI for syndication.

I’d like to work on a simpler UI for the future. The WordPress one is very useful, but has a lot of ‘stuff’ to finish a post. Great for an article, not so great for a note.

Navigation

Level 4

I have previous/next navigation, time based archives, and tag based archive pages, so I’ve covered this category as of now.

Search

Level 4

My site is searchable using the built-in WordPress search functions.

Aggregation

Level 4/5.

Thanks to the work of Matthias Pfefferle, I receive webmentions and show comments and mentions from other people on my site. That achieves the notes for Level 5.

However, I’ve spent a lot of time on reply-contexts, which I am manually entering. My project continues with plans to pull in more of this information automatically, which is more of a Level 4 goal.

Web Actions

Level 3, but not Level 2.

I had hard-coded actions and web actions on my site. They were removed for now, as they didn’t work the way I wanted. They will likely be back.

I do provide syndication links on posts of all other places the post can be found.

Security

Level 5/6

I serve the site now exclusively over https, and redirect anyone requesting a plain unencrypted site. The site supports SPDY for increasing speed over an SSL site.

The site has an A rating with Qualysis SSL Labs. It uses an SHA-2 certificate and supports Mozilla’s Intermediate Compatability Cipher List. This makes it fairly up to date in this category, but I am holding out for the A+.

 Miscellany

This site is also now delivered over IPV6 as well as IPV4.

The site runs on Nginx, and uses a caching system I wrote.

Conclusion

One of the most interesting things about getting involved in this group has been building things. I have always loved making things, and have never been good at it. I still think I am a reasonably good idea person, but a horrible programmer.

I still have 4 days in 2014, if I want to build something else.

Reposted https://www.youtube.com/watch?v=h80l4XIPJC4 (youtube.com)
In 1964, Bob Dylan wrote My Back Pages as one of the last songs he composed for “Another Side of Bob Dylan.” The original version was not as popular as the one above, recorded by the Byrds three years later.

The song has been stuck in my head today. With the song, Dylan comments on what he once accepted and now doubts, and to a degree, celebrates where he is now.

The Problem With and the Future Of Mentions

My involvement with the Indiewebcamp movement continues, and I want to encourage what is possible.

One of the building blocks of Indiewebcamp is the webmention.

Webmention is considered an update to pingback. Pingback was proposed in 2002 as an automated version of the Trackback concept that added link verification. The basic principle of  a Pingback is Person A posts something. Person B posts something that links to Person A’s post, which sends a pingback. Person A confirms by visiting Person B’s site to check the link exists. The pingback specification uses the XML-RPC framework as a method of transport.

Akismet, a hosted anti-spam service, has taken the measure of blocking all of them by default, because they’ve become such an avenue for spammers. We certainly think Trackback support should be discontinued, and Pingback likely behind it. It isn’t just that they’ve become an avenue for spammers…but they add no value.

Webmention is similar to the pingback specification in use, but it is carried over plain HTTP as opposed to XMLRPC. This means it is easier to implement, and a simple HTML form can send webmentions.

Most pingbacks and tracks contain title of the post that sent the trackback and ellipsed […] … […] summary text, which is of little use. No improvement of presentation is likely to go forward without addressing the underlying protocol.

The proof of concept of this is the WordPress webmention plugin, which adds support for webmentions, and its companion plugin, Semantic Linkbacks, which takes the output of any sort of linkback and turns it into human readable text, along with a profile picture. It allows for a much nicer presentation.

The way Semantic Linkbacks does human readable text is that it parses the site that has sent the mention. It counts on the site being microformats 2 complaint, although it will try to fall back on the original microformats standard and other information if needed.

I’ve thus filed a feature request with the people at WordPress, the start of my attempt to make WordPress more friendly. It is specifically for Microformats 2 support in WordPress, which would allow better parsing of WordPress sites.

With this, more sites will display markup that will allow sites receiving mentions from them to better present those mentions. Part of the reason mentions are mostly garbage is we have made them that way with neglect.

I’d like to not only see Webmentions baked into more sites, but improved presentation tools and discussion around them, and then…the Spam problem will be one worth solving. There are efforts underway to address this.