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

HTTPS on NYTimes.com

open.blogs.nytimes.com

Post reply on HN
Print view View original

81–90 of 167 posts

Re: HTTPS on NYTimes.com

#81

Post by notatoad »

mparlane wrote: post #72
redcastle wrote: post #19

Earlier quoted context omitted.

Google Chrome is supposed to soon start flashing a "not secure" warning on HTTP sites that have password forms [0]. That's probably at least one motivation for these publisher moves to HTTPS [0] https://security.googleblog.com/2016/09/moving-towards-more-...

What happens with local LAN machines, like the admin webpage for your wireless access point? It's not like they can go HTTPS?

if those pages are not secure, then they will display "not secure" in the address bar.

They're not trying to force everything over to https, they're just trying to make warnings more sane. And if a page is not secure, marking it as such makes sense.

https://security.googleblog.com/2016/09/moving-towards-more-...

Re: HTTPS on NYTimes.com

#82

Post by xorcist »

dazc wrote: post #70
stephancoral wrote: post #67

Earlier quoted context omitted.

Just use Incognito mode and clear your cookies. The NYT paywall is a joke

Sure, that works fine for specific articles but I miss the serendipity.

Is it not enough to do Preferences / Privacy / Cookie Exceptions and choose to not accept cookies from them?

I block a lot of sites which started to personalize content in an unwanted way.

Re: HTTPS on NYTimes.com

#83

Post by berry_sortoro »

No need, who would like to read the Lügenpresse securely anyway. People must be really uninformed to even pay for their own propaganda and then get a Comcast like experience like described below when wanting to cancel.

And of course a comodo cert, the worst incompetent thing you can get. https://www.youtube.com/watch?v=pDmj_xe7EIQ. I would prefer Letsencrypt over anything and not at all because its free.

Re: HTTPS on NYTimes.com

#84

Post by r3bl »

mparlane wrote: post #72
redcastle wrote: post #19

Earlier quoted context omitted.

Google Chrome is supposed to soon start flashing a "not secure" warning on HTTP sites that have password forms [0]. That's probably at least one motivation for these publisher moves to HTTPS [0] https://security.googleblog.com/2016/09/moving-towards-more-...

What happens with local LAN machines, like the admin webpage for your wireless access point? It's not like they can go HTTPS?

There's gonna be a small "not secure" label next to the URL (like there's now the "secure" label on HTTPS websites in Chrome/Chromium). It's not like you're not going to be able to open the webpage or anything.

Re: HTTPS on NYTimes.com

#85

Post by sjs382 »

caconym_ wrote: post #41

The thing the NYT needs to fix (as of earlier last year) is the fact that you can't cancel your subscription without calling them (which is not the case for signing up). I spent 20 minutes[1] on the phone telling them that yes, I really did want to cancel. It was a worse experience than dealing with Comcast, not least because I felt bad for the poor woman who obviously had some financial incentive to get me to stay o…

Similar issue, but they kept billing me. Then cancelled again, and they kept billing me again. Wasn't until the 3rd time that they stopped. I was able to get reimbursed via chargebacks but still, terrible experience.

Re: HTTPS on NYTimes.com

#86

Post by djsumdog »

compuguy wrote: post #71
caconym_ wrote: post #41

The thing the NYT needs to fix (as of earlier last year) is the fact that you can't cancel your subscription without calling them (which is not the case for signing up). I spent 20 minutes[1] on the phone telling them that yes, I really did want to cancel. It was a worse experience than dealing with Comcast, not least because I felt bad for the poor woman who obviously had some financial incentive to get me to stay o…

So even if you are getting the digital subscription, you still have to phone in to cancel?

It's called a "Dark Pattern" and there are some other HN posts on it.

Re: HTTPS on NYTimes.com

#87

Post by bsdetector »

thampiman wrote: post #25

How is this news worth upvoting though?

Context is the key.

They say HTTPS is complex to enable and imply they've been working on it for up to two years. And they finally get it done nine days before Trump.

Some people and organizations are panicking, either about his behavior or that net neutrality is out the window or about some boogeyman. That's why this story is relevant, now, because it's an indication that NYT may feel the internet will soon be a much more hostile environment.

Re: HTTPS on NYTimes.com

#88

Post by xux »

caconym_ wrote: post #41

The thing the NYT needs to fix (as of earlier last year) is the fact that you can't cancel your subscription without calling them (which is not the case for signing up). I spent 20 minutes[1] on the phone telling them that yes, I really did want to cancel. It was a worse experience than dealing with Comcast, not least because I felt bad for the poor woman who obviously had some financial incentive to get me to stay o…

For all newspaper subscriptions (and all other semi-shady companies), I use Privacy.com. It allows you to create silo-ed credit card numbers and specify how much each card is allowed to charge you per week/month/overall.

When I want to cancel a newspaper subscription and it's impossibly difficult, I just email them telling them I'd like to cancel the subscription delete the associated credit card. Not my problem anymore

Re: HTTPS on NYTimes.com

#89

Post by r3bl »

snug wrote: post #66

I wonder what the reason for HTTPS only for "Articles published in 2014 and later"

Yeah, one would think that it's an easy job, but media organizations tend to have different projects, CMSs, designs, sometimes even (sub)domains for different things.

Media websites are constantly-evolving beasts, with a small tech team trying to hack shit up to make them work, and killing older content is never even an option.

At the end, with a limited amount of (mostly human) resources, you kind of have to draw the line somewhere and introduce the change, otherwise you will end up postponing it for possibly months.

Post reply on HN