Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

When did POP and IMAP become a “legacy protocol?”

boston.conman.org

Post reply on HN
Print view View original

71–80 of 222 posts

Re: When did POP and IMAP become a “legacy protocol?”

#71

Post by Ajedi32 »

Avamander wrote: post #3

I get the impression that the article's author didn't really read the linked help page. It's basic auth that's getting deprecated, due to being considered a legacy authentication protocol. For good reasons, as described. That aside, POP should really be considered legacy, it comes with many downsides that hinder people's e-mail usage. IMAP is definitely more functional, but has a successor - JMAP. So in some sense, i…

Are there any non-Microsoft email clients that support different authentication protocols with IMAP connections to Exchange Online? The message from Microsoft certainly makes it seem like IMAP itself is being deprecated.

Re: When did POP and IMAP become a “legacy protocol?”

#72

Post by Dylan16807 »

johnklos wrote: post #43
Dylan16807 wrote: post #17

Earlier quoted context omitted.

Noting an amusing interaction with the context isn't shaming. Though if someone can set it up in less than 15 minutes, and doesn't, I reserve the right to snark. It's not a bad look in cases like that.

The same people who'd claim http is a bad look would also tell you to pipe curl to bash with sudo.

That's a weird claim to make; what makes you think that?

Though I suppose https is a prerequisite for that pipe to maybe be safe. Piping curl to bash varies from stupid to just fine depending on context.

Re: When did POP and IMAP become a “legacy protocol?”

#73

Post by Wowfunhappy »

okasaki wrote: post #23

> I do have to wonder how long until Google decides that only certain clients can connect with Gmail? Already the case on mobile: > If you use the Play store or GitHub version of FairEmail, you can use the quick setup wizard to easily setup a Gmail account and identity. The Gmail quick setup wizard is not available for third party builds, like the F-Droid build because Google approved the use of OAuth for official bu…

Can you get around this by setting an App Specific password on your Google account?

Re: When did POP and IMAP become a “legacy protocol?”

#74

Post by denkmoon »

josephcsible wrote: post #64
denkmoon wrote: post #63

Earlier quoted context omitted.

DoH is bad use DoT instead.

This couldn't be further from the truth. DoT is easy to block, so anyone who wants to censor or surveil you will just do so. You should always use DoH instead, since it's way more resistant to blocking.

Can't wait til google owns your DNS and you can't do shit about it

Re: When did POP and IMAP become a “legacy protocol?”

#75

Post by cortesoft »

bayindirh wrote: post #66
dhiggdyjkb wrote: post #57

Earlier quoted context omitted.

can you explain further?

Two things have happened in the past. Scenario a: 1. Navigate to https://www.example.com 2. Arrive at https://www.completelyunrelated-adsite.com while your address bar reads https://www.example.com They used to do this regardless of your DNS. They directly hijacked that stream/connection. Scenario b: 1. Navigate to https://www.example.com 2. Get https://www.example.com with an ad-banner on top. They happened rarely,…

Scenario A is impossible and has been impossible for as long as https has been a thing.

The only way it would be possible is if you installed a root cert from your ISP onto your computer so that it would trust a cert issued by them. Otherwise, they would not have a valid cert for example.com and you would be presented with a cert error.

This is literally the exact thing https was designed to prevent. It is and always has been impossible (again, unless the client machine is administered by the ISP or whoever the middleman is, and they can install a cert on the machine)

Re: When did POP and IMAP become a “legacy protocol?”

#76

Post by BeefWellington »

oddlama wrote: post #22
hsbauauvhabzb wrote: post #13

Earlier quoted context omitted.

Exactly what risk does it have being on a low profile blog?

I for example just wouldn't like anyone to be able to see what data I exchange with any server, be it small profile blog or a login page.

    I for example just wouldn't like anyone to be able to see what data I exchange with any server, be it small profile blog or a login page.
Note: It's really, "see and modify undetected" what data you are exchanging with any server.

Re: When did POP and IMAP become a “legacy protocol?”

#77

Post by Gigachad »

bayindirh wrote: post #41
cortesoft wrote: post #35

Earlier quoted context omitted.

> If you're not doing anything requiring security, you don't need HTTPS, IMHO. I disagree, for a lot of reasons. For one thing, I don't want some random WI-FI to know every page I visit, even insecure pages. I also don't want to leak any information about my browsing habits. Using https everywhere limits the information you leak about how much of your traffic is sensitive.

Unless you use DNS over HTTPS, all the effort there is moot. Even then, a flow server can trace all the point to point IP traffic passing over it. Yes, it limits the obtained data a lot (no hostnames to begin with), but a proper traffic analyzer is rarely blinded completely by HTTPS.

DNS over HTTPS is default on some browsers now. Firefox does it iirc.

Re: When did POP and IMAP become a “legacy protocol?”

#78

Post by josephcsible »

denkmoon wrote: post #74
josephcsible wrote: post #64

Earlier quoted context omitted.

This couldn't be further from the truth. DoT is easy to block, so anyone who wants to censor or surveil you will just do so. You should always use DoH instead, since it's way more resistant to blocking.

Can't wait til google owns your DNS and you can't do shit about it

How does DoH make DNS any more centralized than DoT does?

Re: When did POP and IMAP become a “legacy protocol?”

#80

Post by Gigachad »

gkbrk wrote: post #50
cma wrote: post #47

Earlier quoted context omitted.

Comcast injects data into plain http pages, altering them when they see fit (they put in a datacap warning into the text of the page).

If Comcast is doing something wrong, why does everyone else need to do something about it? If Comcast stops routing packets on port 433, should everyone else stop using it as well?

ISPs are evil and untrusted. That’s just a fact. The solution is to not allow them to see or modify anything.
Post reply on HN