top | item 40394887

(no title)

sangupta | 1 year ago

Why not standardize on using HTTP3 using POST requests with JSON payload instead?

discuss

order

gjsman-1000|1 year ago

Heck, after writing this article, I’m wondering why email can’t be a standardized JSON-driven API implemented on a web server..:

immibis|1 year ago

It could, but why change what isn't broken? Email messages are quite agnostic to how you deliver them, though. IIRC Google and Microsoft use a proprietary protocol with each other. Outlook uses a proprietary protocol with Exchange.

Email used to be transferred through a non-internet packet-switched point-to-point network of intermittently connected dial-up links. The fact that the email messages are agnostic to how they're transmitted is actually very cool, because it enables switching to future technologies without any changes to the user agents, and vice versa. You put a file in your outbox and it magically appears in someone else's inbox later. Originally mail readers had to be executed on the mail server and read directly from your inbox directory, then we created new last-mile protocols so the reader could run on a separate computer (which in my understanding is basically identical to a Fidonet "point").

You can easily imagine a mail server connected to an onion router, or to Yggdrasil or some other meshnet, or even to whatever remnant of the original UUCP net someone is still running for fun. The current design enables this sort of thing.

sangupta|1 year ago

Just left this comment on your site. Would be much simpler to maintain, switch-to, and motivate for migration.

amanda99|1 year ago

I'm not sure if this is sarcasm or not.

sangupta|1 year ago

Nopes. I am not deep into how email works, but always had this genuine curiosity. Unless, your reply was for the reply to this comment ;)