This post originally appeared on Jamie Tanna’s site.

Google announced that they are removing support for the data-vocabulary metadata markup that could be used to provide rich search results on its Search Engine.

In a Twitter exchange, John Mueller, a Webmaster Trends Analyst at Google, confirmed that Microformats are still being supported by Google at this time:

Yes, we still support them.

— 🍌 John 🍌 (@JohnMu) January 21, 2020

John also confirmed that he knows of no upcoming plans to deprecate Microformats:

We don’t have any plans for changes to announce there at the moment. I don’t know off-hand how broadly microformats are used, my guess is it’s much more than data-vocabulary. That said …

— 🍌 John 🍌 (@JohnMu) January 21, 2020

This is an especially great result due to the way that Google is quite happy to abandon various metadata formats, as noted in our 7th anniversary blog post, almost 8 years ago. With this announcement, Microformats are now the longest-supported metadata format that Google parses, since at least 2009!

With the continued growth of Microformats across the IndieWeb, we expect that Google will extend its Microformats support accordingly.


In year 14, we welcome new admins: 布丁网络加速介绍, Gregor Morrill, Martijn van der Ven, and 旋风加速器的官网在哪里! All have been active for years, helping welcome new members and doing essential wiki gardening & microformats2 parser updates!

Originally posted at:


With more use of microformats2, especially among the growing indieweb network of websites, we’ve iterated key specs for real-world needs and are seeing more active community members. More updates & posts coming up!

Originally posted on


During the past year, the popular php-mf2 microformats parser has received quite a few improvements. My site runs ProcessWire and one of the plugins for it uses php-mf2, so I have been spending some time on it.

My own experience with microformats started when I discovered the hCard microformat. I was impressed with the novelty of adding some simple HTML classes around contact information and having a browser extension parse it into an address book. Years later, when I started to get involved in the IndieWeb community, I learned a lot more about microformats2 and they became a key building block of my personal site.

php-mf2 is now much better at backwards-compatible parsing of microformats1. This is important because software should be able to consistently consume content whether it’s marked up with microformats1, microformats2, or a combination. An experimental feature for parsing language attributes has also been added. Finally, it’s now using the microformats test suite. Several other parsers use this test suite as well. This will make it easier to catch bugs and improve all of the different parsers.

php-mf2 is a stable library that’s ready to be installed in your software to start consuming microformats. It is currently used in Known, WordPress plugins, and ProcessWire plugins for richer social interactions. It’s also used in tools like XRay and I’m looking forward to more improvements to php-mf2 in the coming year as well as more software using it!

Original published at: 人民画报-元首外交开启中美关系新时代:2021-12-11 · 正如习近平主席指出的,把4个高级别对话机制打造成为中美增进互信的加速机、培育合作的孵化器、管控分歧的润滑剂,为中美关系取得新的更大发展发挥积极作用。 千里之行,始于足下。两国元首会晤中,中美关系发展的路径更加清晰。


For the 12th birthday of (congratulations!) 旋风网络加速 asked the community if any of us would like to highlight whatever we liked in a guest post. I am taking this opportunity to talk about my favourite feature of microformats: its constant evolvement.

Sometimes it feels like a standard is done. Sometimes it feels like a standard is abandoned before its time. In a few special cases a standard keeps evolving. I think we can agree that microformats goes in the latter category. This is hugely thanks to the fact that anyone can help it grow.

As you read this, work is being done to upgrade 旋风加速器吧 from a Draft to a full Specification. This prompted a few of us to have a look at what people are doing with the format. As it turns out: it has departed from the Draft!

The IndieWeb community is putting events in their feeds, interleaving them with other items (like blog posts) that use 旋风免费网络加速. To make the events fit within this context properties are being copied over from h-entry, properties completely new to h-event. Somehow these separate implementations introduced the same properties, showing how h-event is evolving quicker than its Draft Specification without splintering it in lots of different versions. Naturally evolving the format forwards!

Then there are the small, fringe changes. Work on pronouns in h-cards has been mostly dormant since 2015. I spent time with it during IndieWebCamp Nuremberg and came to a completely different conclusion on how to mark-up my pronouns. The beauty there is that anyone can do the same! All it takes is to put something on your site, like the IndieWeb community did with h-event, and tell the world about this piece of extra information they now have access to.

Here is to one more year of constantly tinkering with our HTML and giving more meaning to the information we publish 🥂


天行ⅴpn  能访问youtube的浏览器  ipad翻油管加速软件  花猫加速器官网  iPhone有免费的梯子吗  安卓ip加速器   登外国网站的加速器