Now not to do identity management (read this nintendo) [from 2019]

-

Identity management is hard

Just so everyone understands, I get this...having worked with connected devices and multiple phones/consoles/cars/headsets/speakers all cross linked to other devices and other accounts...I get it's HARD to maintain and/or associate the correct PERSON with the correct DEVICE with the correct ACCOUNT (note, those are all different things...I can have multiple bank accounts, accessible from multiple devices, and multiple people could share my account and/or device, but who can do what from what is difficult.

Add kids and games and shit to the mix

I'm not necessarily saying nintendo has done a poor job (no...scratch that...I'm saying they have)... what I'm really saying is that they have a particular demographic that makes identity and device management difficult...namely KIDS. Now, before all the single parents with one kid who had a nintendo DS once who claim this shit is super simple...and before the folks who can only afford for their kids to play in the street with rocks and dirt...I get it..this is a first world problem...but, I think it's leading indicator of a problem more and more people are gonna have.

Background

I started buying nintendo stuff for the kids...IDK...15-20 years ago? I have no idea...I'd have to ask my oldest daughter, but this evening I tried to just help one of my kids (I have a few, so I realize I'm an outlier, but perhaps this is something to consider if you're trying to manage user/device/vehicle accounts as a fleet manager...just sayin). all we needed to do was link the named user account associated with HIM on a WII-U to his brother's nintendo switch device (actually I don't even know who's device was whose...but you get the idea). So nintendo has this great concept of accounts on the device that may or may not correlate to similarly named accounts on other devices...In addition, each device may have those accounts linked to other "nintendo id's" which apparently have no direct correlation to an email address or other way of knowing who you are.

So here's what happens

So then, every christmas or two, we get a new nintendo device (or two) and try to link everything up....and spend hours upon hours trying to piece together our accounts like some sort of perverse Ikea furniture that also needs some integration between multiple competing javascript libraries. And ultimately, we create either a new burner email account or ... hell I don't even know ... half the time we get things "kinda working" and never figure out how to link everything together.

In the world of selling stuff this isn't bad

In reality, if nintendo is intent on selling hunks of silicon and plastic, this is a non-issue...hell folks are gonna throw that old console away in a year anyway so who cares? In the future, I believe consumers are going to expect a continuity of service...ESPECIALLY within the same brand. Why? Because every one of my kids is completely confounded by this! Like, they seem to look at me like I'm trying to deliberately sabotage their friends lists and accomplishments for some weird reason.

Comments

Post a Comment

Popular posts from this blog

Push versus pull deployment models

-
There are two deployment models: push and pull. In a "Pull" deployment model, the individual servers contact a master server, download their configuration and software, and configure themselves. In a "Push" model, a master server pushes the configuration and software to the individual servers and runs commands remotely. While neither technique is right or wrong, they both have some specific advantages and disadvantages that you should understand when making a decision. In the ruby hosting world, an example of a "push" deployment is heroku , while Engine Yard is an example of a "pull" type deployment. In the Pull model, each server has information about how to obtain it's configuration, when it boots (or whatever the configuration triggering event happens to be) it can continue to proceed without intervention from the master server. In the Push model, because the master server is orchestrating things, it will typically need to have a c
Read more

the myth of asynchronous JDBC

-
Image
I keep seeing people (especially in the scala/typesafe world) posting about async jdbc libraries. STOP IT! Under the current APIs, async JDBC belongs in a realm with Unicorns, Tiger Squirrels, and 8' spiders. While you might be able to move the blocking operations and queue requests and keep your "main" worker threads from blocking, jdbc is synchronous. At some point, somewhere, there's going to be a thread blocking waiting for a response. It's frustrating to see so many folks hyping this and muddying the waters. Unless you write your own client for a dbms and have a dbms that can multiplex calls over a single connection (or using some other strategy to enable this capability) db access is going to block. It's not impossible to make the calls completely async, but nobody's built it yet. Yes, I know ajdbc is taking a stab at this capability, but even IT uses a thread pool for the blocking calls (be default). Someday we'll have async databa
Read more

Installing virtualbox guest additions on Centos 7 minimal image

-
I've just spent some time setting up a bare Centos 7 image to support development stripping out as much as possible. While CoreOS is probably a better choice, we run redhat in production at this point and centos is a better fit for the time being. The problem I've found is that many of the instructions available via google were written against prerelease versions or espouse manually installing random rpms instead of just using yum. While I get this "works", I'm not a huge fan of this approach and would rather do everything with the package manager. After a LOT of scouring and trial and error, I finally found the "magic" combination. The winner is courtesy of http://www.pc-freak.net/ . I've taken these instructions and tweaked them slightly for my purposes. The original poster did this on a more "full fledged" version of centos with a windows host and my instructions are for a minimal install using and OSX host (though I'm certa
Read more