Most pin tumbler locks (like the one on your front door) are pathetically easy to break using a set of bump keys that you can make yourself or buy online for $10.
If you want real security, you need a high security deadbolt. Breaking a good lock like an Abloy Protec is considerably more difficult. The Protec, for example, doesn't use pins. That means that it can't be bumped and it can't be picked (note that I said it can't be picked, not that it can't be manipulated). The end result is that it takes different skills and tools to manipulate a Protec, which means that criminals are far less likely to do so.
The solution to these kind of issues is pretty simple. Tell your boss that you are concerned about the scraping causing liability issues for your company. CC your legal department contact on the issue.
If you believe CCing your legal contact when you have a legal concern is going to get you in trouble, there are real problems with your manager. You can go speak to your legal contact in private, and voice your concern. If you don't have that option, it's time to find another company.
Here in Colorado, there's T-Mobile coverage (EDGE so far - 3G launches next month) all along the front range, including in places like Berthoud (population 5000) and Windsor (population 10,000). The entire Denver metro area is blanketed with coverage, as is the Colorado Springs metro area.
I've also used T-Mobile in the Puget Sound area, which is pretty much 100% covered. As is the Bay Area.
And, you know what? Where I don't have T-Mobile coverage (e.g. Wyoming) I can roam on to another provider (e.g. Union Wireless) for free.
T-Mobile's coverage isn't as bad as people think. In the places I spend the most time, it works better than AT&T.
On Windows, UAC checks the Authenticode signature on the executable. Signed applications (like Apple Software Updater) are validated using a X.509 certificate, and the UAC dialog shows the publisher name (Apple Inc.).
Now on Mac OS X, I have no idea what stops this from happening.
Re:This is a huge amount of work
on
Linux 2.6.27 Out
·
· Score: 5, Interesting
If you suggested that every single change to the codebase be reviewed by multiple developers in a traditional proprietary software development house you would be, rightly, laughed at.
When I was at Microsoft, that's exactly how it worked. All code had to be reviewed and approved by the feature owner and the PM. There was also a team that reviewed any changes to the common libraries, in addition to the PM.
In addition, to actually get code checked in, it had to pass FxCop (code standards verification tool), not break the build, and not break any of the build verification tests (BVTs).
Mind you, I worked in the test team. Developers have to go through all of the same steps, and then their code also gets tested by the test team.
Sounds like a decent deal. AT&T wants $60/mo for 5GB of HSDPA, which is cheaper than the £2/day T-Mobile plan but more than the £20/mo T-Mobile plan.
The big advantage with the £2/day plan is for casual users. Airport Wi-Fi usually costs more than that ($10) in the US, although some airports (Denver, Las Vegas) have free Wi-Fi.
True story - I was at a movie theater seeing "Get Smart", and noticed Nielsen researchers at the theater handing out surveys. I walked up to one, and exclaimed:
I also live in a Comcast/Qwest market (Boulder, CO), but this market isn't nearly as competitive as the Puget Sound area (where I lived over the summer - working for MS).
In general, I've found Comcast to be surprisingly tolerable if you know how to deal with them. Yeah, their billing system sucks. And, yeah, they gave me S-cards for my TiVo HD instead of an M-card. But they have never given me the "unplug your router" crapola.
If you want Comcast to treat you like someone who knows what the hell they are talking about, you need to demonstrate that you know what the hell you are talking about. Being a software engineer or a competent sysadmin doesn't mean that you know shit about an HFC cable system.
If you call up and say, "my cable modem is broken", they're going to have you go through all of the basic troubleshooting. The thing is, Comcast (and every other cable ISP) gets thousands of these calls, and many probably have nothing to do with the modem or the network.
If, on the other hand, you call them up and say, "My upstream power level is 53dBmV", "My downstream signal to noise ratio is 25dB", or "My downstream power level is -15.5dBmV", you won't have to go through the diagnostics.
When my upstream power level was too high (usually referred to as the modem "shouting"), I went on the support chat and told them exactly that. I was asked if the cables were tight. I said yes. The agent scheduled a technician visit, the technician came, and he put his signal analyzer on the line. Result? It appears that the line is fine, and my 2-year-old SB5100 decided to screw itself. Next step? I'm going to rent a modem from Comcast (total time: approximately 5 minutes to drop by the local office) for $3/mo and see if the problem goes away.
Look, I don't like transfer caps. But this cap isn't really anything new. Now they're being explicit about something that they (and most ISPs) have been doing for a long time. My only concern is that in 5 years, 250GB will look woefully inadequate.
No, Java dominates in some fields (enterprise applications) and is hardly used in others.
At the high-end, Java is facing serious competition from ASP.net. At the low-end, PHP continues to be hugely popular, along with newer frameworks like Rails.
Java's problem is that it's a pain in the ass. PHP is dead-simple to install and configure on Linux, which is partly why it's so popular with small websites. And ASP.net integrates extremely well with Microsoft environments (e.g. Windows Server, SQL Server, AD).
Scientific theories only hold out until something else comes along with more facts that change our understanding.
Uh, yeah? That's the whole point of Science. Scientists try to create theories that best fit the available data. More importantly, they are always looking for new evidence which will either corroborate or contradict their theories.
You know, I think that SUVs suck. They're hard to park, they make it difficult for other drivers to see, they increase the risks to people driving smaller vehicles, and, of course, they get terrible fuel economy.
But as for SUVs being "death traps", you're just plain wrong.
Of the 38 vehicles that are "Top Safety Picks" (the highest rating), 20 are SUVs. That's more than half. Meanwhile, there's exactly one small car that recieves the saem result, and the IIHS notes that larger vehicles do better, assuming that the ratings are equal.
Most SUVs don't use body-on-frame construction, and are instead based on car platforms.
So, yeah, maybe I'm a "sucker" for relying on crash test data and fatality statistics.
Pretending that every person who drives an SUV is somehow deluded or evil probably isn't going to get us anywhere. Making up bullshit certainly isn't.
ThinkPad T61 Core 2 Duo 2.0GHz 4GB DDR2 Hitachi 7k200 disk NV Quadro NVS 140m
This is a standard, run of the mill business notebook. It has 4GB of memory, but memory is really, really dirt cheap now. It ran fine before I upgraded it to 4GB, too.
Didn't study Ghandi and Indian independence in school?
Never heard of Vietnam-era anti-war protests?
Yes, because segregation, colonial oppression, and an unjust war are totally the same thing as a company making software that you don't like.
I don't like Apple's policies with software on the iPhone either. Solution? Don't buy one. There's always OpenMoko, Android, Symbian, BlackBerry, and, yes, even WinMo.
To me the name really isn't that important. What is important is giving credit where credit is due.
So, we should call it GNU/Linux/Qt/KDE/MoFo/OOo? Because the office suite, desktop environment, UI toolkit, and web browser is probably much more visible to the user than the GNU utilities, and arguably just as important.
I don't know what you're trying to prove. For me, the first link for "getfirfox" is the MoFo/Google getfirefox.net. The first link for "Linux is linux.com. And the first link for "Open Office" is OpenOffice.org.
Now if you want to argue that the "sponsored links" are crap, I can't help but agree. But Google has the exact same problem.
Uh, you mean like 1997? GSM is newer here than it is in Europe, but it's hardly "new".
T-Mobile and AT&T are GSM, but GSM coverage isn't nearly as widespread here. Once you're out in the sticks, if you've got a GSM phone, you're lucky to get service.
This used to be the case, but it isn't anymore. There are lots of minor regional GSM carriers (e.g. Union Wireless in Wyoming), and you can roam for free, so GSM coverage isn't a whole lot different from CDMA2000 coverage.
We're in the stone-age here.
I'll have to remember that the next time I'm playing with my 3G iPhone.
It's almost cheating for a machine here. Much of the game is based off of your opponents meat-weaknesses and reading their hand from their faces. The computer doesn't have a face and is using pure probability. Even the best poker player cannot read them. So unless they're better at math than a computer and and their poker prowess isn't based on reading people, they're never going to win. It takes the game out of the game really. The perfect odds playing machine against the perfect odds playing player would come out even.
If you think that this is how poker works at a professional level, you don't know very much about poker.
Tells are a small factor at a professional level. Good players already have a firm understanding of the pot odds and expected value of a call.
The major problem with writing a good poker program is that it can't be exploitable. If the program is too "tight", an experienced human player will realize this and can always raise with trash (because the program will fold), with a minimal chance of getting caught. If the program is too "loose", the human player can play good hands far more aggressively, knowing that the program will call.
This is a very general example. In reality, poker strategy is far more nuanced. But the basic problem that computers face is not being predictable. And, no, playing randomly doesn't help - it merely substitutes poor play for predictable play.
Slashdot Mirror
The latest OTA update is RC30, which patches the issue (I confirmed this on my G1).
I'm not sure that having most of Colorado covered with EDGE counts as "all but disappears".
In my experience, people sell T-Mobile's coverage short. AT&T is noticeably inferior throughout the Fort Collins and Boulder areas.
Most pin tumbler locks (like the one on your front door) are pathetically easy to break using a set of bump keys that you can make yourself or buy online for $10.
If you want real security, you need a high security deadbolt. Breaking a good lock like an Abloy Protec is considerably more difficult. The Protec, for example, doesn't use pins. That means that it can't be bumped and it can't be picked (note that I said it can't be picked, not that it can't be manipulated). The end result is that it takes different skills and tools to manipulate a Protec, which means that criminals are far less likely to do so.
The solution to these kind of issues is pretty simple. Tell your boss that you are concerned about the scraping causing liability issues for your company. CC your legal department contact on the issue.
If you believe CCing your legal contact when you have a legal concern is going to get you in trouble, there are real problems with your manager. You can go speak to your legal contact in private, and voice your concern. If you don't have that option, it's time to find another company.
What the hell are you talking about?
Here in Colorado, there's T-Mobile coverage (EDGE so far - 3G launches next month) all along the front range, including in places like Berthoud (population 5000) and Windsor (population 10,000). The entire Denver metro area is blanketed with coverage, as is the Colorado Springs metro area.
I've also used T-Mobile in the Puget Sound area, which is pretty much 100% covered. As is the Bay Area.
And, you know what? Where I don't have T-Mobile coverage (e.g. Wyoming) I can roam on to another provider (e.g. Union Wireless) for free.
T-Mobile's coverage isn't as bad as people think. In the places I spend the most time, it works better than AT&T.
802.16e-2005, the standard that Sprint is using, was ratified in 2005. So you certainly weren't using it in 2003-2004.
On Windows, UAC checks the Authenticode signature on the executable. Signed applications (like Apple Software Updater) are validated using a X.509 certificate, and the UAC dialog shows the publisher name (Apple Inc.).
Now on Mac OS X, I have no idea what stops this from happening.
When I was at Microsoft, that's exactly how it worked. All code had to be reviewed and approved by the feature owner and the PM. There was also a team that reviewed any changes to the common libraries, in addition to the PM.
In addition, to actually get code checked in, it had to pass FxCop (code standards verification tool), not break the build, and not break any of the build verification tests (BVTs).
Mind you, I worked in the test team. Developers have to go through all of the same steps, and then their code also gets tested by the test team.
No, that's what we can thank the market for. OOo started out as a commercial product, remember.
Or are you one of those nutjobs who thinks every open-source project can be traced back to RMS?
Sounds like a decent deal. AT&T wants $60/mo for 5GB of HSDPA, which is cheaper than the £2/day T-Mobile plan but more than the £20/mo T-Mobile plan.
The big advantage with the £2/day plan is for casual users. Airport Wi-Fi usually costs more than that ($10) in the US, although some airports (Denver, Las Vegas) have free Wi-Fi.
True story - I was at a movie theater seeing "Get Smart", and noticed Nielsen researchers at the theater handing out surveys. I walked up to one, and exclaimed:
"You bastards! You killed Firefly!"
I also live in a Comcast/Qwest market (Boulder, CO), but this market isn't nearly as competitive as the Puget Sound area (where I lived over the summer - working for MS).
In general, I've found Comcast to be surprisingly tolerable if you know how to deal with them. Yeah, their billing system sucks. And, yeah, they gave me S-cards for my TiVo HD instead of an M-card. But they have never given me the "unplug your router" crapola.
If you want Comcast to treat you like someone who knows what the hell they are talking about, you need to demonstrate that you know what the hell you are talking about. Being a software engineer or a competent sysadmin doesn't mean that you know shit about an HFC cable system.
If you call up and say, "my cable modem is broken", they're going to have you go through all of the basic troubleshooting. The thing is, Comcast (and every other cable ISP) gets thousands of these calls, and many probably have nothing to do with the modem or the network.
If, on the other hand, you call them up and say, "My upstream power level is 53dBmV", "My downstream signal to noise ratio is 25dB", or "My downstream power level is -15.5dBmV", you won't have to go through the diagnostics.
When my upstream power level was too high (usually referred to as the modem "shouting"), I went on the support chat and told them exactly that. I was asked if the cables were tight. I said yes. The agent scheduled a technician visit, the technician came, and he put his signal analyzer on the line. Result? It appears that the line is fine, and my 2-year-old SB5100 decided to screw itself. Next step? I'm going to rent a modem from Comcast (total time: approximately 5 minutes to drop by the local office) for $3/mo and see if the problem goes away.
Look, I don't like transfer caps. But this cap isn't really anything new. Now they're being explicit about something that they (and most ISPs) have been doing for a long time. My only concern is that in 5 years, 250GB will look woefully inadequate.
No, Java dominates in some fields (enterprise applications) and is hardly used in others.
At the high-end, Java is facing serious competition from ASP.net. At the low-end, PHP continues to be hugely popular, along with newer frameworks like Rails.
Java's problem is that it's a pain in the ass. PHP is dead-simple to install and configure on Linux, which is partly why it's so popular with small websites. And ASP.net integrates extremely well with Microsoft environments (e.g. Windows Server, SQL Server, AD).
20Mbps? Are they kidding me?
PyCon 2008 used a 45Mbps DS3.
And, then, that's nothing compared to SCinet
These teams only work because they are rare. They are easy to exploit if you are at all decent at arenas.
Yes, the nukes hit hard. But these teams are just too easy to CC, too easy to unsync, and too easy to exploit.
These teams are NOT hard to beat. We beat one on my under-geared, 1400 rated screw-around 5v5 team.
Line of sight is absolutely essential in arenas. Anyone who is decent understands how exploit it, and it's extremely easy to do with macroed teams.
All it takes is a well-timed psychic scream and all of the macros go out the window. Macros stop working when you get out of follow range.
No, they didn't. It's called the flat earth myth.
Uh, yeah? That's the whole point of Science. Scientists try to create theories that best fit the available data. More importantly, they are always looking for new evidence which will either corroborate or contradict their theories.
You know, I think that SUVs suck. They're hard to park, they make it difficult for other drivers to see, they increase the risks to people driving smaller vehicles, and, of course, they get terrible fuel economy.
But as for SUVs being "death traps", you're just plain wrong.
Take a look at the IIHS ratings:
http://www.iihs.org/ratings/default.aspx
Of the 38 vehicles that are "Top Safety Picks" (the highest rating), 20 are SUVs. That's more than half. Meanwhile, there's exactly one small car that recieves the saem result, and the IIHS notes that larger vehicles do better, assuming that the ratings are equal.
Most SUVs don't use body-on-frame construction, and are instead based on car platforms.
So, yeah, maybe I'm a "sucker" for relying on crash test data and fatality statistics.
Pretending that every person who drives an SUV is somehow deluded or evil probably isn't going to get us anywhere. Making up bullshit certainly isn't.
Vista 64 runs damn fast on my system.
ThinkPad T61
Core 2 Duo 2.0GHz
4GB DDR2
Hitachi 7k200 disk
NV Quadro NVS 140m
This is a standard, run of the mill business notebook. It has 4GB of memory, but memory is really, really dirt cheap now. It ran fine before I upgraded it to 4GB, too.
Yes, because segregation, colonial oppression, and an unjust war are totally the same thing as a company making software that you don't like.
I don't like Apple's policies with software on the iPhone either. Solution? Don't buy one. There's always OpenMoko, Android, Symbian, BlackBerry, and, yes, even WinMo.
So, we should call it GNU/Linux/Qt/KDE/MoFo/OOo? Because the office suite, desktop environment, UI toolkit, and web browser is probably much more visible to the user than the GNU utilities, and arguably just as important.
I don't know what you're trying to prove. For me, the first link for "getfirfox" is the MoFo/Google getfirefox.net. The first link for "Linux is linux.com. And the first link for "Open Office" is OpenOffice.org.
Now if you want to argue that the "sponsored links" are crap, I can't help but agree. But Google has the exact same problem.
Just FYI, Duplo is a Lego product. They are also compatible with Lego bricks.
Uh, you mean like 1997? GSM is newer here than it is in Europe, but it's hardly "new".
This used to be the case, but it isn't anymore. There are lots of minor regional GSM carriers (e.g. Union Wireless in Wyoming), and you can roam for free, so GSM coverage isn't a whole lot different from CDMA2000 coverage.
I'll have to remember that the next time I'm playing with my 3G iPhone.
If you think that this is how poker works at a professional level, you don't know very much about poker.
Tells are a small factor at a professional level.
Good players already have a firm understanding of the pot odds and expected value of a call.
The major problem with writing a good poker program is that it can't be exploitable. If the program is too "tight", an experienced human player will realize this and can always raise with trash (because the program will fold), with a minimal chance of getting caught. If the program is too "loose", the human player can play good hands far more aggressively, knowing that the program will call.
This is a very general example. In reality, poker strategy is far more nuanced. But the basic problem that computers face is not being predictable. And, no, playing randomly doesn't help - it merely substitutes poor play for predictable play.