3 ms·

would be nice, but it would likely introduce some additional complexity for instances where there might be more than one live session spawned by a user.

• OJFord 10y ago
  > additional complexity for instances where there might be more than one live session spawned by a user I'm trying to imagine the situation that makes that worth supporting? That's not going to be a development server used by an entire team, for example, because whose Github credentials would be on it? Even so, it could just give a list of session IDs in such a case, and ask which of 1/2/3. The additional complexity is only that the lookup value is a list of strings instead of a single one, surely?
  • Operyl 10y ago
    In my head, having to have the session id is almost a good "two factor" if you will.
    • OJFord 10y ago
      I suppose. Having someone's private key and knowing who's offering the legitimate owner of that key a secure session at that point in time is already a tall order though!