Posts

attempt to use Guernsey Post web site results in infinite captcha ordeal

Image
There is a tendancy to make web sites much, much worse than doing things in real life. In this case, Guernsey Post made a form that's otherwise fine, but has the "recaptcha" antipattern.  Nothing says "we hate our customers" like making them spend their labor, which as Seneca points out is limited, on training an AI, for free. After "making an exception" to my rule that I don't do these things, I was taken through an ordeal that involved identifying fire hydrants, steps, motorcycles, traffic lights, and several other categories.  I eventually concluded it was never going to end, and called Guernsey Post, who kindly did the thing. The web is a total disaster.

world's biggest shop: if you can't receive an SMS from us, right now, in real time, you can't buy anything

Another self-defeating Amazon authn fail. I tried to buy thing while on train, they go to the SMS thing, I have the phone on me but the SMS doesn't arrive. Result: thing not bought from Amazon. I've heard that Jeff Bezos likes to ask for root cause analyses for any issues.  Well, here's a root cause analysis for this issue: Jeff Bezos is a drooling idiot.

most web sites don't work on the train

Twitter doesn't work at all.  Everything is "sorry something went wrong".  The connection is a bit glitchy, but not that bad.  I've downloaded several hundred MB, and simple web sites have worked fine. Twitter, being based on short text messages, would be ideal for being reliable, but is one of the least reliable web sites I've ever used.  The slightest glitch in one's internet connection, for example on a train, and everything is "sorry something went wrong", even what should be very simple and basic pages. Gmail also fails pretty badly, becoming unresponsive and giving no indication of what is / isn't happening.   Zoho failed before login, giving an ever-lasting animation of a cube bouncing around or something, with no progress ever happening beyond that.

Bitstamp still insulting logged-in customers with captchas

Image
It looked like Bitstamp may have left their ill-advised captcha anti-feature behind, but I just got double captcha'd WHEN I WAS ALREADY LOGGED IN. I can not overstate how ill-advised this is.  You are failing at authentication, you are disrespecting your customer by valuing their time at zero.  You are presuming to tell them that they must provide, for free, some of the lowest-value labor in the world, that of training AIs.  In this case, food with motor vehicles, and the question is "what does not belong here".  This is not the future of anything.  If you are doing this, you are doing it very, very, very wrong.

Bitstamp extremely slow at loading, pulls in crap from all sorts of domains

A web site providing a financial service should not pull in resources from any other domains.  It should be simple, self-contained, minimising risk. But when I'm logged in to Bitstamp, with the messages page taking forever to load, it is pulling in all kinds of crap from all over the web, from reddit.com, from analytics.google.com, and those are just two I spotted in the status bar.  It's unacceptable.

kraken: failing to show amounts in orders view

Image
When a trading platform provides a report on orders to a custom, some things are important, like the quantities of each thing in the order.  You do not, ever, for any reason, omit part of the amounts and replace with an ellipsis.  Screenshot from Kraken: Taking the top line as an example, a seven-digit amount, three million and something EUR, has been represented as " 3,172,67...".  You can not be serious. Meanwhile, there is tons of free space in the pair column, saying "EUR/CHF" in the middle of a huge amount of whitespace.

apple: subordinating function to silliness

Image
A clock should tell the time.  How well does this clock do that: Not bad, in that you can tell the time from it.  But why obscure part of the last digit?  Just to be cute?  It makes it harder to read. This kind of thing is a very active kind of stupidity.  It didn't just happen like that.  A whole team of renegade employees probably conspired to do it, wrote "codes" and "algorithms" to make it happen, and managed to slip it past management and the entire quality management process, to despoil the front screen of the iphone.  On its way, the "codes" probably got reviewed in a "codes" review system, someone commented on a better way this or that could be computed, and someone checked if the graphics algorithm worked for edge cases.  Some east asians then manually tested it. And it would have been better if all of them had done nothing. This is similar to all the effort put into things sliding around the screen and transitioning: huge amounts of