For what it's worth, RMS' statements on the matter don't appear to concern what is "right", "wrong", or "acceptable" - they appear to concern only the available evidence.
Then again, I've only seen the two quotes appearing in the HN threads.
One of the reasons that this feels so novel is that this is an example of ex post facto enforcement. In this case, Twitter is punishing the user for an action performed at a point in time before such an action was punishable. (In fact, I haven't checked - it may have been punishable, but the punishment was not usually enforced, which is a separate issue of selective enforcement.) The US Constitution prevents both Congress and the individual States from passing ex post facto laws that punish individuals for actions committed before such action was illegal. Obviously, private corporations are not bound by the same laws as the government. So, as platforms like Twitter continue to update their policies and enforcement mechanisms in response to issues such as hate, and as these definitions are broadened, cases such as this are likely to become more common.
When we discovered that neutrinos oscillate, we knew that they had mass because we were able to observe a change from within our frame of reference, implying a finite time dilation. I thought that light was unable to change its physical properties in time (as observed from our frame of reference) due to infinite relativistic time dilation. How is it possible that we can observe torque, a change in angular momentum, for a particle moving at the speed of light?
Judging from the units on the graph, looks like the author measured the inverse reactive current used by the unilateral phase detractors. Cache purging wouldn't play a role unless your prefabulated amulite is out of sync.
Yes, on newer versions, this can happen when Tracking Protection is enabled. This feature causes things like CAPTCHA and other third-party scripts to break. When this occurs, look for a shield icon in the URL bar to the left of the green TLS padlock. Click it and disable Tracking Protection. This has fixed every site issue I've seen so far.