Because I am the firstiest wordiest!
There is something going on with the font sizes on mobile, especially with respect to the headlines. We’ll get that sorted out. I’m not sure what you’re seeing with the left margin. I do see a margin on my phone. But I’ll play with it a little. Both the headlines and the department are serif. That hasn’t changed from the previous design.
The variable width preference does work on article pages as well as the front page. I'm not saying you're not seeing a problem, but the two page types use the same CSS for managing the content width, and variable width on article pages works for me on multiple devices and browsers. So, if you are seeing variable width on the front page, but fixed on article pages, something odd is going on. I'd recommend clearing out your techdirt.com cookies and shift-reloading to be sure you have the latest CSS.
They did modify the email. We would have appreciated it if they modified it (much) less.
There's a way to do this using a preference setting here: https://www.techdirt.com/preferences.php
Set "Page Width" to variable.
I've been using TLS to read Techdirt for over an year. My browser shows it's currently using a Cloudflare certificate. So what's really changed?
While we've "supported" HTTPS/SSL/TLS for a while now, it's only since June that we've defaulted to it and made sure all Techdirt resources are served over a secure connection. But the news here is Namecheap coming on board as a sponsor of that move.
(oh for fucks sake: probative is a fucking word, PLEASE, techdirtia, ditch your idiotic spel czech which is CONSTANTLY flagging real, common words)
Sorry. It appears that some time during the night, one of our 3rd-party spam filters started getting very aggressive. We're working to get that resolved.
My point? You said that Techdirt is "not real code" because it's Wordpress. It's not. Never was. I thought that, you being a genius and all, it might satisfy your intellectual curiosity to know something about the actual origins of the code. So my point was to add a spark to your already brilliant light. But, um, never mind.
Nothing has changed and your votes are being registered. If you vote on a comment and you're not signed in, then you reload the page, of course the button doesn't stick. You're not signed in. We can't assume you're the same person. The behavior you're seeing is expected, correct, and has been exactly the same since the day we launched comment ratings. Feel free to vote as often as you'd like.
Just in case you're interested, Techdirt is not on Wordpress (though perhaps it will be someday). It is run on custom code loosely based on the old slashcode, which we ditched almost a decade ago.
Or you could go to the preferences page (signed out) or account page (signed in) and set the preference to disable the bar.
This is the new version of Wibiya's toolbar, which we're trying out with the hope that our readers will find it more useful than the old one. One thing the old one had, which the new is missing, was a button to collapse the bar. We've already contacted Wibiya about it -- we think there should be a way to collapse the bar, without completely disabling it.
I kinda like it too. Will keep it in mind for the next site redesign.
Should say November. Fix should appear momentarily.
After some investigation, it appears that the problem comes from a combination of the HTTPS Everywhere Firefox extension and the implementation of the Facebook Like button in the Wibiya toolbar (at the bottom of the page). The other Like button we include below the text of each post doesn't appear to have the same problem. We've removed the Like button from the toolbar and reported the problem to Wibiya.
Yeah, we read our posts. Haven't seen this problem though.
However, we have received a few messages in the past 12 hours about the issue. We're looking into it, but it appears to be related to a Firefox extension called HTTPS Everywhere. For some reason, that extension and the Like button appear to not be playing well together. We don't have any more details than that, yet. But we'll let you know when we do.