Jonathan LaCour

FYI, I've updated the [pull request to add this to Known](https://github.com/idno/Known/pull/1764), and have relocated the feeds (original comment edited for clarity). I've also changed the `lat` to `latitude` and the...

FYI, the pull request has been merged into Known, so it now features JSON Feed support. It'd be great to get some feedback on the `_indieweb` extensions and see if...

@voxpelli I don't have an issue changing the `_indieweb` key to something else, or changing the attributes I've added so far to match other, existing formats like jf2. In fact,...

> My plan is to create a profile of jf2 that closely matches jsonfeed, noting what fields MUST/SHOULD be present. It would still use microformats2 vocabulary, so extension can be...

Personally, I like having a type field, in spite of the fact that it can be ignored. Sure, consumers could go through the "post type discovery" algorithm that Tantek outlines,...

Thanks, @dissolve, I think [the h-entry page on microformats.org](http://microformats.org/wiki/h-entry) has all of the details I'm looking for. By my read, it means that the extension (and its implementation in Known),...

I've got an initial implementation of this I completed last night here: https://github.com/cleverdevil/Known/commit/9fc50f5c3838a2615f1be651eb6b6f4baf872b88 I'll be submitting a PR to Known after some testing.

And its also pushed out on my site, if you want to see it in action: * https://cleverdevil.io/content/all/?_t=jsonfeed For some particular post types: * https://cleverdevil.io/content/rsvp/?_t=jsonfeed * https://cleverdevil.io/content/locations/?_t=jsonfeed * https://cleverdevil.io/content/photos/?_t=jsonfeed *...

FYI, this pull request has been merged into Known, so now all Known sites will support this extension, along with JSON Feed.

Critically, I’d say that the population of the metadata could be automated on the server, optionally, but just having it available in the API for clients would be a great...