37

Thanks a lot for your times to write that to explain the situation. It’s really appreciated. I will state it to let other know that I don’t intend to quit my moderation tasks. nb; to state my position on the issue: If some of you are following what unfolded with the new CoC, please know that I was a witness in the start of the event, and in a indirect ...


11

Thanks again for these summaries, Ward. Personally, I've been writing answers under a Don't assume gender rule for many years now. This has generally been pretty easy here. As Ward notes, The strict Q/A format doesn't require much in the way of pronoun usage. Why use a pronoun when you works as well. Where it comes in are comments, especially when more ...


9

Not much has actually happened in the last month or so... SE never responded to Monica's attempts to talk and she eventually decided her only recourse was legal action. Once that started, SE's official had to become "no comment," and they decided to remove any links they become aware of (including profiles and usernames) to the GoFundMe Monica Cellio page ...


8

The biggest barrier standing in the way is that Gravatar doesn't support HTTPS, and Gravatars are a big part of StackExchange as a whole. There are a variety of other items that are included from 3rd party sites which would also prevent full SSL "green-bar" support. Until such items are fixed or engineered around (such as building an HTTPS-enabled Gravatar ...


5

Your question has to do with system administration, and is on topic here. I can't say whether you're more likely to get a good answer at Sharepoint, but most of the questions I have seen there are about using it, rather than administering it. You might also want to ask about the question on their site meta.


5

All the reasons @Chopper3 gave are still valid ones: The actual authentication process is secured over SSL/TLS. (at least if your OpenID provider isn't made of suck) Everything else you do on ServerFault is public* Adding SSL to StackExchange sites is computationally expensive (Good enterprise SSL accelerators range in cost from about as much as a pony to ...


4

tldr; some sub-sites are justified, others are just a pain. I believe so, especially when you consider that revenue is generated via ads, and the more visits to a single SE site the better. I tried to get the good folks over at RPi.SE to see that their questions fit happily inside of a linux SE and a Embedded electronics site such as that proposal I just ...


4

It seems that this only affects Google Chrome beta (Version 30.0), it isn't a problem with Stack Exchange.


3

Declining as we only support Google v31+ (I know it wasn't the case before, but it's not worth fixing it now).


3

The funny thing is that now a proper SSL certificate is installed, the problem is that it only has names stackexchange.com and *.stackexchange.com. It should be simple to get serverfault.com, stackoverflow.com, etc added as alternative names. Update: but most still redirect to http, except for stackexchange.com itself.


3

If you would like to code your own solution to the problems posted, you are welcome to do so. To post it here, simply explain that you coded something, link to it, and most importantly explain how the code solves the problem. We welcome links to your github (or any other repository), but make sure that the Answer you post here contains a whole answer to the ...


1

So, fast forward to 2014, Stackexchange can now be accessed via https (Yay! And rightly so: Wikipedia is "public" too, still I don't want my employer/wifi sponsor/isp/... to eavesdrop on the connection) - but only with mixed content (Imgur? Quantcast?) and with TLS 1.0 only. Are there any plans to fix this as well?


1

An SSL certificate is important when the StackExchange API is used with JavaScript. Any website that wants to display items relevant to user private data, on a page protected with SSL will show errors about unsecure content. And as Yuhong Bao mentioned, https://www.serverfault.com does have a cerificate, but that certificate is invalid as it only covers *....


Only top voted, non community-wiki answers of a minimum length are eligible