summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-06-08 21:25:17 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-06-08 21:25:17 -0400
commit7a22ead98ebe231943a9e1a1873640c372f25077 (patch)
treef384091ad2dee31a3706fbacfb39fadfc5b9facb
parent3f9dd729b3f89c25689bb96d55d71d3eb232951f (diff)
update
-rw-r--r--doc/forum/is_it_possible_to_NOT_add_openid2_meta_tags.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/forum/is_it_possible_to_NOT_add_openid2_meta_tags.mdwn b/doc/forum/is_it_possible_to_NOT_add_openid2_meta_tags.mdwn
index 1a6d01cd3..a364449f9 100644
--- a/doc/forum/is_it_possible_to_NOT_add_openid2_meta_tags.mdwn
+++ b/doc/forum/is_it_possible_to_NOT_add_openid2_meta_tags.mdwn
@@ -47,3 +47,9 @@ lays with the consumers not falling back to the openid1 tags when they are openi
> consumers seem justified in not falling back (guess; I don't know the 2.0 spec).
> The only way this seems fixable is to add an option to meta to allow disabling openid 2. Which
> should be easy enough to do. --[[Joey]]
+
+>> Actually, it seems that identi.ca / certifi.ca do
+>> not interoperate when using openid2. It actually
+>> fails half the time, and succeeds half the time;
+>> seems to be picking openid1 and openid2 randomly and failing
+>> on the latter. --[[Joey]]