#LoqiPost Type Discovery specifies an algorithm for consuming code to determine the type of a post by its content properties and their values rather than an explicit “post type” property, thus better matched to modern post creation UIs that allow combining text, media, etc in a variety of ways without burdening users with any notion of what kind of post they are creating https://indieweb.org/PTD
#Loqimetaformats started as an April Fools joke concept to describe how to both publish using microformats class names and openly parse meta tags as a fallback for what should be in-the-body visible data, including backcompat with OGP, Twitter Cards, and meta author, description, and anything else real sites (like search engines) appear to consume https://indieweb.org/metaformats
#jackyI'm thinking about people who might not publish mf2 but appear in one's reader, a reader that could use it as an extension to mf2 could more apprioriately show their content in-stream
#jackyof course, this is def speculation but I was curious if it was a _novel_ one lol
jacky and mro joined the channel
#[tantek]1jacky, I think the key point here is that /ptd was designed for legacy systems that have an existing post type dependency. New systems, software, services shouldn't because they ought to be designed to adapt layouts, presentation etc. based on the properties present, not based on some abstract typology of posts
#[tantek]1there's enough existing implementations (e.g. FB) that make it clear that not only do implementations not need that abstract explicit post types intermediate step, but that doing so causes a bad backpressure on the UX, forcing users to have to think about post types