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.

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.

How dare you steal our technology! We stole it first!

VDO Ninja is really nice. My friend self hosts it, and it didn’t seem that hard.

There are plenty of easy to set up open source servers. I use a bunch of them. Here’s a few that come to mind:

• jellyseerr
• navidrome
• jswiki
• homeassistant
• docmost
• rustdesk

Those are all ones that only require three or fewer services in a Docker Compose stack. And the docker-compose.yml files are short and easy to understand.

There are plenty that are hard to set up, like:

• jellyfin
• nextcloud
• wordpress
• immich
• mastodon

I’ve installed all of these, and they were not as straightforward, but not too bad.

Matrix is the only one that has taken me more than a day. And I couldn’t even get everything working. Element Call still doesn’t work after trying to set it up for two days.

There is a lot of variance in how difficult these servers are to set up, but Matrix stands alone as the absolute hardest, most convoluted setup process I’ve ever experienced.

That’s legal… for now.

Because the performance gain was basically negligible. That was their explanation in the issue.

What appears to be the person behind the agent resubmitted the PR with a passive aggressive bullshit comment:

https://github.com/matplotlib/matplotlib/pull/31138#issuecomment-3890808045

Not to my knowledge.

Apples to oranges.

It’s the most popular one by a huge margin, and it’s the reference implementation from the protocol devs.

If you set up your community on an existing server, like Matrix.org, it’ll be really easy. And it’s pretty easy to join as an end user.

But if you have your own domain, and you want to host your own Matrix server (mine is matrix.port87.help), be prepared to spend at least a day trying to get everything to work. There are six different services you need to run:

• synapse
• postgres
• element
• coturn
• jwt
• livekit

And there’s no guide for just setting up everything easily. You have to follow several different guides that sometimes have conflicting information. Not all the guides are exactly comprehensive, too, so be prepared to read a lot of documentation. You’ll also need to forward a bunch of ports, and then a port range (thousands of ports, for coturn).

It’s very easy to mess something up, and sometimes it’s very hard to tell. For example, I was running federation on 8448, like you’re supposed to, but my server was advertising that federation was on 443. This caused some rooms on other servers to be unjoinable. It gave me a cryptic error message about it, and I had to read through a few Stack Overflow posts and GitHub issues to finally figure it out.

Synapse will complain about Postgres’ collation and encoding, and that’s quite difficult to fix. You have to add some arguments to the startup command to force the right encoding.

Synapse will also log fucking everything, so make sure to set log level to “ERROR”.

None of this is meant to scare you away from running your own Matrix server. If you want help, I’d even be willing to zip up all my docker compose files and send them to you. This is more meant to indicate that the Matrix team should focus on making this process easier.

I’m in the process of switching my two communities to Matrix. It’s not bad from a user point of view, but running your own server is such an enormous pain in the ass. Like, way harder than it should be.

Why does the notepad app do anything but edit text?

I highly doubt that when you start a “Discord server”, there’s any new machinery spun up. There is a near 100% chance it’s just an entry in a database. Nobody’s running a server just for him. So I don’t think there’s even reason to be charitable.