This blog has been silent for most of the year, and since I’ve been making progress on SLOpenID v3, I thought I’d make a post to bring people up to date on where things are with SLOpenID.

Logo

SLOpenID Logo

SLOpenID is no longer in need of a new logo, and hasn’t been in need of one for some time now. Back in August of last year, I put out a call for a new logo. Well, in March of this year, my friend Trinity Coulter produced a logo (one that has been in use since since at least August this year, in the form of the favicon for the SLOpenID blog/website.

Linden Lab Brand Center progress

After my meeting with Robin last year, I’ve still not heard anything back from Linden Lab regarding my use of “SLOpenID”/”SLopenID”, and the slopenid.net domain name.

SLOpenID v2

SLOpenID v2- the version of SLOpenID based around a WordPress MU install- has been officially retired. There wasn’t sufficient demand for the WordPress-based features to continue development and maintenance of that aspect.

The blogs housed on my.slopenid.net now redirect to their sw.slr pages. This should allow anyone who used the Provider facility to make use of the SLOpenID v3 delegate feature implemented in sw.slr.

SLOpenID v3

SLOpenID v3 will- at least initially- be concentrating on the Consumer/Relying Party side of things, as opposed to the previous generations of SLOpenID concentrating on the Provider aspect. SLOpenID v3 apps will have their logins implemented in such a way that the Resident enters their Second Life username, and not their OpenID (aside from the initial association). As always, SLOpenID will never require Residents to enter their Second Life password- and with v3, no password should ever need to be entered on a site operated by Marvulous when using SLOpenID.

A beta version of a SLOpenID v3 application is currently available- a revamped version of the old relationships manager beta test moved to production location due to providers having issue with the .name TLD. Although the association process is fully operational, I’d prefer to keep the flow of beta testers to a minimum (SLOpenID alpha testers get preference!), so that I can concentrate on fleshing out the relationships manager. At the time of writing, the beta app uses the SLOpenID login process, then presents the user with the relationships manager form. Submission of the relationship data isn’t enabled yet, as a new parser/validator has to be written.

I may also consider adding a login link to sw.slr pages so that Residents can log into the domain without even entering their username, though this would likely be added with a JS enhancement so as to avoid modifying the caches (helping to keep the site running as smoothly as possible).

Site consolidation.

Now that SLOpenID v2 is retired, there is less need for me to keep the WordPress MU install around- slopenid.net will now act as the site and blog for SLOpenID.