JSON Feed

[JSON Feed @jsonfeed]

@gallerdude @viticci @macstoriesnet Great work, Jack! It doesn't matter how many lines of code, the point is it was "not that many!" :)

[JSON Feed @jsonfeed]

@hvrmeer @jsonfeedreader Best thing would be to open an issue on the GitHub project so it can be regarded by folks who have focused on the spec details.

[JSON Feed @jsonfeed]

@hvrmeer @jsonfeedreader Hi Hans - our Twitter account is run by a variety of volunteers, and not all of us is perfectly suited to answer such a question.

[JSON Feed @jsonfeed]

@mawawa Maybe! Thanks for the suggestion.

[JSON Feed @jsonfeed]

@mawawa I don't think anybody is maintaining a master list of such blogs/sites. The early adoption has been so great I wouldn't envy the task!

[JSON Feed @jsonfeed]

We've been working on an official validator. Already pretty useful to catch potential issues in your feed. https://t.co/UjiS2l7U7o

[JSON Feed @jsonfeed]

@Lioncourt Hi Josh - it's Daniel, from @marsedit, on the @jsonfeed duty at the moment, and glad to see your enthusiasm for the format!

[JSON Feed @jsonfeed]

FeedPress support for JSON Feed coming soon. That's a big one: https://t.co/S8nHd6eP9r

[FeedPress @FeedPress]

Teaser: Can you guess what's coming this week? Hint: It rhymes with "basin." 😎🚀 #rss #podcast #blog

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm We now have an experimental validator:

https://t.co/Af3Qn2fl6c

If you move “subtitle” to “_fireside” those feeds should be good.

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm For the podcast-specific fields (like “explicit”), for now, you should either put them in a “_fireside” ext., or omit them and wait.

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm And “attachments” should be an array. That’s one where JSON Feed differs significantly from RSS’s one-and-only one “enclosure”.

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm We really need a public JSON Feed validator. Coming soon, I hope. In the meantime: “owner”, “subtitle”, and “image” are also not valid.

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm What we should do, putting aside for now exactly who “we” are, is come to a consensus on a simple `_podcast` extension to JSON Feed.

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm No argument there. The idea, though, is that JSON Feed defines a limited number of defined fields — extra fields go in extensions.

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm “pubdate”, “explicit”, and “copyright” aren’t valid fields in JSON Feed. See the spec section on extensions:

https://t.co/CisYlVXoCn

[JSON Feed @jsonfeed]

@danbenjamin @firesidefm That’s great. But right now it looks like it’s not quite following the spec — it’s more like RSS-as-JSON than JSON Feed.

[Greg Scown @macgreg]

Quick “How to” on Setting Up and Customizing Your @JSONFeed: https://t.co/A1ndUGr6Rg

[JSON Feed @jsonfeed]

@codeOfRobin Nothing official yet!

[JSON Feed @jsonfeed]

@cpj1 @thatcks Hi - our announcement states the motivation for creating a new format. https://t.co/TsvJvaH87E

[JSON Feed @jsonfeed]

@thatcks By the way, I read your blog posts. Thanks for the feedback. We'll keep these in mind if similar issues are discussed on GitHub.