The whole point of that post is to show that og hasn’t solved it. There are too many flavors of metacrap and no standards. And worse og is not only not “open” it’s a DRY violation.
If you want to spelunk a bit, Cory Doctorow approached the idea back in 2001: Metacrap: Putting the torch to seven straw-men of the meta-utopia
2 thoughts on “”
Ahh I now understand the point of the post was to point out the flavours of metacrap by customizing them. But that misses the point that a single og: tags in 2018 would have been just fine on all platforms.
Agreed it’s a DRY violation in principle, but it’s a small one (1 metacrap versus 8+). Also in reality most tools (certainly the services themselves) automate their creation from the content. Admittedly as @Moondeer has discovered the M.b. plugin for Twitter is janky.
Also, if a single piece of Repeat Yourself is such a concern, are you anti-RSS?
@vv4rner While I love what RSS enables and there’s a huge ecosystem for it, I am against it for DRY reasons. It’s stable in the fact that no one has iterated on it in over a decade. It also helps that WordPress core handles a lot of the admin tax for me on maintaining it, but it has caused metacrap issues for me in the past.
So what to do to replace RSS? If you look at most of my content, I’ve got the HTML marked up with (richer) microformats for those who’d like to consume that directly without needing a side file for it. There’s an existing ecosystem of microformats parsers and even social readers that use microformats over RSS. Incidentally microformats are also part of the semantic layer that makes site-to-site converstions on IndieWeb-based sites work better.