For context, this is the Lars Ingebrigtsen who wrote the manual for Gnus[0], a common Emacs package for reading email and Usenet. It’s clever, funny, and wildly informative. Lars has probably forgotten more about email parsing than 99% of us here will ever have learned. The manual itself says[1]: > Often when I read the manual, I think that we should take a collection up to have Lars psycho-analysed. 0: https://www.g…
Not only the manual, but Gnus itself. I remember this guy from the university (UiO) when he started working on Gnus. He was a small celebrity among us informatics students, and we all used Emacs and Gnus, of course.
What's up with all those equals signs anyway?
171–180 of 200 posts
Re: What's up with all those equals signs anyway?
#172> We see that that’s a quite a long line. Mail servers don’t like that Why do mail server care about how long a line is? Why don't they just let the client reading the mail worry about wrapping the lines?
I don't think kids today realize how little memory we had when SMTP was designed. For example, the PDP-11 (early 1970s), which was shared among dozens of concurrent users, had 512 kilobytes of RAM. The VAX-11 (late 1970s) might have as much as 2 megabytes . Programmers were literally counting bytes to write programs.
Re: What's up with all those equals signs anyway?
#173Re: What's up with all those equals signs anyway?
#174Earlier quoted context omitted.
If you already know where the start of the opening tag is, then I think a regex is capable of finding the end of that same opening tag, even in cases like yours. In that sense, it’s possible to use a regex to parse a single tag. What’s not possible is finding opening tags within a larger fragment of HTML.
For any given regex, an opponent can craft a string which is valid HTML but that the regex cannot parse. There are a million edge cases like: this! -—> but do count this --> and this --> but do count this —-> Now your regex has to include balanced comment markers. Solve that You need a context-free grammar to correctly parse HTML with its quoting rules, and escaping, and embedded scripts and CDATA, etc. etc. etc. I d…
Re: What's up with all those equals signs anyway?
#175Earlier quoted context omitted.
For any given regex, an opponent can craft a string which is valid HTML but that the regex cannot parse. There are a million edge cases like: this! -—> but do count this --> and this --> but do count this —-> Now your regex has to include balanced comment markers. Solve that You need a context-free grammar to correctly parse HTML with its quoting rules, and escaping, and embedded scripts and CDATA, etc. etc. etc. I d…
HTML comments do not nest. The obvious tokenizer you can create with regular expressions is the correct one.
Re: What's up with all those equals signs anyway?
#176Re: What's up with all those equals signs anyway?
#177Earlier quoted context omitted.
Hey, POP3 still makes sense. Having a local copy of your emails is useful.
Isn’t the only difference between pop and imap that pop removes the mail from the server? I only use imap, and all my email is available offline.
Re: What's up with all those equals signs anyway?
#178> So what’s happened here? Well, whoever collected these emails first converted from CRLF (i.e., “Windows” line ending coding) to “NL” (i.e., “Unix” line ending coding). This is pretty normal if you want to deal with email. But you then have one byte fewer: I think there is a second possible conclusion, which is that the transformation happened historically. Everyone assumes these emails are an exact dump from Gmail,…
The shot-callers demand the material, which is a task fobbed off onto some nobody intern who doesn't matter (deliberately, because the lawyers and career LEOs don't want any "officer of the court" or other "party" to put eyes on things they might need to deny knowing about later.) They use only the most primitive, mechanical method possible, with little to no discretion. The collected mass of mangled junk is then shipped to whoever, either in boxes or on CD-ROM/DVD (yes, still) or something. Then, the reverse process is done, equally badly, again by low-level staff, also with zero discretion and little to no technical knowledge or ability, for exactly the same reasons, to get the material into some form suitable for filing or whatever.
Through all of this, the subtle details of data formats and encodings are utterly lost, and the legal archive fills with mangled garbage like raw quoted-printable emails. The parties involved have other priorities, such as minimizing the number of people involved in the process, and tight control over the number of copies created. Their instinct is not to bring in a bunch of clever folk that might make the work product come out better, because "better" for them is different than "better" for Twitter or Facebook. Also, these disclosures are inevitably and invariably challenged by time: the obligation to provide one thing or another is fought to the last possible minute, and when the word does finally go out there is next to no time to piddle around with details.
In the Epstein case, the disclosures were done years ago, the original source material (computers, accounts, file systems, etc.) have all long since been (deliberately) destroyed, and what the feds have is the shrapnel we see today.
Re: What's up with all those equals signs anyway?
#179Earlier quoted context omitted.
Not only the manual, but Gnus itself. I remember this guy from the university (UiO) when he started working on Gnus. He was a small celebrity among us informatics students, and we all used Emacs and Gnus, of course.
Also gmane. The once popular mailing lists search site.