Live data from Hacker News

HTTPS on Stack Overflow: The End of a Long Road

nickcraver.com

81–90 of 183 posts

Re: HTTPS on Stack Overflow: The End of a Long Road

#81
post #61
post #53

Earlier quoted context omitted.

What sort of company do you work at? Why can't everyone just be told not to post code?

What sort of company do you work at where every employee obeys every directive?

What sort of company do you work at that this sort of crude blocking attempt would actually work?

Re: HTTPS on Stack Overflow: The End of a Long Road

#82
post #8
post #5

Note to self: Use subdirectories, not subdomains in the future

TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?

How would they prove that you own every subdomain?

Re: HTTPS on Stack Overflow: The End of a Long Road

#83
post #22
post #4

> The password to our data center is pickles. I didn’t think anyone would read this far and it seemed like a good place to store it. You ought to have more confidence in your writing. BRB stealing all your servers.

Only if you get there first. And it may in fact be pickles2.

It's actually hunter2

Re: HTTPS on Stack Overflow: The End of a Long Road

#84
post #8

Earlier quoted context omitted.

TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?

How would they prove that you own every subdomain?

I'm not sure I understand the question. If you own something.com then you automatically own any possible subdomains.

Re: HTTPS on Stack Overflow: The End of a Long Road

#86
post #8

Earlier quoted context omitted.

TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?

Subdomains were killed by SEO a long time ago (afaik, Google does not transfer domain PageRank credit to subdomains), so this is not limited solely by the cost of wildcard certs.

But this is orthogonal to the issue of LetsEncrypt not delivering wildcard certs.

Re: HTTPS on Stack Overflow: The End of a Long Road

#87
post #8

Earlier quoted context omitted.

TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?

Subdomains were killed by SEO a long time ago (afaik, Google does not transfer domain PageRank credit to subdomains), so this is not limited solely by the cost of wildcard certs.

But this is orthogonal to the issue of LetsEncrypt not delivering wildcard certs.

Re: HTTPS on Stack Overflow: The End of a Long Road

#89
post #45

Earlier quoted context omitted.

Some people don't spy on their customers and don't have these kinds of information available for analyses They're admittedly few though and their moral high ground is debatable considering that there are self hosted FOSS alternatives around nowadays

Calling aggregate anonymous analytics "spying on your customers" is absurd nonsense.

It's "spying" when you're gathering data they didn't consent to give, like mining through their contacts, scanning running processes or uploading unrelated content from their computer. The browser User-Agent string is hardly classified information.

Re: HTTPS on Stack Overflow: The End of a Long Road

#90
post #69
post #49

Stack Exchange is no longer available from my workplace due to this change. We have a strict no-posting-code-fragments policy, and SE was viewed as too risky to allow without some restriction in place to make it read only. Before HTTPS, the IT department had worked out such a read-only restriction by blocking the SE login with firewall rules. But with HTTPS that kludge is no longer possible, so the site is blocked.

Same thing happened to me at a workplace once. They blocked StackOverflow, GitHub, Bitbucket, Sourceforge, CodePlex and Google Code. I told them all estimates go up by 2 years since we would need to reimplement everything. It ended up being unblocked a week later.

I don't know how you'd get anything done since there are answers on Stack Overflow that solve problems that otherwise would involve hours to days of fussing to come up with the same non-intuitive solution.

All roads lead to Stack Overflow these days for progrmaming problems.

Post reply on HN