This is an ideal application for PGP. Most IM clients that support plugins have some kind of GPG plugin that can be used to give you end-to-end security.
I think this illustrates a fundamental misunderstanding of.NET here on Slashdot. Most people didn't actually read up on it but instead dismissed it back in 2000 as another Microsoft thing.
Can you blame them? Microsoft itself didn't seem to know exactly what.NET was back then--it was (still is?) impossible to separate the facts from the marketing bullshit.
:) 17:21 sam@xerces ~ $ ll virus -rw-rw-rw- 1 sam sam 0 2004-06-23 17:21 virus
So a user would have to *deliberatly* mark the file as executable, after saving it to disk and finding where they saved it---and even that simple task is beyond 95% of them---before executing it.
It doesn't work for explorer (the file manager), so you can't use it to manage files, or configure any part of the system that exposes an interface through the file manager (such as network connections).
I call for BS on this one. Now, if you'd have said "GNOME app for GNOME 1.4", then you'd have been right; but, you know: API breaking does happen, from time to time, especially when an API overpasses the point of being sucky enough to be unextensible.
Of course, you wouldn't compile a Gnome 1.4 app against the API for Gnome 2; you'd compile, and run, it against the old Gnome 1.4 libraries. And since we have had versioned libraries for years, you can continue to run, say, Gnucash right alongside newer Gnome 2.6 apps.
It really annoys me when MICROS~1 come up with some bullshit bandaid for creaky old Windows like "Side by side instalations of multiple versions of the same DLL", and all the Windows sycophants claim it's the second goddamn coming of Christ, when it's been working over in Unix land for decades. Argh.
Before installing the base system you are prompted which release you want to install: stable, testing, unstable. So AFAIK you can use debian-installer tc1 to install Woody.
Maybe these are not examples of developer incompetance, but instead evidence that the developer is on your side in the fight againtst the fuckwits in Publishing?:)
I was going to post a links to the XSLT tutorial on w3schools.com, but it was down at the time. It is back now however. It has tutorials and references for a lot of web related tutorials, including XML and XSLT.
gnome-settings-daemon is Gnome's xsettings manager. Your idea of saving these ephermal settings to a file would not work because a) it would be inefficient, and b) you cannot assume that the X server and every X client are all running on hte same machine.
There is a more advanced version in the Vim plugin library with support for symmetric encryption (so you can just decrypt your file with a password, rather than with a GPG private key) and so on.
I would stress that there would be fewer false positives with a Bayesian filter than there would be if a team of people were employed to classify all mail by hand.
Couldn't you have just switched to tty1 and logged in there? No need for ssh, I would have thought.
FYI, the chances were that if you just removed the manually-set v/hsync values, XFree would have defaulted to asking the monitor itself about the ranges it supported, and everything would have Just Worked.
Why? Because, like OS X and unlike windows, they behave predictably and do not mysteriously break or change behavior for no apparent reason. This alone, in the words of my 14 year old niece, made learning Linux worth its while. Not randomly losing her homework to Microsoft crashes or spywar induced bugs helped solidify that opinion.
You are dead right.
Take two puppies (twins, to make this scientific). Your objective is to train them to perform a trick (it doesn't matter which trick).
The first puppy will be rewarded when it performs a task well, and punished when it performs a task poorly.
The second puppy will be rewarded and punished randomly, independant of whether it suceeds or fails.
Which puppy will become a healthy, well adjusted dog? Which one will become a miserable, shivering wreck; afraid to leave the corner of the room it spends all its time being confused, and fucked up in?
Put people in front of a Windows machine, and they will learn nothing. Give them the Mac OS or Linux, and they are empowered. The system's predictable behaviour allows users to explore it, without having to live in constant fear of changing something that alters something else, creating a knock-on effect that breaks their OS and destroys their data.
FYI, the contents of the To, Cc, etc fields are window-dressing only. They can be compared to the letterhead on a physical letter you recieve.
The actual destination of an email is determined by the contents of the message "envelope", which is not a part of the RFC[2]882 message itself--just as a physical envelope that you recieve, containing a letter, is not a part of that letter.
Of course, the analogy breaks down when you consider physical envelopes with windows in them that allow the letterhead to "show through", instead of having the destination address printed on them.:)
The (grand?)parent is still correct though--email disclaimers are the useless invention of (suprise!) overpaid lawyers. As such, they mean approximatly fsck all.
Slashdot Mirror
Does this work for the ones that hardcode it, like Mirc and MSN messenger?
This is an ideal application for PGP. Most IM clients that support plugins have some kind of GPG plugin that can be used to give you end-to-end security.
I think this illustrates a fundamental misunderstanding of .NET here on Slashdot. Most people didn't actually read up on it but instead dismissed it back in 2000 as another Microsoft thing.
.NET was back then--it was (still is?) impossible to separate the facts from the marketing bullshit.
Can you blame them? Microsoft itself didn't seem to know exactly what
Can't this be used to keep unauthorised users off the network? That is what I thought WEP, WPA and now WPA2 were for.
I am astonished to see that no one has mentioned Bash...
And just for good measure:
:) 17:21 sam@xerces ~
$ umask 000
:) 17:21 sam@xerces ~
$ touch virus
:) 17:21 sam@xerces ~
$ ll virus
-rw-rw-rw- 1 sam sam 0 2004-06-23 17:21 virus
So a user would have to *deliberatly* mark the file as executable, after saving it to disk and finding where they saved it---and even that simple task is beyond 95% of them---before executing it.
:) 17:17 sam@xerces ~
./virus ./virus: Permission denied
$ umask 022
:) 17:17 sam@xerces ~
$ touch virus
:) 17:17 sam@xerces ~
$
bash:
:( 17:17 sam@xerces ~
$ ls -l virus
-rw-r--r-- 1 sam sam 0 2004-06-23 17:17 virus
It doesn't work for explorer (the file manager), so you can't use it to manage files, or configure any part of the system that exposes an interface through the file manager (such as network connections).
Me three!
Or kneecapping.
It really annoys me when MICROS~1 come up with some bullshit bandaid for creaky old Windows like "Side by side instalations of multiple versions of the same DLL", and all the Windows sycophants claim it's the second goddamn coming of Christ, when it's been working over in Unix land for decades. Argh.
Before installing the base system you are prompted which release you want to install: stable, testing, unstable. So AFAIK you can use debian-installer tc1 to install Woody.
Maybe these are not examples of developer incompetance, but instead evidence that the developer is on your side in the fight againtst the fuckwits in Publishing? :)
1. Most people use Windows Media Player for everything and so won't notice/care about the file extension.
:)
2. Those that use a different player will presumably use a decent file manager that does not rely on MICROS~1's filename extension brain damage.
Apparantly the mime type is application/ogg; which makes perfect sense really.
I was going to post a links to the XSLT tutorial on w3schools.com, but it was down at the time. It is back now however. It has tutorials and references for a lot of web related tutorials, including XML and XSLT.
Have you looked at XSLT? You can use it to transform XML data from one vocabulary to another; eg from RSS 2 to 0.9/1.0.
That should have been xsettings manager. Forgot to set the post to HTML mode ;)
gnome-settings-daemon is Gnome's xsettings manager. Your idea of saving these ephermal settings to a file would not work because a) it would be inefficient, and b) you cannot assume that the X server and every X client are all running on hte same machine.
That package is in "contrib", and as such is not a part of Debian.
Someone should tell Amazon! about this!
You may be interested in Vim-GPG.
There is a more advanced version in the Vim plugin library with support for symmetric encryption (so you can just decrypt your file with a password, rather than with a GPG private key) and so on.
I would stress that there would be fewer false positives with a Bayesian filter than there would be if a team of people were employed to classify all mail by hand.
Couldn't you have just switched to tty1 and logged in there? No need for ssh, I would have thought.
FYI, the chances were that if you just removed the manually-set v/hsync values, XFree would have defaulted to asking the monitor itself about the ranges it supported, and everything would have Just Worked.
You are dead right.
Take two puppies (twins, to make this scientific). Your objective is to train them to perform a trick (it doesn't matter which trick).
The first puppy will be rewarded when it performs a task well, and punished when it performs a task poorly.
The second puppy will be rewarded and punished randomly, independant of whether it suceeds or fails.
Which puppy will become a healthy, well adjusted dog? Which one will become a miserable, shivering wreck; afraid to leave the corner of the room it spends all its time being confused, and fucked up in?
Put people in front of a Windows machine, and they will learn nothing. Give them the Mac OS or Linux, and they are empowered. The system's predictable behaviour allows users to explore it, without having to live in constant fear of changing something that alters something else, creating a knock-on effect that breaks their OS and destroys their data.
FYI, the contents of the To, Cc, etc fields are window-dressing only. They can be compared to the letterhead on a physical letter you recieve.
:)
The actual destination of an email is determined by the contents of the message "envelope", which is not a part of the RFC[2]882 message itself--just as a physical envelope that you recieve, containing a letter, is not a part of that letter.
Of course, the analogy breaks down when you consider physical envelopes with windows in them that allow the letterhead to "show through", instead of having the destination address printed on them.
The (grand?)parent is still correct though--email disclaimers are the useless invention of (suprise!) overpaid lawyers. As such, they mean approximatly fsck all.