• (nodebb)

    then refused to honor my "unsubscribe" request

    Too bad for dragoncoder047 that we aren't talking about something in the EU, where the GDPR enforcers would jump up and down on GradImages's collective arses.

  • Álvaro González (github)

    All companies operating in the EU have a GDPR contact until you try to actually contact them. So it's pretty much like unsubscribe links.

  • COBOL Dilettante (unregistered)

    I'm being thick - what's wrong with the second Stansted screenshot? It looks like a flight from Bologna arrived just under 4 hours late, which is about right for Ryanair

  • Michael R (unregistered) in reply to COBOL Dilettante

    The arrivals form asks for the destination of the flight which is obviously always STN/Stansted.

  • Darren (unregistered)

    Maybe it's me, but I'm not seeing where the WTF is for those Stansted images. They all show that flights arrived, some a bit early, some a bit/lot late.

    I've long said here that when people are submitting images for the weekend specials that they need to realise that while they might know what it is they're looking at and why it's a WTF, the rest of use are looking at them blind and don't have any idea about the context in which they're being viewed as a WTF.

    Just something as simple as highlighting the bit that you believe is a WTF and a bit of description as to why it's a WTF would go a long way to helping the readers out.

  • Steve (not that one) (unregistered) in reply to Darren

    Compare the actual arrival times with the time the form was last updated. The form should engage in polymarket wagers.

  • Joe (unregistered)

    Something that's optional and also required remind me of Jennifer Aniston's character's struggles in the movie Office Space.

  • (nodebb) in reply to Darren

    The comment on the image is "The Stansted airport website seems to suffer from Directional Confusion."

    You're looking at the "Arrivals" page, but searching by flight number or destination.

  • (nodebb) in reply to Darren

    The first one is missing the context that the current time is somewhere between 22:06 and 22:18. So the F97628 times don't make much sense

    The second one says "destination" but that field is really the origin. It functions as such, just labeled wrong.

  • COBOL Dilettante (unregistered) in reply to Michael R

    Ha! I even thought to myself "It must be something to do with that field, because that field wasn't visible on the other one", and still didn't spot it ... Thanks

  • (nodebb) in reply to Darren

    It's because the 0730 and the 2355 flights from Bucharest have arrived (at 0718 and 0006 respectively). However, the 2220 flight is expected to arrive at 2218.

    Which means the 2220 from Bucharest is supposed to be 2 minutes early, but is likely over 2 hours late since the 2355 arrived already at 0006. Then again, maybe it crashed somewhere along Bucharest to Stansted and no one's realized it yet.

  • Loren Pechtel (unregistered)

    Think!!

    The problem with the flight display is a sorting issue.

    The 23:55 flight departed yesterday.

  • COBOL Dilettante (unregistered) in reply to Worf

    I understood that one as: the arrivals board was only updated at 2206, but somehow it knows a flight has already arrived at 0006 the following morning

  • AussieSusan (unregistered) in reply to COBOL Dilettante

    ...and I interpreted it as the system showed all times less than the current time as having arrived regardless of reality

  • Darren (unregistered)

    That so many people have chimed in with varying thoughts about what they think the Stansted WTF actually is illustrates my point. A couple of lines of description as to what the WTF is would help us all out.

    Not singling Michael R out here, it's a common issue with these Saturday posts.

Leave a comment on “Good Time”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article