When 300 UNIQUE visitors view my page using the same proxy, they look like one visitor.
I still hope to get some time to work on BBStats again, my webstats package - in terrible shape as it is - but I was hoping to solve this by using optional session cookies or the ability to import other cookies from the site.
For example,/. could log my IP to see whether I am unique, but they could also fetch my cookie (and still fall back on IP if it doesn't exist).
We mainly use SSH with keys at work. No direct root access, you must first login as user with your key.
From the outside, only one machine is accessable through SSH, so removing an employee from the list of allowed remote logins is as simple as removing his/her public key from that server.
Surely works a lot better than all the hassle with passwords.. we still update the root password regularly, but if an ex-employee still knows it, that's not immediately a problem.
You would think that they would learn from their own mistakes, and admit that NT is not the answer for EVERYTHING
Just like Linux isn't the answer for everything.. or any other OS.
Each OS has its uses, and each problem asks for a little research which system will work best for the given problem. As someone once explained to me: (and I've seen the statement on/. as well)
"What's the best OS?"
"Depends on what you want to do with it".
Of course it makes sense to move everything to one system to decrease TCO, especially when other systems make up only a very small percentage of the total network. But, I suppose Bungie runs independently from the rest of MS so I doubt that's an issue here.
I wish to hell both bloody groups would stop their bickering and get on with producing a viable, desktop alternative to MS...
Both groups are already doing that. Just because a few developers write articles like these doesn't mean that both developer teams are completely focussed on bashing each other. In fact, they are coding right now.
Let's not discuss whether deCSS should be illegal or not, let's assume - for the linking discussion - that it _really_ is.
I don't like being the devil's advocate, but a few weeks ago I did come up with a thought that could be used to argue that there can indeed be legal action against a person linking to deCSS or something similar:
Not the link itself would be the problem, but the implicated participance in the crime (that of distributing the stuff).
Compare it with the drugs dealer next door [if applicable]. Pointing at the house saying "there is a drugs dealer there" is perfectly legal. Cheering at the beauty of cocaine and putting a sign in your yard saying "Want some cocaine? I can cut you in on a good deal" and then directing people to your neighbours house.. that's a different story.
You are perfectly allowed to do that, free speech is unharmed. But it could implicate that you have some involvement.
Perhaps a bit thin, but I cannot find any flaws in this reasoning other than the grey area to find out what exactly would qualify as involvement.
I can now imagine why a link called "Fsck the MPAA, get deCSS" would be judged as involvement in the act of distributing and thus has a basis for legal action.
Again very personal and hardly of any concern for _real_ end users. Real end users do not have a strong opinion on the GPL or QPL.
Neato software.
You can run either programs in either environment, and let me assure you that some KDE programs are neater than GNOME's. Try KDE2 and see how well Konqueror is doing. Or try Konsole in fullscreen mode.;-)
KDE tries too hard to look like Windows.
Yes and no. Face it, the GUI of Microsoft isn't all bad. It's one of the best parts of Windows. Therefore KDE has taken many good aspects from it. And many aspects from CDE, BeOS, MacOS, etc.
Check the screenshots again, I can assure you KDE does not have to look like Windows at all.
KDE and Gnome both suck, FVWM is still the best window manager in the world.
Then use it within KDE or GNOME instead of Englightenment (or the new GNOME wm) or KWin (kwm's successor).
KDE and GNOME are desktop environments with integrated applications and services. You might not need any of those, but they are in a way different league than regular window managers so don't compare them to those.
Why aren't both Gnome and KDE getting interoperability right so that Gnome vs KDE stops being a monolithic decision and becomes a matter of personal choice?
They _are_ getting it right. They share the.desktop principle for desktop/menu links, there has been work on more compatible WM hints and both use the same drag-and-drop protocol. KDE2 will also include support for importing/exporting GTK themes.
There is plenty of reason between the two teams and the majority of developers strives to interoperability.
But what I don't understand is why this upsets KDE community.
Some (note: *some*) KDE developers feel that GNOME has not really contributed so much yet and that there are more words than there is code.
GNOME seems to pull existing projects into its base, such as Gecko, AbiWord, now StarOffice, etc. While "joining" these efforts and binding them (see GNOME as the glue) is a nice accomplishment and a great effort, some KDE developers feel that the actual coding progress is within KDE, having it's own Office suite, it's own HTML renderer, etc etc. Despite all the external contributions GNOME still hasn't caught up and some developers like to express that.
Personally I wanted not to have any KDE reaction on the GNOME foundation, as (in practice) it doesn't affect KDE development at all. Most KDE developers are coding right now, not engaging in this discussion.
Besides, Helix in particular seems to be pretty unfriendly to even some versions of Linux. How do they expect to take over the UNIX desktop market if they don't even have a working Slackware installer?
t-10m
I was excited when I downloaded the sources, you can compile the Helix installer myself.
KDE is too distributed and diverse to permit me to speak for everybody
Please, please keep this in mind when replying.
You can disagree with Kurt's views, but don't take it out on KDE as a whole. As active member on the kde and kde-devel mailinglist I can tell you that this is not at all the general thought, there are plenty of developers who rather look at their own efforts than paying a lot of attention to GNOME, especially with the nearby release of KDE 2.0 and a heavy debugging rage among the developers.
Let's keep this discussion informative, insightful and interesting. There are obviously hard feelings between the KDE and GNOME teams but let's not degrade ourselves to such nonsense.
Who cares if a few of the desktops run Linux? MSFT's major money makers have always been the Office line of products. If browsers are provided so that Linux users can now buy office licensees then this can only improve their bottom line.
Unfortunately, most Linux users will try and completely avoid.NET because they want to stay in control, not give away more. It was probably one of their reasons to run Linux in the first place.
If we ever encounter an intelligent mechanical machine, we will also have the prove of the existing of intelligent flesh. Something had to build the damn machine in the first place, right?
There is a chance of course that we will only encounter the machine and never its creators, although that is unlikely. For example, by the time our probes have become so distant from us that they are found and cannot be traced down to the source, we should have better means of transportation and communication. Unless we're really not that intelligent at all, or have been extinct for a long time.
Reading this, I must conclude that Linux gaming _is_ profitable for Loki.
This step means that Loki believes there can be a return on investment for BSD, which has - no offense - a lot smaller user base than Linux, especially on the desktop.
There is no way Loki would believe in a BSD market if the Linux market wasn't already working out for them.
It seems like desktop UNIX is no longer in its infancy.
It would be nice for the cookie alert pop-ups most browsers had two more buttons: "Always Accept from This Domain", and "Ban EVERYTHING from This Domain".
You'll like the new KDE Konqueror browser. The two actions "reject" and "accept" have three options "all cookies", "all cookies from this domain" and "this cookie only". Works real nice.
Whenever I see anything ad related, it's reject for the entire domain. And sites I _do_ trust get a permanent clearance.
There's already two GPLed Office Suites around: StarOffice (soon GPL but already functional) and KOffice (already GPL but not fully functional - yet, but it'll be soon)
Couldn't they concentrate effords?
With all respect to the Koffice team (I'm very fond of KDE), they should do with Koffice what the GIMP guys are doing for GIMP 2.0: making it toolkit/environment independant. The new GIMP should allow both KDE and Gnome front-ends with the same engine. Why not follow this approach for the Office suite?
*NIX would be even better if some of these common modules would seperate engine from interface, just like the OS is seperated from the GUI.
A few existing examples: Kicq has done this by creating ICQlib. XMMS uses mpg-123, aKtion uses xanim..
This would be harder for Koffice of course, because of the KParts integration within KDE, but there is no reason to have a unified rendering and file format (including filters) engine for office tasks such as word processing and presentation.
While the legal system is not perfect when it is about software, this doesn't seem like something that could happen.
Every software license I know of, either open-source or proprietary, waivers liability. Big companies such as AOL/* and Microsoft will not be accepting liability ever, so they will make sure there is a way to prevent this from happening.
And whatever way they find to keep the ability to dismiss claims, this way can also be used by open-source. AFAIK it is not possible yet to buy/bribe yourself an exception clause to the law. And if that wold be possible, then it's time for a new Constitution.
Slashdot Mirror
I patented stupid patent tricks contests a *long* time ago. :)
Seriously, why won't they rethink keyboards and actually have both a Trash and Delete key?
I still hope to get some time to work on BBStats again, my webstats package - in terrible shape as it is - but I was hoping to solve this by using optional session cookies or the ability to import other cookies from the site.
For example, /. could log my IP to see whether I am unique, but they could also fetch my cookie (and still fall back on IP if it doesn't exist).
We mainly use SSH with keys at work. No direct root access, you must first login as user with your key. From the outside, only one machine is accessable through SSH, so removing an employee from the list of allowed remote logins is as simple as removing his/her public key from that server. Surely works a lot better than all the hassle with passwords.. we still update the root password regularly, but if an ex-employee still knows it, that's not immediately a problem.
Just like Linux isn't the answer for everything.. or any other OS.
Each OS has its uses, and each problem asks for a little research which system will work best for the given problem. As someone once explained to me: (and I've seen the statement on /. as well)
"What's the best OS?"
"Depends on what you want to do with it".
Of course it makes sense to move everything to one system to decrease TCO, especially when other systems make up only a very small percentage of the total network. But, I suppose Bungie runs independently from the rest of MS so I doubt that's an issue here.
Perhaps. But from my experience, KHTML renders quite flawlessly, supports Netscape plugins, Java, etc etc *and* is a _lot_ faster than Gecko.
If you want the quick viewer use KDE's...
That's what 99% of webbrowsing is about. A quick viewer.
But sure, I'd love Gecko support within Konqueror. On the condition that KHTML remains the default engine.
Oh, wait, AOL owns ICQ also.
Both groups are already doing that. Just because a few developers write articles like these doesn't mean that both developer teams are completely focussed on bashing each other. In fact, they are coding right now.
I don't like being the devil's advocate, but a few weeks ago I did come up with a thought that could be used to argue that there can indeed be legal action against a person linking to deCSS or something similar:
Not the link itself would be the problem, but the implicated participance in the crime (that of distributing the stuff).
Compare it with the drugs dealer next door [if applicable]. Pointing at the house saying "there is a drugs dealer there" is perfectly legal. Cheering at the beauty of cocaine and putting a sign in your yard saying "Want some cocaine? I can cut you in on a good deal" and then directing people to your neighbours house.. that's a different story.
You are perfectly allowed to do that, free speech is unharmed. But it could implicate that you have some involvement.
Perhaps a bit thin, but I cannot find any flaws in this reasoning other than the grey area to find out what exactly would qualify as involvement.
I can now imagine why a link called "Fsck the MPAA, get deCSS" would be judged as involvement in the act of distributing and thus has a basis for legal action.
Sounds more like a Gecko-based KDE browser to me. :-)
This is very personal, so I can advice /. readers to check both the See GNOME in Action KDE2 Screenshots screenshot pages.
Warm GPL fuzzies.
Again very personal and hardly of any concern for _real_ end users. Real end users do not have a strong opinion on the GPL or QPL.
Neato software.
You can run either programs in either environment, and let me assure you that some KDE programs are neater than GNOME's. Try KDE2 and see how well Konqueror is doing. Or try Konsole in fullscreen mode. ;-)
KDE tries too hard to look like Windows.
Yes and no. Face it, the GUI of Microsoft isn't all bad. It's one of the best parts of Windows. Therefore KDE has taken many good aspects from it. And many aspects from CDE, BeOS, MacOS, etc. Check the screenshots again, I can assure you KDE does not have to look like Windows at all.
How about.. if Linux is going to make it on the desktop, you need to stop trolling?
Then use it within KDE or GNOME instead of Englightenment (or the new GNOME wm) or KWin (kwm's successor).
KDE and GNOME are desktop environments with integrated applications and services. You might not need any of those, but they are in a way different league than regular window managers so don't compare them to those.
They _are_ getting it right. They share the .desktop principle for desktop/menu links, there has been work on more compatible WM hints and both use the same drag-and-drop protocol. KDE2 will also include support for importing/exporting GTK themes.
There is plenty of reason between the two teams and the majority of developers strives to interoperability.
The war has begun long ago. GNOME and KDE have already been improving each other. We *are* already winning.
Some (note: *some*) KDE developers feel that GNOME has not really contributed so much yet and that there are more words than there is code.
GNOME seems to pull existing projects into its base, such as Gecko, AbiWord, now StarOffice, etc. While "joining" these efforts and binding them (see GNOME as the glue) is a nice accomplishment and a great effort, some KDE developers feel that the actual coding progress is within KDE, having it's own Office suite, it's own HTML renderer, etc etc. Despite all the external contributions GNOME still hasn't caught up and some developers like to express that.
Personally I wanted not to have any KDE reaction on the GNOME foundation, as (in practice) it doesn't affect KDE development at all. Most KDE developers are coding right now, not engaging in this discussion.
t-10m I was excited when I downloaded the sources, you can compile the Helix installer myself.
t ... if you already have GNOME installed. *sigh*
Please, please keep this in mind when replying.
You can disagree with Kurt's views, but don't take it out on KDE as a whole. As active member on the kde and kde-devel mailinglist I can tell you that this is not at all the general thought, there are plenty of developers who rather look at their own efforts than paying a lot of attention to GNOME, especially with the nearby release of KDE 2.0 and a heavy debugging rage among the developers.
Let's keep this discussion informative, insightful and interesting. There are obviously hard feelings between the KDE and GNOME teams but let's not degrade ourselves to such nonsense.
Unfortunately, most Linux users will try and completely avoid .NET because they want to stay in control, not give away more. It was probably one of their reasons to run Linux in the first place.
There is a chance of course that we will only encounter the machine and never its creators, although that is unlikely. For example, by the time our probes have become so distant from us that they are found and cannot be traced down to the source, we should have better means of transportation and communication. Unless we're really not that intelligent at all, or have been extinct for a long time.
This step means that Loki believes there can be a return on investment for BSD, which has - no offense - a lot smaller user base than Linux, especially on the desktop.
There is no way Loki would believe in a BSD market if the Linux market wasn't already working out for them.
It seems like desktop UNIX is no longer in its infancy.
You'll like the new KDE Konqueror browser. The two actions "reject" and "accept" have three options "all cookies", "all cookies from this domain" and "this cookie only". Works real nice.
Whenever I see anything ad related, it's reject for the entire domain. And sites I _do_ trust get a permanent clearance.
Couldn't they concentrate effords?
With all respect to the Koffice team (I'm very fond of KDE), they should do with Koffice what the GIMP guys are doing for GIMP 2.0: making it toolkit/environment independant. The new GIMP should allow both KDE and Gnome front-ends with the same engine. Why not follow this approach for the Office suite?
*NIX would be even better if some of these common modules would seperate engine from interface, just like the OS is seperated from the GUI.
A few existing examples: Kicq has done this by creating ICQlib. XMMS uses mpg-123, aKtion uses xanim..
This would be harder for Koffice of course, because of the KParts integration within KDE, but there is no reason to have a unified rendering and file format (including filters) engine for office tasks such as word processing and presentation.
Every software license I know of, either open-source or proprietary, waivers liability. Big companies such as AOL/* and Microsoft will not be accepting liability ever, so they will make sure there is a way to prevent this from happening.
And whatever way they find to keep the ability to dismiss claims, this way can also be used by open-source. AFAIK it is not possible yet to buy/bribe yourself an exception clause to the law. And if that wold be possible, then it's time for a new Constitution.
That should've said SourceForge and Server51... sorry!