I wish this functionality was built into the OS, rather than having to do it manually (for example, a way to disallow internet access during installation) -- but at least it's doable on Android. I don't think any other phone platforms give this level of permission separation or control. I'm not so sure that app review would really fix the overall problem; it might catch the obviously-malicious phishing apps like in this story, but I bet that the app auditors' opinion on what is a privacy violation differs greatly from my own.
While I completely agree with OS, the GPL and its enforcement. The question that I ask myself is what impact those lawsuits will have on the OpenSource model.
Will patent trolls become OS Trolls and will OpenSource become Open 'sue us'?
This may be the rise of a new business model...
You're missing the part about how you have to actually *steal code* from a project in order to violate their copyright, whereas a patent violation can be thought up independently without knowledge of the filing.
GPL code is not code you can use in any way you see fit, it's code that you can use provided you comply with the license terms.
So racism is dead in America right? Until that happens of course it is still unacceptable to apply monkey parody to black public figures. You cannot ignore America's (or much of the West's) shameful history of racism. Do not imagine for a second that the people who create images of Michelle Obama that make her look more monkey like are doing it simply because they noticed the striking similarity between humans and monkeys. They are doing it because they are racists.
The problem with using Drupal for the White House is that it's a popular CMS and has lots of people looking for exploits and vulnerabilities. The second a proof of concept piece of code or an easy exploit is discovered, a few thousand script kiddies will decend to get their 15 minutes of fame.
I'm not sure how Drupal fares with bugs and patching speed (I know Wordpress seems to get some high profile holes discovered) but even if all vulns are patched before someone takes advantage of it, you're still going to need an admin who's going to be constantly alert to patching it.
I'm not arguing against closed source vs open, more about popular vs obscure.
They're the federal government. Anything they do won't be obscure.
While I agree they needed the warrant in the first place, proponents would argue that they wouldn't have known about these guys without the program.
Given that these guys were arrested in the U.K. I don't know if the N.S.A. tipped off U.K. authorities, or if the program was entirely useless in this scenario.
Regardless, the real question is was this worth the liberties lost?
What liberties lost?
There aren't any laws protecting the transmission of Email, AFAICT. The analogy I use when explaining email to other people is that of a postcard; anybody who handles it (relay servers, ISPs, etc) can read it, but they *probably* won't. It's not like sealed postal mail, which I believe has some legal status.
If you want any security in your electronic communications, use strong crypto.
Yeah, but then you run into the trouble where some government agency "convinces" one of the developers to put a back door into the encryption module.
Security works better when there's diversity. I've mentioned this in the past with regards to operating systems, but it's like evolution and natural selection. When disaster strikes, the more genetically diverse species will survive. Likewise, when some government agency gets involved, there's a better chance of emerging unscathed when there's more variations in security products.
Fortunately the developers of TC prefer to remain pseudonymous.
Moreover, it's all open-source, so you can compile-from-that and check the code beforehand.
I don't think that word means what you think it means. Given the context, I expect "gloating" or "crowing" or "celebrating" would've been a better fit.
Metamoderation is a second layer of moderation. It seeks to address the issue of unfair moderators by letting "metamoderators" (any logged-in Slashdotter) "rate the rating" of ten randomly selected comment posts. The metamoderator decides if the moderator's rating was fair, unfair, or neither.
Really with the development of better OCR technologies and such comes the elimination of e-mail security by obscurity. If you don't want spam either A) have a decent spam filter (I don't think I've had a single piece of spam pass through G-mails filter and only one false positive) or B) don't share your e-mail address. Those are the only two ways to prevent spam that will continue to work.
Well, my email address is made up of my name, so I just tell people it's myfirstname@mylastname.cc. (use sensible replacements)
The problem with that is that a lot of computers that old don't support booting off of a USB drive. Plus, some of the computers might only have USB 1.1 leading to slower transfer times. If this is your goal why not try to have it be "sugar on a disk" thats going to be infinitely easier than "sugar on a stick".
That's a solution too: all the sugar packages in SoaS are in the Fedora repos (and soon also Debian/Ubuntu), so you can just install it like any other package.
Good lord people, do none of you actually run linux? Sugar on a stick is just a conceptual item, it is to show the versatility of the OS they built. A CD-DVD-hard Disk-Flash port would be trivial from here.
Moreover, the current method of creating a SoaS device is to download an ISO and use the provided livecd-to-usb.sh shell script!
Re the headline, they're also working on backup software to automagically push a kid's work to a centralized (in the school) backup server, thus enabling the sticks to be replaced without data loss if the stick itself is misplaced.
Existing content contributed to Wikipedia was done under the GFDL license, which like the standard GPLv2 includes a "or later version" clause. Wikipedia's license includes this clause.
The latest version of the GFDL now contains a section I think written to specifically allow Wikimedia to do this.
Kinda. It's broad, in that it allows pretty much any wiki to do the same thing, but it *was* a collab between WMF and the FSF.
Hmm...I wonder why they never complained about the limited subset of classes that GWT supports in client-side code.
Because they never said that GWT supports "Java", they said it implements some JRE classes.
And like everyone says, Sun is a sore loser for failing to release a usable cloud-computing project.
Slashdot Mirror
Well, here's another question: if Random Security Expert can hack into TPB, how do we know that Some **AA Hireling hasn't done the same??
Because that'd be illegal, and the evidence inadmissible in court. TPB could even sue for that, and the employees jailed.
I wish this functionality was built into the OS, rather than having to do it manually (for example, a way to disallow internet access during installation) -- but at least it's doable on Android. I don't think any other phone platforms give this level of permission separation or control. I'm not so sure that app review would really fix the overall problem; it might catch the obviously-malicious phishing apps like in this story, but I bet that the app auditors' opinion on what is a privacy violation differs greatly from my own.
Maybe you're thinking of http://wiki.laptop.org/go/Rainbow, which implements http://wiki.laptop.org/go/OLPC_Bitfrost, which does exactly what you're describing. It's currently in Debian ( http://packages.debian.org/unstable/main/rainbow ) and Fedora ( http://ppc.koji.fedoraproject.org/koji/packageinfo?packageID=7262 ).
While I completely agree with OS, the GPL and its enforcement. The question that I ask myself is what impact those lawsuits will have on the OpenSource model.
Will patent trolls become OS Trolls and will OpenSource become Open 'sue us'?
This may be the rise of a new business model...
You're missing the part about how you have to actually *steal code* from a project in order to violate their copyright, whereas a patent violation can be thought up independently without knowledge of the filing. GPL code is not code you can use in any way you see fit, it's code that you can use provided you comply with the license terms.
Flying a plane into the Pentagon? Not terrorism
What about civilian personnel who make up a large component of the Pentagon staff?
So racism is dead in America right? Until that happens of course it is still unacceptable to apply monkey parody to black public figures. You cannot ignore America's (or much of the West's) shameful history of racism. Do not imagine for a second that the people who create images of Michelle Obama that make her look more monkey like are doing it simply because they noticed the striking similarity between humans and monkeys. They are doing it because they are racists.
But when people do the same of George Bush it's simply parody? http://images.google.com/images?hl=en&um=1&q=george+bush+monkey
The problem with using Drupal for the White House is that it's a popular CMS and has lots of people looking for exploits and vulnerabilities. The second a proof of concept piece of code or an easy exploit is discovered, a few thousand script kiddies will decend to get their 15 minutes of fame. I'm not sure how Drupal fares with bugs and patching speed (I know Wordpress seems to get some high profile holes discovered) but even if all vulns are patched before someone takes advantage of it, you're still going to need an admin who's going to be constantly alert to patching it. I'm not arguing against closed source vs open, more about popular vs obscure.
They're the federal government. Anything they do won't be obscure.
While I agree they needed the warrant in the first place, proponents would argue that they wouldn't have known about these guys without the program. Given that these guys were arrested in the U.K. I don't know if the N.S.A. tipped off U.K. authorities, or if the program was entirely useless in this scenario. Regardless, the real question is was this worth the liberties lost?
What liberties lost? There aren't any laws protecting the transmission of Email, AFAICT. The analogy I use when explaining email to other people is that of a postcard; anybody who handles it (relay servers, ISPs, etc) can read it, but they *probably* won't. It's not like sealed postal mail, which I believe has some legal status. If you want any security in your electronic communications, use strong crypto.
Yeah, but then you run into the trouble where some government agency "convinces" one of the developers to put a back door into the encryption module.
Security works better when there's diversity. I've mentioned this in the past with regards to operating systems, but it's like evolution and natural selection. When disaster strikes, the more genetically diverse species will survive. Likewise, when some government agency gets involved, there's a better chance of emerging unscathed when there's more variations in security products.
Fortunately the developers of TC prefer to remain pseudonymous. Moreover, it's all open-source, so you can compile-from-that and check the code beforehand.
I don't think that word means what you think it means. Given the context, I expect "gloating" or "crowing" or "celebrating" would've been a better fit.
Signed, Your eight-grade English teacher
*eighth*, anyone?
YouTube will not offer both h.264, flash and OGG at the same time; too expensive.
They can offer h.264 and Flash-processing-h.264 at the same time, however. They currently have no problem with a dep. on Flash.
No it isn't. Go have a look at it - meta mod is just "here's 10 comments. Wanna mod them up or down?"
From http://slashdot.org/faq/metamod.shtml:
Metamoderation is a second layer of moderation. It seeks to address the issue of unfair moderators by letting "metamoderators" (any logged-in Slashdotter) "rate the rating" of ten randomly selected comment posts. The metamoderator decides if the moderator's rating was fair, unfair, or neither.
Just as it was childish of me to mod your post down and bookmark your user page for the next batch of mod points.
... which is why we have meta-moderation.
While "Open Source", the project is not Free Software, banning one-to-many redistribution and commercial use.
Really with the development of better OCR technologies and such comes the elimination of e-mail security by obscurity. If you don't want spam either A) have a decent spam filter (I don't think I've had a single piece of spam pass through G-mails filter and only one false positive) or B) don't share your e-mail address. Those are the only two ways to prevent spam that will continue to work.
Well, my email address is made up of my name, so I just tell people it's myfirstname@mylastname.cc. (use sensible replacements)
The problem with that is that a lot of computers that old don't support booting off of a USB drive. Plus, some of the computers might only have USB 1.1 leading to slower transfer times. If this is your goal why not try to have it be "sugar on a disk" thats going to be infinitely easier than "sugar on a stick".
That's a solution too: all the sugar packages in SoaS are in the Fedora repos (and soon also Debian/Ubuntu), so you can just install it like any other package.
Good lord people, do none of you actually run linux? Sugar on a stick is just a conceptual item, it is to show the versatility of the OS they built. A CD-DVD-hard Disk-Flash port would be trivial from here.
Moreover, the current method of creating a SoaS device is to download an ISO and use the provided livecd-to-usb.sh shell script!
...if the old codebase is not maintained: http://dev.laptop.org/git/sugar/
and the original copyright owner switches to the new codebase:
http://lists.laptop.org/pipermail/devel/2009-May/024487.html
Correct. OLPC is in fact becoming the new downstream of Sugar, pulling in the new packages in future OLPC distro releases.
I know, individually, what all the words/acronyms mean but when put together in that order, they make no sense to me.
Huh? I only see one acronym, an initialism. Sugar doesn't stand for anything.
Re the headline, they're also working on backup software to automagically push a kid's work to a centralized (in the school) backup server, thus enabling the sticks to be replaced without data loss if the stick itself is misplaced.
Existing content contributed to Wikipedia was done under the GFDL license, which like the standard GPLv2 includes a "or later version" clause. Wikipedia's license includes this clause. The latest version of the GFDL now contains a section I think written to specifically allow Wikimedia to do this.
Kinda. It's broad, in that it allows pretty much any wiki to do the same thing, but it *was* a collab between WMF and the FSF.
Hmm...I wonder why they never complained about the limited subset of classes that GWT supports in client-side code.
Because they never said that GWT supports "Java", they said it implements some JRE classes. And like everyone says, Sun is a sore loser for failing to release a usable cloud-computing project.