Of course people won't be changing their sites for the iPhone. Hovers and mouseovers generally aren't used to direct action, just to highlight the potential for it.
There are a *few* UI mechanisms that may take advantage of the mouseover, but not much.
And if your site has hover-over-drop-down menus, you're already an asshole. Nothing's more annoying than going from the system menu bar down to a link only to have it obscured by a menu you didn't click on.
You kidding me? That's more interesting than anything else. I'd love to see *why* it does that, and *how*.
For one thing, WGA is supposed to check Product key, PC manufacturer, Windows version, PID/SID, BIOS information, BIOS MD5 Checksum, Language setting and version, and Hard drive serial number, among other things.
Since your winver and product key don't technically exist (I believe the former comes up as Win 98), I don't see how WGA gets a false positive in this case (which means it's also going to be an easy bug to track down).
But, theoretically, since xubuntu doesn't need a 'valid' key, it may throw random numbers out (which would be very unlikely to trip the 'pirated' check, but would mean WGA doesn't check if your key is valid.
Oh, and I like disassembling things. It's a hobby. Also, it's why I like Nokias; you can literally take them down to a circuit board and about 20 little chachkis before you'd have to start desoldering stuff to get it any further apart. You can hardly say that about a RAZR.
I'm a little neurotic about asthetics, and I have a high skin-grease content (and I tend to drop food into the 'board; I work at home, so I eat lunch at my computer pretty often), and I smoke. As a result, my keys get unacceptably yellow/brown and sticky every two months or so. Nothing to do with bacteria, really, though it's good to know they're gone if they were there.
Every two months I disassemble my keyboard and run the plastic bits through the dishwasher. I hand-clean the little metal chachkis, and dust off the electronics. Then I reassemble. Works pretty well, I think.
The funniest solution was the first comment on that blog:
"To solve these problems, it would be best if developers stopped using languages like Ajax, HTML, Perl, e.t.c. Instead webpages should be written in new safe language which is compiled and executed within a sandbox. This is somewhat like writing the entire webpage as a Java Applet and the applet alone runs. (No HTML, Javascript, e.t.c.)"
Ok. I didn't know about all that. Still, it's more oxide impurity level than damage; it doesn't actually hurt the RAM. And it dissipates 'eventually' - which could mean from minutes to months, so maybe you could recover the data that way.
Still an academic question, though; the instantaneous data found on the RAM would only have the IP addresses of the last 10, perhaps 20 visitors, and would be nigh-impossible to extract.
Ok. First off, 'delivered as a text file' is meaningless; we're talking about binary data. You can't just convert back and forth willy nilly. Does he want a hex dump? Would he (or, hell, anyone) know what to *do* with a hex dump?
Meanwhile, an apache process occupies roughly 13M of ram.
What refresh rate? Anything that could be reasonably likely to catch a 'hit' (and, thus, contain useful data) would need to be >1Hz - but that would require storage in excess of 1.06TB/day for *maybe* a thousand or so IP addresses.
That's, of course, for each Apache process. There's normally two, and they branch off if they get enough traffic.
Riiiight.
Of course, the server could parse out this memory dump and filter for IP addresses (which, in Apache, are indistinguishable from any other spot in memory; they're just stored as sets of four bytes - ie: impossible to distinguish).
But then, Apache actually has the capability of doing this: it's called 'logging' - which the judge can't or won't specifically request.
But this is fine. I suggest emailing a RAM dump of the Apache processes, hexed, gzipped, once every five seconds.
"Ultimately, pulling user information off a server's RAM might be a bigger privacy problem than it's worth, said one file sharer, who asked to remain anonymous."
Not to mention that it's actually impossible. Anything the MPAA wants off the server's RAM has already been overwritten. This is actually the most retarded court decision I've heard of in a long time.
"Your not reading the "state" of the bit at all , but the damage the flow of electricity is doing to the oxide on the chip itself."
>.- (brain snap)
Wow. HUGE misunderstanding of how RAM works.
In DRAM, each bit is stored in a capacitor, which needs continuously refreshed (ie: rewritten). In SRAM, each bit is stored in a nifty little transistor/capacitor array, just just needs continuously powered.
I don't know where this oxide damage nonsense comes from, but... wow.
Anyway, this is all academic and based on a bigger misunderstanding by the judge; see, even if their RAM chips were in some way non-volitile (flash, EEPROM, something else unreasonably expensive, short-lived, slow, and generally better suited as portable harddrives and settings holders), they'd only have that nanosecond's connection information - hardly a 'log' of any sort.
Ok, I know you're an AC, and this is probably trollfeeding but where the hell did you get the DRM shill idea?
My suggestion to the record execs has to do with *removing* DRM by providing a far less restrictive alternative.
Unless you consider culpability for what you buy to be DRM. It's not; your rights are unrestricted, all my suggestion does is allow for a way for a person to be held accountable for their purchases.
Of course, there's the theft argument. But then, such a thing would have to be determined in a civil court. You know, like most things.
If a person reports the theft, he's cool. If he doesn't, he can just claim theft and the plaintiff would have to show that theft didn't happen. More likely is that a real pirate wouldn't even *buy* from an online store - they already don't.
Slashdot Mirror
Aw, how cute. Look, another corporate shill finds his way to slashdot.
Does it count as 'another' woman if it's a different one each time?
I believe the correct response for this is "Pics or it didn't happen."
'Course, I'd prefer video, but it just wouldn't be Slashdot without the idiotic memes, would it?
The question is stupid.
Of course people won't be changing their sites for the iPhone. Hovers and mouseovers generally aren't used to direct action, just to highlight the potential for it.
There are a *few* UI mechanisms that may take advantage of the mouseover, but not much.
And if your site has hover-over-drop-down menus, you're already an asshole. Nothing's more annoying than going from the system menu bar down to a link only to have it obscured by a menu you didn't click on.
Props for the random inclusion of everyone's favorite british robot butler - aside from Mr. Butlertron.
You kidding me? That's more interesting than anything else. I'd love to see *why* it does that, and *how*.
For one thing, WGA is supposed to check Product key, PC manufacturer, Windows version, PID/SID, BIOS information, BIOS MD5 Checksum, Language setting and version, and Hard drive serial number, among other things.
Since your winver and product key don't technically exist (I believe the former comes up as Win 98), I don't see how WGA gets a false positive in this case (which means it's also going to be an easy bug to track down).
But, theoretically, since xubuntu doesn't need a 'valid' key, it may throw random numbers out (which would be very unlikely to trip the 'pirated' check, but would mean WGA doesn't check if your key is valid.
Thanks for that. Never seen it written, but my girlfriend has me hooked on the word.
I used to say gatsadili.
*smacks you*
Don't use soap; the grime on keys isn't baked on or anything, so the normal heat/impact combination does the trick.
Oh, and I like disassembling things. It's a hobby. Also, it's why I like Nokias; you can literally take them down to a circuit board and about 20 little chachkis before you'd have to start desoldering stuff to get it any further apart. You can hardly say that about a RAZR.
I'm a little neurotic about asthetics, and I have a high skin-grease content (and I tend to drop food into the 'board; I work at home, so I eat lunch at my computer pretty often), and I smoke. As a result, my keys get unacceptably yellow/brown and sticky every two months or so. Nothing to do with bacteria, really, though it's good to know they're gone if they were there.
Paraphrase TFA's title:
"Should the consequences of reality be imposed on politics?"
Phrased that way, the answer's pretty obvious.
Every two months I disassemble my keyboard and run the plastic bits through the dishwasher. I hand-clean the little metal chachkis, and dust off the electronics. Then I reassemble. Works pretty well, I think.
The problem is the level of knowledge to make the above post; it's frighteningly remincient of a few executives I've known.
You know, the almost-intelligent combination of buzzwords into the Stupidest Thing You've Ever Heard.
The funniest solution was the first comment on that blog:
"To solve these problems, it would be best if developers stopped using languages like Ajax, HTML, Perl, e.t.c. Instead webpages should be written in new safe language which is compiled and executed within a sandbox. This is somewhat like writing the entire webpage as a Java Applet and the applet alone runs. (No HTML, Javascript, e.t.c.)"
I'll let the vultures pick at that one...
Ok. I didn't know about all that. Still, it's more oxide impurity level than damage; it doesn't actually hurt the RAM. And it dissipates 'eventually' - which could mean from minutes to months, so maybe you could recover the data that way.
Still an academic question, though; the instantaneous data found on the RAM would only have the IP addresses of the last 10, perhaps 20 visitors, and would be nigh-impossible to extract.
Ok. First off, 'delivered as a text file' is meaningless; we're talking about binary data. You can't just convert back and forth willy nilly. Does he want a hex dump? Would he (or, hell, anyone) know what to *do* with a hex dump?
Meanwhile, an apache process occupies roughly 13M of ram.
What refresh rate? Anything that could be reasonably likely to catch a 'hit' (and, thus, contain useful data) would need to be >1Hz - but that would require storage in excess of 1.06TB/day for *maybe* a thousand or so IP addresses.
That's, of course, for each Apache process. There's normally two, and they branch off if they get enough traffic.
Riiiight.
Of course, the server could parse out this memory dump and filter for IP addresses (which, in Apache, are indistinguishable from any other spot in memory; they're just stored as sets of four bytes - ie: impossible to distinguish).
But then, Apache actually has the capability of doing this: it's called 'logging' - which the judge can't or won't specifically request.
But this is fine. I suggest emailing a RAM dump of the Apache processes, hexed, gzipped, once every five seconds.
"Ultimately, pulling user information off a server's RAM might be a bigger privacy problem than it's worth, said one file sharer, who asked to remain anonymous."
Not to mention that it's actually impossible. Anything the MPAA wants off the server's RAM has already been overwritten. This is actually the most retarded court decision I've heard of in a long time.
"Your not reading the "state" of the bit at all , but the damage the flow of electricity is doing to the oxide on the chip itself."
>.- (brain snap)
Wow. HUGE misunderstanding of how RAM works.
In DRAM, each bit is stored in a capacitor, which needs continuously refreshed (ie: rewritten). In SRAM, each bit is stored in a nifty little transistor/capacitor array, just just needs continuously powered.
I don't know where this oxide damage nonsense comes from, but... wow.
Anyway, this is all academic and based on a bigger misunderstanding by the judge; see, even if their RAM chips were in some way non-volitile (flash, EEPROM, something else unreasonably expensive, short-lived, slow, and generally better suited as portable harddrives and settings holders), they'd only have that nanosecond's connection information - hardly a 'log' of any sort.
'cept that, even if they were to send out their 'RAM logs', they'd only be for the instant a sample was taken; ie: useless.
Say wha?
Ok, I know you're an AC, and this is probably trollfeeding but where the hell did you get the DRM shill idea?
My suggestion to the record execs has to do with *removing* DRM by providing a far less restrictive alternative.
Unless you consider culpability for what you buy to be DRM. It's not; your rights are unrestricted, all my suggestion does is allow for a way for a person to be held accountable for their purchases.
Of course, there's the theft argument. But then, such a thing would have to be determined in a civil court. You know, like most things.
If a person reports the theft, he's cool. If he doesn't, he can just claim theft and the plaintiff would have to show that theft didn't happen. More likely is that a real pirate wouldn't even *buy* from an online store - they already don't.
most likely:
% defaults write apple.com.Safari IncludeDebugMenu 1
My karma was already 'excellent'. I have no need for karma whoring.
/. stripped it, but it seems to have.
Meanwhile, the preview looked correct. I don't know why
Hm.
That looks remarkably like Kate.
I think you win.
Java-based != lightweight or fast.
Also, I've used JEdit. It's crap on large files.