What you want is 4K77, 4K80, and 4K83.

These are not official releases that have been “despecialized”. These are fan made 4K scans of the theatrical release film (film that was actually shown in a theater).

https://www.thestarwarstrilogy.com/project-4k77/

It is the best way to watch them, because it is basically as close to what you would have gotten in the actual theater as possible, film grain and all.

(Idk about the prequels, sorry.)

When my dad was a boy, he got the polio vaccine in the form of a sugar cube.

What a perfect time to stop using social security numbers for specifically the thing they were not designed to be.

Yeah, I suppose so. It just sucks that it seems like every single company is run by a monster.

I don’t know how all these tech companies keep making obviously stupid and immoral decisions like this.

“We need someone to process our emails.”

“Oh well we have two options. This one costs a hundredth of a cent less per email, but they also run their machines on the blood of children and they ritualistically sacrifice minorities as part of their business model.”

“You said a hundredth of a cent? Perfect!”

We all have to make sacrifices.

They say the engagement ring should be two months of salary, so a single chip of DDR5 should do.

Thank you too. I’m glad I don’t have that incorrect factoid in my head now! :D

That’s the unfortunate reality. Google can force their will on the internet because they own around 35% of all email. And Microsoft owns another ~35%, so if the two decide to change how email works, it’s everyone else who has to conform.

Yep, you are right. So Gmail is following the spec, but still altering headers. So at least it’s not breaking the email, just breaking the authentication.

Atom is defined as such:

atext           =       ALPHA / DIGIT / ; Any character except controls,
                        "!" / "#" /     ;  SP, and specials.
                        "$" / "%" /     ;  Used for atoms
                        "&" / "'" /
                        "*" / "+" /
                        "-" / "/" /
                        "=" / "?" /
                        "^" / "_" /
                        "`" / "{" /
                        "|" / "}" /
                        "~"

atom            =       [CFWS] 1*atext [CFWS]

So since atom does not contain white space, there should be no white space. Only comments can separate 1*atom.

If they wanted to allow separating atoms by a space, it would be written:

atom *(SP atom)

Edit: wait, I’m wrong. CFWS includes white space. You’re right.

Folding white space is a different issue. It’s the atom / quoted-string part. That’s the standard form of a display name. Meaning if it’s more than one word (separated by white space), it should use the quoted string form. It does list obs-phrase as an alternative, but using obsolete syntax should be avoided when possible.

The section right below shows that it’s obsolete:

A.6.1. Obsolete addressing

   Note in the below example the lack of quotes around Joe Q. Public,
   the route that appears in the address for Mary Smith, the two commas
   that appear in the "To:" field, and the spaces that appear around the
   "." in the jdoe address.

----
From: Joe Q. Public <john.q.public@example.com>
To: Mary Smith <@machine.tld:mary@example.net>, , jdoe@test   . example
Date: Tue, 1 Jul 2003 10:52:37 +0200
Message-ID: <5678.21-Nov-1997@example.com>

Hi everyone.
----

And in the spec itself, that syntax is named as “obs-phrase”.

But yes, though obsolete, it is still legal syntax. So I guess I shouldn’t say it “does not conform to the standard”, but rather “just barely conforms to the standard”.

Lettre is following the spec, where if the display name contains a space, the modern way to encode it is to put quotes around it.

Quotes around the display name in a header certainly conforms to the standard (and in fact, the way Gmail rewrites it does not conform to the standard when it contains a space, but is the obsolete form), and I would expect any decent mail program to leave it alone. Then again, Gmail is not a decent mail program, and hasn’t been for a long time.

Edit: @w2xel@gehirneimer.de points out below that Gmail’s rewrite does follow the spec, so it is conforming to the standard when white space is in the display name. It’s only when there is a dot (.) that it would be using the obsolete form.

Without porn, is a platform really a platform?

Gongabazongodongoloogs!

Yeah, I understand how the mail that Gmail receives is not necessarily the mail that the user sent (in regards to headers), and I understand Gmail can add headers (like auth results, spam scores, other sorts of records), but is Gmail really changing the “From” header or other headers included in the DKIM signature?? I would think that would be absolutely unacceptable.

Wait, so when you download what is supposed to be the original email from Gmail, it’s not actually the original? How is that ok?

Let me do it for you, kermie.