For some reason it wasn't until I read your post that I realized that despite all the claims of RSA encryption in Skype the keys are still on Skype's servers, otherwise end-lusers would have to keep track of a key file which is just begging for disaster. So from a security standpoint, the entire protocol is just one big obfuscation mechanism. Back door? More like "it was never secure to begin with".
The goal of transactions is to make the window of data loss on the database's side infinitesimally small. PostgreSQL's default configuration will not tell you it has committed a transaction until it can guarantee that nothing short of lying hardware will cause that transaction to be lost. Hence, it's up to the software to handle errors (like the database sever disappearing) by informing the user that their action failed, or to put the work aside until the database comes back. That said, the probability of losing data is very very small but still not zero (primarily due to lying hardware like RAID controllers), so you don't want to take any chances. Unless you're running MySQL, a few minutes is all you need to cleanly stop the database and shut down.
Boy am I glad someone had enough sense to respond to a reasonable claim with ad-hominem attacks! I was getting worried! It is by no means a foregone conclusion that global warming is a man-made phenomenon. That's not how science works. Even laws of nature are open to challenges brought about by new evidence. This entire climate change debacle is just a political freak show, with both sides calling the other names and insulting the people instead of just refuting the hypotheses. Tree-huggers? Deniers? Please, leave this to people who know what they're talking about.
Perhaps, but I'm puzzled too -- the least the submitter could have done is allocated half a sentence to informing the blissfully ignorant such as ourselves.
This problem has been solved probably thousands of different ways, all subtly different. The odds of any particular solution resembling another solution by sheer chance are rather high.
YAML and JSON are text-based formats intended for human readability.
Actually, JSON's human-readability is (or originally was) secondary to the fact that it is JavaScript so you can just paste it into the output of your dynamic web pages to make data available to scripts running on the page. Naturally, JavaScript is a programming language, and programming languages are supposed to be human readable (or at least more human readable than machine code; I can't speak more highly of some languages). This doesn't detract from the fact that they are legible, but it's a different class than XML and YAML which are originally designed to be manageable by mere mortals, particularly YAML.
That 6 mbit or 10 mbit pipe isn't designed to be used at full capacity 24/7 by each subscriber, it's designed to be a shared service between multiple people, splitting the cost of the full 6 mbit or 10 mbit pipe between them.
Which is why I think that ISPs should just advertise clearly how much you can use at full speed. Say 6mbit burstable and 100kbit sustained, and enforce that policy fairly, and I'll use your service over the hand-wavy "6mbit when we feel like it" that everyone sells today.
That's what DNS was made for in the first place. You don't type in 105.195.75.18 very often either, do you? The only people who memorize IP addresses (v4 or v6) are "network people"
More generally, the wireframe is not copyrightable, but the thing being modelled is. Same goes for MP3 files - a stream of bits is not a work of art, but when you run it through a MPEG decoder and a DAC, you get a song. It's the concept that counts, not the implementation.
This article is presented as if most sysadmins are a bunch of non-ethical geeks but please keep in mind that at first this was a US study. Sorry, sometimes we Americans forget that you ferrigners are perfect, especially in ethical matters and at not being geeky.
So how can low minority (even by US standards) set the tone for the market as a whole? Take a statistics class and find out.
I'm somewhat surprised that Google doesn't have a manpage service already. They could even collate it into different *nix flavors and let you see what df looks like on Solaris, etc.
Instead of bitching about a spider deleting all your files, how about programming the website to not use GET requests to modify data, let alone allow them to log in without credentials in the first place? GET is not supposed to modify data. POST, PUT, and DELETE modify data. Spiders don't POST, PUT, or DELETE -- they GET.
On the other hand, red is lower energy and preserves night vision more, making it less noticeable in dark places like movie theaters when you're not actively looking for it.
I had encoding acceleration in mind when I first saw it. It would probably do quite well, but I'm not spending $1500 on hobbyist hardware in a field I know nothing about just so I can spend a few days trying to write a h264 accelerator and give up. I might, however, consider the spartan 3 developer kit (a mere $350... heh). Then again, maybe I should learn to actually program these things first.
The fact is, the drivers are very nearly more important than the GPU. The GPU only does what you tell it to, and only the drivers know how to translate "draw this list of polygons" into the specific calculations that the GPU needs to execute in order to get the pixels into the buffer and onto your screen. If they open source their drivers, there isn't much left aside from a maze of twisty pipelines.
Of course, this is ideal if open source is their goal: anyone can write new code to get the GPU to do something completely different and very cool or useful. See for example the GPU version of folding@home (windows only), which uses NVidia GPUs to crunch numbers (though I believe it's done by adapting a shader API provided by the existing drivers), or even the PS3 version, as the PS3's SPEs are similar in nature to the average GPU in that they are specialized number-crunching units, unlike a CPU which is a generic logic unit designed to do a wide variety of things.
And even if they wanted to open source their drivers, both NVidia and ATI are beholden to various companies from which they have licensed technologies that are incorporated in the drivers, and so they would be violating contract by exposing it. It's quite likely that NVidia doesn't even have the source code to some of the things they link their drivers against in the first place.
Better yet - MAC address are only useful identifiers if you're either on the user's computer (frequently used to ban people from online games) or on their LAN (e.g. wireless router access control). As soon as the packet hits a router, the originating MAC changes to that of the router (and the target MAC to that of the next hop), because it's too low level to deal with routing. So it's entirely useless for snooping!
Incorrect. The installer merely compiles a wrapper around the blob in order to interface it with your kernel. The installer is not the "blob"; you can extract the (clearly unencrypted) tarball from it, as is done in many distributions to automate the build.
And Broadcom is everywhere. Especially in my laptop, where the disgusting heap of silicon they call a wireless chipset can't even connect to an AP 15 feet away without me reloading the firmware 8 times and bouncing the interface as if it were a broken VGA cable.
Slashdot Mirror
For some reason it wasn't until I read your post that I realized that despite all the claims of RSA encryption in Skype the keys are still on Skype's servers, otherwise end-lusers would have to keep track of a key file which is just begging for disaster. So from a security standpoint, the entire protocol is just one big obfuscation mechanism. Back door? More like "it was never secure to begin with".
The goal of transactions is to make the window of data loss on the database's side infinitesimally small. PostgreSQL's default configuration will not tell you it has committed a transaction until it can guarantee that nothing short of lying hardware will cause that transaction to be lost. Hence, it's up to the software to handle errors (like the database sever disappearing) by informing the user that their action failed, or to put the work aside until the database comes back. That said, the probability of losing data is very very small but still not zero (primarily due to lying hardware like RAID controllers), so you don't want to take any chances. Unless you're running MySQL, a few minutes is all you need to cleanly stop the database and shut down.
Boy am I glad someone had enough sense to respond to a reasonable claim with ad-hominem attacks! I was getting worried! It is by no means a foregone conclusion that global warming is a man-made phenomenon. That's not how science works. Even laws of nature are open to challenges brought about by new evidence. This entire climate change debacle is just a political freak show, with both sides calling the other names and insulting the people instead of just refuting the hypotheses. Tree-huggers? Deniers? Please, leave this to people who know what they're talking about.
Perhaps, but I'm puzzled too -- the least the submitter could have done is allocated half a sentence to informing the blissfully ignorant such as ourselves.
This problem has been solved probably thousands of different ways, all subtly different. The odds of any particular solution resembling another solution by sheer chance are rather high.
YAML and JSON are text-based formats intended for human readability.
Actually, JSON's human-readability is (or originally was) secondary to the fact that it is JavaScript so you can just paste it into the output of your dynamic web pages to make data available to scripts running on the page. Naturally, JavaScript is a programming language, and programming languages are supposed to be human readable (or at least more human readable than machine code; I can't speak more highly of some languages). This doesn't detract from the fact that they are legible, but it's a different class than XML and YAML which are originally designed to be manageable by mere mortals, particularly YAML.
As mentioned in the link, thunder is a much bigger problem. I demand that PETA immediately notify God to cease and desist from all stormy weather.
Can't think of something that uses GTK or I'd continue the fun!
That 6 mbit or 10 mbit pipe isn't designed to be used at full capacity 24/7 by each subscriber, it's designed to be a shared service between multiple people, splitting the cost of the full 6 mbit or 10 mbit pipe between them.
Which is why I think that ISPs should just advertise clearly how much you can use at full speed. Say 6mbit burstable and 100kbit sustained, and enforce that policy fairly, and I'll use your service over the hand-wavy "6mbit when we feel like it" that everyone sells today.
That's what DNS was made for in the first place. You don't type in 105.195.75.18 very often either, do you? The only people who memorize IP addresses (v4 or v6) are "network people"
More generally, the wireframe is not copyrightable, but the thing being modelled is. Same goes for MP3 files - a stream of bits is not a work of art, but when you run it through a MPEG decoder and a DAC, you get a song. It's the concept that counts, not the implementation.
I'm somewhat surprised that Google doesn't have a manpage service already. They could even collate it into different *nix flavors and let you see what df looks like on Solaris, etc.
...any less relevant?
Instead of bitching about a spider deleting all your files, how about programming the website to not use GET requests to modify data, let alone allow them to log in without credentials in the first place? GET is not supposed to modify data. POST, PUT, and DELETE modify data. Spiders don't POST, PUT, or DELETE -- they GET.
On the other hand, red is lower energy and preserves night vision more, making it less noticeable in dark places like movie theaters when you're not actively looking for it.
Only the terrorists need locks. Peaceful citizens have nothing to hide.
No no no... I'm putting my foot down. No pedestrian pun threads on slashdot!
I had encoding acceleration in mind when I first saw it. It would probably do quite well, but I'm not spending $1500 on hobbyist hardware in a field I know nothing about just so I can spend a few days trying to write a h264 accelerator and give up. I might, however, consider the spartan 3 developer kit (a mere $350... heh). Then again, maybe I should learn to actually program these things first.
Do they come with spare exclamation points, too?
The fact is, the drivers are very nearly more important than the GPU. The GPU only does what you tell it to, and only the drivers know how to translate "draw this list of polygons" into the specific calculations that the GPU needs to execute in order to get the pixels into the buffer and onto your screen. If they open source their drivers, there isn't much left aside from a maze of twisty pipelines.
Of course, this is ideal if open source is their goal: anyone can write new code to get the GPU to do something completely different and very cool or useful. See for example the GPU version of folding@home (windows only), which uses NVidia GPUs to crunch numbers (though I believe it's done by adapting a shader API provided by the existing drivers), or even the PS3 version, as the PS3's SPEs are similar in nature to the average GPU in that they are specialized number-crunching units, unlike a CPU which is a generic logic unit designed to do a wide variety of things.
And even if they wanted to open source their drivers, both NVidia and ATI are beholden to various companies from which they have licensed technologies that are incorporated in the drivers, and so they would be violating contract by exposing it. It's quite likely that NVidia doesn't even have the source code to some of the things they link their drivers against in the first place.
-1 Depressing Smiley
Better yet - MAC address are only useful identifiers if you're either on the user's computer (frequently used to ban people from online games) or on their LAN (e.g. wireless router access control). As soon as the packet hits a router, the originating MAC changes to that of the router (and the target MAC to that of the next hop), because it's too low level to deal with routing. So it's entirely useless for snooping!
Incorrect. The installer merely compiles a wrapper around the blob in order to interface it with your kernel. The installer is not the "blob"; you can extract the (clearly unencrypted) tarball from it, as is done in many distributions to automate the build.