Daniel Kaplan wrote:
Quote:
"Jukka K. Korpela" <jkorpela@cs.tut.fiwrote in message
news:4dSWj.1174$_03.220@reader1.news.saunalahti.fi ...
Quote:
>Which part of the abbreviation "URL" do you fail to understand?
>>
>Which part of the abbreviation "html" in the newsgroup name do you fail to
>understand?
>>
>Please continue using the same apparently forged From field until you have
>a clue. Thank you in advance.
Quote:
>
Actually, the forged from field is common for a plethora of reasons:
"Common" doesn't always equal "right" or "good".
Use something like
daniel.kaplan@myfirm.com.invalid. People (who even
care) will trim the .invalid, spammers will probably not take the time.
Quote:
Hackers who will Google your name (for newsgroups postings) in the hopes of
finding a way into your site
So use some non-traceable address, like
daniel.kaplan@gmail.com.invalid.
Then there's no connection to D-Kaplan Amalgamated Industries, Inc.
Quote:
and high and mighty people like you that need to stop being so
condescending.
Wait, you're afraid that Jukka, because he's so high and mighty, might
reverse the character you've perceived him to have and will start
*spamming* you? Why would someone so condescending deign to send you a
single e-mail?
Quote:
>
Strange, with such an attitude one would think you've already learned the
reason for using a forged field in newsgroups.
Someone claiming as much Internet experience as you will presumably have
realized the effects of posting someone else's domain in a forged
address. Or do you actually own or control nospam.com?
Quote:
>
I'll have to make a duplicate page of my site one which works, and one which
doesn't and post it in the right group (mis-posts happen you know).
Yes. But that saves us all, individually, making a new file, copying
your markup from your post (although you hadn't provided it here),
pasting it into the new file, copying the CSS from your post (which may
or may not have been complete), pasting that into the new file, saving
the file and viewing in a browser locally, or uploading to a server and
then viewing it from the server, and STILL not knowing whether we are
using the same doctype or charset or content-type.
So it would be a big waste of time, even before we actually started to
think about your actual question, and we'd be doing it repeatedly, all
over the world.
Which sounds more efficient?
BTW, the added bonus of making simplified versions of troublesome pages
is that one often finds the problem oneself, without even having to ask.
Quote:
Hopefully someone there less snobbish will be kind enough to look at it.
Yes, one hopes so. But people react less warmly when one repeatedly
offends (for varying values of "offend").
--
John