• Squiggle (unregistered)

    Blankety blank / blankety blank

    ...blankety frist!

  • chubertdev (cs)

    I prefer Costco for my bulk lorem ipsum purchases.

  • Menno (unregistered)

    Obviously 7.62939453125 MiB * Math.pow(1024 / 1000, 2) equals 8 MB.

  • Bernie The Bernie (unregistered)

    STRICT STANDARDS: NON STATIC METHOD WTF::FRIST() SHOULD NOT BE CALLED STATICALLY IN \Comments\AddComment.aspx?ArticleId=7822 ON LINE 42 FROM AS LOW AS WTF 69

  • moz (unregistered)

    Would you join a club run by people who can't even decide if it's called "Sams" or "Sam's"?

  • foxyshadis (unregistered)

    I've had plenty of frustration with sites claiming that long, unique passwords were not complex enough (for not including a symbol, or worse, having a symbol but not a number), but this is the first time I've seen Schrodinger's Password Complexity Theorem implemented.

  • Shinobu (unregistered)

    sigh Only PHP.

  • faoileag (unregistered)

    Builds that run so fast that they finish in the past are a real pita. You always have to be extra careful to check the time the build finished against the timestamps of the latest submissions into your source control system to see if all submissions have been considered in the build.

    When things finally got so bad that I had to wait for more than ten minutes after each submit before it was reasonably safe to start the build process, I gave up and reactivated an old 486 from the early nineties as my build machine.

    Now everything is fine again and all submissions up to the start of the build process are included. And sometimes even submissions that took place after the start of the build process!

  • faoileag (unregistered)
    Comment held for moderation.
  • Ben Peddell (unregistered)

    So with the build, the backend sets the end date to 0 instead of NULL, and the UI doesn't treat 0 as special, so it displays the OLE Automation Date epoch.

  • faoileag (unregistered) in reply to chubertdev
    Comment held for moderation.
  • faoileag (unregistered)

    The Bugzilla message is weird - to attach a file, I have to place it in a file? And the size of the file path must not exceed 7.62MB? That's a mighty long file path, that is!

  • Peter Wolff (unregistered)
    Comment held for moderation.
  • ClaudeSuck.de (unregistered) in reply to moz

    and then their button for the internet shop yields in "We can't find the page you're looking for, or it no longer exists"

  • anonymous (unregistered)

    Actually the bugzilla one is the configuration problem in php max_upload_size.

    The server php max_upload_size is set to 80000000 bytes (8MB, power 100), which equals to 7.62939453125 MiB (power 1024).

    I don't see there is any WTF here indeed.

  • anonymous (unregistered) in reply to anonymous
    anonymous:
    Actually the bugzilla one is the configuration problem in php max_upload_size.

    The server php max_upload_size is set to 80000000 bytes (8MB, power 100), which equals to 7.62939453125 MiB (power 1024).

    I don't see there is any WTF here indeed.

    8MB, power 100 -> I mean power 1000 ....

  • Peter Wolff (unregistered) in reply to anonymous
    anonymous:
    Actually the bugzilla one is the configuration problem in php max_upload_size.

    The server php max_upload_size is set to 80000000 bytes (8MB, power 100), which equals to 7.62939453125 MiB (power 1024).

    I don't see there is any WTF here indeed.

    Not a WTF, but impressive: exact down to the level of millibytes!

  • Yoo Suk (unregistered)

    The real WTF is OpenSSH providing a hidden API into its memory image.

  • vindico (unregistered) in reply to anonymous
    anonymous:
    Actually the bugzilla one is the configuration problem in php max_upload_size.
    That would be impressive, given that Bugzilla is written in Perl.
    anonymous:
    The server php max_upload_size is set to 80000000 bytes (8MB, power 100), which equals to 7.62939453125 MiB (power 1024).

    I don't see there is any WTF here indeed.

    The WTF is the lack of rounding.

  • nmclean (unregistered) in reply to anonymous
    anonymous:
    The server php max_upload_size is set to 80000000 bytes (8MB, power 100), which equals to 7.62939453125 MiB (power 1024).

    I don't see there is any WTF here indeed.

    How is it not a WTF? Just because we recognize what's happening doesn't mean it should be. The server configuration and the page view should follow the same convention to avoid user-unfriendly conversion bizarreness like this.

    On top of that, it's displaying the number as megabits (Mb) instead of megabytes. The whole thing is a cataclysm of value confusion.

  • Tux "Tuxedo" Penguin (unregistered)

    I don't care if skype report error like it's in Win 3.1, but can please SOMEONE tell me WHAT THE HANDLE IS???

  • BK (unregistered)

    Wil Wheaton's post might be intentional. I think it's a reference to the game "Cards against Humanity". Although, this is only my speculation. However, I will be watching it later to confirm.

  • Anonymoose (unregistered)

    Little known fact:

    "Go To Statement Considered Harmful" was written after an incident where somebody attempted to program a time machine in BASIC and accidentally sent it to 10 AD.

    This functionality is built in to modern microprocessors to help maintain a growth in speed that should be physically impossible. Sometimes a rogue instruction slips through, triggering the time circuits inadvertently, leading to things such as builds completing 115 years before they were started.

  • notme (unregistered) in reply to Yoo Suk
    Yoo Suk:
    The real WTF is OpenSSH providing a hidden API into its memory image.

    a) This has nothing to with the article. b) I think you're thinking of OpenSSL, not OpenSSH. c) If you really have evidence of OpenSSH doing such a thing, please contact the OpenBSD team about it and publish it after some reasonable time. Theo de Raadt could use some humility.

  • Steve The Cynic (cs) in reply to faoileag
    faoileag:
    When things finally got so bad that I had to wait for more than ten minutes after each submit before it was reasonably safe to start the build process, I gave up and installed NTP clients everywhere and stopped using SourceSafe.
    There, FTFY.

    Timestamps in SourceDangerous are according to the client machine's clock (UTC, at least...), and are therefore subject to all sorts of flakiness. When you create a label in SD, the client timestamps the label the same way it timestamps everything else. If the label is made on a machine whose clock is behind the clock on a machine somewhere else that checked in some piece of code, and it is so far behind that the timestamp on the code is in the labeller's future, the label is inserted before the already-checked-in code. Much hilarity ensues...

  • The Balance (unregistered)

    I have seen: "Your password must be less than 16 characters."

    Why?

  • HardwareGeek (cs)

    At least the handle is OK.

  • Jon (unregistered) in reply to anonymous
    anonymous:
    Actually the bugzilla one is the configuration problem in php max_upload_size.

    The server php max_upload_size is set to 80000000 bytes (8MB, power 100), which equals to 7.62939453125 MiB (power 1024).

    I don't see there is any WTF here indeed.

    Actually, this is 8000000 Bytes. You added one too many, but you're right. No real WTF here, except they didn't change the max upload to M and just say "8" upload_max_filesize = 8M

  • anon (unregistered)

    SureWest (now Consolidated Communications, Inc. [CCI]) recently requested that I change my 18-character long password with numbers, punctuation, upper and lower case letters into a 4-digit number. THE REAL WTF.

    Captcha: gravis. As in, I don't think CCI understands the gravis of their password situation.

  • Mike Dimmick (unregistered) in reply to Tux "Tuxedo" Penguin
    Comment held for moderation.
  • Loren Pechtel (cs) in reply to Menno
    Menno:
    Obviously 7.62939453125 MiB * Math.pow(1024 / 1000, 2) equals 8 MB.

    Why get fancy?

    7.62939453125 * 1024 * 1024 = 8000000

  • Loren Pechtel (cs) in reply to foxyshadis
    foxyshadis:
    I've had plenty of frustration with sites claiming that long, unique passwords were not complex enough (for not including a symbol, or worse, having a symbol but not a number), but this is the first time I've seen Schrodinger's Password Complexity Theorem implemented.

    Yeah. Long is more important than how big the character set is.

  • doctor_of_ineptitude (unregistered)

    I think Kelly L is missing an opportunity here. At 1189940 Kelvin, what it really is a portable Plasma Generator & Enemy Incinerator in EXCELLENT health and with EXCELLENT performance, disguised as a hard disk. Its temperature makes even the Sun sweat. Take that Gun control nut-jobs.

    TL;DR: Kelly L is a fool. Mistook plasma weapon for hard disk.

  • chubertdev (cs) in reply to faoileag
    faoileag:
    Ok, the National Geographic password bug calls for it: Password Selection Rules

    And, of course, the mandatory xkcd cartoon.

    http://xkcd.com/1354/

    Look very closely at the output in the last panel.

  • Jake (unregistered)

    The max size is coincidentally 8000000 bytes...

  • nunya (unregistered)

    Dear Denise, Your password WASN'T classified as 'very strong' that's why it's not highlighted green and there is no check mark next to the item. Ya twat.

  • Beast (unregistered) in reply to Tux "Tuxedo" Penguin
    Tux "Tuxedo" Penguin:
    I don't care if skype report error like it's in Win 3.1, but can please SOMEONE tell me WHAT THE HANDLE IS???

    I don't know, but I could not care less, because I know it's OK anyway.

  • chubertdev (cs) in reply to BK
    BK:
    Wil Wheaton's post might be intentional. I think it's a reference to the game "Cards against Humanity". Although, this is only my speculation. However, I will be watching it later to confirm.

    No, you'd see "_______" instead of "BLANK"

  • Glen (unregistered)

    In Marketing speak, 7.62939453125 Mb = 8.0 MB.

    7.62939453125 Mb = 7812.5 kb = 8000000 bytes.

  • Dragnslcr (cs) in reply to The Balance
    The Balance:
    I have seen: "Your password must be less than 16 characters."

    Why?

    Because the database field is char(16).

  • Gurth (cs) in reply to nunya
    nunya:
    Your password WASN'T classified as 'very strong' that's why it's not highlighted green and there is no check mark next to the item.
    Nope, thanks for playing. That line either says “Password does not meet requirements”, “Password strength: Strong” or “Password strength: Very strong” — I can’t, on a quick attempt to test it, make it display other strengths if I punch in some random characters. In any case, it definitely isn’t an item that gets checked off when the password meets certain criteria.
  • chubertdev (cs) in reply to Dragnslcr
    Dragnslcr:
    The Balance:
    I have seen: "Your password must be less than 16 characters."

    Why?

    Because the database field is char(16).

    No one should ever need more than 26^16 password complexity.

  • chubertdev (cs) in reply to Gurth
    Gurth:
    nunya:
    Your password WASN'T classified as 'very strong' that's why it's not highlighted green and there is no check mark next to the item.
    Nope, thanks for playing. That line either says “Password does not meet requirements”, “Password strength: Strong” or “Password strength: Very strong” — I can’t, on a quick attempt to test it, make it display other strengths if I punch in some random characters. In any case, it definitely isn’t an item that gets checked off when the password meets certain criteria.

    Sorry, but nunya is correct. The requirement hasn't been met, hence why it's gray and not green, and has no checkmark.

  • capio (unregistered) in reply to chubertdev
    Comment held for moderation.
  • BillClintonsWeiner (unregistered) in reply to The Balance
    The Balance:
    I have seen: "Your password must be less than 16 characters."

    Why?

    The resulting hash or encrypted value will be larger than the column width in the database.

    Or its so they can crack your password faster.

  • chubertdev (cs) in reply to capio
    capio:
    chubertdev:
    Sorry, but nunya is correct. The requirement hasn't been met, hence why it's gray and not green, and has no checkmark.
    Sorry¹, but you're an idiot². Go to the site, click "Join" in the top-right corner (it may take a few seconds to appear), click "JOIN NOW WITH EMAIL ADDRESS", and you'll clearly see that the item in question displays the strength of the password you entered, it's not part of the list of requirements. When you focus the password field, it starts off showing "Password does not meet requirements", then once you enter something at least 8 characters long with at least one letter and one digit, it varies from "Password strength: Weak" (for example, "abcdefg1") to "Password strength: Very strong" (for example, "ewk2,)4lP;[Wl1Jp@l&"). At no point does it change colour or add a check mark, unless there's some level above "Very strong" that I haven't been able to achieve

    [1] This is a lie. [2] This is entirely true.

    It goes green with "Extremely strong", there's your problem

  • Prof. Foop (unregistered) in reply to Anonymoose

    Amazingly, 115 years in the past is only 317 milliseconds ago!

  • immibis (cs)

    Did anyone else notice the method is "HOTEL::GETUSUALLOWPRICE"?

    That is "Hotel::GetUsualLowPrice" and not just "Hotel::GetPrice". The marketing is creeping into the code!

  • Peter Wolff (unregistered) in reply to Tux "Tuxedo" Penguin
    Tux "Tuxedo" Penguin:
    I don't care if skype report error like it's in Win 3.1, but can please SOMEONE tell me WHAT THE HANDLE IS???
    The handle is a Whitespace (or, in this case, Grayspace) object, duh.
  • Multiplier (unregistered)

    7.62939453125 MB is exactly 8,000,000 bytes.

Leave a comment on “Visit Scenic NON-STATIC METHOD”

Log In or post as a guest

Replying to comment #:

« Return to Article