You think someone else is paying for all of this, don't you? Sorry, but it is you (and the rest of us).
Dude, the point of insurance is that you spread out the risk - not every uninsurable guy brought it on themselves, not even most. Some had a chronic condition, got laid off, and now can't get coverage due to screwed up rules on coverage.
You could mandate a minimum group size for public insurance companies and require them to offer it to anyone who qualifies; combine that with portability, pretax or tax deductible premiums, and geographical groups and you have a winner. Not as profitable, but that's to be expected - insurance shouldn't be wildly profitable.
Really, all you have to do is charge in a different currency: if you can show that a company knew or should have known about some fatal design flaw, then someone goes to jail, and their title starts with a C.
The optimist in me says maybe it's like the way the Eskimo language has 15 different words for "snow."
No, they have an agglutinative language where you tack lots of descriptive stems onto a root to make your words. It's like german, where whole phrases turn into a single word.
Of course, I'd never just jump into a COBOL codebase older than I am as my first COBOL project. Likewise, only a fool unleashes a bunch of COBOL noobs on a codebase without at least a couple old hands to ride herd.
Is it? depends on whether you're playing the odds or assuming that all people with jewish names are jews. They certainly are ethnically, and the actual proportion that are religious jews is likely to be high, although I don't know exactly. The GP stated that the Doc is jewish and, if his reason for doing so is sound, the rest of the argument is fairly sound; the Torah is pretty legalistic in places.
They already use captchas (sort of). If someone is sitting in a corner mining gold or killing beasts for hours on end and talking to nobody at all, they can send a GM over to talk to them directly - no reaction = probable bot.
More worrying was some of the conversations we had in San Fransisco with apparently random strangers. Sounded more like Scientology interview processes than spur of the moment chat sprung up with total strangers.
Well, they may have been scientologists - it is SF, after all.
There was a question, "You have two dark alleys to walk down, one has a gruop of white guys in business suits and the other a group of black gang bangers. which alley to you walk down?"
what if you use that dye-acrylic stuff to distribute your light to the edge of the panel, then line the edge with 37% efficient cells? That could make for some nice cheap panels.
These are the guys who have been fighting it since day one due to them running the lines in the first place. Good luck there.
I assume you're talking about comcast sharing bandwidth on their lines; copyright has nothing to do with running lines. Comcast can run lines because they've been granted that right by the cities they operate in. Those cities won't want two companies tearing the roads up and anyway, it'd be cost prohibitive for guy #2. Sounds like a good reason to move move to a model where anyone can use the lines for a reasonable fee. Of course, the haven't done that with the phone lins and those were actually paid for by the taxpayers.
You're unaware that branch offices have locks, alarms, and/or security systems, and I'm the dumbass? I'm beginning to wonder if your sig is a critique of the government or an endorsement of Newspeak!
Your standard office isn't secure. It keeps out burglars most of the time, but someone who wants to hack the city network can break in and steal a router. The steps he took prevent that attack.
First and foremost, your assertions that the routers that had been messed with were in "branch offices," or that branch offices were "unsecured locations," are assertions you've pulled out of your ass, not from even the most sympathetic news reports.
No, they're from sympathetic sources. Of course, doing it in all the routers implies he didn't trust his coworkers, and note that he did this with approval more than a year ago.
it appears (on further research that contradicts my earlier understanding) that Childs had not originally been the sole person with access: other administrators had access until Childs issued the password changes, and it appears that those changes were made in the hours or days just before he got fired.
I haven't seen anything that I trust to support that. I support the scenario where the admins monkeyed with the system and got locked out due to existing paranoid configs.
The more facts that come out, however, the more this looks like mutiny, malfeasance, and deliberate sabotage.
What sabotage? The network never went down. Everyone could do work. The only thing that happened is that they arrested a fired admin for not divulging a password and set an absurd bail. I don't see support for a $5m bail, and I predict that the city will be on the hook for about that much once this is all settled.
dumbass. What would you recommend for a branch office with an unsecured location where equipment can easily walk out the door? You lock it down so that physical access won't compromise the network. Power blips aren't an issue - the router won't lose its brains. The DR plan is to reload the config after the disaster is over.
Slashdot Mirror
No, it's because that makes you a security risk, just like being gay when it's illegal.
You think someone else is paying for all of this, don't you? Sorry, but it is you (and the rest of us).
Dude, the point of insurance is that you spread out the risk - not every uninsurable guy brought it on themselves, not even most. Some had a chronic condition, got laid off, and now can't get coverage due to screwed up rules on coverage.
You could mandate a minimum group size for public insurance companies and require them to offer it to anyone who qualifies; combine that with portability, pretax or tax deductible premiums, and geographical groups and you have a winner. Not as profitable, but that's to be expected - insurance shouldn't be wildly profitable.
Really, all you have to do is charge in a different currency: if you can show that a company knew or should have known about some fatal design flaw, then someone goes to jail, and their title starts with a C.
Any idiot can cut. The point of schooling is so you cut the right thing. Or would you prefer to get worked on by a butcher?
The optimist in me says maybe it's like the way the Eskimo language has 15 different words for "snow."
No, they have an agglutinative language where you tack lots of descriptive stems onto a root to make your words. It's like german, where whole phrases turn into a single word.
so, how do you go back? Also, do you give them their old salary backdated to today when the budget passes?
Of course, I'd never just jump into a COBOL codebase older than I am as my first COBOL project. Likewise, only a fool unleashes a bunch of COBOL noobs on a codebase without at least a couple old hands to ride herd.
nope. Copyright law is silent on your rights to use a work. You just can't copy random stuff and distribute it.
Why host your own mail? Just go to some webmail outfit and get imap hosting for $20/yr.
Is it? depends on whether you're playing the odds or assuming that all people with jewish names are jews. They certainly are ethnically, and the actual proportion that are religious jews is likely to be high, although I don't know exactly. The GP stated that the Doc is jewish and, if his reason for doing so is sound, the rest of the argument is fairly sound; the Torah is pretty legalistic in places.
well, kiddy porn is always illegal. Source code, not so much.
They already use captchas (sort of). If someone is sitting in a corner mining gold or killing beasts for hours on end and talking to nobody at all, they can send a GM over to talk to them directly - no reaction = probable bot.
You're pretty much guaranteed if your code is 'hacked' while its fate is being decided by a judge.
More worrying was some of the conversations we had in San Fransisco with apparently random strangers. Sounded more like Scientology interview processes than spur of the moment chat sprung up with total strangers.
Well, they may have been scientologists - it is SF, after all.
There was a question, "You have two dark alleys to walk down, one has a gruop of white guys in business suits and the other a group of black gang bangers. which alley to you walk down?"
First thought was "oh boy, Yakuza or Bloods".
what if you use that dye-acrylic stuff to distribute your light to the edge of the panel, then line the edge with 37% efficient cells? That could make for some nice cheap panels.
So anything that isn't 100% cruel capitalism is evil socialism? I'd hate to live in your world.
If your mail config depends on a DB, it'll be shouting HEY LOOK, I'M LOOKING STUFF UP IN A DB. IT isn't exactly subtle.
I guess it's hard to compete with exxon for d-bagginess, huh?
These are the guys who have been fighting it since day one due to them running the lines in the first place. Good luck there.
I assume you're talking about comcast sharing bandwidth on their lines; copyright has nothing to do with running lines. Comcast can run lines because they've been granted that right by the cities they operate in. Those cities won't want two companies tearing the roads up and anyway, it'd be cost prohibitive for guy #2. Sounds like a good reason to move move to a model where anyone can use the lines for a reasonable fee. Of course, the haven't done that with the phone lins and those were actually paid for by the taxpayers.
Nah, info wants to be free like Hydrogen
You're unaware that branch offices have locks, alarms, and/or security systems, and I'm the dumbass? I'm beginning to wonder if your sig is a critique of the government or an endorsement of Newspeak!
Your standard office isn't secure. It keeps out burglars most of the time, but someone who wants to hack the city network can break in and steal a router. The steps he took prevent that attack.
First and foremost, your assertions that the routers that had been messed with were in "branch offices," or that branch offices were "unsecured locations," are assertions you've pulled out of your ass, not from even the most sympathetic news reports.
No, they're from sympathetic sources. Of course, doing it in all the routers implies he didn't trust his coworkers, and note that he did this with approval more than a year ago.
it appears (on further research that contradicts my earlier understanding) that Childs had not originally been the sole person with access: other administrators had access until Childs issued the password changes, and it appears that those changes were made in the hours or days just before he got fired.
I haven't seen anything that I trust to support that. I support the scenario where the admins monkeyed with the system and got locked out due to existing paranoid configs.
The more facts that come out, however, the more this looks like mutiny, malfeasance, and deliberate sabotage.
What sabotage? The network never went down. Everyone could do work. The only thing that happened is that they arrested a fired admin for not divulging a password and set an absurd bail. I don't see support for a $5m bail, and I predict that the city will be on the hook for about that much once this is all settled.
dumbass. What would you recommend for a branch office with an unsecured location where equipment can easily walk out the door? You lock it down so that physical access won't compromise the network. Power blips aren't an issue - the router won't lose its brains. The DR plan is to reload the config after the disaster is over.
I fully expect that Childs has excellent grounds for a hefty defamation lawsuit.