You're geeks right, so budget for every little thing you can think of (haircuts, petrol, emergencies... everything and I mean everything), put an estimate of the weekly / fortnightly total in a database / spreadsheet. Also include say $50 per week each to do what ever you want with.
If you can't agree to purchase something and budget for it together, you can still save some of your own allowance.
You should be able to automate a work around at the application layer. Randomly generate a few domain queries, if you don't get any NXDOMAIN responses, and instead get a single IP back, blacklist that IP... But I agree, this breaking of DNS is abhorrent and should be fought with everything we have.
Can you set up a connection specific DNS suffix? So that if you try to resolve internalmail, it will only try internalmail.company.com on the VPN DNS Server?
You could build a resolver send a DNS request for say 10 random 10-15 character domain names when it starts up and black list any IP addresses that are returned more than once (just on the off chance that one of those random addresses collided with a real one). But still, this is stupid. If you want to put training wheels on an internet connection and sell it as a feature, force the user to visit a config page once when they sign up via say a transparent proxy, giving one place to go to turn all that crap off.
Mainstream economics has certainly failed. This crisis should teach us that there should be some hard and solid boundaries that the economy can operate within. One big problem however is that a stable economy is de-stabilising. The more it looks like everything is rosy, the more we drop our guard and the bigger the risks we take. And the harder the fall will be when there is a systematic failure like the "sub-prime crisis" that finally broke the camels back.
Even quicker and simpler if you can swap the keyboard with a spare of the same model. I'd probably program it to capture the first N keys pressed after powering on. That way you should get the users login username / password.
Wave doesn't have to directly generate a profit to be useful for google. If they can make it harder for their competitors to generate profit in their key market segments, they still win. See this post to an earlier Wave article from a google employee.
This isn't about google making money. It's about taking something their competitors are making huge profits from and reducing marginal profit of these services to zero by turning it into a commodity. See this post to an earlier Wave article from a google employee.
While they may have listed a dozen potential vulnerabilities that *might* be used to construct their doomsday senario, how in the hell is an evil vilian going to test each exploit and assemble their master plan without the other side catching on and plugging up these holes? All this l337 haxxor scaremongoring is waaay overblown.
FedEx has a whole bunch of people whose only job is to look at scanned images of labels and type in the actual address when the machines fail to read them.
Here's a thought, do you think you could crowd source some of this with web based turing tests ala re-captcha?
My understanding of "why we are here" is based on God's desire for a family of autonomous and willing people.
He could have built completely predictable robots, but the moment he turned them on he could calculate exactly what they would do for the rest of their existance. He could have made his existance unavoidable, but if we could never choose to ignore his presense would we really be willing?
So instead we are left with a world where a few bad apples can make life unbearable for everyone they come in contact with. Where the biggest reward that has been promised must be taken on faith. Where the position and momentum of a particle cannot be accurately determined, a universe based on randomness and uncertainty. A universe where even an omnipotent God cannot pre-compute the outcome, though the outcome would still be known to him.
Now I don't believe that God depends on our involvement to tell everyone about him. I think he's perfectly capable of ensuring that everyone is given enough clues to his existance that they can make up their own mind. In fact I would go as far as saying there is no argument I can give that would force you to believe in the existance of a god. No argument that could back you into an intellectual corner leaving you no escape route. I believe the existance of such an argument would go against the very nature of this universe that God may or may not have created.
Pffft, I've been going to LAN parties for years, heck I used to organise them. There were some initial teething problems with steam, CSS, TF2 etc requiring an internet connection to play, and everyone rocking up needing updates. But these days? Nah, needing an internet connection seems normal now.
Re:C is the only starting language
on
Hello World!
·
· Score: 1
There were a bunch of programming students at a course I was attending who kept seeing the Borland copyright message.
But then if you allow trivially simple passwords, but have thousands of login names in your system, then you pick a single common password and try it with a dictionary attack against every user instead...
And then you come back 2 months later, guess your password or they send you an email (which is of course unencrypted, but then so was the login prompt) and force you to change it to something else that you wont remember.
Another thing that was certainly missing from my own CS curriculum (admittedly 10 years ago) was practical experience with using source control systems. I'm not trying to suggest that using source control or SQL should require an extra semester subject, just that the way contrived assignments are designed should be similar to the way real world applications are written.
It's not learning about SQL I have an issue with, I just think CS grads should have more exposure and practice working with it.
A CS grad get's quite a bit of practice coding in C / Java / etc. I just think SQL is a very useful language that a programmer could use a lot more practice with. I think a reasonable compromise would be to teach the basics of SQL early in a CS course and use databases for source data in the smaller assignments that students must complete.
From my own point of view, writing code to read and write to files is a very small part of what I do. But I'd say about half the job of any business data entry / reporting application / web site is working with databases and sql.
Personally, I'd push SQL a fair way up the list. I'd introduce it slowly though along side other things that you are teaching. Starting with Java, use sql to serialise the state of objects, but provide most of the code to do this for any assignments. For example you could supply a database with the raw data that must be sorted or otherwise analysed instead of supplying flat text files.
If there is a single language that is not taught enough for real world experience, it's SQL. Just about any business programming job is going to involve storing and reporting on data. While a CS degree is going to give you a basic introduction to SQL, I feel that SQL should be introduced earlier and worked into more of the assignments you are asked to write.
But it's the one job where he doesn't have to see kids all year round. And even on the one night when he has to go around and give them something, they have to be asleep. If you ask me santa can't stand kids.
Slashdot Mirror
3 - drop the "my money" and "your money" bull.
You're geeks right, so budget for every little thing you can think of (haircuts, petrol, emergencies... everything and I mean everything), put an estimate of the weekly / fortnightly total in a database / spreadsheet. Also include say $50 per week each to do what ever you want with.
If you can't agree to purchase something and budget for it together, you can still save some of your own allowance.
You should be able to automate a work around at the application layer. Randomly generate a few domain queries, if you don't get any NXDOMAIN responses, and instead get a single IP back, blacklist that IP... But I agree, this breaking of DNS is abhorrent and should be fought with everything we have.
Can you set up a connection specific DNS suffix? So that if you try to resolve internalmail, it will only try internalmail.company.com on the VPN DNS Server?
You could build a resolver send a DNS request for say 10 random 10-15 character domain names when it starts up and black list any IP addresses that are returned more than once (just on the off chance that one of those random addresses collided with a real one). But still, this is stupid. If you want to put training wheels on an internet connection and sell it as a feature, force the user to visit a config page once when they sign up via say a transparent proxy, giving one place to go to turn all that crap off.
Mainstream economics has certainly failed. This crisis should teach us that there should be some hard and solid boundaries that the economy can operate within. One big problem however is that a stable economy is de-stabilising. The more it looks like everything is rosy, the more we drop our guard and the bigger the risks we take. And the harder the fall will be when there is a systematic failure like the "sub-prime crisis" that finally broke the camels back.
Even quicker and simpler if you can swap the keyboard with a spare of the same model. I'd probably program it to capture the first N keys pressed after powering on. That way you should get the users login username / password.
Wave doesn't have to directly generate a profit to be useful for google. If they can make it harder for their competitors to generate profit in their key market segments, they still win. See this post to an earlier Wave article from a google employee.
This isn't about google making money. It's about taking something their competitors are making huge profits from and reducing marginal profit of these services to zero by turning it into a commodity. See this post to an earlier Wave article from a google employee.
... they saw a young man dressed in a white robe sitting on the right side ...
... when suddenly two men dressed in white stood beside them ...
While they may have listed a dozen potential vulnerabilities that *might* be used to construct their doomsday senario, how in the hell is an evil vilian going to test each exploit and assemble their master plan without the other side catching on and plugging up these holes? All this l337 haxxor scaremongoring is waaay overblown.
If you don't have the time to spare, there's an abridged version.
Then you better be sure to stay off Wikipedia, Mr. Avenaim.
Too Late. It even looks like he has uploaded his own portrait to Wikimedia Commons under a CC license.
But still the bag or container the mail is sitting in will be scanned and that should be counted the same.
FedEx has a whole bunch of people whose only job is to look at scanned images of labels and type in the actual address when the machines fail to read them.
Here's a thought, do you think you could crowd source some of this with web based turing tests ala re-captcha?
My understanding of "why we are here" is based on God's desire for a family of autonomous and willing people.
He could have built completely predictable robots, but the moment he turned them on he could calculate exactly what they would do for the rest of their existance. He could have made his existance unavoidable, but if we could never choose to ignore his presense would we really be willing?
So instead we are left with a world where a few bad apples can make life unbearable for everyone they come in contact with. Where the biggest reward that has been promised must be taken on faith. Where the position and momentum of a particle cannot be accurately determined, a universe based on randomness and uncertainty. A universe where even an omnipotent God cannot pre-compute the outcome, though the outcome would still be known to him.
Now I don't believe that God depends on our involvement to tell everyone about him. I think he's perfectly capable of ensuring that everyone is given enough clues to his existance that they can make up their own mind. In fact I would go as far as saying there is no argument I can give that would force you to believe in the existance of a god. No argument that could back you into an intellectual corner leaving you no escape route. I believe the existance of such an argument would go against the very nature of this universe that God may or may not have created.
Pffft, I've been going to LAN parties for years, heck I used to organise them. There were some initial teething problems with steam, CSS, TF2 etc requiring an internet connection to play, and everyone rocking up needing updates. But these days? Nah, needing an internet connection seems normal now.
There were a bunch of programming students at a course I was attending who kept seeing the Borland copyright message.
char c;
printf("%s", c);
But then if you allow trivially simple passwords, but have thousands of login names in your system, then you pick a single common password and try it with a dictionary attack against every user instead...
And then you come back 2 months later, guess your password or they send you an email (which is of course unencrypted, but then so was the login prompt) and force you to change it to something else that you wont remember.
Another thing that was certainly missing from my own CS curriculum (admittedly 10 years ago) was practical experience with using source control systems. I'm not trying to suggest that using source control or SQL should require an extra semester subject, just that the way contrived assignments are designed should be similar to the way real world applications are written.
It's not learning about SQL I have an issue with, I just think CS grads should have more exposure and practice working with it.
A CS grad get's quite a bit of practice coding in C / Java / etc. I just think SQL is a very useful language that a programmer could use a lot more practice with. I think a reasonable compromise would be to teach the basics of SQL early in a CS course and use databases for source data in the smaller assignments that students must complete.
From my own point of view, writing code to read and write to files is a very small part of what I do. But I'd say about half the job of any business data entry / reporting application / web site is working with databases and sql.
Personally, I'd push SQL a fair way up the list. I'd introduce it slowly though along side other things that you are teaching. Starting with Java, use sql to serialise the state of objects, but provide most of the code to do this for any assignments. For example you could supply a database with the raw data that must be sorted or otherwise analysed instead of supplying flat text files.
If there is a single language that is not taught enough for real world experience, it's SQL. Just about any business programming job is going to involve storing and reporting on data. While a CS degree is going to give you a basic introduction to SQL, I feel that SQL should be introduced earlier and worked into more of the assignments you are asked to write.
But it's the one job where he doesn't have to see kids all year round. And even on the one night when he has to go around and give them something, they have to be asleep. If you ask me santa can't stand kids.
You might find this kind of test useful;
if (dnsDomainIs(host, ".local") || isPlainHostName(host)) { return "DIRECT"; }
Assuming you always access "local" machines from a short list of domain names.