...the green bits are 30fps. Everything else, i.e about 2/3 of the planet, is 25fps. 25 does not go into 60. I suppose at a pinch it could be run at 24fps with the 120Hz timebase you suggested, but that's not exactly optimal...
The trouble is that your "2/3 of the planet" equates to about "10% of produced content". Besides, the people in the land of PAL have had to deal with 24 to 25 fps horse shit since the dawn of time, so they're used to it. And dropping 1 out of every 6 frames to go from 60 to 50 is much less offensive than the 24 to 30 shit we deal with now. And PAL itself is going down the toilet in favor of DVB, so there are no analog constraints even for broadcast signals that restrict anyone to 50 fps.
60 Hz (120 for 3D) for production would solve everything. Broadcast/cable/satellite can push it out whenever the fuck they please as long as they're using digital. 24 fps, 30 fps, 60 fps fit perfectly. 25 and 50 fps shit will have less distortion than anything that's ever been telecined. People can display it to the best of their TVs ability. And for NTSC shit (the vast majority of content) that PAL people want to watch, you could send the original frame rate shit to the PAL territories and have it display properly. No need to run a film at sped up at 25 fps or send video 5-in-6 decimated (30 to 25).
Huh? Most video is at 24 fps. Even if we generously triple that, we're nowhere near 120 fps. Hobbit 3D's highest encode was 48 fps which was considered super high quality, and most theaters were still at 24.
24 fps is trash.
30 fps is trash.
48 fps is trash too. If you want the Hobbit in decent 3D you need to display 96 fps. If you want to watch it on a fixed-refresh rate display (all modern consumer TVs and monitors) you're fucked. We just got 120 Hz displays which allow near-perfect display of 24 and 30 fps content. With the Hobbit in 2D you'd need a 240 Hz display to properly handle 24, 30, and 48 fps content. Want decent 3D? Now you need 480 Hz. The dipshit should have gone with 60 Hz. Then 120 Hz displays would display it just fine, even in 3D. The BluRay would display it just fine as well, though at a culled frame rate. Broadcasters would have plenty of options for stuffing the thing into their standard 60i streams or 60p streams as 2D or 3D.
I really just wish the fucking world would settle on 60 fps.
Either way, something that can brick your machine so easily with software shouldn't be soldered to the board.
UEFI isn't causing bricking any more than any BIOS chip in the past has. You may as well argue against memory controllers being integrated into CPUs or any northbridge/southbrdge chip being soldered onto a motherboard.
How can you trust what you can never see, or even know is there?
Thesis: Security requires trust.
You are not trusted to know these secrets, therefore you are not secured through their application.
The whole UEFI boondoggle is false security. Worse, this proves that it is vulnerability risk, sold under masquerade, as security.
UEFI is a replacement for BIOS. It has many features that let us deal with hardware that BIOS couldn't provide. UEFI is not a boondoggle, nor is it about security.
Amen to that. People don't realize the protocol is absolutely, 100% perfectly fraud-proof. It is designed to be impossible to forge a bad block or fake a transaction or gain ownership of coins you don't own. The only way to actually do it is to outprocess the entire rest of the network, which is impossible.
Unless honest participants in the network definitively control more than half of the computing power on the planet, it is at best impractical rather than impossible. Its not "absolutely, 100% perfectly fraud-proof".
It is actually 100% fraud-proof.
If someone seizes control of the network by exceeding 50% of the total computational power of the network (including their own), they introduces phony blocks in an attempt to double spend, they're forking the block chain. The honest miners will quickly see that certain hosts are accepting phony blocks and ignore them, and stick with their own, clean fork of the block chain.
There was an example of the block chain being forked a few weeks ago due to some bullshit about BerkeleyDB and 512 KB datagram sizes. The networked converged on one fork and kept on trucking.
If someone is simply double spending and saying "Yup, verified!" without forking the block chain, anyone can trace the transactions involved and call bullshit.
For an individual merchant accepting bitcoins, you can protect yourself from localized instances of this attack by simply waiting for more verifications. The only way to get fucked is by having someone control your network and preventing you from accessing legitimate nodes. If they're doing that, they can fuck you in so many other ways, such as telling customers to send payment to their wallet's address instead of yours.
I do this for ISP techs, too. Bridge the ethernet adapter, install Windows of some variety in a virtual machine. (Don't even bother activating or updating it, it's going away as soon as they leave.) Most of them don't give a crap that they're installing in a virtual machine if they even notice at all. Just stand around and shoo them away when the host OS's interface pops up briefly during the reboot process.
Why in the fuck would an ISP tech need to install anything on your computer?
And put it in its own separate guest network, which is logically isolated from your own stuff by a firewall, maybe run a print server too (people often want to print boarding passes)... As for funny looks, a browser is a browser and i've never had any problems giving someone a linux livecd, it has both firefox and chrome and most people are perfectly familiar with these applications.
Why go to the trouble of a separate network? The odds of even the most retarded of users inadvertently fucking anything beyond the one machine they're touching is absurdly low, unless you're running outdated shit on your network. Remote exploits are remote exploits, and you should protect each device regardless or whether or not you trust the rest of the network.
If someone is so fuck-up prone that you think your proper boxen could be fucked by some schlub lolcatting around on the same network, you should be more worried about them tripping in your house and suing you.
OK, I know it's April fools, but why would a packet traveling faster than the speed of light necessarily arrive before it is sent? Do bullets shot faster than the speed of sound arrive before the gun makes a sound? No, it just arrives before the sound does.
You shoot ur lazer beemz at an enemy ship. The enemy has a tachyon shield system that emits a field of tachyons devices that relay information back to the ship FTL. When the lazer enters the field, the tachyon shield system tells the enemy ship to power up its shields. The ship powers up its shields by energizing the tachyon device field and creating a barrier, stopping your lazer beemz. Whenever the tachyon device field is powered up or the shield takes a hit, some of the tachyon devices fly out FTL, reducing total shield capacity.
The end result is that you fire your lazer and soon after you see tachyons fly at you and then you see the flash of your lazer beemz impacting the tachyon shield. Makes sense.
A third ship (depending on its relative position and the speed of the the tachyons) could see the tacyons fly out, then see you fire the lazer, then see the lazer beemz impact, and wonder why the fuck you would fire ur lazer beems after they powered up their shields.
Okay, smarty. One quantum particle occupies 2 places in space at the same time (aka quantum entangled). You move them a lightyear apart then spin one. What happens to the "other" particle and when?
There is no causality when it's actually the same particle. The cause and effect are both that it is the same particle.
1: It's not the same particle. 2: Information is not transferred, you don't get to spin one, you can merely read the spin of one and instantly know the spin of the other.
Imaging flipping a coin. You look at it as it lays on your hand or on the ground. You see the top and see that it's heads. You instantly know that the bottom is tails.
The information of the bottom being tails didn't arrive faster than light. You discerned it to be the opposite of the top before the experiment, and you learned of the top's state without violating the speed of light by looking at it. If you entangle particles and know the relation of their spins and then send them far apart, you're doing the same thing. Absolutely no information is transferred FTL.
Key people from Wikileaks got visited by spooks and quickly changed their tune about how they felt about the leaks, and blamed everything on Assange and said they didn't agree with releasing thigs that could "harm" people, even though nothing ever released by Wikileaks has actually harmed anyone. They then started OpenLeaks, which is basically a useless copy of WikiLeaks that the government has control over.
Assange is still trapped in the Ecuadorean embassy. Until he dies, gets out, or they come and grab him, nothing of importance will happen with WikiLeaks.
1: Encrypt everything in software so the key nor a hash of it could never possibly be stored on the drive in unencrypted form. 2: Physical destruction.
Agreed
Most people dont realize how permanent solid state drives really are. I send USB keys through the wash in my pants by accident and the data was fine.
I now use software encryption on all my hard drives. To wipe them I use/dev/urandom and then smash them with a hammer on pavement to complete the process.
I expect in many years, SD drives, sticks and cards will be a significant archaeological find.
With any luck, solid state's durability will put Jodi Arias on death row. Bitch put the camera containing pics of the murder in the washing machine, but they got the data.
SSD's are already internally encrypted with 256bit AES. You just have to run the drive erase tool from the manufacturer, which erases the internal table the SSD uses. It takes 5 seconds.
Not all SSDs are. And why would you trust the manufacturer? Do you trust OCZ?
TRIM doesn't do anything with regards to excess space that is hidden from the host. TRIM just means the controller is told to overwrite a block, not just mark it as available.
Won't work on an SSD. You have no idea what the controller is doing behind the scenes. There is capacity on the SSD that is completely and utterly inaccessible to the host. When you write 256 GB of zeros to your 256 GB SSD, you've probably got 16 or 32 GB the controller hasn't told you about, with data you know nothing about. You have to issue the ATA SECURE ERASE command, and even then you'll have no idea if the controller actually respected it and wiped everything.
For SSDs there are two reliable options.
1: Encrypt everything in software so the key nor a hash of it could never possibly be stored on the drive in unencrypted form. 2: Physical destruction.
I don't care who in the world fucking says it, it's wrong. Quotation marks are used to enclose an exact quote. By collapsing or removing punctuation, you introduce ambiguity and lose meaning. The purpose of any language is to convey information. Introducing ambiguity or losing meaning is contrary to the purpose of language, and is thus the wrong fucking thing to do by any objective measure.
And those fucking style guides weren't in widespread use in US public education until the 1980s. Prior to that, teachers taught grammar and spelling. The proper way to quote something is to quote only the thing you're fucking quoting. It's what the quotation marks fucking mean. "Style guides" are absolutely not an authority, and they have no founding in reason or logic. The fact that there are several major ones just serves to highlight how arbitrary their "rules" are.
You can't do it anymore because they implemented search so you can just start typing for what you want and eliminate all those numbered steps. So old fashioned.
Except the search doesn't fucking work as well as the old search from Windows 95. If some file type is not indexed you're fucked. Windows will tell you to fuck off with your search unless you click on a secondary link to include non-indexed locations. And then the whole thing turns to shit because it wants to fucking search contents as well as file names. Even on 2 SSDs in RAID 0 I end up sitting for minutes trying to find a file.
Some smartass is already writing up a post about how I should use "name:" and "type:". But that doesn't work if you have shit with a "name" metadata column or you don't know what Windows has decided to call that "type" in metadata land.
If I want to find my my FRAPS binaries I have to run filename:="fraps*" type:file
Except that doesn't work. Why? Because "type:file" includes "file folder". So you need to do the opposite of the opposite. filename:="fraps*" type:directory
Except that doesn't work. Why? Because type:directory doesn't work because the "Type" is both "file folder" AND directory and the "" operator excludes literally on either, so it always returns true for directories.
filename:="fraps*" AND NOT type:="file folder" AND NOT type:="directory"
But the * doesn't work with =.
filename:~<"fraps" AND NOT type:="file folder" AND NOT type:="directory" Is what actually works. And it's still butt slow.
And if you want a reference of all the fields you can search against or the operators you can use or what they mean? Good fucking luck!
I don't think an elemental gas counts as a "material."
Ladies and gentleman what we have here is a person who is a product of public education in the United States during the 1990s. In the 1980s we decided to stop teaching children things such as grammar and spelling. The reasoning ranged from "It's too hard for the students!" to "It's too hard for the teachers!".
This is why no one under the age of 32 today has any fundamental understanding of the English language. This is why they can't spell. This is why they say someone who eats a healthy diet "eats healthy" instead of "eats healthily". This is why they put their punctuation inside of quotation marks even when the punctuation is not part of the thing being quoted, and even when it forces them to collapse two different punctuation marks into a single one. This leads to shit like "But I thought you were going to the store today?". Unless you're a surfer, there shouldn't be a fucking question mark in that sentence. This is why people "could care less" about the proper usage of "their", "there", and "they're". This is why people think "ironic" means "unexpected".
I could go on for days, but the ultimate point of all this is that X0563511 is fucking clueless about the English language and babbles without considering the meaning of the words he uses. Let's revisit his mind-numbing post:
I don't think an elemental gas counts as a "material."
X0563511, did you know that hydrogen is made up of matter, and is thus a material?
Oh, sorry to burst your bubble - no, Firefox/Chrome/Safari et. al. all require just as many hacks as modern IE versions to ensure consistency across all browsers to the greatest extent possible.
Any evidence for the "just as many hacks" assertion or did you just pull this out your ass?
True story: Chrome gives me far, far more issues than IE 9 or IE 10. And if your shit works in Chrome on Tuesday it'll be busted on Thursday, only to be partially fixed on Wednesday.
Even from a user perspective I have no idea why people use Chrome outside of Google fanboyism. It's got ads and tracking out the ass with limited options to block/remove that shit, but it runs some shitty javascript benchmark a little bit faster? Who gives a shit? I'd much rather turn off shitty javascript on shitty sites via NoScript than have it complete 2 milliseconds faster. The time I save by not downloading ads (ABP in FF) vs. downloading them and then hiding them (Chrome) is orders of magnitude more significant anyway.
The price jumped from $40 per BTC to $70 per BTC since this news broke.
All this does is require people who buy and sell Bitcoins for USD to report their activities over a certain threshold. Anyone can still freely use BTC directly.
Slashdot Mirror
Right now, if you can harm MtGox, you harm the entire Bitcoin network.
If you can harm Mt.Gox, you can harm a group of idiotic Bitcoin speculators.
The Bitcoin network has nothing to do with Mt.Gox.
I really just wish the fucking world would settle on 60 fps.
There is a slight problem with that:
http://en.wikipedia.org/wiki/File:PAL-NTSC-SECAM.svg
...the green bits are 30fps. Everything else, i.e about 2/3 of the planet, is 25fps. 25 does not go into 60. I suppose at a pinch it could be run at 24fps with the 120Hz timebase you suggested, but that's not exactly optimal...
The trouble is that your "2/3 of the planet" equates to about "10% of produced content". Besides, the people in the land of PAL have had to deal with 24 to 25 fps horse shit since the dawn of time, so they're used to it. And dropping 1 out of every 6 frames to go from 60 to 50 is much less offensive than the 24 to 30 shit we deal with now. And PAL itself is going down the toilet in favor of DVB, so there are no analog constraints even for broadcast signals that restrict anyone to 50 fps.
60 Hz (120 for 3D) for production would solve everything. Broadcast/cable/satellite can push it out whenever the fuck they please as long as they're using digital. 24 fps, 30 fps, 60 fps fit perfectly. 25 and 50 fps shit will have less distortion than anything that's ever been telecined. People can display it to the best of their TVs ability. And for NTSC shit (the vast majority of content) that PAL people want to watch, you could send the original frame rate shit to the PAL territories and have it display properly. No need to run a film at sped up at 25 fps or send video 5-in-6 decimated (30 to 25).
3D or High Framerate: 120 fps
Huh? Most video is at 24 fps. Even if we generously triple that, we're nowhere near 120 fps. Hobbit 3D's highest encode was 48 fps which was considered super high quality, and most theaters were still at 24.
24 fps is trash.
30 fps is trash.
48 fps is trash too. If you want the Hobbit in decent 3D you need to display 96 fps. If you want to watch it on a fixed-refresh rate display (all modern consumer TVs and monitors) you're fucked. We just got 120 Hz displays which allow near-perfect display of 24 and 30 fps content. With the Hobbit in 2D you'd need a 240 Hz display to properly handle 24, 30, and 48 fps content. Want decent 3D? Now you need 480 Hz. The dipshit should have gone with 60 Hz. Then 120 Hz displays would display it just fine, even in 3D. The BluRay would display it just fine as well, though at a culled frame rate. Broadcasters would have plenty of options for stuffing the thing into their standard 60i streams or 60p streams as 2D or 3D.
I really just wish the fucking world would settle on 60 fps.
subject says it
Shooting the moon
Google it. Or Bing it for the free Redbox rentals or Amazon gift cards.
Either way, something that can brick your machine so easily with software shouldn't be soldered to the board.
UEFI isn't causing bricking any more than any BIOS chip in the past has.
You may as well argue against memory controllers being integrated into CPUs or any northbridge/southbrdge chip being soldered onto a motherboard.
How can you trust what you can never see, or even know is there?
Thesis: Security requires trust.
You are not trusted to know these secrets, therefore you are not secured through their application.
The whole UEFI boondoggle is false security. Worse, this proves that it is vulnerability risk, sold under masquerade, as security.
UEFI is a replacement for BIOS. It has many features that let us deal with hardware that BIOS couldn't provide. UEFI is not a boondoggle, nor is it about security.
Unless honest participants in the network definitively control more than half of the computing power on the planet, it is at best impractical rather than impossible. Its not "absolutely, 100% perfectly fraud-proof".
It is actually 100% fraud-proof.
If someone seizes control of the network by exceeding 50% of the total computational power of the network (including their own), they introduces phony blocks in an attempt to double spend, they're forking the block chain. The honest miners will quickly see that certain hosts are accepting phony blocks and ignore them, and stick with their own, clean fork of the block chain.
There was an example of the block chain being forked a few weeks ago due to some bullshit about BerkeleyDB and 512 KB datagram sizes.
The networked converged on one fork and kept on trucking.
If someone is simply double spending and saying "Yup, verified!" without forking the block chain, anyone can trace the transactions involved and call bullshit.
For an individual merchant accepting bitcoins, you can protect yourself from localized instances of this attack by simply waiting for more verifications. The only way to get fucked is by having someone control your network and preventing you from accessing legitimate nodes. If they're doing that, they can fuck you in so many other ways, such as telling customers to send payment to their wallet's address instead of yours.
I do this for ISP techs, too. Bridge the ethernet adapter, install Windows of some variety in a virtual machine. (Don't even bother activating or updating it, it's going away as soon as they leave.) Most of them don't give a crap that they're installing in a virtual machine if they even notice at all. Just stand around and shoo them away when the host OS's interface pops up briefly during the reboot process.
Why in the fuck would an ISP tech need to install anything on your computer?
And put it in its own separate guest network, which is logically isolated from your own stuff by a firewall, maybe run a print server too (people often want to print boarding passes)...
As for funny looks, a browser is a browser and i've never had any problems giving someone a linux livecd, it has both firefox and chrome and most people are perfectly familiar with these applications.
Why go to the trouble of a separate network?
The odds of even the most retarded of users inadvertently fucking anything beyond the one machine they're touching is absurdly low, unless you're running outdated shit on your network. Remote exploits are remote exploits, and you should protect each device regardless or whether or not you trust the rest of the network.
If someone is so fuck-up prone that you think your proper boxen could be fucked by some schlub lolcatting around on the same network, you should be more worried about them tripping in your house and suing you.
OK, I know it's April fools, but why would a packet traveling faster than the speed of light necessarily arrive before it is sent? Do bullets shot faster than the speed of sound arrive before the gun makes a sound? No, it just arrives before the sound does.
You shoot ur lazer beemz at an enemy ship.
The enemy has a tachyon shield system that emits a field of tachyons devices that relay information back to the ship FTL.
When the lazer enters the field, the tachyon shield system tells the enemy ship to power up its shields.
The ship powers up its shields by energizing the tachyon device field and creating a barrier, stopping your lazer beemz.
Whenever the tachyon device field is powered up or the shield takes a hit, some of the tachyon devices fly out FTL, reducing total shield capacity.
The end result is that you fire your lazer and soon after you see tachyons fly at you and then you see the flash of your lazer beemz impacting the tachyon shield. Makes sense.
A third ship (depending on its relative position and the speed of the the tachyons) could see the tacyons fly out, then see you fire the lazer, then see the lazer beemz impact, and wonder why the fuck you would fire ur lazer beems after they powered up their shields.
Okay, smarty. One quantum particle occupies 2 places in space at the same time (aka quantum entangled). You move them a lightyear apart then spin one. What happens to the "other" particle and when?
There is no causality when it's actually the same particle. The cause and effect are both that it is the same particle.
1: It's not the same particle.
2: Information is not transferred, you don't get to spin one, you can merely read the spin of one and instantly know the spin of the other.
Imaging flipping a coin. You look at it as it lays on your hand or on the ground. You see the top and see that it's heads. You instantly know that the bottom is tails.
The information of the bottom being tails didn't arrive faster than light. You discerned it to be the opposite of the top before the experiment, and you learned of the top's state without violating the speed of light by looking at it. If you entangle particles and know the relation of their spins and then send them far apart, you're doing the same thing. Absolutely no information is transferred FTL.
Key people from Wikileaks got visited by spooks and quickly changed their tune about how they felt about the leaks, and blamed everything on Assange and said they didn't agree with releasing thigs that could "harm" people, even though nothing ever released by Wikileaks has actually harmed anyone. They then started OpenLeaks, which is basically a useless copy of WikiLeaks that the government has control over.
Assange is still trapped in the Ecuadorean embassy. Until he dies, gets out, or they come and grab him, nothing of importance will happen with WikiLeaks.
dd if=/dev/zero of=/dev/sda bs=1024 &
Won't work on an SSD.
For SSDs there are two reliable options.
1: Encrypt everything in software so the key nor a hash of it could never possibly be stored on the drive in unencrypted form.
2: Physical destruction.
Agreed
Most people dont realize how permanent solid state drives really are. I send USB keys through the wash in my pants by accident and the data was fine.
I now use software encryption on all my hard drives. To wipe them I use /dev/urandom and then smash them with a hammer on pavement to complete the process.
I expect in many years, SD drives, sticks and cards will be a significant archaeological find.
With any luck, solid state's durability will put Jodi Arias on death row. Bitch put the camera containing pics of the murder in the washing machine, but they got the data.
SSD's are already internally encrypted with 256bit AES. You just have to run the drive erase tool from the manufacturer, which erases the internal table the SSD uses. It takes 5 seconds.
Not all SSDs are. And why would you trust the manufacturer? Do you trust OCZ?
TRIM doesn't do anything with regards to excess space that is hidden from the host. TRIM just means the controller is told to overwrite a block, not just mark it as available.
The "neither" is not necessary, actually.
Hell, I nearly but the "nor a hash of it" in parenthesis, which would make the "neither" straight up wrong.
dd if=/dev/zero of=/dev/sda bs=1024 &
Won't work on an SSD. You have no idea what the controller is doing behind the scenes. There is capacity on the SSD that is completely and utterly inaccessible to the host. When you write 256 GB of zeros to your 256 GB SSD, you've probably got 16 or 32 GB the controller hasn't told you about, with data you know nothing about. You have to issue the ATA SECURE ERASE command, and even then you'll have no idea if the controller actually respected it and wiped everything.
For SSDs there are two reliable options.
1: Encrypt everything in software so the key nor a hash of it could never possibly be stored on the drive in unencrypted form.
2: Physical destruction.
I don't care who in the world fucking says it, it's wrong. Quotation marks are used to enclose an exact quote. By collapsing or removing punctuation, you introduce ambiguity and lose meaning. The purpose of any language is to convey information. Introducing ambiguity or losing meaning is contrary to the purpose of language, and is thus the wrong fucking thing to do by any objective measure.
And those fucking style guides weren't in widespread use in US public education until the 1980s. Prior to that, teachers taught grammar and spelling.
The proper way to quote something is to quote only the thing you're fucking quoting. It's what the quotation marks fucking mean. "Style guides" are absolutely not an authority, and they have no founding in reason or logic. The fact that there are several major ones just serves to highlight how arbitrary their "rules" are.
Fucking slashdot ate my brackets.
filename:="fraps*" type:directory
should be
filename:="fraps*" type:<>directory
You can't do it anymore because they implemented search so you can just start typing for what you want and eliminate all those numbered steps. So old fashioned.
Except the search doesn't fucking work as well as the old search from Windows 95.
If some file type is not indexed you're fucked. Windows will tell you to fuck off with your search unless you click on a secondary link to include non-indexed locations. And then the whole thing turns to shit because it wants to fucking search contents as well as file names. Even on 2 SSDs in RAID 0 I end up sitting for minutes trying to find a file.
Some smartass is already writing up a post about how I should use "name:" and "type:". But that doesn't work if you have shit with a "name" metadata column or you don't know what Windows has decided to call that "type" in metadata land.
If I want to find my my FRAPS binaries I have to run
filename:="fraps*" type:file
Except that doesn't work. Why? Because "type:file" includes "file folder". So you need to do the opposite of the opposite.
filename:="fraps*" type:directory
Except that doesn't work. Why? Because type:directory doesn't work because the "Type" is both "file folder" AND directory and the "" operator excludes literally on either, so it always returns true for directories.
filename:="fraps*" AND NOT type:="file folder" AND NOT type:="directory"
But the * doesn't work with =.
filename:~<"fraps" AND NOT type:="file folder" AND NOT type:="directory"
Is what actually works. And it's still butt slow.
And if you want a reference of all the fields you can search against or the operators you can use or what they mean?
Good fucking luck!
As more and more people write text in public, so will their mistakes be persistant enough to become part of the language.
Repeating a mistake does not make it valid.
It doesn't matter how many people state that 1+1=1. It will never be true.
I don't think an elemental gas counts as a "material."
Ladies and gentleman what we have here is a person who is a product of public education in the United States during the 1990s.
In the 1980s we decided to stop teaching children things such as grammar and spelling. The reasoning ranged from "It's too hard for the students!" to "It's too hard for the teachers!".
This is why no one under the age of 32 today has any fundamental understanding of the English language. This is why they can't spell. This is why they say someone who eats a healthy diet "eats healthy" instead of "eats healthily". This is why they put their punctuation inside of quotation marks even when the punctuation is not part of the thing being quoted, and even when it forces them to collapse two different punctuation marks into a single one. This leads to shit like "But I thought you were going to the store today?". Unless you're a surfer, there shouldn't be a fucking question mark in that sentence. This is why people "could care less" about the proper usage of "their", "there", and "they're". This is why people think "ironic" means "unexpected".
I could go on for days, but the ultimate point of all this is that X0563511 is fucking clueless about the English language and babbles without considering the meaning of the words he uses. Let's revisit his mind-numbing post:
I don't think an elemental gas counts as a "material."
X0563511, did you know that hydrogen is made up of matter, and is thus a material?
Oh, sorry to burst your bubble - no, Firefox/Chrome/Safari et. al. all require just as many hacks as modern IE versions to ensure consistency across all browsers to the greatest extent possible.
Any evidence for the "just as many hacks" assertion or did you just pull this out your ass?
True story: Chrome gives me far, far more issues than IE 9 or IE 10.
And if your shit works in Chrome on Tuesday it'll be busted on Thursday, only to be partially fixed on Wednesday.
Even from a user perspective I have no idea why people use Chrome outside of Google fanboyism. It's got ads and tracking out the ass with limited options to block/remove that shit, but it runs some shitty javascript benchmark a little bit faster? Who gives a shit? I'd much rather turn off shitty javascript on shitty sites via NoScript than have it complete 2 milliseconds faster. The time I save by not downloading ads (ABP in FF) vs. downloading them and then hiding them (Chrome) is orders of magnitude more significant anyway.
We hardly knew ye!
The price jumped from $40 per BTC to $70 per BTC since this news broke.
All this does is require people who buy and sell Bitcoins for USD to report their activities over a certain threshold.
Anyone can still freely use BTC directly.