You call it hairsplitting, I call it appropriately assigning blame. Google isn't preventing you from removing just about anything from Android... Motorola, Samsung, HTC, the various cell providers, et. al are. For example, I own a Virgin Mobile branded Samsung phone with Android, and there are several apps specific to VMobile and Samsung, but with no direct connection to Google which I cannot remove; other Android phones from different manufacturers and on different networks have different suites of such software (including, theoretically, no such software). Google isn't to blame for this, because vanilla Android doesn't come with this software.
Vanilla Android comes with a lot of crap, actually. It's just Google crap.
No no, it's deadly serious. Of coure, we can't just jump in blindly. We'll have to probe Uranus first.
I think you mean "deadlily serious" (as serious as something deadly), or perhaps "deathly serious" (as serious as death). Now it's time for you all to go to your favorite online dictionaries and see "deadly" listed as an adverb, even thought it isn't one.
Re:they don't need to reboot, they need to end it
on
DC Reboots Universe
·
· Score: 2
That's the difference between manga and comics. Mangas, in general, have an ending, so you can write a coeherent and complex story wihout the necessity of adding tons of new characters to keep it running, kill and ressurect the protagonist 15 times, create tens of multiverses or reboot everything at each 10-15 years because everything is so full os contradictions. No only manga, but series like Sandman, Watchmen (and even Calin & Hobbes), have endings too. They only need to reboot because they don't know when to stop.
Uh, no. Many mangas are ridiculously convoluted, run on way to long, have the typical problems of endless new characters, death/resurrection, time warps and retcons, etc, and spawn endless derivative works, alternate versions (both official and unofficial), sequel, prequels, and sidequels.
Mangas can and usually do have all the problems American comics do. They often have these problems to a much worse degree. The problem is that the story is never fully written. The story is made up as they go along (sometimes with a basic framework, usually not), and it stretched to fit however many issues they think they can sell. This is why TV shows get worse in later seasons. This is why movie sequels usually suck. The basic form of storytelling is at odds with the basic desire to milk a teat until it's dry.
If you want those free Amazon apps, you have Unknown Sources allowed, so there's that protection gone. (It's why Amazon doesn't work on AT&T right now, and probably why AT&T is going to have the option - some Amazon-AT&T deal).
I have the Amazon store shit. I am on AT&T. What are you talking about?
You're just oh so wrong. Nvidia used to use 4 digits (FX 5xxx, 6xxx, 7xxx, 8xxx, 9xxx), then they went to 2xx.
After 2xx they went to 4xx. Along the way they peppered in a few 1xx and 3xx parts that nobody bought (they were all rebadges of the defective G92 chips. The 9xxx and early 2xx were also defective. The revamps in the 8xxx (8800 GT, and the second revision of the 8800 GTS) line were also defective. Then they went to 5xx.
The last number hasn't always been 0, either. There's the GTX 285, for example. And of course, OEMs can add whatever bullshit they want at the end of it, such as OC, SE, SSE. And of course they have to include the Nvidia shitfest of GT, GTX, Ultra, M, whatever.
In order of performance (best to worst) it goes Ultra, GTX, GT, GTS, (nothing), GS, then M, LE, and other shit. You can compare within a single model number, but not across generations. These monikers didn't exist until the 6800 family came out. We had the 6800, the 6800 GT, and the 6800 Ultra. The 7000 series was just a rehash of the 6000 series. The 8000 series was indeed a new GPU, and introduced the shitfuck of GTS (which seemed to be tacked on to the cards that would otherwise NOT have a GT/Ultra/whatever shit added to them). Now we start adding GX or GX 2 to shit to indicate it's a dual-gpu card. The next family of chips came with the 2xx series. Not the first few out the door, mind you, but the Fermi 280s.
The only thing consistent about Nvidia for the last decade is that if the second number is an 8, you have the flagship part. You always want the flagship part, because it is the only one that actually receives proper engineering and testing. You can choose whatever binning (ultra gtx gt gts) or overclocked horseshit you want from msi/asus/whoever. 6800 Ultra/GT/vanilla. 8800 Ultra/GTX/GTS. 280, 480, 580, etc into the future maybe.
When they start futzing around with 8600s or 7950s, or GX2s, or the 8800 GT or 8800 GTS v2 (aka 8800 GTS 512), what's happening is they're hastily tweaking shit to adapt to the market sectors and reduce cost (or slap as much shit as they can fit in an ATX case and go for the supid performance crown for bragging rights). These are always sloppy jobs. With Nvidia, we had bumpgate. But in general, you get less reliable shit, at a later date, for a bit less money.
With ATi/AMD, you've got a whole different can of worms. They were doing 8xxx and 9xxx a decade ago, then went to x1xxx (the firxt x is a literal x) and x2xxx. Then they went to HD 3xxx, HD 4xxx, HD 5xxx, and HD 6xxx.
They've used monikers such as XT, Pro, and LE. They've stopped using the 8 as the flagship indicator (from the old 9800 pro to the 5800 series) and now use 9 for the flagship. As such, a 5850 is better than/the same as a 6850, and a 5870 is better/the same as than a 6870. The generational bump this round added a 1 to the second number. The 6970 is the big brother of the 5870. And if you want to compare the 5970 to something, you'll be looking at the 6990.
So no. In short, it makes zero sense. You can't look at the name and discern anything when they add changing and intentionally consufing XT Pro GT GTX GTS GTS v2 GS LE M GX GX2 etc, along with model numbers that can't be directly compared unless the first digit is the same. Add in the OC tweaks and branding, ePeen gun-style cases, and CG girls and orcs, and no one can tell you the difference between the Gigabyte Radeon HD 5870 SOC and the MSI Radeon HD 6870 HAWK without looking at benchmarks.
The Reese's family made peanut butter cups and other confections. No chocolate, just creamy little cups (about the size of a caramel, or today's "mini" Reese's) of peanut butter and some stuff to make it hard on the outside.
It was an accident when someone poured chocolate sauce into the the wrong reservoir, resulting in peanut butter cups with swirls of chocolate. Reese's family sold the recipe to Hershey's after his death. (This wasn't a slimy cash-in by his family - Reese had worked with Hershey before, and had great respect for him. Hershey inspired Reese to open his own candy shop, which exclusively used Hershey's chocolate.)
Because you don't have a 100ft wide screen with more than 7 channels (movie theaters have many more channels than 7).
I bet you also listen to your iPod rather than going to see a musician live...
Movie theaters can have all the speakers they want, but the movie is mastered for a stereo mix and a 5.1 mix. (Then they shit out a bit more separation for rear/side to get a 7.1 mix as well.) The appropriate listening setup, from best to worst, is:
You have to have access to the system that stores the password file, or perform a MITM attack to listen in.
If they're sending passwords in plaintext, unencrypted wireless, or wireless at all, that's their own fault. Certificates are subject to the same MITM attacks.
If they're accessing a web service, you can only brute force against the web service front end. You'll never get anywhere doing this if there's any policy in place to limit login attempts per ip and per account.
A key is a password. It's just along password that people write down and store somewhere, typically as a file on a computer.
Your problem is now securing that key. People typically encrypt their keys. With passwords.
The safest place for a password is in your brain. If your brain can't remember a password that's complex enough to withstand brute forcing for longer than it takes for you to change your password, then too bad.
This is gonna sound a bit wacky because I'm still something of an amateur at computer security, but what if as a start Sony used the e-mail addresses on file to send individualized password reset links to each customer?
Won't work because users didn't have to provide a valid email address when setting up the PSN account. Many users used fake / throwaway addresses.
The other method would have been to force the reset request to come from the PS3 / PSP the account was most recently used on, by looking at the system's UID. But the PSP and PS3 are both fully cracked, and months ago the hackers were spoofing UIDs to get around the PSN bannings. The UIDs are not secure, and this wouldn't account for people who sold / broke / whatever their system. There is no viable option that can catch all cases at this point.
There are 3 problems, with 3 simple ways to prevent it / mitigate damage:
Credit cards lost. Don't store credit card data on a central server. Don't store it at all. Worried about convenience? Allow the user the option, with copious warnings, to store the credit card number locally. Encrypted, of course.
Passwords lost. Don't use the same password for multiple accounts and this won't be a problem. Don't store the password in plaintext (we're not sure if this is the case or not, but I bet it is). Enforce strong passwords.
User accounts compromised: See "passwords lost". Provide an alternate means of account ownership verification (requiring a VALID email with confirmation code during account setup). Give users the option to set / manage security tokens for their accounts. The tokens can be their PS3 / PS3.
No. It's a 20 year study. 17% of men get prostate cancer over their lifetimes. If the study population were 50+ at the start that seems low. if the study population were under 30 at the start that that seems really high and I suspect their population consisted of Chernobyl residents...
No. 17% of men get diagnosed with prostate cancer at some point. Nearly 100% of men who live past andropause will get prostate cancer.
The difference comes from prostate cancer often not being the thing that kills you, and from prostate cancer usually being diagnosed as "enlarged prostate" so your HMO won't have to deal with it.
True, but this is better in a registry how? (Btw, my point is merely that this sort of thing would likely only be found by perusing the docs or having someone tell you about it, regardless of how the setting is stored)
The setting can be controlled through Active Directory, with a happy little UI to boot. All registry settings can. And the AD templates have descriptions for the keys and their values.
Assuming you meant "oil", the premise is still preposterous.
We have dams. We have nuclear reactors. We have vegetables that literally ooze disgusting oils useful only for burning and causing diabetes. When we run out of all of those, we can burn the diabetics.
Then, we have human-powered generators such as hand cranks, and flesh lights.
Slashdot Mirror
You call it hairsplitting, I call it appropriately assigning blame. Google isn't preventing you from removing just about anything from Android... Motorola, Samsung, HTC, the various cell providers, et. al are. For example, I own a Virgin Mobile branded Samsung phone with Android, and there are several apps specific to VMobile and Samsung, but with no direct connection to Google which I cannot remove; other Android phones from different manufacturers and on different networks have different suites of such software (including, theoretically, no such software). Google isn't to blame for this, because vanilla Android doesn't come with this software.
Vanilla Android comes with a lot of crap, actually.
It's just Google crap.
Kinda hard to do that after the fact.
Playing picture swap with a married man and a member of congress are both pursuits that are obviously going to end well.
member of congress
member
congress
Because member can mean penis and congress can be of the sexual kind.
Fucking typo.
No no, it's deadly serious. Of coure, we can't just jump in blindly. We'll have to probe Uranus first.
I think you mean "deadlily serious" (as serious as something deadly), or perhaps "deathly serious" (as serious as death).
Now it's time for you all to go to your favorite online dictionaries and see "deadly" listed as an adverb, even thought it isn't one.
That's the difference between manga and comics. Mangas, in general, have an ending, so you can write a coeherent and complex story wihout the necessity of adding tons of new characters to keep it running, kill and ressurect the protagonist 15 times, create tens of multiverses or reboot everything at each 10-15 years because everything is so full os contradictions. No only manga, but series like Sandman, Watchmen (and even Calin & Hobbes), have endings too. They only need to reboot because they don't know when to stop.
Uh, no.
Many mangas are ridiculously convoluted, run on way to long, have the typical problems of endless new characters, death/resurrection, time warps and retcons, etc, and spawn endless derivative works, alternate versions (both official and unofficial), sequel, prequels, and sidequels.
Mangas can and usually do have all the problems American comics do. They often have these problems to a much worse degree.
The problem is that the story is never fully written. The story is made up as they go along (sometimes with a basic framework, usually not), and it stretched to fit however many issues they think they can sell. This is why TV shows get worse in later seasons. This is why movie sequels usually suck. The basic form of storytelling is at odds with the basic desire to milk a teat until it's dry.
They have to completely rewrite Superman, since they lost the rights to his original origin story.
Well, I was wrong. The DigiAnts are a godsend.
But isn’t that a bit short-sighted? What happens when we’re overrun by DigiAnts?
No problem. We simply release wave after wave of Chinese DigiAnteater. They’ll wipe out the DigiAnts.
But aren’t the DigiAnteaters even worse?
Yes, but we’re prepared for that. We’ve lined up a fabulous type of DigiGorilla that thrives on DigiAnteater bits.
But then we’re stuck with DigiGorillas!
No, that’s the beautiful part. When IPv6 rolls around, the DigiGorillas simply get null routed.
Let me guess - you didn't buy your phone from AT&T, did you?
I'm not retarded, so I don't buy phones from carriers.
It's one thing to feed a troll, but to feed a troll and get thoroughly called out and owned?
That's shameful.
I have the Amazon store shit.
I am on AT&T.
What are you talking about?
You're just oh so wrong.
Nvidia used to use 4 digits (FX 5xxx, 6xxx, 7xxx, 8xxx, 9xxx), then they went to 2xx.
After 2xx they went to 4xx. Along the way they peppered in a few 1xx and 3xx parts that nobody bought (they were all rebadges of the defective G92 chips. The 9xxx and early 2xx were also defective. The revamps in the 8xxx (8800 GT, and the second revision of the 8800 GTS) line were also defective. Then they went to 5xx.
The last number hasn't always been 0, either. There's the GTX 285, for example. And of course, OEMs can add whatever bullshit they want at the end of it, such as OC, SE, SSE. And of course they have to include the Nvidia shitfest of GT, GTX, Ultra, M, whatever.
In order of performance (best to worst) it goes Ultra, GTX, GT, GTS, (nothing), GS, then M, LE, and other shit. You can compare within a single model number, but not across generations. These monikers didn't exist until the 6800 family came out. We had the 6800, the 6800 GT, and the 6800 Ultra. The 7000 series was just a rehash of the 6000 series. The 8000 series was indeed a new GPU, and introduced the shitfuck of GTS (which seemed to be tacked on to the cards that would otherwise NOT have a GT/Ultra/whatever shit added to them). Now we start adding GX or GX 2 to shit to indicate it's a dual-gpu card. The next family of chips came with the 2xx series. Not the first few out the door, mind you, but the Fermi 280s.
The only thing consistent about Nvidia for the last decade is that if the second number is an 8, you have the flagship part. You always want the flagship part, because it is the only one that actually receives proper engineering and testing. You can choose whatever binning (ultra gtx gt gts) or overclocked horseshit you want from msi/asus/whoever.
6800 Ultra/GT/vanilla.
8800 Ultra/GTX/GTS.
280, 480, 580, etc into the future maybe.
When they start futzing around with 8600s or 7950s, or GX2s, or the 8800 GT or 8800 GTS v2 (aka 8800 GTS 512), what's happening is they're hastily tweaking shit to adapt to the market sectors and reduce cost (or slap as much shit as they can fit in an ATX case and go for the supid performance crown for bragging rights). These are always sloppy jobs. With Nvidia, we had bumpgate. But in general, you get less reliable shit, at a later date, for a bit less money.
With ATi/AMD, you've got a whole different can of worms.
They were doing 8xxx and 9xxx a decade ago, then went to x1xxx (the firxt x is a literal x) and x2xxx.
Then they went to HD 3xxx, HD 4xxx, HD 5xxx, and HD 6xxx.
They've used monikers such as XT, Pro, and LE.
They've stopped using the 8 as the flagship indicator (from the old 9800 pro to the 5800 series) and now use 9 for the flagship.
As such, a 5850 is better than/the same as a 6850, and a 5870 is better/the same as than a 6870.
The generational bump this round added a 1 to the second number. The 6970 is the big brother of the 5870.
And if you want to compare the 5970 to something, you'll be looking at the 6990.
So no. In short, it makes zero sense. You can't look at the name and discern anything when they add changing and intentionally consufing XT Pro GT GTX GTS GTS v2 GS LE M GX GX2 etc, along with model numbers that can't be directly compared unless the first digit is the same. Add in the OC tweaks and branding, ePeen gun-style cases, and CG girls and orcs, and no one can tell you the difference between the Gigabyte Radeon HD 5870 SOC and the MSI Radeon HD 6870 HAWK without looking at benchmarks.
It was peanut butter in their chocolate
Actually, no.
The Reese's family made peanut butter cups and other confections. No chocolate, just creamy little cups (about the size of a caramel, or today's "mini" Reese's) of peanut butter and some stuff to make it hard on the outside.
It was an accident when someone poured chocolate sauce into the the wrong reservoir, resulting in peanut butter cups with swirls of chocolate. Reese's family sold the recipe to Hershey's after his death. (This wasn't a slimy cash-in by his family - Reese had worked with Hershey before, and had great respect for him. Hershey inspired Reese to open his own candy shop, which exclusively used Hershey's chocolate.)
What the fuck does that even mean?
While kosher's actual definition doesn't fit here, it's clear by context that they intend it to mean cromulent.
So, let's recap again: ...
Home theatre:
- No noisy neighbors
Except for that asshole who watches movies on his home theater setup all the time.
Because you don't have a 100ft wide screen with more than 7 channels (movie theaters have many more channels than 7).
I bet you also listen to your iPod rather than going to see a musician live...
Movie theaters can have all the speakers they want, but the movie is mastered for a stereo mix and a 5.1 mix. (Then they shit out a bit more separation for rear/side to get a 7.1 mix as well.) The appropriate listening setup, from best to worst, is:
5.1
2.1 (5.1 folds perfectly into 2.1)
Stereo
7.1
6.1
Quadrophonic
Mono
No, trying to get modded down to show that people are morons.
Mod up if you hate 3D movies.
Mod down if you're a moron.
You have to have access to the system that stores the password file, or perform a MITM attack to listen in.
If they're sending passwords in plaintext, unencrypted wireless, or wireless at all, that's their own fault.
Certificates are subject to the same MITM attacks.
If they're accessing a web service, you can only brute force against the web service front end. You'll never get anywhere doing this if there's any policy in place to limit login attempts per ip and per account.
A key is a password. It's just along password that people write down and store somewhere, typically as a file on a computer.
Your problem is now securing that key. People typically encrypt their keys. With passwords.
The safest place for a password is in your brain. If your brain can't remember a password that's complex enough to withstand brute forcing for longer than it takes for you to change your password, then too bad.
This is gonna sound a bit wacky because I'm still something of an amateur at computer security, but what if as a start Sony used the e-mail addresses on file to send individualized password reset links to each customer?
Won't work because users didn't have to provide a valid email address when setting up the PSN account.
Many users used fake / throwaway addresses.
The other method would have been to force the reset request to come from the PS3 / PSP the account was most recently used on, by looking at the system's UID. But the PSP and PS3 are both fully cracked, and months ago the hackers were spoofing UIDs to get around the PSN bannings. The UIDs are not secure, and this wouldn't account for people who sold / broke / whatever their system.
There is no viable option that can catch all cases at this point.
There are 3 problems, with 3 simple ways to prevent it / mitigate damage:
Credit cards lost. Don't store credit card data on a central server. Don't store it at all. Worried about convenience? Allow the user the option, with copious warnings, to store the credit card number locally. Encrypted, of course.
Passwords lost. Don't use the same password for multiple accounts and this won't be a problem. Don't store the password in plaintext (we're not sure if this is the case or not, but I bet it is). Enforce strong passwords.
User accounts compromised: See "passwords lost". Provide an alternate means of account ownership verification (requiring a VALID email with confirmation code during account setup). Give users the option to set / manage security tokens for their accounts. The tokens can be their PS3 / PS3.
No. It's a 20 year study. 17% of men get prostate cancer over their lifetimes. If the study population were 50+ at the start that seems low. if the study population were under 30 at the start that that seems really high and I suspect their population consisted of Chernobyl residents...
No. 17% of men get diagnosed with prostate cancer at some point.
Nearly 100% of men who live past andropause will get prostate cancer.
The difference comes from prostate cancer often not being the thing that kills you, and from prostate cancer usually being diagnosed as "enlarged prostate" so your HMO won't have to deal with it.
True, but this is better in a registry how? (Btw, my point is merely that this sort of thing would likely only be found by perusing the docs or having someone tell you about it, regardless of how the setting is stored)
The setting can be controlled through Active Directory, with a happy little UI to boot.
All registry settings can.
And the AD templates have descriptions for the keys and their values.
Assuming you meant "oil", the premise is still preposterous.
We have dams.
We have nuclear reactors.
We have vegetables that literally ooze disgusting oils useful only for burning and causing diabetes.
When we run out of all of those, we can burn the diabetics.
Then, we have human-powered generators such as hand cranks, and flesh lights.
Pretty sure such a stack, properly affixed to the earth, would slow down the earth's rotation significantly.