SHOCKING NEWS: Discourse Not Ready To Load All Posts
Continuing the discussion from SHOCKING NEWS: Big Banks Not Ready For Mobile:
A result that would surprise absolutely fucking no one, big banks report they don't have the IT infrastructure or technical know-how to create mobile payment products. (The article focuses on Canadian banks, but I would bet dollars to high-frequency donut futures that I could throw a dart at a map and hit a country with equally shitty banks).
There's some bitching and moaning about unfair regulations in the article too, but FUCK YOU, "too big to fail" assholes. How does unfair regulation result in me being able to sum up your entire shitty approach to online banking with a single screenshot:
Filed Under: For additional security, we've massively reduced the keyspace you can use. Special characters are scary. Just as scary as the implication of this rule is that we don't know how to use hashing or encoding-- so somewhere, your password is being handled in plaintext. Please please please don't put a single quote in your character, we haven't finished reading How To Program 101 yet.
Filed Under: How does this even happen???
It's a discorace condition!
Doesn't race condition usually imply that too things happen at the same time?
Because @Lorne_Kates replying to @aliceif does not seem to indicate anything like that
Filed Under: Then again, we ARE talking about DiscoTime...
loopback0 last edited by
Post streaming broken? Definite shocker.
mrguyorama last edited by
"two" Sorry I just hate that one the most
This happens because the Discodevs have literally no idea how to do anything involving computers. This could screw up in a lot of ways, but I can't fathom a way in which it wouldn't be directly their fault for bad programming/design
This happens to me constantly. If any request fails (but doesn't return failed) for any reason (for example, our silly proxy freaking out at some bad words in the URL), any and all subsequent attempts to ajax in data silently hang forever.