Indeed - every silo wants you to use their own specific markup, but even then they choose what to show. I made a post a while back that gave a different summary on every silo platform https://www.kevinmarks.com/partialsilos.html
Of course, since then some of the silos have died or given up on their own systems, but microformats remains useful if you want to co-operate.
That's not exactly accurate. The wiki has been edited recently, and change discussions are now done through github issues before updating the wiki, as that is more convenient than inline chat in many cases https://github.com/microformats
Also a lot of the practical discussion of microformats use is at the indieweb wiki - see https://indieweb.org/posts#Types_of_Posts for h-entry for example
Hi Clay, Kevin Marks here. I an help you scrape it out of wordpress into a static site if you like, I've done similar for Dan Gilmor and other old bloggers. Ping me - [email protected]
Read the post - previously deleted tweets showed the blockquote fallback. Now they get a useless injected blank iframe, removing the blockquote from the dom.
If they want to change this, they can have a new version of the widgets script that makes it clear that it will edit your site, and switch to that in future embed links from the site. Changing the existing one is leaving holes all over the web. Buzzfeed is decimated.
It's not a dogma so much as a warning from experience. If you post to your own site first you do retain control. If you rely on the silos' api to extract it back to your site you are dependent on them remaining committed to their api. That has not been a good bet in the last decade.
Refusing to use attributes in this kind of *ML and using <param> instead makes this a mess to parse safely. I imagine this will be read as HTML and the params will show up in the document oddly.
The specific reference to email was based on frustration with endless mailing list bikeshedding, especially on 'standards' mailing lists. Building a community around irc, wikis and posting on our own sites was a deliberate alternative.
It is a very ugly term; 'eat what you cook' is clearer. The point is that rather than theorising about 'what people want' you should build tools that solve your own problems, and practice with your own site first.
This was important early on in Indieweb as there are a lot of people proposing that online social networks should work in a specific way, and demanding others change; building something you use daily yourself is a better basis for discussion.