Most authors retain the copyright to their own works (unlike anyone involved with music or movies). Chances are your great-great grandmother held the original copyright, and it's now held by her estate or a descendant. I'm not very familiar with how wills work, but, if it wasn't explicitly mentioned, it probably passed to her husband or child(ren) when she died. It's likely still in your family, somewhere.
If you can track down your great-great grandmother's will (and possibly the wills of those who her possessions went to, you can probably figure it out with a little work.
All the medics in that game can do is to stop you bleeding -- not even heal you at all. It makes you stop *losing* health (though sometimes you'll stop bleeding on your own, depending on the wound), and I think it restores a bit of your mobility. It's been years since I last played it, though, so the details are hazy. I do remember if you took more than about one or two bullets, you were almost certainly dead, though. Made for interesting strategy requirements at times.
The internet interprets censorship as damage and routes around it. It's an older quote, but it's still accurate. If the telcos start putting in more and more blocks, people will find ways around them. Strong encryption (as is already used in some BitTorrent clients), stenography, more decentralisation, and even, if things get pushed so far that such 'digital' techniques are hard to avoid censorship with, a return to the 'sneakernet' (or smaller, semi-private neighbourhood/town/city-wide, possibly wireless, networks).
The cat is long out of the bag. No matter how much they do, they're never going to get it in there again. The best they can do, in the long run, is limit the damage by giving people what they evidently want -- no DRM, low prices, convenient access, among other things.
The article linked to from the Slashdot story discusses this a bit in the "No Significant Pattern" subsection, noting that the trends didn't change much in the late 1990s (compared to the 1970s and 1980s) when cellphone usage increased far faster than the cancer rates -- the most anomalous change being a larger-than-average increase in tumors for women over 60 (who were stated to already be the most at-risk subgroup).
It's not conclusive proof, of course, but it's a fairly solid correlation, particularly given the lack of any evidence that cellphones do cause cancer.
Not stopping there, there is at least one major study that shows no significant link between cellphones and cancer -- not just a lack of any confirmation.
They should keep these sort of 'warning' labels to items that have solid, reproducible evidence of significant increases in risks of cancer -- like cigarettes. If they start slapping them on everything that they (in their position as 'a legislator') think might cause cancer, these sort of warnings will lose all meaning.
Not really, since the salt would need to be publicly known for Gravatar to work (and it would break any backwards compatibility to add it in now). This was a 'social engineering' attack, not a rainbow table lookup – it pieced the name together with common providers to find a matching MD5. Salt would just add a single extra step.
I believe it's exactly the same problem/attack as was brought up about MicroID in the past. The idea of Pavatar is a much better way to do this sort of avatar-finding (though the decentralisation comes with its own problems), since it relies on a public web address instead of a semi-private e-mail address.
It's still vendor lock in if there's no competing product that reads their open formats.
Umm... There are a huge number of programs that read/write ODF (OpenOffice's default format). Wikpedia has a fairly extensive list of software that handles the various ODF files.
Except for the fact that the phone will likely still have only one SIM card, only one telephone number, and you'll now be on-call when you need your phone for personal business.
Ah, I didn't realise 'gb' was in common usage for gigabits. I've more commonly seen it referred to by Gbit/gbit or Gbps/gbps (when someone isn't using 'Gb'). I'm a bit of a stickler for proper units and prefixes for some reason -- maybe I'm just anal about clarity or something. Someone drag Bios_Hakr back here to clarify all this!:-)
Though I don't think I've ever actually seen someone measure upload amounts in gigabits. Well, until (possibly) the OP, I suppose.;-)
It's more like 600-800 KiB/s (assuming the grandparent was just lazy in not capitalising any part of the 'gb's they used). 2-3 GiB per hour is about 700 KiB/s. 2-3 Gib is only about 80-100 KiB/s.
Handy listing of prefixes (si followed by binary for each): k: 1000 (yes, the 'k' prefix is supposed to be lowercase) Ki: 1024 (yes, they decided to capitalise this 'K') M: 1000000 Mi: 1048576 (1024 * 1024; 2^20) G: 1000000000 Gi: 1073741824 (1024 * 1024 * 1024; 2^30)
Handy listing of units: b: bit (a single zero or one) B: byte (an octet of bits; eight bits)
This doesn't even seem to be fair use to me. It doesn't really fit the criteria. Maybe "teaching" or "research", but you'd have to kinda stretch it – and fight it out in court, as the parent mentioned. Fair use is a lot more specific than "anything I think doesn't hurt them", after all – it, and fair dealing, have quite specific categories that the usage of a copyrighted work must fall into, as well as being fought in court if challenged on the reasoning.
Yes, it's stupid of them (since it's just going to piss off their customer base), but it hardly seems like an incorrect usage of copyright law. Stupid, yes. Unethical, maybe. Incorrect, not likely.
I know for a fact that Google has a ton of spy crap watching us on the web.
And all Chrome OS does is the web. It runs all your Google Apps, on your Google Browser, on your Google OS, in your Google Life (beta!). They're never going to make features like JavaScript or cookies able to be turned off, or add any real ability to run adblocking (there goes the revenue stream). If they intend to subsidise the OS or the netbooks that are likely to run it, expect to see the hardware locked down so you can't reflash it with a custom image, and expect to see advertising embedded everywhere, also without the ability for you to disable any tracking of your movements (hey, all those ads need to be context-sensitive, after all!).
Yes, that's a bit of a cynical view of Google, but I've found it to serve me well to be a bit paranoid about my personal data in the past.
Not entirely. In some cases they can be, but not in others.
They might be if something is opaque enough that anyone who is not a 'dummy' will simply fail to produce something working. Like trying to create an assembly program with no knowledge. However, they might not be if they're more in-between incomprehensibility and English. Like someone enters the wrong command into a shell.
For the latter, imagine if, instead of "rm -rf *", you'd have to type "delete all files in this folder, and I'm sure I want to do this". It's more verbose and much less efficient, but it's both more human-readable and likely much more dummy-proof. If someone can more easily understand what they're doing, they're more likely to stop and realise it may not be what they actually intended to do.
I wonder if Apple's 'late' release of a public SDK and the app store (compared to the initial release of the iPhone) actually significantly helped the app store. Instead of opening it up when there's only a tiny bit of market share (with anyone who starts early being driven away by the lack of customers), they opened it up when there was demand (quite literally) for apps and enough of a market share to support it. And it seems to have worked out very, very well for them and the developers.
Maybe Apple's original "use the web to make apps! we don't need a SDK!" was just misdirection away from their real plan... I suppose it depends on how devious you give Apple credit for being, whether this is a possibility or not.
There are (by my count) 88 characters that should be standardly-enterable on almost any keyboard. Assuming that anyone who is a crazy felon is at least as paranoid as I am, they'll be able to memorise a 12-character random password without too much trouble. There are around 2.16x10^23 possibilities (88^12), taking, at 4 million per second, over 1.7 billion years to test all of them. Once they triple this with 60 PS3s, they'll only be down to 569 million years or so!
Of course this could crack any old user's password in a few minutes – perhaps that's their real target, the general population.
Like I said, I only use the TOR on my ironkey when I'm say at class on an open wifi signal.
What are you doing at class that needs privacy/security from those around you on wifi, but not from an unknown party (the TOR nodes you're routing through)?
In thirty minutes, post the status "lol watching tv" to Facebook. It's not complete (due to logins and cookies not being utilised by curl in most cases), but it explains the idea pretty clearly if you know a bit about at and curl.
I'm pretty certain most pirated content (yarr!) doesn't even use analog copying. Most of them just break the DRM somehow, since DRM can never be perfect... This is just another method of control and forced upgrades for the average consumer, many of whom couldn't afford it. When their income goes down again, they'll say "Look, the pirates did it again! We need more laws!".
The phrase originates from a story where the crying of "WOLF! WOLF!" is about the wolf coming to town to devour the village – not that there are no wolves nearby, and certainly not that no wolves exist.
Apple could still be a wolf (whether they are or aren't is debatable), but they're not coming to devour the village right now.
I'm not sure how modern automatic cars handle it (I drive a few-year-old standard, which still uses a physical key), but this likely causes the engine to rev out of control. Granted, better situation than having the car hurtling towards high speeds on a road, but it's not even close to the equivalent of turning the car off, not at all.
I'm fairly certain that most places have similar laws. I know my car's speedometer (and odometer) reads about 3-5% faster than actual speed(/distance), tested against both a GPS and road distance markers. It's a late 2006 Jetta station wagon.
Yes, there are some employees who have access to the e-mails, but they are not exposed on a regular basis to the content of those e-mails, unless they're excessively abusing the power they've been trusted with.
Slashdot Mirror
Most authors retain the copyright to their own works (unlike anyone involved with music or movies). Chances are your great-great grandmother held the original copyright, and it's now held by her estate or a descendant. I'm not very familiar with how wills work, but, if it wasn't explicitly mentioned, it probably passed to her husband or child(ren) when she died. It's likely still in your family, somewhere.
If you can track down your great-great grandmother's will (and possibly the wills of those who her possessions went to, you can probably figure it out with a little work.
All the medics in that game can do is to stop you bleeding -- not even heal you at all. It makes you stop *losing* health (though sometimes you'll stop bleeding on your own, depending on the wound), and I think it restores a bit of your mobility. It's been years since I last played it, though, so the details are hazy. I do remember if you took more than about one or two bullets, you were almost certainly dead, though. Made for interesting strategy requirements at times.
The internet interprets censorship as damage and routes around it. It's an older quote, but it's still accurate. If the telcos start putting in more and more blocks, people will find ways around them. Strong encryption (as is already used in some BitTorrent clients), stenography, more decentralisation, and even, if things get pushed so far that such 'digital' techniques are hard to avoid censorship with, a return to the 'sneakernet' (or smaller, semi-private neighbourhood/town/city-wide, possibly wireless, networks).
The cat is long out of the bag. No matter how much they do, they're never going to get it in there again. The best they can do, in the long run, is limit the damage by giving people what they evidently want -- no DRM, low prices, convenient access, among other things.
The article linked to from the Slashdot story discusses this a bit in the "No Significant Pattern" subsection, noting that the trends didn't change much in the late 1990s (compared to the 1970s and 1980s) when cellphone usage increased far faster than the cancer rates -- the most anomalous change being a larger-than-average increase in tumors for women over 60 (who were stated to already be the most at-risk subgroup).
It's not conclusive proof, of course, but it's a fairly solid correlation, particularly given the lack of any evidence that cellphones do cause cancer.
no real studies confirm the notion
Not stopping there, there is at least one major study that shows no significant link between cellphones and cancer -- not just a lack of any confirmation.
They should keep these sort of 'warning' labels to items that have solid, reproducible evidence of significant increases in risks of cancer -- like cigarettes. If they start slapping them on everything that they (in their position as 'a legislator') think might cause cancer, these sort of warnings will lose all meaning.
Perian is also a little low on developers, though obviously not as much so as VLC...
Not really, since the salt would need to be publicly known for Gravatar to work (and it would break any backwards compatibility to add it in now). This was a 'social engineering' attack, not a rainbow table lookup – it pieced the name together with common providers to find a matching MD5. Salt would just add a single extra step.
I believe it's exactly the same problem/attack as was brought up about MicroID in the past. The idea of Pavatar is a much better way to do this sort of avatar-finding (though the decentralisation comes with its own problems), since it relies on a public web address instead of a semi-private e-mail address.
It's still vendor lock in if there's no competing product that reads their open formats.
Umm... There are a huge number of programs that read/write ODF (OpenOffice's default format). Wikpedia has a fairly extensive list of software that handles the various ODF files.
Except for the fact that the phone will likely still have only one SIM card, only one telephone number, and you'll now be on-call when you need your phone for personal business.
I'd expect that a good percent of the jury would be too...
Ah, I didn't realise 'gb' was in common usage for gigabits. I've more commonly seen it referred to by Gbit/gbit or Gbps/gbps (when someone isn't using 'Gb'). I'm a bit of a stickler for proper units and prefixes for some reason -- maybe I'm just anal about clarity or something. Someone drag Bios_Hakr back here to clarify all this! :-)
Though I don't think I've ever actually seen someone measure upload amounts in gigabits. Well, until (possibly) the OP, I suppose. ;-)
It's more like 600-800 KiB/s (assuming the grandparent was just lazy in not capitalising any part of the 'gb's they used). 2-3 GiB per hour is about 700 KiB/s. 2-3 Gib is only about 80-100 KiB/s.
Handy listing of prefixes (si followed by binary for each):
k: 1000 (yes, the 'k' prefix is supposed to be lowercase)
Ki: 1024 (yes, they decided to capitalise this 'K')
M: 1000000
Mi: 1048576 (1024 * 1024; 2^20)
G: 1000000000
Gi: 1073741824 (1024 * 1024 * 1024; 2^30)
Handy listing of units:
b: bit (a single zero or one)
B: byte (an octet of bits; eight bits)
Combination examples:
gb: meaningless (g is not a prefix)
Gb: gigabit (1000000000 bits)
Gib: gibibit (1073741824 bits)
kb: kilobit (1000 bits)
kB: kilobyte (1000 bytes; 8000 bits)
KiB: kibibyte (1024 bytes; 8192 bits)
This doesn't even seem to be fair use to me. It doesn't really fit the criteria. Maybe "teaching" or "research", but you'd have to kinda stretch it – and fight it out in court, as the parent mentioned. Fair use is a lot more specific than "anything I think doesn't hurt them", after all – it, and fair dealing, have quite specific categories that the usage of a copyrighted work must fall into, as well as being fought in court if challenged on the reasoning.
Yes, it's stupid of them (since it's just going to piss off their customer base), but it hardly seems like an incorrect usage of copyright law. Stupid, yes. Unethical, maybe. Incorrect, not likely.
I know for a fact that Google has a ton of spy crap watching us on the web.
And all Chrome OS does is the web. It runs all your Google Apps, on your Google Browser, on your Google OS, in your Google Life (beta!). They're never going to make features like JavaScript or cookies able to be turned off, or add any real ability to run adblocking (there goes the revenue stream). If they intend to subsidise the OS or the netbooks that are likely to run it, expect to see the hardware locked down so you can't reflash it with a custom image, and expect to see advertising embedded everywhere, also without the ability for you to disable any tracking of your movements (hey, all those ads need to be context-sensitive, after all!).
Yes, that's a bit of a cynical view of Google, but I've found it to serve me well to be a bit paranoid about my personal data in the past.
Not entirely. In some cases they can be, but not in others.
They might be if something is opaque enough that anyone who is not a 'dummy' will simply fail to produce something working. Like trying to create an assembly program with no knowledge. However, they might not be if they're more in-between incomprehensibility and English. Like someone enters the wrong command into a shell.
For the latter, imagine if, instead of "rm -rf *", you'd have to type "delete all files in this folder, and I'm sure I want to do this". It's more verbose and much less efficient, but it's both more human-readable and likely much more dummy-proof. If someone can more easily understand what they're doing, they're more likely to stop and realise it may not be what they actually intended to do.
I wonder if Apple's 'late' release of a public SDK and the app store (compared to the initial release of the iPhone) actually significantly helped the app store. Instead of opening it up when there's only a tiny bit of market share (with anyone who starts early being driven away by the lack of customers), they opened it up when there was demand (quite literally) for apps and enough of a market share to support it. And it seems to have worked out very, very well for them and the developers.
Maybe Apple's original "use the web to make apps! we don't need a SDK!" was just misdirection away from their real plan... I suppose it depends on how devious you give Apple credit for being, whether this is a possibility or not.
There are (by my count) 88 characters that should be standardly-enterable on almost any keyboard. Assuming that anyone who is a crazy felon is at least as paranoid as I am, they'll be able to memorise a 12-character random password without too much trouble. There are around 2.16x10^23 possibilities (88^12), taking, at 4 million per second, over 1.7 billion years to test all of them. Once they triple this with 60 PS3s, they'll only be down to 569 million years or so!
Of course this could crack any old user's password in a few minutes – perhaps that's their real target, the general population.
Like I said, I only use the TOR on my ironkey when I'm say at class on an open wifi signal.
What are you doing at class that needs privacy/security from those around you on wifi, but not from an unknown party (the TOR nodes you're routing through)?
In thirty minutes, post the status "lol watching tv" to Facebook. It's not complete (due to logins and cookies not being utilised by curl in most cases), but it explains the idea pretty clearly if you know a bit about at and curl.
I'm pretty certain most pirated content (yarr!) doesn't even use analog copying. Most of them just break the DRM somehow, since DRM can never be perfect... This is just another method of control and forced upgrades for the average consumer, many of whom couldn't afford it. When their income goes down again, they'll say "Look, the pirates did it again! We need more laws!".
I imagine finding anything that expires on the 23th of any month would be very weird...
The phrase originates from a story where the crying of "WOLF! WOLF!" is about the wolf coming to town to devour the village – not that there are no wolves nearby, and certainly not that no wolves exist.
Apple could still be a wolf (whether they are or aren't is debatable), but they're not coming to devour the village right now.
I'm not sure how modern automatic cars handle it (I drive a few-year-old standard, which still uses a physical key), but this likely causes the engine to rev out of control. Granted, better situation than having the car hurtling towards high speeds on a road, but it's not even close to the equivalent of turning the car off, not at all.
I'm fairly certain that most places have similar laws. I know my car's speedometer (and odometer) reads about 3-5% faster than actual speed(/distance), tested against both a GPS and road distance markers. It's a late 2006 Jetta station wagon.
Yes, there are some employees who have access to the e-mails, but they are not exposed on a regular basis to the content of those e-mails, unless they're excessively abusing the power they've been trusted with.