About 20% beyond core case of government-critical speech in formally public spaces and media I'd say.
There are only 3 real challenges to free speech at the tech level a) the need for CDNs at scale b) distortions of net neutrality c) nation-state firewalls.
All other claims are about social governance on private sites, where applying free speech doctrine is a stretch at best
About 20% beyond core case of government-critical speech in formally public spaces and media I'd say.
That's a genuine de facto increase in practical, informal free speech/expression.
This is reasonable. You should not expect no-strings-attached access to the attention of potentially billions of people under the same terms as ranting from a soapbox in a 19th century town square.
More from Venkatesh Rao
Both this thread and the outraged response threads are... something.
This is why I never wanted kids. Way too much responsibility for another human’s development. Depending on the child, this might either be the day they discovered who they were or the day that traumatized them into a lifelong fuckup. Either way I don’t want to direct the show.
As far as the can opener goes, it wouldn’t even occur to me to try and turn it into a teachable moment. That sounds vaguely quixotic. I’d just show them how immediately. I think my default is to try and instruct clearly but not demonstrate unless the person is truly disoriented.
I think there’s basically a right answer here: show the kid. If the kid has the aptitude they’ll enjoy the mechanism so much they’ll develop the figure-it-out skill with other devices. If not, it’s a training data point that will build remedial levels of intuition more slowly.
I think perseverance is both misframed and over-rated as a virtue. Misframed as in: everybody has potential for it in some areas and lacks it in others. Aptitude is those areas where perseverance comes easily to you. Meta-skill of knowing where/why you persist is more important.
So, yesterday my daughter (9) was hungry and I was doing a jigsaw puzzle so I said over my shoulder \u201cmake some baked beans.\u201d She said, \u201cHow?\u201d like all kids do when they want YOU to do it, so I said, \u201cOpen a can and put it in pot.\u201d She brought me the can and said \u201cOpen it how?\u201d
— john roderick (@johnroderick) January 2, 2021
This is why I never wanted kids. Way too much responsibility for another human’s development. Depending on the child, this might either be the day they discovered who they were or the day that traumatized them into a lifelong fuckup. Either way I don’t want to direct the show.
As far as the can opener goes, it wouldn’t even occur to me to try and turn it into a teachable moment. That sounds vaguely quixotic. I’d just show them how immediately. I think my default is to try and instruct clearly but not demonstrate unless the person is truly disoriented.
I think there’s basically a right answer here: show the kid. If the kid has the aptitude they’ll enjoy the mechanism so much they’ll develop the figure-it-out skill with other devices. If not, it’s a training data point that will build remedial levels of intuition more slowly.
I think perseverance is both misframed and over-rated as a virtue. Misframed as in: everybody has potential for it in some areas and lacks it in others. Aptitude is those areas where perseverance comes easily to you. Meta-skill of knowing where/why you persist is more important.
Heh, one thing the nyt piece managed was to do a Cunningham's law nerdsnipe-wmd at newspaper scale... now a bunch of people are energetically trying to post the right answer.
IMO trying to correct whatever the NYT writer thought he knew/understood is futile. "Willing to be misunderstood by the NYT" should be the default stance unless you want to waste a lot of time correcting an obsolete 2013 map for people who don't care.
The thing is, the NYT still has enough normative cultural power, even as it has fallen from newspaper-of-record, that it takes a particular sort of heretical self-confidence to sort of ignore whatever they happen to be wrong about on any given week, whether or not it concerns you
A subtle shift has occurred in the workings of the Gell-Mann amnesia effect. It used to be an individual private amnesia re: media ("I'll believe myself when I am certain they got it wrong because I'm an expert, but still believe them when I am not"). Now it's a collective effect
A sort of common-knowledge threshold has been crossed lately. "Everybody knows that everybody knows the NYT is wrong on X across largish subcultures." It's no longer mutual beliefs being validated occasionally 1:1.
One other thing I should really clarify and that the @nytimes piece got *severely* wrong: while I believe there are very strong sociological and even causal links between rationalism and NRx (especially in the Silicon Valley homes bases) their ideological and methodological
— (((E. Glen Weyl))) (@glenweyl) February 14, 2021
IMO trying to correct whatever the NYT writer thought he knew/understood is futile. "Willing to be misunderstood by the NYT" should be the default stance unless you want to waste a lot of time correcting an obsolete 2013 map for people who don't care.
The thing is, the NYT still has enough normative cultural power, even as it has fallen from newspaper-of-record, that it takes a particular sort of heretical self-confidence to sort of ignore whatever they happen to be wrong about on any given week, whether or not it concerns you
A subtle shift has occurred in the workings of the Gell-Mann amnesia effect. It used to be an individual private amnesia re: media ("I'll believe myself when I am certain they got it wrong because I'm an expert, but still believe them when I am not"). Now it's a collective effect
A sort of common-knowledge threshold has been crossed lately. "Everybody knows that everybody knows the NYT is wrong on X across largish subcultures." It's no longer mutual beliefs being validated occasionally 1:1.
More from Tech
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Machine translation can be a wonderful translation tool, but its uses are widely misunderstood.
Let's talk about Google Translate, its current state in the professional translation industry, and why robots are terrible at interpreting culture and context.
Straight to the point: machine translation (MT) is an incredibly helpful tool for translation! But just like any tool, there are specific times and places for it.
You wouldn't use a jackhammer to nail a painting to the wall.
Two factors are at play when determining how useful MT is: language pair and context.
Certain language pairs are better suited for MT. Typically, the more similar the grammar structure, the better the MT will be. Think Spanish <> Portuguese vs. Spanish <> Japanese.
No two MT engines are the same, though! Check out how human professionals ranked their choice of MT engine in a Phrase survey:
https://t.co/yiVPmHnjKv
When it comes to context, the first thing to look at is the type of text you want to translate. Typically, the more technical and straightforward the text, the better a machine will be at working on it.
Let's talk about Google Translate, its current state in the professional translation industry, and why robots are terrible at interpreting culture and context.
Straight to the point: machine translation (MT) is an incredibly helpful tool for translation! But just like any tool, there are specific times and places for it.
You wouldn't use a jackhammer to nail a painting to the wall.
Two factors are at play when determining how useful MT is: language pair and context.
Certain language pairs are better suited for MT. Typically, the more similar the grammar structure, the better the MT will be. Think Spanish <> Portuguese vs. Spanish <> Japanese.
No two MT engines are the same, though! Check out how human professionals ranked their choice of MT engine in a Phrase survey:
https://t.co/yiVPmHnjKv
When it comes to context, the first thing to look at is the type of text you want to translate. Typically, the more technical and straightforward the text, the better a machine will be at working on it.