The last couple of days I've been seeing layout bugs (like right now one of the sidebar boxes is blocking the "Load More Comments" button) and links to stories getting disabled a few seconds after loading the front page.
Has Dice decided to make classic the new beta or something?
Whats in that section is basically a catalogue of what we already know the US government is doing, and an extra one at the bottom about Governments adding a man in the middle that gives them access to everything.
They say its a list of everything that they promise to resist, but we know from Snowdon's work and other public disclosure that its all actually happening.
Their Government Data Requests Principles is a catalogue of the things they're forced to do that they don't like. The last one on that list would seem to apply to China (but I wouldn't be at all surprised if they've been forced to bend over on this one by US and other Western countries as well).
The timing is suspicious, given the mail they just sent out to all their users updating the TOS with an additional "Government Data Request Principles" section.
Once upon a time ABS was an exotic tech used only on aircraft. I was impressed when they became a car option.
In other words, ABS software (and hardware) was very expensive to develop, and only the development budgets of airliners was large enough to cover its development. Once developed, the companies that developed it realized that adapting it for automotive use would be within the budget of luxury car makers, and once it was working there, it became very cheap to adapt for standard cars, as the differences are very minor (in fact it is basically a case of the luxury car makers funding continued improvements, and standard cars getting the previous generation that already has its development paid for).
Self proclaimed masters of the trade have no place in safety critical software systems. Can you guarantee that the coder who will be maintaining your code 10 years from now will also be a "master of the trade"?
MISRA C, which is a mandatory coding standard across pretty much all the automotive industry, does outlaw recursion. So I find this speculation on the cause to be very unlikely, and is just lawyers bringing in "software experts" to speculate. If you want to speculate, there are many other potential software bug causes as well. Some of them would even pass MISRA C coding checks, and not be easily detectable by static analysis.
~/passwords.txt.gpg contains all my important passwords, I have copies of it everywhere. For non-important passwords (like Slashdot logon), I just use a password I can remember, which is the same or minor variants based on the site's password limitations.
Google's fight with Sun was over the APIs essential to the language (java.*, javax.*). The case did not cover com.sun.*, which would be the equivalent of the Google APIs.
To fix the bug in older versions, you'd have to fork the Android API, as the patch involved an API change which Google themselves have not backported to older versions.
The page I was looking at was more like "Bacon bacon bacon beacon bacon pork. Beacon bacon pork bacon bacon beacon.... ad nauseum, the lines morphing over time but the repitition being constant. It was illustrated with a half dozen naked cherubs, but I can't seem to find it now (was on the first page of a Google image search this morning). Looking at other pages, there seem to be many pages with patterns in the text (same word not quite lining up vertically the entire way up the page), which make it look like it is not natural prose. As for the script, it has more in common with cursive Latin script than Burmese or other Asian scripts.
Looking at a random page from the book, the manuscript is clearly nonsensical, perhaps someone's attempt to leave a coded riddle, but certainly no ancient record of exotic flora or other scientific knowledge. The same "word" is repeated four or five times on each line, with only one different word appearing on the line, often differing from the repeated word by only one "letter", at other times looking like it could be an English word in barely legible script.
How do you adjust the temperature without looking at the screen to see where it is now, and where you want it to go? How do you change the air direction from front defroster to foot vents without looking at the screen?
Audio or haptic feedback. The same as you do when you use a knob without looking.
However, in the other car, for some reason the designers chose to use a physical knob with a lighted dot [images-amazon.com] to show where the knob is pointed, so you still have to look at it to see what setting it's on.
Why do you care what setting it is on? Either you want it cooler or warmer, and you turn the knob in the appropriate direction by about how much you think you need to. Swiping gestures are no different in this respect.
In 2G & 3G networks, phones got NAT'd 10.x.x.x IP addresses. The downside being no listening services accessible to the internet, even if you wanted to run a web server, or SSHd on your phone.
On the upside (for the phone companies), NAT wrecks havoc with SIP.
I think it comes down to understanding and ability... not to mention capabilities of certain hardware. It's relatively easy for an engineer to keep a series of IPv4 address blocks, and routes in memory... not so much with IPv6.
It should be easier for engineers to deal with IPv6 rollout. Instead of separate IPv4 blocks which they've been allocated over time as the organization expanded its network use, they can get a single IPv6 block that is big enough for their organization's needs now and for the foreseeable future and beyond. They can then subdivide that logically to suit their needs. When properly planned, routing becomes based on simple mathematical relationships, just as was the original intention behind IPv4 before it grew beyond 4 layers of routing.
Basically the problem now, is that one of the grownups in charge of network operations at a major telco needs to grow some balls and be the first to throw the switch. Pretty much every major provider announced that they will be ready for IPv6 by two or three years ago. They are just scared that something unknown might hit them if they throw the switch, and want someone else to be the first. Several networks in Japan have done it already, and probably Korea and China as well, but language barriers get in the way of letting US and European network managers know that their fear of the unknown is unfounded.
I think the GP was talking about the IPv6 case. The typical case is that your carrier will assign your router a/64 block, so it can assign public addresses from that block to any devices within its network.
This is also a tremendous security advantage: it reduces the exposed attack surface for script kiddies and casual network scanners
Actually the converse is true. Instead of wasting their time scanning a vast address-space which is 99% empty, script kiddies and casual network scanners get a hit on pretty much every IP address and port combination they try.
This is the age of firewalls and all that (and even NAT provides a very basic level of firewalling).
NAT as a firewall is completely ineffective. Once you've solved the source routing and other vulnerabilities and secured your NAT firewall, you have a firewall that is perfectly capable of securing a network of devices with public IP addresses.
On the other hand, whatismyip.com tells me I have a public IP address with no proxy detected. You need to look on your actual device for the IP address you are being assigned. Carrier grade NAT is transparent to most of the websites that claim to tell you your IP address.
Slashdot Mirror
The last couple of days I've been seeing layout bugs (like right now one of the sidebar boxes is blocking the "Load More Comments" button) and links to stories getting disabled a few seconds after loading the front page.
Has Dice decided to make classic the new beta or something?
Whats in that section is basically a catalogue of what we already know the US government is doing, and an extra one at the bottom about Governments adding a man in the middle that gives them access to everything.
They say its a list of everything that they promise to resist, but we know from Snowdon's work and other public disclosure that its all actually happening.
It seems like there must be a flaw in your logic somewhere, but I can't quite spot what it is.
Their Government Data Requests Principles is a catalogue of the things they're forced to do that they don't like. The last one on that list would seem to apply to China (but I wouldn't be at all surprised if they've been forced to bend over on this one by US and other Western countries as well).
The timing is suspicious, given the mail they just sent out to all their users updating the TOS with an additional "Government Data Request Principles" section.
In other words, ABS software (and hardware) was very expensive to develop, and only the development budgets of airliners was large enough to cover its development. Once developed, the companies that developed it realized that adapting it for automotive use would be within the budget of luxury car makers, and once it was working there, it became very cheap to adapt for standard cars, as the differences are very minor (in fact it is basically a case of the luxury car makers funding continued improvements, and standard cars getting the previous generation that already has its development paid for).
And those idiots would be right. Show me a car that has a faster 0-60 time than its best 60-0 time.
Self proclaimed masters of the trade have no place in safety critical software systems. Can you guarantee that the coder who will be maintaining your code 10 years from now will also be a "master of the trade"?
MISRA C, which is a mandatory coding standard across pretty much all the automotive industry, does outlaw recursion. So I find this speculation on the cause to be very unlikely, and is just lawyers bringing in "software experts" to speculate. If you want to speculate, there are many other potential software bug causes as well. Some of them would even pass MISRA C coding checks, and not be easily detectable by static analysis.
Yes, aerospace software has solved the problem of software bugs. We should all be following its perfect example. </sarcasm>
~/passwords.txt.gpg contains all my important passwords, I have copies of it everywhere. For non-important passwords (like Slashdot logon), I just use a password I can remember, which is the same or minor variants based on the site's password limitations.
Google's fight with Sun was over the APIs essential to the language (java.*, javax.*). The case did not cover com.sun.*, which would be the equivalent of the Google APIs.
To fix the bug in older versions, you'd have to fork the Android API, as the patch involved an API change which Google themselves have not backported to older versions.
The page I was looking at was more like "Bacon bacon bacon beacon bacon pork. Beacon bacon pork bacon bacon beacon. ... ad nauseum, the lines morphing over time but the repitition being constant. It was illustrated with a half dozen naked cherubs, but I can't seem to find it now (was on the first page of a Google image search this morning). Looking at other pages, there seem to be many pages with patterns in the text (same word not quite lining up vertically the entire way up the page), which make it look like it is not natural prose. As for the script, it has more in common with cursive Latin script than Burmese or other Asian scripts.
Looking at a random page from the book, the manuscript is clearly nonsensical, perhaps someone's attempt to leave a coded riddle, but certainly no ancient record of exotic flora or other scientific knowledge. The same "word" is repeated four or five times on each line, with only one different word appearing on the line, often differing from the repeated word by only one "letter", at other times looking like it could be an English word in barely legible script.
Audio or haptic feedback. The same as you do when you use a knob without looking.
Why do you care what setting it is on? Either you want it cooler or warmer, and you turn the knob in the appropriate direction by about how much you think you need to. Swiping gestures are no different in this respect.
The point of this is that you don't need to look at it.
On the upside (for the phone companies), NAT wrecks havoc with SIP.
It should be easier for engineers to deal with IPv6 rollout. Instead of separate IPv4 blocks which they've been allocated over time as the organization expanded its network use, they can get a single IPv6 block that is big enough for their organization's needs now and for the foreseeable future and beyond. They can then subdivide that logically to suit their needs. When properly planned, routing becomes based on simple mathematical relationships, just as was the original intention behind IPv4 before it grew beyond 4 layers of routing.
Basically the problem now, is that one of the grownups in charge of network operations at a major telco needs to grow some balls and be the first to throw the switch. Pretty much every major provider announced that they will be ready for IPv6 by two or three years ago. They are just scared that something unknown might hit them if they throw the switch, and want someone else to be the first. Several networks in Japan have done it already, and probably Korea and China as well, but language barriers get in the way of letting US and European network managers know that their fear of the unknown is unfounded.
I think the GP was talking about the IPv6 case. The typical case is that your carrier will assign your router a /64 block, so it can assign public addresses from that block to any devices within its network.
Actually the converse is true. Instead of wasting their time scanning a vast address-space which is 99% empty, script kiddies and casual network scanners get a hit on pretty much every IP address and port combination they try.
NAT as a firewall is completely ineffective. Once you've solved the source routing and other vulnerabilities and secured your NAT firewall, you have a firewall that is perfectly capable of securing a network of devices with public IP addresses.
On the other hand, whatismyip.com tells me I have a public IP address with no proxy detected. You need to look on your actual device for the IP address you are being assigned. Carrier grade NAT is transparent to most of the websites that claim to tell you your IP address.
Yours maybe. Mine is giving me only an IPv4 address in the 10.* range.