• scallowag (unregistered)

    TRWTF is not recognizing two numbers separated by a comma and a space.

  • pudin9 (unregistered)

    Wow, that battery chart is really cool. Kudos to the developers for handling(?) that... multi-valued function-thing?

  • (nodebb)

    I need a hint for the first one, I think. The one from Allie. I just don't get it.

  • Anon (unregistered)

    @jkshapiro: The y-axis

  • Robin (unregistered) in reply to scallowag

    Agreed. I mean, it's potentially confusing so you probably shouldn't present the information this way, but it's hardly a WTF.

  • Rocky (unregistered) in reply to pudin9

    I've seen charts like that before, mostly because people using local time as a timestamp and plotting a graph during DST-change or TZ-change it gets funky.

    For this graph, If someone didn't fiddle with the time on the device it was probably due to faulty time in a cell-network which is usually used by cell-phones to sync their time. YMMV.

  • (nodebb) in reply to scallowag

    If I had written that sentence, I probably would have read it back and then changed the punctuation mark after "17,522" because reading it fast might be a bit confusing at first.

    I don't think it is a WTF though.

  • Tim (unregistered) in reply to Robin

    it should be a semicolon (or possibly a full-stop) between the two numbers

  • superluser (unregistered)

    I do suppose it's technically possible that the certificate for time.gov is actually a MITM attack. If an attacker found a collision in an older certificate, they could present that one.

    But I believe the time required to find collisions in the protocols currently accepted by Chrome exceeds the length of time that those certificates have been in use. (somebody check me)

    I think it's telling that when we see an error like this which is supposed to warn us of danger, our first reaction is to assume there is no danger, which I guess is TRWTF.

  • (nodebb)

    Did Marek With The Battery happen to travel to a different time zone, like from Poland to Brexitannia?

  • (nodebb) in reply to Tim

    or the word "with" or "and"

  • Anon The Moose (unregistered)

    The gap in battery tracking could simply be that the battery tracking service wasn't running, therefore wasn't polling the battery status and therefore, left gaps in the data. Or the phone was off.

  • (nodebb)

    The comment failed. The reason is:

    $error
    
  • JNA (unregistered) in reply to superluser

    It could also be a device going through a web content filter that does MITM for inspection. If the device doesn't have the WCF trusted cert installed that error would show up. I've seen this a lot w/ non-managed devices on business/corporate networks. (think guest wi-fi when they still want to block some content.)

  • davethepirate (unregistered)

    The first one is probably a rounding error because someone decided you can't have a fraction of a person.

  • (nodebb)

    I usually see those certificate errors when somebody forgets to renew all their certificates in time, such as thinking all the certificates renew on March 30, so he plans on renewing them on March 25, but one of them renews March 20 and suddenly your ticket system gets filled up with certificate error reports. "Are we under attack?! No, Dave just forgot to keep an eye on the clock."

    Addendum 2022-03-11 10:52: Oh, yeah, this can also happen if the clock in your computer is off by a few days.

  • (nodebb) in reply to Nutster

    Addendum 2022-03-11 10:52: Oh, yeah, this can also happen if the clock in your computer is off by a few days.

    These days, there's no excuse for that. OK, for "a few days", there was never(1) an excuse, but nowadays, even being off by a few seconds is inexcusable.

    (1) Unless it was Monday morning and you had a Personal System/2 Model 50. (They had a BIOS bug which meant that the clock would sometimes glitch out and only advance as far as some time on Saturday if you left them on over the weekend.)

    Addendum 2022-03-11 12:08: Oops. If you left them off over the weekend.

  • (nodebb)

    The ClassCastException on the Danish site seems to have happened for a longer time already. Java has the strange behavior to not create stack traces any more when the same exception is thrown thousands of times. This seems to be the case here, that's why we only see the exception type.

  • (nodebb) in reply to scallowag

    Looking at the anglo-saxons in the world using , and . inverted... ;)

  • Ryan S (unregistered)

    I see the battery gaps on my MacBook whenever it's closed so that's normal, but what confuses me is the cliff hanging over... The battery was both 60% and 50% simultaneously?

  • NeverConfusedForNaught (unregistered) in reply to BernieTheBernie

    I didn't travel then. I honestly suspect some sudden power loss, and then on boot it maybe accessed the same buffer? The phone sometimes just rebooted randomly on 60% battery, maybe RAM was still dirty after boot?

  • (nodebb) in reply to scallowag

    You're seeing it blown up to about five times life size. In particular on a mobile device, which is how most people would read the site, it's essentially invisible.

    So the WTF is professional journalists creating such an ambiguous headline.

  • Erwin (unregistered) in reply to Tim

    17,522. 696 with a full stop would resemble a decimal fraction. And to add to the confusion, it would no longer be obvious if this notation uses a decimal point or a decimal comma.

  • Wat (unregistered) in reply to Ryan S

    That battery can time travel!

  • (nodebb) in reply to Erwin

    All it needs is the use of a single word, "with":

    cases up to 17,522 with 696 in hospital

  • RLB (unregistered) in reply to Tim

    En-dash.

  • (nodebb) in reply to RLB

    Em-dash, surely? It's not a range of numbers.

  • clubs21ids (unregistered)
    Comment held for moderation.
  • clubs21ids (unregistered)
    Comment held for moderation.
  • clubs21ids (unregistered)
    Comment held for moderation.

Leave a comment on “Past Time”

Log In or post as a guest

Replying to comment #:

« Return to Article