Comment 6 for bug 1468422

Bill, I don't see any problem with recording a bit more info with the "seed" blob in memcache resulting from the .init call.

Thomas, I think having an API (or, 2, really) for "strictly either username or barcode" login is fine, but I'd suggest that refactoring the existing code to be strict based on the method name by which it is called (or not be strict, if called with today's name) is better than adding an optional parameter. We can just add ".init.barcode" and ".init.username" variants, and be strict based on what was called.

Thoughts?