Not only will the person itself be under much scrutiny in the event of, say, a PDA left in a breast pocket (could be hard to discern from a block of C-4)....
That is why they have you remove them before you pass through the metal detectors.
Microsoft hasn't done this for their own reasons, but consider that they have consistently dragged their feet from day one regarding system security on Win32, Lookout, etc., and are only recently talking about end user system security integrations.
This isn't the *future* of spam, it's the *present* of spam. It's basically a way for spammers to track valid addresses - rather than wait for a bounce to kill one, wait for an open to validate one.
Could the RIAA be found on barratry? I mean, they are filing or threatening to file lawsuits to incite action - can't that be counted as barratry, which last I checked was against the law?
Click here. This guy is a software engineer that I recall doing temp contract gigs here and there. Furry fandom to the extreme, or following a tribal calling? You decide - he points to the latter, but expands on it.
My wife and I know him. By every definition, eccentric, but overall a pretty cool cat.
I say this with no authority beyond theory. I am not a programmer or a hacker.
I have been told that one *could* design aa trojan/virus/worm in assembler - but assembler, that I understand it, is very platform specific. You couldn't necessarily run code geared for an Athlon on a second-gen Pentium, and that 2g Pentium code won't have system calls of said Athlon.
What I got to telling my wife is that the only way this could happen is by either embedding in hardware or putting a software driver in.
Now figure this - who in their right mind is going to design hardware that self-destructs, outside of a military application where a self-destruct may be necessary? (Yeah, fine, MI and Star Trek and all that.) If I knowingly bought hardware that was set to let the blue smoke out of itself on a perceived copyright violation, I'd be a God damned fool.
This reminds me of those occasional commercials that the UFCW or Teamsters unions will do when urging a boycott of a particular independent non-union supermarket or two - buy ad time, say don't buy, and watch as their commercials had no effect.
If I drink decaf though, it's because of social reasons and that I don't want to go to sleep at 2:00 AM rather than 11:00 PM like is normal for me. IOW, it comes down to one thing: "Decaf coffee?...why?"
Actually, the reaction to this would be that the resulting liquid would start to carbonate as it froze. The more enclosed space, of course, the better the carbonation. (To explain, if you leave the lid off, the carbonation will not be sufficient to warrant a proper root beer, as you need pressure to properly dissolve CO2 into liquid.)
A little something I learned from watching some Mormons make root beer using Hires extract, sugar, water, and a big block o' dry ice in a bright orange Igloo brand drink cooler/dispenser.
You might keep in mind, though, that one can shoot themselves in the foot by allowing IP to become defacto standard, and then try and collect on its use. It's little more than a shot to credibility, though, but in some cases it can potentially be enough to totally disrupt a company.
You may consider what happened to Unisys with GIF a few years back (the community at larged migrated to PNG or JPG, seemingly out of protest, generally out of compliance (and GIFs these days are just crap by standards anyway)), as well as the company that is now laying claim to JPEG. The standards were established, the company came in years later ("Hey! That's ours! Pay!"), and any credibility the company had at one time was heavily crippled.
In the end, this may not be a landmark case of why you should protect your IP from the beginning if you intend to protect it (since there are now just so damn many of these cases), and I think it'll be Yet Another of these. But it will probably serve as a better example than the Unisys/GIF case.
Slashdot Mirror
Not only will the person itself be under much scrutiny in the event of, say, a PDA left in a breast pocket (could be hard to discern from a block of C-4).... That is why they have you remove them before you pass through the metal detectors.
Microsoft hasn't done this for their own reasons, but consider that they have consistently dragged their feet from day one regarding system security on Win32, Lookout, etc., and are only recently talking about end user system security integrations.
This isn't the *future* of spam, it's the *present* of spam. It's basically a way for spammers to track valid addresses - rather than wait for a bounce to kill one, wait for an open to validate one.
That's fine, but what are you running a server for if you're on a dynamic IP? That's painful from a logistical standpoint.
C'mon, this is governed by a body who is known for having spent $50k for toilet seats. You figure it out.
Could the RIAA be found on barratry? I mean, they are filing or threatening to file lawsuits to incite action - can't that be counted as barratry, which last I checked was against the law?
These guys seem to know how to make some *really* good antennas. Why not farm it out to one of these guys?
My wife and I know him. By every definition, eccentric, but overall a pretty cool cat.
I have been told that one *could* design aa trojan/virus/worm in assembler - but assembler, that I understand it, is very platform specific. You couldn't necessarily run code geared for an Athlon on a second-gen Pentium, and that 2g Pentium code won't have system calls of said Athlon.
What I got to telling my wife is that the only way this could happen is by either embedding in hardware or putting a software driver in.
Now figure this - who in their right mind is going to design hardware that self-destructs, outside of a military application where a self-destruct may be necessary? (Yeah, fine, MI and Star Trek and all that.) If I knowingly bought hardware that was set to let the blue smoke out of itself on a perceived copyright violation, I'd be a God damned fool.
Verizon customer service just plain sucks. When they were GTE it was fine, but now it's just Evil. Don't go there.
This reminds me of those occasional commercials that the UFCW or Teamsters unions will do when urging a boycott of a particular independent non-union supermarket or two - buy ad time, say don't buy, and watch as their commercials had no effect.
If I drink decaf though, it's because of social reasons and that I don't want to go to sleep at 2:00 AM rather than 11:00 PM like is normal for me. IOW, it comes down to one thing: "Decaf coffee? ...why?"
But MCA and EISA died out rather quickly. I think they were basically "left-behind" standards. IIRC, only IBM picked up on MCA bus anyway.
Ah, yes, for those who don't want the heart palpitations or the sugar, but wish to simply have carcinogen-flavored carbonated water instead.
OK, so give them IP addresses instead.
Last I checked, one was innocent until proven guilty. Maybe the media has skewed this, but does this not still hold true in a court of law?
Maybe Utah natives ("Utahans"?) could take a hint at this breakthrough strategy(TM).
Yes, but just using a Vita-Mix mixer takes all the fun out of doing it with the LN2. =^_^=
A little something I learned from watching some Mormons make root beer using Hires extract, sugar, water, and a big block o' dry ice in a bright orange Igloo brand drink cooler/dispenser.
Theodore gray is down, ladies and gentlemen. It fought well. =^_^=
APIG is investigating spam... verrrry interesting. But not funny.
There already has been. It's called Microsoft.
Look here.
Could it be then that one could find SCO guilty of pump and dump?
You may consider what happened to Unisys with GIF a few years back (the community at larged migrated to PNG or JPG, seemingly out of protest, generally out of compliance (and GIFs these days are just crap by standards anyway)), as well as the company that is now laying claim to JPEG. The standards were established, the company came in years later ("Hey! That's ours! Pay!"), and any credibility the company had at one time was heavily crippled.
In the end, this may not be a landmark case of why you should protect your IP from the beginning if you intend to protect it (since there are now just so damn many of these cases), and I think it'll be Yet Another of these. But it will probably serve as a better example than the Unisys/GIF case.
Chalk it up to chutzpah in the end.