I recently learned about MicroID, a microformat for verifying ownership of content on web pages, from a post on Phil Windley’s blog. MicroID, which is a simple hash of an email address and a URL, can be used to claim ownership of a blog, a blog post, or a blog comment.
Phil developed a MicroID plugin for MovableType.
Likewise, I created a MicroID plugin for WordPress [zip].
This WordPress plugin does three things:
- Inserts a MicroID meta tag in the head of your blog. This is calculated from the administrator email and the blog URL listed in your WordPress blog’s General Options.
- Attaches a MicroID to each post. This is calculated from the email address of the author of that post (which may be different if your blog has multiple authors) and the permalink of that post.
- Attaches a MicroID to each comment. This is calculated from the email address and URL submitted with each comment.
This a very new concept with little practical application so far, but the possibilities are interesting: “Blog comment systems can check the given email address against a MicroID from the entered home page link to help reduce link spamming and blatant spoofing.” (microid.org)
Thanks!
The plug-in acts inconsistently and not fully correctly. All claimID (and presumably others looking for microid) is looking for is that the one correct microid ### be formatted as and placed within the HEAD tags. But the plug-in generates two microid’s, and formatting and placement are inconsistent.
On all pages, it adds an almost properly formatted microid tag within the HEAD tags (almost proper because the mailto+http:/sha1: is missing), but the ### is the same across all pages/posts in a given website, and I can’t tell where it’s coming from.
The second microid seems to be handled in two ways.
On home page, it is formatted properly as and placed correctly within the HEAD tags.
On pages/posts, it is formatted incorrectly as and placed incorrectly outside the HEAD tags.
Incidentally, claimID support also noted that the plug-in isn’t using v.3 of the microID spec, but they don’t think that’s impacting much here.
Thoughts?
With http://potluck.com/ I had entered the trailing slash at claimID, and it verified okay. Because of a similar comment here for the plug-in, I made sure to add that trailings slash when adding a http://potluckcreativearts.com/ link at claimID as well. But that failed — mismatched microid #s.
Lo and behold, I tested just to see, by removing that slash to yield http://potluckcreativearts.com I was able to match the # being generated for that page by the plug-in.
Isn’t it strange that one site would need the slash included and the other would need it excluded?
claimid is expecting
meta name=”microid” content=”5904a3c454eeeb4a91d942903c195cfa657962d5″
and wp-microid is generating
meta name=’microid’ content=’69668ef663714057de2bbc054bdfa404d586301a’
and wp-microid is outputing
so obviously validation fails. I’ve triple checked that my admin email address is the same as the one on my openid (thingles.myopenid.com) and that the URL’s are exactly the same.
Any suggestions?
RDF tags create page validation errors, and it is really your syndicated content which needs to have meta data added to it in order to identify its origin.
I get this error when I activate it š
I am running WordPress 1.5.1.2
What am I doing wrong?
Help me please!