TeledyN: MT To Reinvent Drupal Authentication:
To mimick the proposed TypeKey selective-ban policies, any network member site would apply a JayAllen ban-pattern list to the full login name@server, but they might also now ban the specific authenticating server — if some server starts to pollute our network with bad IDs, like a lame nameserver, it gets itself excluded from the gene pool (but it could still be considered reliable and just in some other network); we may even improve on the JayAllen content-based filter by adding a facility to ban by point of entry into the network.
Gary reviews the various arguments for and against the new TypeKey authentication {proposal|meme}, and perhaps unintentionally makes a counter-proposal.
The whole thing is quite tiresome (don’t any of us have anything more important to talk/think about?), but one of the reasons webloggers even take up the filthy habit is a sense of “I know better” . . .
What seems to stick in everyone’s throat about this is the lack of transparency and openness about it: “just trust us, we know best” doesn’t get you far with this crowd.
I guess the only thing to do is wait for MT 3.0 to be released so the new APIs can be leveraged for something people will hate less.