"Revenge of the Jedi" wasn't a ploy; the name was changed at the last minute.
True; it was changed to prevent confusion with Star Trek II: The Revenge of Khan, which was in production at the same time. Upon discovering the similarity, both movie studios agreed to change their titles.
> Umm... isn't Content-type: text/html an HTML header, not an HTTP header?
Uh, no. HTML is a language that uses tags enclosed in angle brackets ("<" and ">") to define the structure of the document. HTTP headers precede a document of any type and are of the form "keyword: value". "Content-type: text/html" is not HTML, it's HTTP.
How can you think that Spammers should all be attacked, and made illegal, when you think
that DeCSS should be free, because it is speech?
The difference is obvious; the DeCSS authors aren't trying to insert something into someone else's private mailbox against the wishes of the mailbox owner.
Spammers are trespassers, plain and simple. Fighting spam has nothing to do with free speech, this is about the right to control one's own property.
It looks like Napster will soon be afflicted with the same problem that Slashdot has been suffering from: a falling signal-to-noise ratio, caused by malicious attempts to drown out the real conversation with huge amounts of garbage. This "cuckoo" guy is no different than the idiot who posts here about beer everyday.
If this catches on, Napster will need to implement some sort of moderation scheme. Perhaps, after a download is complete (or after it's been manually aborted), the user should be prompted to give a positive or negative point to the person he downloaded from. Those with sufficient negative points (from unique userids) could be automatically disconnected and banned from the server (by IP, not by nickname) for a few hours.
New userids are easy to create, and the Cuckoo guy could get back on without too much difficulty, but having the connection dropped will be an inconvenience.
The change was made as part of the agreement with the US govt. and other registrars.
Previously, a whois query on the default server would return information about a domain only if Network Solutions was the registrar for that domain, and a negative result if the domain was registered elsewhere.
Now, all registrars are at an equal distance from the default whois server. To look up a domain, first do a 'whois' with the default server, and see what whois server serves that domain; then do a second query against that server, and you'll get all information you expect.
A script to parse the output of the first "whois" and issue a second query is trivial and is left as an exercise for the reader.
This is a good thing. The default "whois" is no longer NSI-only, and we no longer have to guess where the other whois servers are to track down a domain contact.
Four years ago, I started working in tech support for a small local ISP*. I was paid $8.50/hour, which seemed like a good deal at first. I was usually working 60 hour weeks or more. Then, I was "promoted" and given a "raise" -- I now had a salary of $23,000 yearly.
Strangely, after this "raise", my paycheck was smaller than the week before. Based on a 60 hour week, that's about $7.66 per hour. But the president of the company claimed that I had been given a "75% raise" and expected me to be grateful for that. I was still expected to work 60-hour weeks.
Within a few months, I had a much better job.
*(Chicago-area readers may know of an ISP formerly owned by a man named Karl.)
When the inevitable verdict is announced, I'll be opening the two bottles of four-year-old Chimay Blue Label "Grande Riserve" Trappist Ale that I've been saving for this happy occasion.
Most folks use the same password everywhere. Just think... if you were, you'd have passwords to hundreds of thousands of root accounts, etc.
I would hope no slashdotters would be foolish enough to do that.
I've changed the password for "my" account and for those of the Fortune 100 company I work for to such things as "idiots.nsi", "nsi-criminals", etc.
(I also got into "amazon", "bn", and "msn", but don't want to be seen as trying to "take" those accounts... they're available right now if anyone wants them!)
My copies of "Advanced Programming in the Unix Environment" and "UNIX Network Programming" are well worn from years of use. I have only the highest esteem for Mr. Stevens, truly a giant among technical authors.
Slashdot Mirror
True; it was changed to prevent confusion with Star Trek II: The Revenge of Khan, which was in production at the same time. Upon discovering the similarity, both movie studios agreed to change their titles.
> Umm... isn't Content-type: text/html an HTML header, not an HTTP header?
Uh, no. HTML is a language that uses tags enclosed in angle brackets ("<" and ">") to define the structure of the document. HTTP headers precede a document of any type and are of the form "keyword: value". "Content-type: text/html" is not HTML, it's HTTP.
...slime molds will be getting AOL accounts.
How can you think that Spammers should all be attacked, and made illegal, when you think
that DeCSS should be free, because it is speech?
The difference is obvious; the DeCSS authors aren't trying to insert something into someone else's private mailbox against the wishes of the mailbox owner.
Spammers are trespassers, plain and simple. Fighting spam has nothing to do with free speech, this is about the right to control one's own property.
It looks like Napster will soon be afflicted with the same problem that Slashdot has been suffering from: a falling signal-to-noise ratio, caused by malicious attempts to drown out the real conversation with huge amounts of garbage. This "cuckoo" guy is no different than the idiot who posts here about beer everyday.
If this catches on, Napster will need to implement some sort of moderation scheme. Perhaps, after a download is complete (or after it's been manually aborted), the user should be prompted to give a positive or negative point to the person he downloaded from. Those with sufficient negative points (from unique userids) could be automatically disconnected and banned from the server (by IP, not by nickname) for a few hours.
New userids are easy to create, and the Cuckoo guy could get back on without too much difficulty, but having the connection dropped will be an inconvenience.
Sorry -- some of that was lost because it contained angle brackets (< >).
The correct version is at http://www.cynico.com/whois2.txt
#!/usr/bin/perl
/^[[]/)
# whois2 -- do a whois on the default server
# then parse output to find the server of the
# registrar that manages that name.
die ("Usage: $0 domainname\n") if ($#ARGV)
{
chop($line);
$line =~ s/^\s//g;
if ($line =~
{
print "$line\n";
} elsif ($line =~ m/(Domain Name|Registrar|Name Server): (.*)/) {
print "$line\n";
} elsif ($line =~ m/Whois Server: (.*)/) {
$server=$1;
print "$line\n";
}
}
close(W);
if ($server)
{
system("whois $dom\@$server"); ## LINUX
# system("whois -h $server $dom"); ## BSD, Solaris
}
# Sorry for the formatting... slashdot editors, please add support for HTML <PRE>!
The change was made as part of the agreement with the US govt. and other registrars.
Previously, a whois query on the default server would return information about a domain only if Network Solutions was the registrar for that domain, and a negative result if the domain was registered elsewhere.
Now, all registrars are at an equal distance from the default whois server. To look up a domain, first do a 'whois' with the default server, and see what whois server serves that domain; then do a second query against that server, and you'll get all information you expect.
A script to parse the output of the first "whois" and issue a second query is trivial and is left as an exercise for the reader.
This is a good thing. The default "whois" is no longer NSI-only, and we no longer have to guess where the other whois servers are to track down a domain contact.
Four years ago, I started working in tech support for a small local ISP*. I was paid $8.50/hour, which seemed like a good deal at first. I was usually working 60 hour weeks or more. Then, I was "promoted" and given a "raise" -- I now had a salary of $23,000 yearly.
Strangely, after this "raise", my paycheck was smaller than the week before. Based on a 60 hour week, that's about $7.66 per hour. But the president of the company claimed that I had been given a "75% raise" and expected me to be grateful for that. I was still expected to work 60-hour weeks.
Within a few months, I had a much better job.
*(Chicago-area readers may know of an ISP formerly owned by a man named Karl.)
When the inevitable verdict is announced, I'll be opening the two bottles of four-year-old Chimay Blue Label "Grande Riserve" Trappist Ale that I've been saving for this happy occasion.
I would hope no slashdotters would be foolish enough to do that.
I've changed the password for "my" account and for those of the Fortune 100 company I work for to such things as "idiots.nsi", "nsi-criminals", etc.
(I also got into "amazon", "bn", and "msn", but don't want to be seen as trying to "take" those accounts... they're available right now if anyone wants them!)
My copies of "Advanced Programming in the Unix Environment" and "UNIX Network Programming" are well worn from years of use. I have only the highest esteem for Mr. Stevens, truly a giant
among technical authors.