Kind: Notes

short content: a post or status update with just plain content and typically without a title
Released Post Kind 3.3.0. This has a lot of major changes under the hood. A completely new load system for dependencies and a lot of parsing improvements from the Parse This library. On the user facing side, Post Kinds takes over generating RSS and Atom feeds to remove empty title properties, adds Aaron Parecki’s Media Fragment script, adds remote as an RSVP property, and a bunch of other little fixes.

The biggest change is the continuation of moving media related metadata into the attachment itself in the media library, rather than storing it in the post. When you edit the response properties, they will go directly into the attachment data.

In a future version, I hope to continue with that to add better displaying of photos. Right now, the title of the photo is not showing, only, because it is using the built in gallery to generate the photos, the caption, which maps to the summary property. I will release a future version that shows the title if the caption is not set, as well as some other related fixes.

There is always more to do. Being as this was a major change, I wanted to let it sit for a little while before I released another version.

Simple Location 3.8.1 released. Fixes two bugs and automatically adds location name to attachments if they have location data in the photo itself. Also takes the timestamp in the photo, recalculates timezone based on the location data, and stores a timestamp.
Released an update to the JSONFeed plugin for WordPress. It addressed several open issues, noted compatibility with the latest version of WordPress, and adds comment feeds for parity with the defaults.
Released a new version of Post Kinds. This fixes the ?kindurl= variable that externally sets the URL in the post editor to allow it to be passed from another program. It also adds a basic template for and enables usage of the eat and drink kinds.
Realized that the IndieAuth for WordPress update I pushed last week, because it uses more secure SHA256 hashing, should have prompted people to refresh their tokens. Sorry everyone. You’ll have to revoke your old tokens and get new ones. Apologies. Good opportunity to visit the manage token page under the User menu if you’ve never seen it.