Loading Profile...
Let users "prove" that a site has OpenID support.
Let people "prove" that a site supports OpenID by submitting one of two types of links:
1: A link to the login page containing a form with and "openid_identifier" input field.
2: A link to a website that describes the site in question as having OpenID support (a blog post for example)
1: A link to the login page containing a form with and "openid_identifier" input field.
2: A link to a website that describes the site in question as having OpenID support (a blog post for example)
I’m feeling clever.
8
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 best point from everyone
-
When you launch a campaign essentially petitioning and calling out someone to change behavior, it requires four things.
- A method of collecting signators. (check)
- A method of delivering the signatures to the petitioned. (?)
- A method of documenting a the response of the petitioned. (check)
- A method of celebrating success within the community of supporters. (missing)
That final point is what helps keep up enthusiasm amongst the signators and encourages them to stay actively involved and recruit more supporters.
Documentation means boldly highlighting success. Demand OpenID quietly adds a note and makes no attempt to boldly (keyword here) highlight that a site has adopted OpenID. A signatory could easily add GetSatisfaction.com to the list and never notice the little green text at the top denoting it already offers OpenID.
Demand.Openid.com needs to be more than just a list.
I’m pleased but more is needed.
3 people think
this is one of the best points
-
Inappropriate?What happens when a developer or site on the Demand OpenID list finally implements OpenID?
If I ran a site, I would like a way to remove, or better yet, annotate the Demand list to let people know that I have succumb to demand.
I’m sad. Obvious problem goes unfixed.
2 Comments Add a comment
This is one of the best points
-
Or announce even! -
Yes, that is what my proposed idea might solve. With my idea, you'd just paste a link onto the Demand OpenID list, and then some software (or a human) would then use that link to verify that the site is now OpenID enabled.
-
Inappropriate?Or even just check to see if there's some meta tags or headers (Yadis?) in the HTTP response when querying the site in question.
1 person thinks
this is one of the best points
-
Inappropriate?When you launch a campaign essentially petitioning and calling out someone to change behavior, it requires four things.
- A method of collecting signators. (check)
- A method of delivering the signatures to the petitioned. (?)
- A method of documenting a the response of the petitioned. (check)
- A method of celebrating success within the community of supporters. (missing)
That final point is what helps keep up enthusiasm amongst the signators and encourages them to stay actively involved and recruit more supporters.
Documentation means boldly highlighting success. Demand OpenID quietly adds a note and makes no attempt to boldly (keyword here) highlight that a site has adopted OpenID. A signatory could easily add GetSatisfaction.com to the list and never notice the little green text at the top denoting it already offers OpenID.
Demand.Openid.com needs to be more than just a list.
I’m pleased but more is needed.
3 people think
this is one of the best points
-
Inappropriate?Yes! We got demands to implement OpenID on PlannerX. We tested it and found that the system can work with Basecamp's OpenID support.
Now we don't know how to let people know that it works - except a blog post - which we already did.
I like Joel's idea to let people prove that a site has implemented OpenID support.
