cdevroe.com » authentication

37signals dropping support for OpenID on May 1, 2011

Colin Devroe — Wed, 26 Jan 2011 15:55:29 +0000

I have been a supporter of OpenID for a long time. But I agree with the decision by 37signals to drop it. What could have been never happened and, as it would seem that not much is being done to fix that, it would be better to just get rid of it so as to cut down on confusion.

I’ve converted my account already.

Ma.gnolia Blog: On Our New Front Doors

Colin Devroe — Fri, 04 Apr 2008 17:28:51 +0000

Ma.gnolia, my favorite social bookmarking service, recently switched from merely supporting OpenID to actually restricting all new user signups to use the authentication platform. This received a lot of attention – most good – while Matt Mullenweg (and others I’m sure) chimed in to say that this method shouldn’t be viewed as a good strategy to cut spam.

Larry Halff, founder of Ma.gnolia, chimed in today via the site’s official blog to give some background on the discussion, statistics that made the reasoning come up in the first place, and why they believe that while it isn’t a strategy to cut down on spam, it has, indeed, cut down on spam.

So now you know the rest of the story.

Source: Ma.gnolia Blog: On Our New Front Doors.

Problems with LiveJournal and OpenID

Colin Devroe — Wed, 20 Jun 2007 13:55:27 +0000

Back on May 25th I uploaded this screenshot to my Flickr account hoping that someone else would have had the same issues that I was having using my OpenID while trying to leave a comment on LiveJournal. Yet, no one has responded yet.

Fast forward nearly a month and I’ve since emailed Live Journal, did some browsing on the Internet trying to find a solution, and still I have yet to figure out why my OpenID is not working when I try to leave a comment on a friend’s LiveJournal. Here is a screencast to show exactly what happens:

A video demonstration of the LiveJournal error

If you are having similar issues using your OpenID on LiveJournal, please leave your experiences in the comments and hopefully someone from their development team will see this entry. If you know why this is happening and how I can fix it, please let me know. Thanks in advance.