And it's pretty easy to confirm: Nautilus 1.0 was released in March 2001. The patent application wasn't filed until June 2001. An article on Linux Planet confirms that v1.0 had preview capability.
That's a pretty serious allegation, and something the campaign would be interested in knowing about.
The Obama campaign has no reason to spoof phone numbers for its own robocalls. Same goes with any official political call, unless it's a slimy call to start with...
The search priority of the Awesomebar has been fixed in 3b5, I think. I used to have to type three or four characters to get to some of my favorite sites, and now it's back to searching the URL first. YEAY!
Keyword: Beta. In Firefox terms, that means working toward release, aka stabilizing. Not the time to be rushing in with major changes to the code.
The Firefox 3 Betas have made major steps forward in memory use, rendering, and speed, and they've added significant UI functionality as well (the Awesome Bar is, well, awesome now that they have their search priorities fixed in 3b5...). I'll take a delay on Acid3 compliance in exchange for what FF3 is delivering.
Two reasons: 1) The disclaimer that anti-spam admins install saying that spam isn't allowed, but more importantly 2) The excessive abuse of system resources and user time.
Requesting a zone transfer isn't terribly abusive in terms of bandwidth (unless you're requesting a zone transfer from IBM or a fully-populated Class A in-addr.arpa zone...), and it takes no permanent resources. A mechanism exists and is in standard use to prevent unauthorized access.
With spam, its cumulative effect is terribly wasteful of bandwidth, it takes significant storage resources, and with the use of anti-spam software, it also takes valuable CPU resources. Furthermore, with the existence of the Presto service and other similar e-mail to printer gateways, it runs afoul of the anti-fax laws (the intent of which was to prevent others from "spending your money" in an abusive manner). Unlike DNS servers, the functional configuration of an SMTP server is to accept e-mail by default; no other configuration is functionally useful for a vast majority of cases, nor can spam be blocked before or during delivery without extensive analysis (and then unreliably).
A DNS server is, as some people have analogized, like a club - private, but with a public interface. The owner can choose to lock the door or only admit certain people. An SMTP server is more like a phone line - anyone can call, but harassing calls and unsolicited calling in violation of the do-not-call laws are forbidden despite the open access.
If this is the totality of the OVC system, I hate to say it, but it's not going to make it in the real world for quite some time. By failing to meet accessibility requirements, it's an instant non-starter in a real election. I'm also concerned that any vote tabulation software is required; shouldn't that be standardized code based on the ballot?
Premier systems are the only ones NOT decertified. This is contradictory to every other decertification and audit performed in other states and brings into question the validity of the testing in Colorado.
Been out there photographing, and I did find a couple of rocks that had obvious signs of people moving them, mostly toward the edge of the playa. But there's no way someone got to all of the rocks that had been moved without leaving signs - too many rocks, scattered across too much territory, and if the rocks left tracks, so would anything else.
Having traffic laws and obeying traffic laws are two completely different things.
Just because it says "one way" did not prevent a traffic cop from telling us to go down the street the wrong way for 50' so that we could get to another street, and just because it says "three-way stop, fourth direction does not stop" does not mean that everyone who had a stop sign actually stopped while we were allowed to proceed through the intersection. It's a generalized case of the "California Stop Sign" - it's *all* optional.
You use a lot of CMYK in your high-end photo work, then? I have yet to run into a professional photo printer that wanted my images in CMYK. I know a lot of photo pros that will drop into LAB color, but none that use CMYK.
Personally, I haven't been using GIMP for my photo work because it didn't have 16-bit support and ICC support. But with the release of 2.4 I can at least use GIMP for some of its unique tools and stay within my ICC-profiled workflow; most printers don't support >8-bit printout, so provided I don't do any major color adjustments within GIMP those tools are now useful...
Re:Now corrects barrel distortion!
on
GIMP 2.4 Released
·
· Score: 1
16-bit is a necessary feature for any serious photo editor. Admittedly with UFRaw in front of GIMP it's less of a necessity than it might otherwise be, but you can't expect to do any major color editing or layer compositing if you're serious about your photos.
If you're using GIMP for minor touch-up work, or for web buttons, you don't need it. Otherwise, you should have it...
CMYK is of more limited use for most GIMP users, and for the public in general. Unless you're in the print publication business, CMYK is a non-factor in today's world. Color printers take RGB-profiled data (even though they're some variant of CMYK internally), and digital cameras use RGB for their sensor data representation. Even many digital printing presses deal with RGB now. I no longer have to soft-proof my magazine submissions to CMYK (the magazine editors do that final work...), I can get business cards and brochures using RGB files...
That assumes that everyone likes the Photoshop UI. I don't, and I use it for just about everything I do as a photographer. Admittedly, as Adobe's most popular program, it's better than their other product UIs - but it's still not good.
The GIMP has some major shortcomings that will be hopefully resolved through GEGL in the near future, but the UI is no worse nor better than any other tool I've used for photo editing.
Best bet: find a number of Storm C&C servers and have them DDoS each other for a while. If you're lucky, the C&C servers give up control rather than random zombies spontaneously picking it up.
But, I'll never look at the shopping channels quite the same again. If they want to lower my cable bill, fine - I think I can manage to let you give them to me.
But paying for ESPN despite my never EVER watching sports outside of a bar? There's got to be something illegal in that.
My bad, though there are a lot of ambiguities here. There's some fascinating reading on the Series of Tubes about circumstances where the GPL pretty much falls over in this respect - including a response or two in this thread.
In our case, we're linking to LGPL and proprietary libraries - don't think there's much GPL library code distributed with Linux. Also, we distribute source to our customers, not binaries; our code supports multiple vendor libraries depending on platform, so we don't derive specifically from any GPL library.
Love the legalisms of this and I should have been more careful in my statement.
In this case, the argument appears to be that VMWare actually needs to modify the kernel code in order to load its module. That is, it takes a stock Linux kernel, modifies it with some hooks that it needs in order to load properly, and then uses those hooks when loading its binary driver. That's more than just loading a binary driver - that's creating a derivative work.
There's no significant problem creating proprietary works that run on Linux; the company I work for has done it successfully for years now. We follow the rules and we have no problems. If you don't use someone else's GPL'd program in your own code, you're good; libraries are okay because they're just linked, or under LGPL or BSD licenses.
In this case, good. If ESX violates the license terms of the Linux kernel/GPL, then it needs to come clean. The whole "viral license" schtick is a bunch of crap - proprietary code has much, much worse terms and no-one complains about those...
A bit late on the response, but I thought I should get back to you...
Punchscan does not address physical handicaps; people with CP, MD and other severely disabling diseases cannot use paper systems - they have to have computer-assisted voting if they want to vote on their own without assistance.
Braille doesn't assist with ballot verification. How do you know your ballot was just marked? Ballot receipts are not a secure answer, and they only work if you check up after the election is over.
While the Punchscan system appears to resolve the problems of auditability and vote tampering quite well, the issuance of a ballot receipt - no matter how indirect - allows verifiable vote buying.
The system also does not resolve one of the key points of HAVA - which, while deeply flawed, addresses some very deeply held concerns of disabled voters. That problem is one of ballot access - Punchscan is not disabled-friendly.
You do realize that one of the rights and privileges given under the Constitution to the Congress is the right to determine how Federal elections are run. Right?
If you're going to ask rhetorical questions, be sure to get them right.
the general legal standing seems to be that the use of an unsecured wifi AP without the explicit permission of it's owner is illegal, the presumption being that not securing your AP does not imply consent.
Now can we try to get that applied back to e-mail ports again, so we can execute^H^H^H^H^H^H^Hprosecute spammers more effectively?
Slashdot Mirror
And it's pretty easy to confirm: Nautilus 1.0 was released in March 2001. The patent application wasn't filed until June 2001. An article on Linux Planet confirms that v1.0 had preview capability.
It's good for this application... Let's not get ahead of logic here.
That's a pretty serious allegation, and something the campaign would be interested in knowing about.
The Obama campaign has no reason to spoof phone numbers for its own robocalls. Same goes with any official political call, unless it's a slimy call to start with...
What is the link layer protocol on Ethernet? CSMA/CD
Carrier Sense Multiple Access with Collision Detection.
The search priority of the Awesomebar has been fixed in 3b5, I think. I used to have to type three or four characters to get to some of my favorite sites, and now it's back to searching the URL first. YEAY!
Keyword: Beta. In Firefox terms, that means working toward release, aka stabilizing. Not the time to be rushing in with major changes to the code.
The Firefox 3 Betas have made major steps forward in memory use, rendering, and speed, and they've added significant UI functionality as well (the Awesome Bar is, well, awesome now that they have their search priorities fixed in 3b5...). I'll take a delay on Acid3 compliance in exchange for what FF3 is delivering.
It's a copyright, not a trademark. You don't lose your Copyright if you don't enforce.
Two reasons:
1) The disclaimer that anti-spam admins install saying that spam isn't allowed, but more importantly
2) The excessive abuse of system resources and user time.
Requesting a zone transfer isn't terribly abusive in terms of bandwidth (unless you're requesting a zone transfer from IBM or a fully-populated Class A in-addr.arpa zone...), and it takes no permanent resources. A mechanism exists and is in standard use to prevent unauthorized access.
With spam, its cumulative effect is terribly wasteful of bandwidth, it takes significant storage resources, and with the use of anti-spam software, it also takes valuable CPU resources. Furthermore, with the existence of the Presto service and other similar e-mail to printer gateways, it runs afoul of the anti-fax laws (the intent of which was to prevent others from "spending your money" in an abusive manner). Unlike DNS servers, the functional configuration of an SMTP server is to accept e-mail by default; no other configuration is functionally useful for a vast majority of cases, nor can spam be blocked before or during delivery without extensive analysis (and then unreliably).
A DNS server is, as some people have analogized, like a club - private, but with a public interface. The owner can choose to lock the door or only admit certain people. An SMTP server is more like a phone line - anyone can call, but harassing calls and unsolicited calling in violation of the do-not-call laws are forbidden despite the open access.
If this is the totality of the OVC system, I hate to say it, but it's not going to make it in the real world for quite some time. By failing to meet accessibility requirements, it's an instant non-starter in a real election. I'm also concerned that any vote tabulation software is required; shouldn't that be standardized code based on the ballot?
Premier systems are the only ones NOT decertified. This is contradictory to every other decertification and audit performed in other states and brings into question the validity of the testing in Colorado.
Been out there photographing, and I did find a couple of rocks that had obvious signs of people moving them, mostly toward the edge of the playa. But there's no way someone got to all of the rocks that had been moved without leaving signs - too many rocks, scattered across too much territory, and if the rocks left tracks, so would anything else.
Having traffic laws and obeying traffic laws are two completely different things.
Just because it says "one way" did not prevent a traffic cop from telling us to go down the street the wrong way for 50' so that we could get to another street, and just because it says "three-way stop, fourth direction does not stop" does not mean that everyone who had a stop sign actually stopped while we were allowed to proceed through the intersection. It's a generalized case of the "California Stop Sign" - it's *all* optional.
You use a lot of CMYK in your high-end photo work, then? I have yet to run into a professional photo printer that wanted my images in CMYK. I know a lot of photo pros that will drop into LAB color, but none that use CMYK.
Personally, I haven't been using GIMP for my photo work because it didn't have 16-bit support and ICC support. But with the release of 2.4 I can at least use GIMP for some of its unique tools and stay within my ICC-profiled workflow; most printers don't support >8-bit printout, so provided I don't do any major color adjustments within GIMP those tools are now useful...
16-bit is a necessary feature for any serious photo editor. Admittedly with UFRaw in front of GIMP it's less of a necessity than it might otherwise be, but you can't expect to do any major color editing or layer compositing if you're serious about your photos.
If you're using GIMP for minor touch-up work, or for web buttons, you don't need it. Otherwise, you should have it...
CMYK is of more limited use for most GIMP users, and for the public in general. Unless you're in the print publication business, CMYK is a non-factor in today's world. Color printers take RGB-profiled data (even though they're some variant of CMYK internally), and digital cameras use RGB for their sensor data representation. Even many digital printing presses deal with RGB now. I no longer have to soft-proof my magazine submissions to CMYK (the magazine editors do that final work...), I can get business cards and brochures using RGB files...
That assumes that everyone likes the Photoshop UI. I don't, and I use it for just about everything I do as a photographer. Admittedly, as Adobe's most popular program, it's better than their other product UIs - but it's still not good.
The GIMP has some major shortcomings that will be hopefully resolved through GEGL in the near future, but the UI is no worse nor better than any other tool I've used for photo editing.
Best bet: find a number of Storm C&C servers and have them DDoS each other for a while. If you're lucky, the C&C servers give up control rather than random zombies spontaneously picking it up.
That's screwed up...
But, I'll never look at the shopping channels quite the same again. If they want to lower my cable bill, fine - I think I can manage to let you give them to me.
But paying for ESPN despite my never EVER watching sports outside of a bar? There's got to be something illegal in that.
My bad, though there are a lot of ambiguities here. There's some fascinating reading on the Series of Tubes about circumstances where the GPL pretty much falls over in this respect - including a response or two in this thread.
In our case, we're linking to LGPL and proprietary libraries - don't think there's much GPL library code distributed with Linux. Also, we distribute source to our customers, not binaries; our code supports multiple vendor libraries depending on platform, so we don't derive specifically from any GPL library.
Love the legalisms of this and I should have been more careful in my statement.
In this case, the argument appears to be that VMWare actually needs to modify the kernel code in order to load its module. That is, it takes a stock Linux kernel, modifies it with some hooks that it needs in order to load properly, and then uses those hooks when loading its binary driver. That's more than just loading a binary driver - that's creating a derivative work.
There's no significant problem creating proprietary works that run on Linux; the company I work for has done it successfully for years now. We follow the rules and we have no problems. If you don't use someone else's GPL'd program in your own code, you're good; libraries are okay because they're just linked, or under LGPL or BSD licenses.
In this case, good. If ESX violates the license terms of the Linux kernel/GPL, then it needs to come clean. The whole "viral license" schtick is a bunch of crap - proprietary code has much, much worse terms and no-one complains about those...
A bit late on the response, but I thought I should get back to you...
Punchscan does not address physical handicaps; people with CP, MD and other severely disabling diseases cannot use paper systems - they have to have computer-assisted voting if they want to vote on their own without assistance.
Braille doesn't assist with ballot verification. How do you know your ballot was just marked? Ballot receipts are not a secure answer, and they only work if you check up after the election is over.
While the Punchscan system appears to resolve the problems of auditability and vote tampering quite well, the issuance of a ballot receipt - no matter how indirect - allows verifiable vote buying.
The system also does not resolve one of the key points of HAVA - which, while deeply flawed, addresses some very deeply held concerns of disabled voters. That problem is one of ballot access - Punchscan is not disabled-friendly.
Yes. Other people using the monicker are imitators. ;)
You do realize that one of the rights and privileges given under the Constitution to the Congress is the right to determine how Federal elections are run. Right?
If you're going to ask rhetorical questions, be sure to get them right.
Now can we try to get that applied back to e-mail ports again, so we can execute^H^H^H^H^H^H^Hprosecute spammers more effectively?