Vidoop
is committed to open conversation about its products and services. Conversations should be conducted in the spirit of the Company-Customer Pact.
If you use this product, we'll add it to your dashboard. If you work for the company that makes this product, we'll connect you with other employees. Got it, thanks!
Everyone's identity is implicit, if not explicit, in their email address. This is why an email address works well for identity purposes when logging in to websites and applications.
Our service, emailtoid, takes an email address and makes it work as an OpenID by mapping email addresses to URLs.
"This URL appears to be a broken link." error message on trying to associate a functioning openid page.
However, the pages (with delegated openid) I tried (weblog.vanhecke.info and pascal.vanhecke.info - hosted by different parties) work perfectly fine for me.
You seem to have an MX issue again. My mail server rejected your email saying that "all relevant MX records point to non-existent hosts". And, indeed, it looks like while editing your zone database you put the FQDN for MX without the trailing dot:
emailtoid.net mail is handled by 10 mail.emailtoid.net.emailtoid.net.
I can handle it on my server side, but you definitely want to fix it.
It would be really neat if when my visitors got dumped to emailtoid they could get a message saying "you've been sent here by X to verify your email address" or something. As it stands, it kinda just looks like I randomly dumped them to someone else's site.
“a XRDS discovery is made on the top level domain (eg, gmail.com).”
But gmail.com isn't a top level domain. The top level domain (TLD) would be com. Hopefully this is a typographical error or a thinko. But if not it reveals a terrible misunderstanding of how DNS works, which would suggest that the service isn't to be trusted since it relies on DNS.
I am using the EAUT PHP library on my Web site and when I try to connect with an email linked to an myOpenID URL with Emailtoid, the answer is "Invalid OpenID.".
or more importantly what exaly do i need to put into the sites opedID box as when i put my E-mail all i get is "This is NOT a Valid ID" so what exacly do i need to do to make this work ??
It seems scary having all my information in one place. What if a hacker gains access to Open ID. Won't they then have access to all my passwords to all my emails and bank information?
It would be awesome if emailtoid were integrated with JanRain's idselector project so that users could click "email" and enter their email and have it use emailtoid
First off, excellent work on Emailtoid. It's potential to advance the social web is exciting.
I've been experimenting with it this morning, and discovered a problem. I successfully signed on to the example relying party multiple times. Then, I associated my OpenID with my Emailtoid account. It properly redirected to my OpenID provider from that point forward.
However, I then removed the OpenID associated with my account. Now, whenever I try to use that email address with Emailtoid, I get an error that states: "OpenID failed - The OpenID was invalid"
In case it matters, I'm using a gmail.com address to sign on.
Trying to use Emailtoid I have the answer :
"Sorry, the domain of your email address doesn't exist - perhaps you mistyped it?"
The domain used in my email is a domain name own by me, and it exists, so what are restrictions in using email address ?
Jul 26 18:27:17 baden postgrey[3274]: action=pass, reason=client AWL, client_name=milan.sjobeck.com, client_address=70.102.131.197, sender=verification@emailtoid.net, recipient=jason@sjobeck.com
Jul 26 18:27:17 baden postfix/smtpd[19733]: NOQUEUE: reject: RCPT from milan.sjobeck.com[70.102.131.197]: 450 4.1.7 <verification@emailtoid.net>: Sender address rejected: unverified address: host relay2.netnames.net[212.53.64.44] said: 451 lowest numbered MX record points to local host (in reply to RCPT TO command); from=<verification@emailtoid.net> to=<jason@sjobeck.com> proto=ESMTP helo=<milan>
I am not able to confirm my email address since our mail filter wont allow your email through, for what seems like an invalid MX configuration in your DNS.</milan>
Regarding EAUT lookups - it would be nice if there were a DNS lookup stage first, rather than hardcoding @company.com addresses to http://company.com or http://www.company.com. A SRV or TXT record would allow any server to be specified similar to how MX records work for mail.
Many organisations will have their TLD hogged by legacy services and all manner of odd restrictions. Checking the TLD for a web based record first may not incur instant failure but timeouts that could take some minutes which would be a major usability issue.
I love the discover-on-URL, discover-on-domain, fallback-to-emailtoid path you recommend. Any tips on how to do this with existing libraries (mostly the JanRain libraries).
Loading Profile...
coyee
last replied
on July 01, 2009 17:13
Stuart Rubenstein
last replied
on June 08, 2009 09:33
Michael Richardson
last replied
on January 05, 2009 01:27
Will Norris
last replied
on November 24, 2008 20:54
Sam Alexander
last replied
on September 30, 2008 19:21
Chris Messina
last replied
on August 14, 2008 18:23
Stephen Paul Weber
last replied
on July 04, 2008 01:05
