@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.
@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.
@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.
@danbenjamin@firesidefm And “attachments” should be an array. That’s one where JSON Feed differs significantly from RSS’s one-and-only one “enclosure”.
@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.
@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.
@danbenjamin@firesidefm No argument there. The idea, though, is that JSON Feed defines a limited number of defined fields — extra fields go in extensions.
149 Followers 809 FollowingFascinated by search engines and #AI! Software creator of productivity apps. #BASB #Buildinpublic current hobby: 🔎+🎲=Randomize your default search engine ⬇️
691 Followers 1K FollowingTeam Lead of Community & Partner Engineering @CircleCI | Co-founder @TheReserveForce. Formally #DevRel at CircleCI and @Linode | @USNavy Veteran
713 Followers 243 FollowingEnables +700 000 researchers, developers, journalists and curious people to follow web sources they care about in one place.
278 Followers 1K FollowingYou want to know where are your visits are coming from?
You want to know where domain is hosted?
Come to https://t.co/so7R6qO9BX and discover it!