On Monday, 11 March 2024 05:34 -0000,
[mercy snip]
Post by The DoctorPost by Randolf Richardson å¼µæéPost by The DoctorYou can track Gmail spam at
https://www.nk.ca/blog/index.php?/categories/14-Google-Spam
<aside>
Nice of Dave to remind us of his propensity for spamming, although
he's no longer reposting spam, as was his wont, when it was
originated via Gargoyle Gropes.
</aside>
Post by The DoctorPost by Randolf Richardson å¼µæéThat looks similar to what we've been seeing.
The page is confusing to look at because the headers is
double-spaced, although it is still readable.
Is that data published in a database format of some sort, such as
CSV or BIND DNS zone?
Just raw text cut and paste.
Dave, what is displayed, on your NetKnow blog, is something quite
other than raw plain text. It was likely plain text, when you
received the emails in question. It no longer is.
First, I highly suspect you did not just cut and paste, with the first
error being the mistaking of the concept of cut (^x), with copy (^c).
I'd give odds that the original email text was not eviscerated, rather
that the text in question was copied.
While you may very well has pasted the text, into whatever you might
be using for website management, it was no longer plain text when you
did so. Your text was HTMLized, which significantly modified how it
was displayed, regardless how what sort of web browser, CLI or GUI,
may have been used to read your page. The HTMLization turns the
formerly plain text into a barely readable mishmash or word salad.
Email and Usenet header lines all begin with an uppercase alphabetic
character, without fail, showing the header description. When a
header requires more than one line, the remaining lines begin with
white space. This is because, this is how headers are defined in
RFC822 and all its successors. What you refer to as header, on your
blog, show leading lower case characters and show no leading white
space, as expected.
While Mr. Richardson refers to double spacing in the headers, this
artifact will only display in a GUI web browser, as CLI browsers, such
as Lynx, will only single space the shortened header lines, all of
which have been jammed up against the left border, inline with the
header descriptions. While not double spaced, it is still garbled to
the cusp of intelligibility.
The double spacing, which is clearly visible when using a GUI web
browser, as does the vast majority of Internet users, comes from
before the history of computing. The terms, "line feed" (LF) and
carriage return (CR) are borrowed from teletype and Linotype
operation. For this discussion, see how computers indicate a newline,
in ASCII text. (<https://en.wikipedia.org/wiki/Newline>)
POSIX standard oriented systems use <LF>, where Microsoft uses <CRLF>
and Classic Mac used <CR>. It seems when GUI web browsers interpret
the POSIX <LF> in HTML, they add the <CR>, which creates a blank line,
where there was none. Sadly, this makes your COPY and paste even more
difficult to interpret.
Fortunately, there is a way of doing what you're attempting, without
any HTMLizing of the pasted plain text, by inserting the copied text
into a plain text block, within the HTML. Do note, this will restore
the full line lengths, as they were received, which may interfere with
the links displayed to the right in a GUI browser, along with a
seemingly never-ending series of serendipity errors. This may have
the added advantage of displaying the text block in a monospaced font.
While you, Dave, may be able to track Gmail spam using your website, I
suspect that would leave you in a distinct minority.
HTH HAND
- --
David Ritz <***@mindspring.com>
Be kind to animals; kiss a shark.