Not everyone has a static IP address. Are you suggesting that unsavory individuals trying to find you will give up if an IP trace didn't work? This tracking can and will be used for malicious purposes.
You're right. It is worse. With a magstripe, the cost of fraud often gets eaten by the credit card company. With crypto chips, the cost always gets eaten by the vendor because of the presumption that the system is secure.
That's a policy issue, not a technical issue. It's also short lived, very soon all fraud on the magstripe will be eaten by the vendor as incentive to migrate to the chip. If the vendor has a cracked crypto chip reader, well, it's their responsibility to prevent that.
Horrified because my bank is supposed to refuse the transaction if the PIN isn't sent along with the transaction data. I wasn't aware they granted exceptions to the USA system.
Chip-and-pin is no more secure than magswipes, it contains the same data and can often broadcast the data a 100m around you through RFID activation.
RFID isn't a requirement for chip-based cards. In fact, one of my chipped cards doesn't support RFID. And you're kidding yourself if you think that the cryptographic chip is equivalent to the mag strip.
I'd rather keep my mag swipe, in case it gets compromised or even a problem with the vendor (if they won't do a warranty return), my bank will happily take the charges off the card. Once I've entered a PIN or used any of their stupid 'security measures' (eg. Verified by Visa which is a horribly broken design), they assume I'm to blame for any problem with my card.
You do that. Meanwhile, we don't use the mag strip in Australia, so I'll happily prevent my card from being compatible with the less secure USA methodology.
I visited USA last year, and was horrified when my transaction went through when the merchant swiped the mag strip on my Australian chip-and-PIN card, without requiring my PIN or signature. I wasn't aware my card issuer would even allow such a transaction. I've since destroyed the mag strip portion of my replacement card.
So you're suggesting that since the MPAA isn't funding the IR LED banks, the theatres need expensive night vision goggles instead?
I've seen people in the theater recording films with their smartphone, and the theater staff do nothing. The way you do this is by making sure that theater tickets assign seats, and have a "snich" app that reports the film, showing and seat of the pirate. eg "2 rows ahead and 4 seats to the right (of me|row)" and thus allow the theater manager to call law enforcement if needed.
And how can you be sure they're actually filming it rather than just obnoxiously holding up their phone (using IM or something) without using the camera?
I came to say exactly the same thing, but this AC beat me. One potential risk though is that the pirates could potentially use filters to block the IR portion of the spectrum. At least it would hinder the casual pirates.
I still don't see why some sort of filter hasn't been implemented. These troll posts are usually just direct copy/pastes, which would be really easy to filter once identified.
AMD usually overpromises, but even if we assume they get a 40% IPC improvement, it still won't be enough to catch the current Intel chips. At least it's a step in the right direction.
The affected service was Google Computer Engine, meaning that data may be changing. Replication isn't instantaneous, so I'd imagine the lost data was pending modifications.
If you're that severely bottle-necked by a 4+ GHz quad core then this is not a typical DX11 game.
We already know this isn't a typical DX11 game. They're using way more draw calls than a typical DX11 game simply because DX12 allows them to make more. That's even stated in the article.
As long as the enemy has superior dogfighters that are outclassed in other modes of combat, the dogfighting capabilities of your planes will be forced into relevancy. Especially when the rules of engagement require visual confirmation before weapons release. We've already had one commercial airliner "accidentally" shot down during a military conflict last year (MH17), so it's unlikely those requirements will be relaxed any time soon.
Sleep and Suspend are two different names for the same thing. Windows supports Hibernate, but it's often disabled by users to save hard drive space. Suspend/Sleep saves the current state of the system in RAM and powers off pretty much everything else (including the CPU) for quick resume. Hibernate copies the contents of RAM to the hard drive, and powers everything off. Resuming is slower, but it will survive a complete power outage.
So, a few issues here and there, but really, why not?
The amount of effort required. Not only does Google have to rewrite the relevant portions of Android to use C#, all the apps in the store need to be ported too.
Slashdot Mirror
Not everyone has a static IP address. Are you suggesting that unsavory individuals trying to find you will give up if an IP trace didn't work? This tracking can and will be used for malicious purposes.
It can be used for other stuff other than advertisement. <snip>: Others use it in order to know when/how/where to run their own ad campaign next.
That's still using it for the purposes of advertising...
Maybe you should tell that to the families of the people in Bangladesh who were murdered for posting blogs that were tracked back to them.
I'm in my 30s, I most definitely was around in '93.
And there isn't a single /. member who didn't benefit from their download site years ago.
A bold claim. I've never used it.
You're right. It is worse. With a magstripe, the cost of fraud often gets eaten by the credit card company. With crypto chips, the cost always gets eaten by the vendor because of the presumption that the system is secure.
That's a policy issue, not a technical issue. It's also short lived, very soon all fraud on the magstripe will be eaten by the vendor as incentive to migrate to the chip. If the vendor has a cracked crypto chip reader, well, it's their responsibility to prevent that.
Chip-and-pin is no more secure than magswipes, it contains the same data and can often broadcast the data a 100m around you through RFID activation.
RFID isn't a requirement for chip-based cards. In fact, one of my chipped cards doesn't support RFID. And you're kidding yourself if you think that the cryptographic chip is equivalent to the mag strip.
I'd rather keep my mag swipe, in case it gets compromised or even a problem with the vendor (if they won't do a warranty return), my bank will happily take the charges off the card. Once I've entered a PIN or used any of their stupid 'security measures' (eg. Verified by Visa which is a horribly broken design), they assume I'm to blame for any problem with my card.
You do that. Meanwhile, we don't use the mag strip in Australia, so I'll happily prevent my card from being compatible with the less secure USA methodology.
I find it faster to type in a PIN than to write my signature on a piece of paper.
I visited USA last year, and was horrified when my transaction went through when the merchant swiped the mag strip on my Australian chip-and-PIN card, without requiring my PIN or signature. I wasn't aware my card issuer would even allow such a transaction. I've since destroyed the mag strip portion of my replacement card.
I've seen people in the theater recording films with their smartphone, and the theater staff do nothing. The way you do this is by making sure that theater tickets assign seats, and have a "snich" app that reports the film, showing and seat of the pirate. eg "2 rows ahead and 4 seats to the right (of me|row)" and thus allow the theater manager to call law enforcement if needed.
And how can you be sure they're actually filming it rather than just obnoxiously holding up their phone (using IM or something) without using the camera?
I came to say exactly the same thing, but this AC beat me. One potential risk though is that the pirates could potentially use filters to block the IR portion of the spectrum. At least it would hinder the casual pirates.
I still don't see why some sort of filter hasn't been implemented. These troll posts are usually just direct copy/pastes, which would be really easy to filter once identified.
AMD usually overpromises, but even if we assume they get a 40% IPC improvement, it still won't be enough to catch the current Intel chips. At least it's a step in the right direction.
They didn't, IT World got it wrong.
Apparently making sure HTML tags are formatted correctly is too difficult for the "editors" around here...
The affected service was Google Computer Engine, meaning that data may be changing. Replication isn't instantaneous, so I'd imagine the lost data was pending modifications.
Bingo. Also, trying to back up more than 1TB of data on 1Mbit upload bandwidth is an exercise in futility.
If you're that severely bottle-necked by a 4+ GHz quad core then this is not a typical DX11 game.
We already know this isn't a typical DX11 game. They're using way more draw calls than a typical DX11 game simply because DX12 allows them to make more. That's even stated in the article.
DirectX is a Microsoft API, so yes, it's pretty likely to be Windows only. For Linux, there's Vulkan.
The Developer now must know MORE about the underlying hardware to make the best use of Direct X 12?
Uh, yeah, that's what a lower level API means.
Not unless they're faster than you. Which they're not.
There are plenty of older fighter jets that are noticeably faster than the F-35.
Especially when the rules of engagement require visual confirmation before weapons release.
and the F-35's stealth capabilities pretty much ensure it's going to get the first shot at BVR.
You completely ignored the fact that rules of engagement don't currently permit firing BVR.
As long as the enemy has superior dogfighters that are outclassed in other modes of combat, the dogfighting capabilities of your planes will be forced into relevancy. Especially when the rules of engagement require visual confirmation before weapons release. We've already had one commercial airliner "accidentally" shot down during a military conflict last year (MH17), so it's unlikely those requirements will be relaxed any time soon.
Sleep and Suspend are two different names for the same thing. Windows supports Hibernate, but it's often disabled by users to save hard drive space. Suspend/Sleep saves the current state of the system in RAM and powers off pretty much everything else (including the CPU) for quick resume. Hibernate copies the contents of RAM to the hard drive, and powers everything off. Resuming is slower, but it will survive a complete power outage.
No.
So, a few issues here and there, but really, why not?
The amount of effort required. Not only does Google have to rewrite the relevant portions of Android to use C#, all the apps in the store need to be ported too.