Show HN: Loud – Podcast-first feed syndication protocol
&gt; AvatarURL string
&gt; Square show avatar, recommended 2000x2000px minimum size, 1:1 aspect ratio<p>A 2000 pixel minimum, huh?<p>It&#x27;s also a bit weird that the yaml keys are all lowercase but the other two formats are camel cased<p>As far as the spec goes:<p>You will want to be cautious using string for everything and then trying to define the payload using natural language. Let&#x27;s take &quot;EpisodeHost []string - List of episode hosts&quot; as a concrete example. Is it their name, email, URL to their IMDb page, does it support html, or (worst case from the perspective of a podcast client implementator) &quot;it depends on the network&quot;? When a field in a spec is string and &quot;do whatever you want&quot;, without fail one will find a chocolate chip recipe and an XSS possibly in the same file<p>In that same vein, the fact that FeedURL is singluar but the feed has 3 media types implies that the return type is either negotiated by an Accept header, is chosen by the network provider, or random. That means as a client implementator, I have to immediately support all three parsers with parity out of the gate because I have no means to choose what bytes are sent back.<p>Speaking of bytes, presumably the spec makes the assumption that the file itself is UTF-8 but assumption and standard are at odds with one another<p>I would be surprised if one couldn&#x27;t extend the Atom spec with these concepts, but I guess the intro section saying it was designed to be more experimental implies that wasn&#x27;t a consideration