• (disco) in reply to abarker
    abarker:
    I hereby sentence you to play DF with @ben_lubar for 4 hours.

    That's just mean spirited, couldn't you just sentence him to death?

  • (disco) in reply to abarker
    abarker:
    Oh no! The apocalypse is nigh! Every man (and woman) for themself!

    I dub you sir abarker the irony-challenged.

  • (disco) in reply to locallunatic
    locallunatic:
    That's just mean spirited, couldn't you just sentence him to death?

    No.

  • (disco) in reply to FrostCat
    FrostCat:
    I dub you sir abarker the irony-challenged.

    Too late:

    Arantor:
    Lord Knight @­abarker, Master of the Frequently Shifting Avatar
  • (disco) in reply to locallunatic
    locallunatic:
    >abarker: I hereby sentence you to play DF with @ben_lubar for 4 hours.

    That's just mean spirited, couldn't you just sentence him to death?

    There's a great clip from Phineas and Ferb of Doofenshmirtz stopping Perry and going "Whoa, whoa, whoa, whoa, WHOA!". It's another one I haven't been able to find on YT, but if I could, it would fit either after your or abarker's post.

    Actually DF's not even all that bad. I even bought the obvious ripoff on Steam when it was Early Access or otherwise on sale, although it was so unfinished the time you couldn't really do much. In one game, one fo the first things one of my gnomes made was a legendary chair. I might have a screenshot at home.

  • (disco) in reply to abarker

    Titles are generally "multiples allowed".

  • (disco) in reply to FrostCat
    FrostCat:
    Titles are generally "multiples allowed".

    Tell that to Discourse.

  • (disco) in reply to FrostCat
    FrostCat:
    Actually DF's not even all that bad.
    [image]
  • (disco) in reply to abarker
    abarker:
    Tell that to Discourse.

    By "generally" I was acknowledging Discourse lack of this feature.

    Hey, @codinghorror, we should be able to select multiple titles, and then a dropdown would appear in posts where the titles go so people can peruse at their leisure.

  • (disco) in reply to Luhmann

    What? There's some pretty deep Transport Tycoon-type play there, for example. And really, who doesn't want to simulate moving all those rocks and stuff into stockpiles?

  • (disco) in reply to FrostCat
    FrostCat:
    And really, who doesn't want to simulate moving all those rocks and stuff into stockpiles?

    :wave:

  • (disco) in reply to abarker

    Fortunately for you, it's optional. You can let your dwarves stumble over the rubble filling the fortress, you heartless etc.

  • (disco) in reply to FrostCat

    How about this:

    Who doesn't want to play Dwarf Fortress?

    :wave:

  • (disco) in reply to abarker

    In Lubar Milwaukee, Fortress dwarfs you.

  • (disco) in reply to FrostCat
    FrostCat:
    Actually DF's not even all that bad.

    If I had time for games any more, it's something I would definitely check out.

  • (disco) in reply to abarker
    abarker:
    Every man (and woman) for themself!

    oh, it's early.

    /me heads for the bomb shelter and locks the door so no one else can get in.

    :smiling_imp:

  • (disco) in reply to abarker
    abarker:
    I hereby sentence you to play DF with @ben_lubar for 4 hours.

    http://steamcommunity.com/broadcast/watch/76561198013565588

  • (disco) in reply to ben_lubar
    ben_lubar:
    http://steamcommunity.com/broadcast/watch/76561198013565588

    I'm not signing in to watch a video, but why the hell was the page in (I assume) Portuguese?

  • (disco) in reply to FrostCat

    You have to sign in to watch those? It was just me playing Dwarf Fortress with no audio.

  • (disco) in reply to ben_lubar

    Here, have an @ben_lubar-sized screenshot:

    [image]

    That's what I get when I click your link.

    Also, I see someone fixed Discurse so it shrinks you-sized images.

  • (disco) in reply to FrostCat

    Steam's site is somehow foul at Geolocation. Whenever I go to the site it's in Polish.

  • (disco) in reply to ben_lubar

    You have to sign in for everything at steamcommunity.com, IIRC. It's just steampowered.com that's open to all.

  • (disco) in reply to blakeyrat

    It seems to just be the broadcasting stuff that requires logging in. The screenshots don't: http://steamcommunity.com/id/nightgunner5/screenshots/?appid=72850

    Any link on this page does: http://steamcommunity.com/?subsection=broadcasts

  • (disco) in reply to Kensey
    Kensey:
    I'm not sure I understand the WTF here. Obviously the old design firm doesn't want to advertise themselves as the designers of a site they no longer control, because God only knows what horrors Felix might be inflicting on it over their name. So the "Designed by" credit calls back to a server the designer controls and can change the reply from at any time. "We got fired" = "our credit line is now a blank space" (or just block the customer site).
    Or add goatse to their page footer. Or a browser exploit.
  • (disco) in reply to DaveK

    They could also add sleep(1e20); to their page and take down everyone else's websites.

  • (disco) in reply to Kensey
    Kensey:
    Having the list be parsed out of a page rather than fed as a query result may save enough in CPU cycles/administrative aggravation (one less database to maintain) to make the bit of extra bandwidth to serve out the whole list to be parsed worth it, especially if it's a small firm whose customers aren't getting huge amounts of traffic.
    What do you think would take more CPU power: building an entire webpage out of dynamic components, easily requiring a dozen queries or more, downloading all that HTML, utilizing a DOM parser to go through it, index it, then use a search to find a specifically labelled element in it...

    or producing and consuming a JSON string out of a single query?

    It is just somewhat possible that the entire page is either cached (so no database call needed) or plain old static HTML (not very likely for a design company, these guys like to build CMSs into their CMSs), but even then you could also just cache / plain-text a string response. Adding all that markup and especially parsing all that markup is a bugger of an overhead, worse even than using XML. And they do it on each and every page-view.

    Worse, there is apparently no clean way to handle failure; what if the company's website is offline? All their client sites will display errors, or at the very best fail to display the designer's credits.

    I agree that having a controllable list of which clients can refer back to you is a sensible idea, albeit a somewhat paranoid one. But there are proper ways of inserting rarely-changing external data into your site, and scraping a whole website on every page-view is not one of them.

  • (disco) in reply to ben_lubar
  • (disco) in reply to FragFrog
    FragFrog:
    What do you think would take more CPU power: building an entire webpage out of dynamic components, easily requiring a dozen queries or more, downloading all that HTML, utilizing a DOM parser to go through it, index it, then use a search to find a specifically labelled element in it...

    or producing and consuming a JSON string out of a single query?

    It doesn't have to be that complicated. I'm envisioning something as simple as a set of <div>s with a company name in each. if your company is there, spit out this string. If it's not, don't.

    It is just somewhat possible that the entire page is either cached (so no database call needed) or plain old static HTML (not very likely for a design company, these guys like to build CMSs into their CMSs), but even then you could also just cache / plain-text a string response. Adding all that markup and especially parsing all that markup is a bugger of an overhead, worse even than using XML. And they do it on each and every page-view.

    It's a little more reliable to parse very basic HTML than plain text would be because you can use many tools that understand HTML to manipulate and validate it and you don't have as much worry about delimiters getting confused (unless a company's name has <div> or </div> in it...) And they don't care about parsing overhead because that's their client's site's server's problem. Making it the client's problem saves the designer maintaining a database and/or exposing an existing one to more query traffic. If there's a low-cost cache between them and the client, they don't even have to care much about their own server bandwidth.

    Worse, there is apparently no clean way to handle failure; what if the company's website is offline? All their client sites will display errors, or at the very best fail to display the designer's credits.

    Most likely the latter, and arguably that's a feature: if you're a web designer and your site is offline, you certainly don't want to call attention to it.

    I agree that having a controllable list of which clients can refer back to you is a sensible idea, albeit a somewhat paranoid one. But there are proper ways of inserting rarely-changing external data into your site, and scraping a whole website on every page-view is not one of them.

    It's a little unusual, but it's not so wacky that I automatically go "there's no way in which that is a right or acceptable solution" (however, I suspect I would find the code archaeology of how it came to be, fascinating). And it's probably not that much data to scrape and not that complex to parse. You can fit a lot of company names into a 1500-byte packet's payload.

    The real issue here is they are using untrustworthy client-side validation -- but since anybody with the technical skills to make changes presumably wants credit for them, that's probably more of a theoretical problem than otherwise. I have a hard time imagining a former client, even an ill-treated one, deliberately botching up their website and placing a static credit to a design firm they're no longer on good terms with on it, just for spite.

  • (disco) in reply to FrostCat
    FrostCat:
    above-and-beyond the call pendantry

    You mean catching the ones that are not merely garden-variety hanging offenses, such as anyone might commit on an off day, but full-fledged hanged-by-the-neck-until-dead offenses?

  • (disco) in reply to Zainab58

    Are you suggesting that some hanging offenses, you cut the person down while they're still alive?

  • (disco) in reply to FrostCat

    well, how else would Moist von Lipwig have gotten his job?

  • (disco) in reply to FrostCat
    FrostCat:
    That's what I get when I click your link.
    I can confirm that is indeed Portuguese. I get English, btw.
  • (disco) in reply to Zecc
    Zecc:
    I can confirm that is indeed Portuguese.I get English, btw.

    I did spot, after I took the screenshot, a "change language" dropdown at the top of the page.

  • (disco) in reply to Kensey
    Kensey:
    I'm not sure I understand the WTF here. Obviously the old design firm doesn't want to advertise themselves as the designers of a site they no longer control

    There's probably 2 or 3 ways of doing that without resorting to a page scraping script. If you don't want database lookups or scripts, then create a bunch of static HTML/text files with the client's customer ID as the name and embed those.

  • (disco) in reply to FrostCat
    FrostCat:
    Are you suggesting that some hanging offenses, you cut the person down while they're still alive?
    And the "didn't get the joke" award goes to...

    Sure, historically there is a reason for the "until dead" line. It only takes one broken rope and one clever lawyer. But that was, ahem, not exactly my point.

  • (disco) in reply to Zainab58
    Zainab58:
    And the "didn't get the joke" award goes to...

    Promises, promises.... Also, I'm going to say "I was just taking the joke and making my own."

    Zainab58:
    But that was, ahem, not exactly my point.

    Were you suggesting there's no such thing as "above-and-beyond" pendantry? I just re-read what you wrote and I can't think of any other explanation.

  • (disco) in reply to FrostCat
    FrostCat:
    Are you suggesting that some hanging offenses, you cut the person down while they're still alive?

    Yes, so then they get to enjoy the things you do to them afterwards, like dragging their entrails out with a hook, cutting pieces like hands off them, or burning them a little. Do you have no imagination?

  • (disco) in reply to anonymous234
    anonymous234:
    Covering the camera, pointing it away from you or not smiling enough when reading the state-provided news will be punished with up to 15 years in a reeducation camp.

    In Soviet Society, Computer Reads YOU!

  • (disco) in reply to another_sam
    another_sam:
    Do you have no imagination?

    That's a big assumption.

  • (disco) in reply to FrostCat
    FrostCat:
    That's a big buttumption.
    CTFY
  • (disco) in reply to accalia
    accalia:
    FrostCat:
    That's a big buttumption.
    CTFY

    https://www.youtube.com/watch?gl=BE&v=2ImZTwYwCug

  • (disco) in reply to accalia
    accalia:
    CTFY

    TDWTFTFY

    Edit: HTML better n00b

  • (disco) in reply to another_sam
    another_sam:
    Edit: HTML better n00b

    me?

    sorry, i was abusing discourses habit of auto closing open tags at the end of a post.

  • (disco) in reply to accalia
    accalia:
    me?

    No, me. My edit was to improve my HTML after I looked at the source for your post. :)

  • (disco) in reply to another_sam
    another_sam:
    Yes, so then they get to enjoy the things you do to them afterwards, like dragging their entrails out with a hook, cutting pieces like hands off them, or burning them a little.

    http://en.wikipedia.org/wiki/Hanged,_drawn_and_quartered

  • (disco) in reply to HardwareGeek

    To hang someone without killing them, AIUI, takes a bit of effort, because you have to place the knot right so that it doesn't break the neck.

  • (disco) in reply to FrostCat

    You have it backwards. You need to drop someone far enough to break their neck if you want to kill them quickly. That's the purpose of the modern gallows.

    If you want it to take a while, don't drop them at all, just hoist them by the neck.

  • (disco) in reply to FrostCat

    AIUI, not really — a sufficiently short drop will not break the neck, pretty much regardless of knot placement. Rather, it will leave the person dangling while the rope obstructs their ability to breathe. Breaking the neck with a short drop does require careful knot placement — in a place never, ever seen in any movie hanging, directly in front of the face, snapping the head backward.

    As @another_sam posted more quickly than I did, a long drop will break the neck with much less careful knot placement, but a drop sufficient to assure breaking the neck without worrying about knot placement runs the risk of ripping the neck in two — effective, but messy.

  • (disco) in reply to FrostCat
    FrostCat:
    Were you suggesting there's no such thing as "above-and-beyond" pendantry?
    No, I was merely commenting on the word "**pendantry**". But I'm not sorry, seeing the entertaining line of discussion that ensued.
  • (disco) in reply to Zainab58
    Zainab58:
    No, I was merely commenting on the word "**pendantry**".

    You must be new here.

Leave a comment on “You Can't Fire Us Until We Quit”

Log In or post as a guest

Replying to comment #:

« Return to Article