The author is Raymond Chen, and the blog is probably the single most influential blog on windows internals. He has decades of amazing posts that are well worth a read.
That's not how it works. Rather, there's a tug of war between upvotes and flags. If the flags get the upper hand, [flagged] appears, and if they dominate, then the post also gets killed. In the latter case users with 'showdead' turned on in their profile will see [flagged][dead].
Most likely due to some physical (not legal) issue that would make it mechanically unsafe to operate the vehicle above that speed even in an otherwise appropriate location. (Or perhaps it's due to some obscure state law, or the manufacturer is just out to spoil your fun, or ... who knows?)
More generally, I agree with the point you make here about the responsibility to configure things correctly. However, it seems to me that Microsoft is also on the hook for failing to include the necessary context when an MFA request is sent. It's a bit like selling a car with seat belts that superficially appear to work but fail at the slightest provocation, no?
I thought the way you wrote it was clear but these comments got me curious what the various conventions might be so I took a quick look at :help in Vim (since it lists an awful lot of key bindings). I'm now officially confused and don't think you can go too far wrong.
In some contexts :help notates things as characters (ex zh, zH, and z<CR>). In other cases I'm seeing things written as <S-F11> and <C-G>. There's also CTRL-H (instead of <C-H>) but I'm not seeing shift written out like that for whatever reason. Sometimes they get mixed (I'm not sure what the rules are) such as for hh<Space> and hh<C-]>. Amusingly enough, :help appears to treat Meta-{char} as case sensitive but CTRL-{char} as case insensitive (I assume there's a reason). I also spotted a <kPlus> (for the keypad).
> Who spends that much time just in the command line these days?
Just stop using GUI utilities. It really is that simple. If you just don't use them you'll end up in a shell out of necessity because you still need to get things done.
Of course, the majority of my time is spent in my web browser reading documentation followed closely by vim for writing things. Actual time spent interacting with CLIs is a small minority at the end of the day.
> We limit speech already, you can't advocate for the killing of other people, races, etc...
Actually, not that I support such behavior but (at least in the US) you can generally advocate for it. People usually don't (thankfully) so I don't have any examples immediately to hand, but my understanding is that the legal test is "imminent lawless action". (https://en.wikipedia.org/wiki/Brandenburg_v._Ohio)
> free speech is the solution to all democratic problems, it's not an absolute good
Rather than an absolute good, I would argue that it ought to be viewed as an absolute right. I would also argue that, whether used for good or ill, free political speech is a functional necessity of any democracy. (Necessary but not sufficient and all that.)
> in a way censorship might be already happening. In this case non-arousing messages are being suppressed
Agreed, but it's a separate issue and I've no idea what anyone is actually supposed to do about it.
Those aren't mutually exclusive. The government can simultaneously regulate specific behaviors of large entities where there is reason for concern while otherwise largely leaving them to do whatever they want.
I don't think GP is necessarily suggesting that Trump will address their objections or that they personally support him. Rather, I read it as suggesting that much of his support may in fact be due to backlash against such cultural trends on the left.
You have an incredibly well put message here, but then you went and tacked on those last two paragraphs that border on uncivil, are polarizing, and (IMO) fail to add anything meaningful.
This mirrors my experience perfectly. Conduct on HN is uncommonly civil (for the internet) across the board - props to Dang and whoever else moderates things. Insightful discussion, however, is almost entirely limited to the extremely technical submissions. From biochemistry to compilers to machine learning, they consistently attract participation at a truly impressive caliber.
Sometimes I wonder what HN would be like if it were somehow possible to preemptively block the majority of the "fluff" articles that make it to the front page. I guess there's no way to automate such a determination though, and even if there were any such action would probably anger the majority of the user base.
Actually, in the age of ML it more or less does. You wire up the model, specify the metrics to optimize for, and then feed it lots of data. The algorithm figures out the details of how to achieve the specified goal on it's own. Have a look at (https://cs.stanford.edu/people/karpathy/convnetjs).
I suspect you're being rhetorical, but the algorithm and specific metrics to use are selected by the developer. The data is entirely user generated - it's the result of collecting the metrics over some period of time. The trained model is the result of feeding the collected data into the chosen algorithm.
The point is that the algorithm is, for all practical purposes, tuning itself. The developer has essentially selected a black box to feed the data into, told it what to optimize for, and given it the ability to wiggle a bunch of unlabeled knobs. Which knobs it should tweak and in precisely what way is never specified by the developer. Instead of "show the following things to the following users", the developer just says "maximize number of videos viewed per visit" and the algorithm tweaks whatever parameters have been made available to it until it finds something that works.
Unfortunately, "something that works" is often not what we might have liked. ML is a bit like a Djinn, fulfilling wishes in an unpredictable and borderline malicious manner.
The original devblog from 2005 is (https://devblogs.microsoft.com/oldnewthing/20050412-47/?p=35...). Aside: Upon pulling that up, I recognized the author as the one who wrote my favorite article about undefined behavior (https://devblogs.microsoft.com/oldnewthing/20140627-00/?p=63...).