aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfr33domlover <fr33domlover@web>2014-06-18 14:54:53 -0400
committeradmin <admin@branchable.com>2014-06-18 14:54:53 -0400
commit05dc871a5621b0b7b1bba2887134824e1f47ab2a (patch)
tree9869154f9b66a88035db67fb83a71df3c7f32d9d
parent236c63d5b68c2fe57a87b952bd9968ff685c86a2 (diff)
downloadikiwiki-05dc871a5621b0b7b1bba2887134824e1f47ab2a.tar
ikiwiki-05dc871a5621b0b7b1bba2887134824e1f47ab2a.tar.gz
Express thoughts about OpenID
-rw-r--r--doc/news/openid/discussion.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/news/openid/discussion.mdwn b/doc/news/openid/discussion.mdwn
index bc9856ad9..5abdd5a13 100644
--- a/doc/news/openid/discussion.mdwn
+++ b/doc/news/openid/discussion.mdwn
@@ -94,3 +94,21 @@ One caveat to the above is that, of course, OpenID is a distributed trust system
----
Submitting bugs in the OpenID components will be difficult if OpenID must be working first...
+
+------
+
+# Privacy and Decentralization
+
+Maybe I don't understand OpenID well enough, but it looks like there are just few providers, most
+of which are huge companies or belong to such, and I don't trust them to verify me identity
+or to not track all my logins. I'll use OpenID only if I can make my own home server
+be my OpenID provider, and if doing so doesn't interfere with the design and security and
+privacy of OpenID, and doesn't require me to use centrally-signed certificates or pay to some
+company or anything like that.
+
+Is it possible to use OpenID in a way keeping the user in full control and allowing any user to
+have their personal provider without damaging the architecture behind OpenID?
+
+I'm worried, at least until the issue is cleared.
+
+-- [[fr33domlover]]