Having been a member of the original beta of WoW, and one of the first to stop playing WoW after it's release, trust me - it had more than it's share of missing content, and broken features.
It's had a lot of polish time since release, and it seems a lot of people have forgotten the issues - such as unscheduled patch windows, weekly outages to reboot servers that apparently had memory leaks, database corruption issues, etc... Back then, everyone compared the upstart WoW to Everquest, and not kindly...
Thanks for the personal attacks, it shows your level of inteligence in how you choose to respond to what should be a civil conversation.
I'm saying that the computer industry, as a whole has totally made the terms Kilo, Mega and Giga ambiguous, with no strict definition of the terms. This is why they came up with the Kibi, Mibi, etc...
To want to stick to an archaic, inexact terminology, also expresses a desire for things to never change.
I'm perfectly fine with changing to the exabinary notation, and leaving the metric (base 10) notation behind me, you should be as well, as there would be no way they could use those terms with any other meaning.
Today, they get away with it because they can point to a dictionary that shows that metric is a base 10 system, not a binary system.
So, regardless of your desire to stick with what wasn't, it's time to move on.. Maybe if the terms didn't sound so bad, they would have caught on sooner.
I'd like to see a class action suit brought against storage manufacturers forcing them to use exabinary, as it is just as misleading as the 19" monitor (17.1" visible) used to be.
dude - K M G - have NOT always stood for factors of 1024.
the 3.5" floppy is a perfect example - however, we are referring to the term kilobyte, megabyte and gigabyte - not necessarily the letters K M and G....
when using those, they most definitely haven't been just 1024....
when a term's meaning is decimal, it's kind of hard to apply it to binary. to state that "everyone does it" or "everyone has always done it" is bullshit, as obviously, everyone hasn't always done it, or there would never have been a need to differentiate between them.
Now, if you wanted to say that using the terms kilobyte implies 1024 bytes, that's one thing. To say that kilobyte *means* 1024 bytes, unfortunately, that's wrong. Hell, even the modem industry did that - when talking about Kb, rather than KB, they meant exactly what they said. 9600 baud meant 9.6Kb or 9600 bits per second not 9830.4 bits per second.
Yet when you deny members entry, because "there is no more room left", then let 5 more pro-MS members in, is that following rule of law? or is it breaking it?
When you say the vote is over, ask those who voted against to leave, then take a new vote, is that following the rule of law? or is it breaking it?
Remember, each of these types of events did occur according to reports.
It seems kind of odd to me that certain members of the ISO are fighting so hard to defend their questionable actions during the process. Could it be they are afraid of what may surface during an investigation of what really happened? Could it be they are afraid of what they might lose if it's overturned? Just curious...
Piracy to use the term loosely, hasn't become more prevalant. Sales are declining because they keep putting out garbage, with audio-compression schemes to increase volume and distortion levels.
Having been in the industry for over 24 years, I truly do understand the acronymns and usage.
I've been exposed to almost every variation of usage for the KB/MB/GB you can imagine.
kilo, mega, giga are all metric terms - base 10. kibi, mibi, gibi are all binary terms - base 2.
I just want drive manufacturers to use the term that's appropriate - and since it was the computer nerds who misappropriated the decimal metric enumaration schemes for computer usage, we only have ourselves to blame.
The IEC/ISO standards defining kibi, mibi, gibe, etc. were not developed by idiots, but by people who put at least a bit of thought into it, to express a metric-binary enumaration. kilo-binary, mega-binary, giga-binary - it becomes very clear what we are talking about.
With the past usage of kilobyte to mean 1000 bytes, or 1024 bytes, and megabyte to mean 1000*1000 or 1000*1024 or 1024*1024 (remember the 3.5" floppy - that was 1000*1024) - the amount of flexibility or inability to be accurate to all people, makes those terms too general.
now, since they like to use big, round numbers, lets see them put out the 1TiB or 1.5TiB drive and really wow us....
And do you think that this EULA provision would stand up in court?
Your honor, the motherboard died, I replaced it with another make/model, and now M$ tells me I have to buy another license? I object....
Especially when with that shrink-wrapped OEM license, in most cases, you never got to see/read the EULA before purchasing, and in no-way, shape, or form agreed to it.
Most of the time, if you ask someone, did you read the EULA, you get, huh?
Yes, I'll agree it could be taken that way, but I'll also state that it would fall into a grey area..
ie - you bought a license - xyz vendor may have paid less for that license as a volume distributor, but it's a valid license. I don't believe this application of the EULA would hold up in court if ever taken to test.
If you can transfer the OS when the system is sold, you can surely transfer the license when a component makes the system unusable, and replace failed component.
And laptops can be repaired - system boards, keyboards, power-supplies, wireless, lan, video are often times sub-components in many laptops, that can be commoditized and dropped into the same chassis - the number of options is fewer, but the idea is the same... motherboard goes out, it gets replaced/repaired - your license stays the same.
> Once these become mainstream, think of the poor software utility companies like GRC (spinrite) and Diskeeper Corporation..... One of their main revenue streams gone.... >
Considering that most oem's allow you to buy an oem license with as little as a hard drive purchase, yank the drive, move it elsewhere - copy it to another drive prior to that drive failing, and done..
so yeah, the eula means something, just depends on what the license is tied to...
if it's tied to the pc, and the motherboard, video card, power supply, and harddrive all get replaced, is it the case that the license is tied to? or was it just a license and as you've swapped out parts, it carries over....
But could it be that the geeks are buying them with XP, just to get another XP license to use for something else, knowing full well they can load their own Linux on it?
While the housewives, not really thinking about it - go with the cheaper model which just happens to have Linux pre-loaded?
From what I've read, it sounds like 3 things are happening.
1st thing - files are being broken up into chunks and randomly encrypted. 2nd thing - these randomly encrypted chunks are being distributed out, to random locations within the brightnet. 3rd thing - the mapping of the encrypted chunks, as well as decryption keys are being stored in a URL string.
Now - any member of the brightnet can be held as offering up storage for various bits, and unless they have the keys, have no way of knowing what those bits are. No one person has enough bits stored locally to recreate the entire file. This means that no one person has the entire set of data, so they themselves could not be held accountable for copyright violation.
The person with the keys, as long as they don't distribute them, also cannot be held accountable for copyright violation, they are just storing their own data, which due to fair use still treading water, is not considered illegal.
Now - as soon as someone shares the keys, they can - and probably should, be held accountable for copyright violation, in the form of distribution. If someone were to steal the keys from said person, then no, they should not be held accountable, but due to the way the RIAA/MPAA they would probably try to claim that they did it anyway.
So, this methodology does not, in and of itself, constitute a shield to copyright infringement, but it does give a novel approach to distributed data storage, and protection.
Thanks for the enlightenment - that I hadn't seen...
And yes, when I do get to the point of having enough equipment to do this, I will be wanting at least 10TB of storage, possibly more. I eventually would like to have my entire CD/DVD/??? collection migrated to online storage so that I can use a keyboard to make my selection and watch from my video room couch/easy chair.
Slashdot Mirror
Just have to look at where it *came from*... yup... that's right...
Follow the money trail, then see if there's that pesky old "conflict of interest" thing going on...
Uhm - wtf? my freak here again?
Let's see - company applies for massive tax credits, then fires everyone after receiving it, and outsourcing...
Yup - that sure smells of fraud alright... In order to get the money, you have to provide the jobs in Florida (AND KEEP THEM IN FLORDIA)...
You know, point them in the right direction... Sure sounds like fraud or scam to me...
Sounds like grounds for a massive civil lawsuit... (all the workers impacted by the layoffs) aimed directly at Habib...
Having been a member of the original beta of WoW, and one of the first to stop playing WoW after it's release, trust me - it had more than it's share of missing content, and broken features.
It's had a lot of polish time since release, and it seems a lot of people have forgotten the issues - such as unscheduled patch windows, weekly outages to reboot servers that apparently had memory leaks, database corruption issues, etc...
Back then, everyone compared the upstart WoW to Everquest, and not kindly...
Has anyone done an audit of EVP Mitchell Habib's bank accounts and lifestyle????
It might be nothing, but then again, it might not....
Thanks for the personal attacks, it shows your level of inteligence in how you choose to respond to what should be a civil conversation.
I'm saying that the computer industry, as a whole has totally made the terms Kilo, Mega and Giga ambiguous, with no strict definition of the terms.
This is why they came up with the Kibi, Mibi, etc...
To want to stick to an archaic, inexact terminology, also expresses a desire for things to never change.
I'm perfectly fine with changing to the exabinary notation, and leaving the metric (base 10) notation behind me, you should be as well, as there would be no way they could use those terms with any other meaning.
Today, they get away with it because they can point to a dictionary that shows that metric is a base 10 system, not a binary system.
So, regardless of your desire to stick with what wasn't, it's time to move on.. Maybe if the terms didn't sound so bad, they would have caught on sooner.
I'd like to see a class action suit brought against storage manufacturers forcing them to use exabinary, as it is just as misleading as the 19" monitor (17.1" visible) used to be.
dude - K M G - have NOT always stood for factors of 1024.
the 3.5" floppy is a perfect example - however, we are referring to the term kilobyte, megabyte and gigabyte - not necessarily the letters K M and G....
when using those, they most definitely haven't been just 1024....
when a term's meaning is decimal, it's kind of hard to apply it to binary.
to state that "everyone does it" or "everyone has always done it" is bullshit, as obviously, everyone hasn't always done it, or there would never have been a need to differentiate between them.
Now, if you wanted to say that using the terms kilobyte implies 1024 bytes, that's one thing. To say that kilobyte *means* 1024 bytes, unfortunately, that's wrong.
Hell, even the modem industry did that - when talking about Kb, rather than KB, they meant exactly what they said. 9600 baud meant 9.6Kb or 9600 bits per second not 9830.4 bits per second.
Yet when you deny members entry, because "there is no more room left", then let 5 more pro-MS members in, is that following rule of law? or is it breaking it?
When you say the vote is over, ask those who voted against to leave, then take a new vote, is that following the rule of law? or is it breaking it?
Remember, each of these types of events did occur according to reports.
It seems kind of odd to me that certain members of the ISO are fighting so hard to defend their questionable actions during the process. Could it be they are afraid of what may surface during an investigation of what really happened? Could it be they are afraid of what they might lose if it's overturned? Just curious...
Piracy to use the term loosely, hasn't become more prevalant. Sales are declining because they keep putting out garbage, with audio-compression schemes to increase volume and distortion levels.
Then they wonder why they're losing money...
Good gawd *IAAs, get a clue...
fack - I can't spell today... unumeration.... gah - I thought that looked wrong...
Having been in the industry for over 24 years, I truly do understand the acronymns and usage.
I've been exposed to almost every variation of usage for the KB/MB/GB you can imagine.
kilo, mega, giga are all metric terms - base 10.
kibi, mibi, gibi are all binary terms - base 2.
I just want drive manufacturers to use the term that's appropriate - and since it was the computer nerds who misappropriated the decimal metric enumaration schemes for computer usage, we only have ourselves to blame.
The IEC/ISO standards defining kibi, mibi, gibe, etc. were not developed by idiots, but by people who put at least a bit of thought into it, to express a metric-binary enumaration. kilo-binary, mega-binary, giga-binary - it becomes very clear what we are talking about.
With the past usage of kilobyte to mean 1000 bytes, or 1024 bytes, and megabyte to mean 1000*1000 or 1000*1024 or 1024*1024 (remember the 3.5" floppy - that was 1000*1024) - the amount of flexibility or inability to be accurate to all people, makes those terms too general.
now, since they like to use big, round numbers, lets see them put out the 1TiB or 1.5TiB drive and really wow us....
Just doesn't sound as good as the 1.5TB drive now does it...
When do we start the push to force drive manufactures to advertise in real capacity, not the misleading, never attainable capacities...
Unless you can write partial blocks, you can never get 1,500,000,000,000 bytes onto a 1.5TB drive, due to rounding, CHS, TPS, BpB and others.
I won't even go into the AS/400 use of 520byte blocks vs factor of 512byte blocks for most systems.
---- grumbles off into a corner
I suppose so... but others might not think it through and do it, or others might think it through and do it..
Otherwise, how would you explain geeks going with XP? Surely not to play games on the EeePC unless they were pseudo-geeks....
Hmmm - wonder if they have them pre-loaded with Solaris x86???? That might be interesting...
And do you think that this EULA provision would stand up in court?
Your honor, the motherboard died, I replaced it with another make/model, and now M$ tells me I have to buy another license? I object....
Especially when with that shrink-wrapped OEM license, in most cases, you never got to see/read the EULA before purchasing, and in no-way, shape, or form agreed to it.
Most of the time, if you ask someone, did you read the EULA, you get, huh?
Yes, I'll agree it could be taken that way, but I'll also state that it would fall into a grey area..
ie - you bought a license - xyz vendor may have paid less for that license as a volume distributor, but it's a valid license. I don't believe this application of the EULA would hold up in court if ever taken to test.
If you can transfer the OS when the system is sold, you can surely transfer the license when a component makes the system unusable, and replace failed component.
And laptops can be repaired - system boards, keyboards, power-supplies, wireless, lan, video are often times sub-components in many laptops, that can be commoditized and dropped into the same chassis - the number of options is fewer, but the idea is the same... motherboard goes out, it gets replaced/repaired - your license stays the same.
uhm - no...
the ls entries listed above work perfectly well on Solaris, AIX, HP-UX and Linux.
ksh is the only shell I use, although I'm sure it would work with bash.
I primarily work on Solaris (SPARC/x86/x64) platforms - I won't go into any kind of flame wars over it, it's just what my company uses primarily.
>
Once these become mainstream, think of the poor software utility companies like GRC (spinrite) and Diskeeper Corporation..... One of their main revenue streams gone....
>
Considering that most oem's allow you to buy an oem license with as little as a hard drive purchase, yank the drive, move it elsewhere - copy it to another drive prior to that drive failing, and done..
so yeah, the eula means something, just depends on what the license is tied to...
if it's tied to the pc, and the motherboard, video card, power supply, and harddrive all get replaced, is it the case that the license is tied to? or was it just a license and as you've swapped out parts, it carries over....
or an even shorter solution...
ls -c1 | grep "^a"
and if you wanted upper and lower-case a files,
ls -c1 | grep -i "^a"
But could it be that the geeks are buying them with XP, just to get another XP license to use for something else, knowing full well they can load their own Linux on it?
While the housewives, not really thinking about it - go with the cheaper model which just happens to have Linux pre-loaded?
Just a thought...
it was fixed years ago....
find . -name "a*" -prune -exec ls -ld {} \;
(note: this command line was generated by reading the man page for gnu find - may not work on all unix/linux variants)
Now we can't even spell for posting of stories? Sheesh... Or are we afraid of some potential copyright issues over the term Olympics?
From what I've read, it sounds like 3 things are happening.
1st thing - files are being broken up into chunks and randomly encrypted.
2nd thing - these randomly encrypted chunks are being distributed out, to random locations within the brightnet.
3rd thing - the mapping of the encrypted chunks, as well as decryption keys are being stored in a URL string.
Now - any member of the brightnet can be held as offering up storage for various bits, and unless they have the keys, have no way of knowing what those bits are. No one person has enough bits stored locally to recreate the entire file. This means that no one person has the entire set of data, so they themselves could not be held accountable for copyright violation.
The person with the keys, as long as they don't distribute them, also cannot be held accountable for copyright violation, they are just storing their own data, which due to fair use still treading water, is not considered illegal.
Now - as soon as someone shares the keys, they can - and probably should, be held accountable for copyright violation, in the form of distribution.
If someone were to steal the keys from said person, then no, they should not be held accountable, but due to the way the RIAA/MPAA they would probably try to claim that they did it anyway.
So, this methodology does not, in and of itself, constitute a shield to copyright infringement, but it does give a novel approach to distributed data storage, and protection.
Thanks for the enlightenment - that I hadn't seen...
And yes, when I do get to the point of having enough equipment to do this, I will be wanting at least 10TB of storage, possibly more.
I eventually would like to have my entire CD/DVD/??? collection migrated to online storage so that I can use a keyboard to make my selection and watch from my video room couch/easy chair.