Loading Profile...
MicroID and Google Apps.
What about MicroID implementation? That would make my site automatically verified on my ClaimID account :nD. Having Google Apps available would be something interesting to have. Greetings!
I’m restless
6
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
The best point from the company
-
The release with microid has now been enabled. Additionally we added support for setting your site title (what appears in the title element in the head) and the description (which appears as a meta tag in head). All of these are available from Settings -> Site Settings.
I’m happy
The company thinks
this is one of the best points
-
Inappropriate?We actually had microID enabled and disabled it because of privacy concerns. If we bring it back it'd probably need to be optional.
1 person thinks
this is one of the best points
-
Inappropriate?Ow, I didn't know that... Make it optional can work, since ClaimID only needs to verify once, so that could be a good choice...
I’m excited!
-
Inappropriate?What about allowing us to modify the <head>? Then we could add the microid code manually and take it off whenever we need to.</head>
I’m sniffing!
-
Inappropriate?We've added the ability to enable or disable microid for your site. Initially it will be disabled and you will be able to enable it through a site settings screen. This will be part of the next release. Thanks for your patience!
I’m happy
-
Inappropriate?The release with microid has now been enabled. Additionally we added support for setting your site title (what appears in the title element in the head) and the description (which appears as a meta tag in head). All of these are available from Settings -> Site Settings.
I’m happy
The company thinks
this is one of the best points
-
Inappropriate?the microid I'm seeing in my chi.mp page is not the same one claimID is looking for. Im using the same email address and the finalcut.mp domain on both so I wonder what the problem is?
I’m unsure
1 Comment Add a comment
This is one of the best points
-
The microid we generate is the SHA1 of mailto:your_login_email + SHA1 of http://yoursite.mp . Perhaps it's a difference in email addresses? -
Inappropriate?I think that claimID and you use a different means of creating the microID then. I'm not sure how to add to hashes together (unless it is basic hex math) but the microID from you for me is:
e46d82650762499f5ef363efa6849accb5e72d0a
claim id has:
37310b9eebf34d29dbedd886cd7dd9113faabe80
I’m frustrated
3 Comments Add a comment
This is one of the best points
-
hrm. I can't seem to reproduce the microID that is created on the finalcut.mp page - however I can recreate the claimID microID it thinks you will create. If you want I can provide you with my specific ruby method that creates the claimID value so maybe you can tell me what is different.
I used ruby just because it was quick and easy -
Sorry, I gave you a bit less than you needed before. Here is the full microid generation, which is based on what is specified on http://microid.org/ :
"mailto+http:sha1:" + Digest::SHA1.hexdigest(
Digest::SHA1.hexdigest("mailto:#{email}") + Digest::SHA1.hexdigest("http://#{domain}/")
)
Where email is the email you provided when you first signed up and domain is your .mp domain name *without the www*. -
Ahh ha. the trailing / after the domain is the source of my discrepancy. Thanks for helping me find it! I'll update the reference at claimID and all will be good.
EMPLOYEE
