Unless I'm mistaken, all human bodies are basically the same. Human minds on the other hand are totally different.
No, physically they are all pretty much the same. I bet at an airport most of the travelers have very similar thought patterns as well (I hope I make my connection, can't wait to see mom, did I turn the oven off?)
For example, right now I'm thinking how wonderful a orange infused whiskey would be. I'm all for privacy, but there is really nothing to hide on the human body.
And why, pray tell, are you concerned about someone finding out that you are thinking about an orange infused whiskey? If the mind scanners made the lines go faster at the airports (which the other scans don't btw), why would you not support it?
Even in the paranoid USA, naked children != child porn. I believe the law requires that the images be sexual in nature to be porn. Granted, there is a lot of room for overzealous prosecutors to contend that something is sexual, and innocent people have been harassed that way, but it is not automatic.
Very true, the children in photographs don't even have to be naked to be considered child porn. All you need is some lascivious exhibition of the genitals.
It's not automatic, but it's a possibility, and considering the hefty punishment involved, you may as well consider pictures of naked children to be child porn in the USA.
Contrary to what the people on Slashdot tell you, every image of a nude person under the age of 18 is not necessarily child porn -- and a millimeter-wave scanner isn't exactly taking a nude photograph.
The devil is in the details, eh? Since pictures of minors with clothes on can be considered child porn, it's not much of a stretch to think that fuzzy naked body outlines could be worked into the definition as well.
I don't care if there is demand or not. I don't want that junk anywhere near me or my family thanks - even accidentally.
Oh? You run into child pornography a lot accidently? Or are there child porn pushers that keep trying to give it to your family. Clearly your precious family must be protected from the constant barrage of child porn being offered to them. I recommend filtering the entire internet. Sound good?
I think your insults are feeding an underground industry of internet insults, where sickos pay money to watch trolls and dimwits like yourself try to stumble through arguments. Indirectly, I believe children are probably being raped while being read your inane slashdot comments out loud. I could give you actual proof, but it is a shady business, so there are no records.
To sum up, every time you post a comment on slashdot, a child is raped. Think about that next time before you hit the submit button.
That they refuse to provide an option to remove it, and that others are welcome to.
How do I do that?
There's an applet or plasmoid or whatever that you can download (from kde-look.org I believe) that allows you to hide the cashew. Not a very elegant solution.
Someone correct me if I'm wrong, but can't you access the cashew config by right clicking the desktop? I'm not sure why it is needed, and seems to piss a lot of people off.
I wish they wouldn't refer to it as child abuse. While sexually/mentally abusing children is child abuse, child abuse often times focuses on the physical abuse (at leaset in my area of the country in the US). That said, this law is probably targeted at filtering pornographic images of children who were abused. There (is?) should be a better term to describe what they're trying to filter.
I'm curious as to why you wish there was a clear distinction. Is one much worse than the other?
An interesting idea, and additional methods of maintaining privacy on the net are welcome, but this part of their project seems silly:
Usable: OneSwarms interface is web-based and supports real-time transcoding of many audio and video formats for in-browser playback, eliminating the need for casual users to master a new applications interface or search for custom media codecs.
Does it seem even remotely plausible that someone using Oneswarm (either now or in the future) would have problems mastering "a new application's interface" or searching for custom media codecs? If you're downloading bittorrent files, you can play avi files, and I'm sure most people would prefer to play media in their preferred media application rather than in some slow java app.
And as others have mentioned, it seems similar to freenet, but without the datastore of each other's material on each node, and no "open-net" option.
KDE4 has an amazing new paradigm for file sharing with other desktop environments. There are several fantastic spectacular new methods of sharing all of your photos, music, and data with friends and colleagues. In KDE4, as with everything else, file sharing is built around a desktop widget. The file sharing widget (or plasmoid) is quite shiny and can be rotated and resized. It can even be dragged onto the taskbar.
This desktop file-sharing widget is truly the dawn of a new file-sharing age. A entirely new way to think about desktop file-sharing widgets. A revolution, if you will.
Currently, file sharing is not yet implemented in the file-sharing plasmoid, but by 4.5 this should be working. It also cannot yet be dragged to the taskbar, or resized, or actually placed on the desktop, but all of these features are in the works. This is the start of something great, after all.
So be part of the new paradigm in file sharing, and use KDE4.2 today!
Unlike you, some of use actually have a basic understanding of the KDE projects numbering system. Why in the world would you base your assumptions concerning general readiness off of a version number if you are not familiar with how/why those numbers are assigned? How could you honestly expect there to not be regressions from 3.5.x to 4.0.0? Give be a fucking break and quit bitching about the past.
I expected regressions. I did not expect a barely unusable, unstable alpha project full of obvious glaring bugs that was tagged with a final release number.
I will stop bitching about the past when people stop trying to rewrite recent history, and stop claiming that the KDE team communicated the state of the project clearly. I didn't submit my post out of the blue; I wrote a response to someone who stated that the 4.0 release notes claimed that 4.0 was an alpha release and not ready for production machines, which it did not.
And the link also says: "KDE 4.0 is the innovative Free Software desktop containing lots of applications for every day use as well as for specific purposes."
Can you honestly say that you get the impression that 4.0 was a test alpha release after reading that announcement in its entirety?
And yes, everyone knew it was alpha-quality software after they tried it. The KDE team had been promising flying unicorns and butt-rainbows until about a week before release. But don't listen to me, listen to the KDE team's logic... they didn't want to name it an alpha release or developer's release because they wanted more people to test it. They wanted people to not have a clue so that more people would try to use their buggy alpha project.
But whatever, as long as you enjoy the software then that's what matters.
Unlike everyone who is bitching and moaning, I read the notes about how KDE 4.0 was just a preview, do not use, do not install on production machines, etc... so I continued to use KDE 3.5 until 4.2 came out.
Oh you mean these http://www.kde.org/announcements/4.0/ release notes? Where it says nothing about 4.0 being a preview or not installing on production machines?
Nice try, but it's not easy to rewrite history that soon. I'm sure the KDE devs appreciate your efforts though. IMO KDE4.2 still isn't ready for use on production machines anyway.
Yep, I have the same experience. Firefox operations are much, much slower in linux than in windows. Another example is tab switching. In XP/Vista it is instantaneous, but in linux there is a slight delay. Things like this make the GUI feel very sluggish (I'm using the nvidia driver btw).
Whenever you guys talked about "Child Porn" being used as a scare tactic, I didn't believe you. "I never see that."
But this article, the issue which is clearly being fueled by the MPAA and RIAA, mentions Child Porn three times, including the subheading!
I am beginning to believe.
Why would you not believe that? Nearly every single restriction or attempted restriction of rights or freedoms relating to the internet have used child porn as an excuse.
$100 million from law enforcement wireless (original bill $200 million)
$100 million from FBI construction (original bill $400 million)
Need to keep pumping that taxpayer money into law enforcement so they can keep us safe from "obscene porn" http://www.usdoj.gov/criminal/optf/ and continue to win the drug war.
There was lots of interesting stuff on dot.kde.org from the 4.0 release timeframe, but much of it wasn't spun the way you think it was. Generally the devs defended the release decision (and most still seem to currently).
For instance, this is aseigo's reply to someone who was "still wonderig about the need for a 'truth in advertising' page detailing what doesn't work so well, what doesn't work at all, and what was deferred to 4.1"
there's enough good stuff in the release to concentrate on that for the time being. the blogosphere is actually very positive on this release right now, and 4.1 will end up being an answer-through-action for much of the rest. the "this is the beginning" communication has been very effective. i even saw it echoed on wired blogs today. people get it. =)
I honestly don't think Aaron Seigo or a lot of the rest of the KDE team learned anything from the 4.0 release. They've been so busy going to parties and patting themselves on the back that they've missed the big picture. After being in a PR nightmare for a year now, the only thing they seemed to have learned is how to easily dismiss any criticism (whether constructive or not) as inconsequential trolling.
I will let it go when people stop trying to rewrite recent history and claim that the KDE team loudly proclaimed that KDE4.0 wasn't ready for users. By responding, I was simply pointing out inaccurate information in another slashdotter's post. And show me where Aaron "it was the distros fault" Seigo admitted that they misrepresented what 4.0 was.
Early release of 4.0 was targeted precisely at developers and in fact release notes claimed nothing else but "stabilized interface for KDE 4.x series".
"The KDE 4 Desktop has gained some major new capabilities. The Plasma desktop shell offers a new desktop interface, including panel, menu and widgets on the desktop as well as a dashboard function. KWin, the KDE Window manager, now supports advanced graphical effects to ease interaction with your windows.
Lots of KDE Applications have seen improvements as well. Visual updates through vector-based artwork, changes in the underlying libraries, user interface enhancements, new features, even new applications -- you name it, KDE 4.0 has it. Okular, the new document viewer and Dolphin, the new file manager are only two applications that leverage KDE 4.0's new technologies. "
That type of marketing talk is aimed directly at users, not developers.
My favorite piece of eye candy was the "static" when opening the photo.
When the hell is somebody going to fix that, and whos fault is it?
The KDE team will get right on that once they perfect another bouncy ball desktop widget.
The most annoying missing feature of KDE4 IMO (now that they've gotten keyboard shortcuts somewhat working) is the lack of video thumbnails in dolphin/konqueror. Doesn't every other desktop environment/file manager have those these days?
AS far as I can remember KDE 4.0 was well know not to be really ready.
Yeah, after everyone tried it and declared it was not really ready. Sure, if you were an avid reader of KDE devel blogs you may have gotten the impression that it wasn't ready for end users (though always followed by the caveat of "but it's fantastic!"), but if you thought that the distinction between their beta/RCs and final release actually meant something, or just read the release announcement http://www.kde.org/announcements/4.0/, you'd have understandably believed it was ready.
If a man takes a car and gets in a freak accident that blows it up because he didn't read the manual, it isn't the car company's fault. If no one could be bothered to read anything surrounding KDE 4.0 or 4.1, it isn't KDE's fault that there was confusion. They probably could've addressed such confusion in a more timely manner, but I'm sorry, I don't know of anyone else who managed to miss the fact that KDE 4.0 was anything other than a developer release.
And here is the crux of the problem. The KDE team attempted to redefine the meaning of betas, RCs, and final releases.
If a man takes an experimental rocket-car for a drive and it blows up, it isn't the rocket-car company's fault. However, if a man takes a Honda Civic for a drive, and it blows up unexpectedly, then Honda would most certainly would take a lot of the blame.
And please... lots of people missed the fact that KDE 4.0 wasn't anything but a developer release. Hence the controversy. If they wanted it to be just a developer release, they could have (duh) labeled it a developer release!
Slashdot Mirror
Unless I'm mistaken, all human bodies are basically the same. Human minds on the other hand are totally different.
No, physically they are all pretty much the same. I bet at an airport most of the travelers have very similar thought patterns as well (I hope I make my connection, can't wait to see mom, did I turn the oven off?)
For example, right now I'm thinking how wonderful a orange infused whiskey would be. I'm all for privacy, but there is really nothing to hide on the human body.
And why, pray tell, are you concerned about someone finding out that you are thinking about an orange infused whiskey? If the mind scanners made the lines go faster at the airports (which the other scans don't btw), why would you not support it?
Even in the paranoid USA, naked children != child porn. I believe the law requires that the images be sexual in nature to be porn. Granted, there is a lot of room for overzealous prosecutors to contend that something is sexual, and innocent people have been harassed that way, but it is not automatic.
Very true, the children in photographs don't even have to be naked to be considered child porn. All you need is some lascivious exhibition of the genitals.
It's not automatic, but it's a possibility, and considering the hefty punishment involved, you may as well consider pictures of naked children to be child porn in the USA.
Contrary to what the people on Slashdot tell you, every image of a nude person under the age of 18 is not necessarily child porn -- and a millimeter-wave scanner isn't exactly taking a nude photograph.
The devil is in the details, eh? Since pictures of minors with clothes on can be considered child porn, it's not much of a stretch to think that fuzzy naked body outlines could be worked into the definition as well.
I don't care if there is demand or not. I don't want that junk anywhere near me or my family thanks - even accidentally.
Oh? You run into child pornography a lot accidently? Or are there child porn pushers that keep trying to give it to your family. Clearly your precious family must be protected from the constant barrage of child porn being offered to them. I recommend filtering the entire internet. Sound good?
you are a weak mind
You have to resort to bland insults this quickly?
I think your insults are feeding an underground industry of internet insults, where sickos pay money to watch trolls and dimwits like yourself try to stumble through arguments. Indirectly, I believe children are probably being raped while being read your inane slashdot comments out loud. I could give you actual proof, but it is a shady business, so there are no records.
To sum up, every time you post a comment on slashdot, a child is raped. Think about that next time before you hit the submit button.
Stop shilling for corporations. Clearly the unlimited broadband model has been extremely profitable.
Bears repeating. In bold.
What did they say?
That they refuse to provide an option to remove it, and that others are welcome to.
How do I do that?
There's an applet or plasmoid or whatever that you can download (from kde-look.org I believe) that allows you to hide the cashew. Not a very elegant solution.
Someone correct me if I'm wrong, but can't you access the cashew config by right clicking the desktop? I'm not sure why it is needed, and seems to piss a lot of people off.
Women are pregnant for 12 months in East Asia? Weird.
I wish they wouldn't refer to it as child abuse. While sexually/mentally abusing children is child abuse, child abuse often times focuses on the physical abuse (at leaset in my area of the country in the US). That said, this law is probably targeted at filtering pornographic images of children who were abused. There (is?) should be a better term to describe what they're trying to filter.
I'm curious as to why you wish there was a clear distinction. Is one much worse than the other?
Usable: OneSwarms interface is web-based and supports real-time transcoding of many audio and video formats for in-browser playback, eliminating the need for casual users to master a new applications interface or search for custom media codecs.
Does it seem even remotely plausible that someone using Oneswarm (either now or in the future) would have problems mastering "a new application's interface" or searching for custom media codecs? If you're downloading bittorrent files, you can play avi files, and I'm sure most people would prefer to play media in their preferred media application rather than in some slow java app.
And as others have mentioned, it seems similar to freenet, but without the datastore of each other's material on each node, and no "open-net" option.
I don't understand all the hate for Bill.
Stay off my lawn.
KDE4 has an amazing new paradigm for file sharing with other desktop environments. There are several fantastic spectacular new methods of sharing all of your photos, music, and data with friends and colleagues. In KDE4, as with everything else, file sharing is built around a desktop widget. The file sharing widget (or plasmoid) is quite shiny and can be rotated and resized. It can even be dragged onto the taskbar.
This desktop file-sharing widget is truly the dawn of a new file-sharing age. A entirely new way to think about desktop file-sharing widgets. A revolution, if you will.
Currently, file sharing is not yet implemented in the file-sharing plasmoid, but by 4.5 this should be working. It also cannot yet be dragged to the taskbar, or resized, or actually placed on the desktop, but all of these features are in the works. This is the start of something great, after all.
So be part of the new paradigm in file sharing, and use KDE4.2 today!
Strike the word "barely". It was just plain unusable. I blame KDE4 for that editing error.
Unlike you, some of use actually have a basic understanding of the KDE projects numbering system. Why in the world would you base your assumptions concerning general readiness off of a version number if you are not familiar with how/why those numbers are assigned? How could you honestly expect there to not be regressions from 3.5.x to 4.0.0? Give be a fucking break and quit bitching about the past.
I expected regressions. I did not expect a barely unusable, unstable alpha project full of obvious glaring bugs that was tagged with a final release number.
I will stop bitching about the past when people stop trying to rewrite recent history, and stop claiming that the KDE team communicated the state of the project clearly. I didn't submit my post out of the blue; I wrote a response to someone who stated that the 4.0 release notes claimed that 4.0 was an alpha release and not ready for production machines, which it did not.
And the link also says: "KDE 4.0 is the innovative Free Software desktop containing lots of applications for every day use as well as for specific purposes."
Can you honestly say that you get the impression that 4.0 was a test alpha release after reading that announcement in its entirety?
And yes, everyone knew it was alpha-quality software after they tried it. The KDE team had been promising flying unicorns and butt-rainbows until about a week before release. But don't listen to me, listen to the KDE team's logic... they didn't want to name it an alpha release or developer's release because they wanted more people to test it. They wanted people to not have a clue so that more people would try to use their buggy alpha project.
But whatever, as long as you enjoy the software then that's what matters.
Unlike everyone who is bitching and moaning, I read the notes about how KDE 4.0 was just a preview, do not use, do not install on production machines, etc ... so I continued to use KDE 3.5 until 4.2 came out.
Oh you mean these http://www.kde.org/announcements/4.0/ release notes? Where it says nothing about 4.0 being a preview or not installing on production machines?
Nice try, but it's not easy to rewrite history that soon. I'm sure the KDE devs appreciate your efforts though. IMO KDE4.2 still isn't ready for use on production machines anyway.
Yep, I have the same experience. Firefox operations are much, much slower in linux than in windows. Another example is tab switching. In XP/Vista it is instantaneous, but in linux there is a slight delay. Things like this make the GUI feel very sluggish (I'm using the nvidia driver btw).
Why would you not believe that? Nearly every single restriction or attempted restriction of rights or freedoms relating to the internet have used child porn as an excuse.
$100 million from law enforcement wireless (original bill $200 million)
$100 million from FBI construction (original bill $400 million)
Need to keep pumping that taxpayer money into law enforcement so they can keep us safe from "obscene porn" http://www.usdoj.gov/criminal/optf/ and continue to win the drug war.
there's enough good stuff in the release to concentrate on that for the time being. the blogosphere is actually very positive on this release right now, and 4.1 will end up being an answer-through-action for much of the rest. the "this is the beginning" communication has been very effective. i even saw it echoed on wired blogs today. people get it. =)
I honestly don't think Aaron Seigo or a lot of the rest of the KDE team learned anything from the 4.0 release. They've been so busy going to parties and patting themselves on the back that they've missed the big picture. After being in a PR nightmare for a year now, the only thing they seemed to have learned is how to easily dismiss any criticism (whether constructive or not) as inconsequential trolling.
I will let it go when people stop trying to rewrite recent history and claim that the KDE team loudly proclaimed that KDE4.0 wasn't ready for users. By responding, I was simply pointing out inaccurate information in another slashdotter's post. And show me where Aaron "it was the distros fault" Seigo admitted that they misrepresented what 4.0 was.
Early release of 4.0 was targeted precisely at developers and in fact release notes claimed nothing else but "stabilized interface for KDE 4.x series".
Really? Try reading it again: http://www.kde.org/announcements/4.0/
Here's a taste:
"The KDE 4 Desktop has gained some major new capabilities. The Plasma desktop shell offers a new desktop interface, including panel, menu and widgets on the desktop as well as a dashboard function. KWin, the KDE Window manager, now supports advanced graphical effects to ease interaction with your windows.
Lots of KDE Applications have seen improvements as well. Visual updates through vector-based artwork, changes in the underlying libraries, user interface enhancements, new features, even new applications -- you name it, KDE 4.0 has it. Okular, the new document viewer and Dolphin, the new file manager are only two applications that leverage KDE 4.0's new technologies. "
That type of marketing talk is aimed directly at users, not developers.
The KDE team will get right on that once they perfect another bouncy ball desktop widget.
The most annoying missing feature of KDE4 IMO (now that they've gotten keyboard shortcuts somewhat working) is the lack of video thumbnails in dolphin/konqueror. Doesn't every other desktop environment/file manager have those these days?
AS far as I can remember KDE 4.0 was well know not to be really ready.
Yeah, after everyone tried it and declared it was not really ready. Sure, if you were an avid reader of KDE devel blogs you may have gotten the impression that it wasn't ready for end users (though always followed by the caveat of "but it's fantastic!"), but if you thought that the distinction between their beta/RCs and final release actually meant something, or just read the release announcement http://www.kde.org/announcements/4.0/, you'd have understandably believed it was ready.
If a man takes a car and gets in a freak accident that blows it up because he didn't read the manual, it isn't the car company's fault. If no one could be bothered to read anything surrounding KDE 4.0 or 4.1, it isn't KDE's fault that there was confusion. They probably could've addressed such confusion in a more timely manner, but I'm sorry, I don't know of anyone else who managed to miss the fact that KDE 4.0 was anything other than a developer release.
And here is the crux of the problem. The KDE team attempted to redefine the meaning of betas, RCs, and final releases.
If a man takes an experimental rocket-car for a drive and it blows up, it isn't the rocket-car company's fault. However, if a man takes a Honda Civic for a drive, and it blows up unexpectedly, then Honda would most certainly would take a lot of the blame.
And please... lots of people missed the fact that KDE 4.0 wasn't anything but a developer release. Hence the controversy. If they wanted it to be just a developer release, they could have (duh) labeled it a developer release!