3 ms·
I agree with your comments about web-based e-mail clients, but: > many organizations don't allow anything but HTTP, so it's easier to just use it. Remember wh
by djsumdog 10y ago
I agree with your comments about web-based e-mail clients, but:
> many organizations don't allow anything but HTTP, so it's easier to just use it.
Remember when we allowed for newer protocols to have their own ports and didn't blacklist everything but HTTP? Why are we doing this again, now? Please don't say security/firewalls or else I'm going to ram an ice pick in my eye.
If your organisation is blocking ports, they're probably filtering HTTP. Companies that care about filtering deny access to most personal e-mail on work machines. So basically you're saying "let's abuse HTTP so people can violate company policy."
You may or may not also being saying, "Let's build a brand new awesome shiny latest and greatest protocol...and permanently tie it to the technical debt wreckage of HTTP/2.
oh and Google could just fix their terrible broken IMAP implementation.