In 2003's Pattern Recognition, @greatdismal discusses the role of "apophenia" - finding patterns where none exist - in paranoid thinking. We are a pattern-matching animal, prone to seeing faces in clouds and hearing speech in static.

https://t.co/lKHfKbvzLN

1/

The Night of the Short Fingers saw many of the US's largest tech companies blocking Trump and trumpist platforms like Parler, provoking a storm of punditry about What It All Means for the tech companies to have taken this content moderation step.

1/

The best expert I know on the subject is @jilliancyork, my @eff colleague. She's published "an ongoing list" of "everything pundits are getting wrong about this current moment in content moderation."

You should read it.

Here's some highlights:

“Deplatforming Trump sets a precedent."

York: "The only 'precedent' set here is that this is indeed the first time a sitting US president has been deplatformed by a tech company."

3/

But political leaders around the world have already received this treatment: Lebanon, Burma, etc. Even the reach of the deplatforming is nothing new: last summer's US Iran ban saw blocks of everything, up to and including Etsy listings for "Persian dolls."

4/

As the Qanon prophecies fail and the cult-members struggle to resolve their cognitive dissonance, it's a good time to revisit the history of paranoid, conspiratorial political movements in American history - the "paranoid style" that has dominated since the Revolution.

1/

After all, the very first skirmishes of the US war of independence were based on a conspiracy theory: that the levy on tea was a prelude to a sellout of the colonists to transnational mercantalist interests. US politics have always been conspiratorial.

2/

I found @zacharykarabell's @politico history of the Know Nothing party especially useful, as it tells the story of what happens when surging, paranoid, fractious political movements

The American Party was a secret 19th century organization founded on a conspiracy theory: that Irish immigrants were secretly planning a takeover of the US on behalf of the Pope.

4/

If you think "It's not censorship unless the government does it," I want to change your mind.

It's absolutely true that the First Amendment only prohibits government action to suppress speech based on its content, but the First Amendment is not the last word on censorship.

1/

Here are some kinds of private speech-suppression that I think most of us can agree are censorship: when the John Birch Society burned mountains of rock records and novels - or when Tipper Gore's PMRC pressured record stores to drop punk, metal and rap albums.

2/

Or the Comics Code Authority, which signed up all comics publishers and retailers to block comics if they contained anything unfit for small children, which stunted American comics for generations while their European counterparts created entire sophisticated genres.

3/

Or MPAA ratings, in which a secret group of censors (falsely described as frequently rotated, randomly selected parents - really they're long-serving studio insiders) decides whether movies get NC-17 ratings and thus be blocked from nearly every screen in the country.

4/

(You can learn more about this from Kirby Dick's unmissable doc, "This Film Is Not Yet Rated," which documents both how the MPAA misleads the public about ratings, and uses them to block LGBTQ

2022 is shaping up to be a bloodbath. The Trump census cooked the numbers to advantage Republicans, and GOP statehouses are poised to redistrict in ways that will hand potentially permanent minority rule to the GOP in Congress.

1/

There's a potential way out: #HR1, an omnibus bill of electoral reforms that would create durable, structural protections for voting rights and a level playing field for campaigning.

2/

To get a sense of how urgent the looming crisis is - and of how important HR1 is - listen to @ryangrim interviewing @schwarz and Rep @JohnSarbanes [D-MD] on this week's

In theory, HR1 could be blasted through - Dems control the Senate, Congress, and the White House, and the future of the party depends on it, but I'm far from confident that they'll find the discipline and political will to make it happen.

4/

The Democrats keep squandering their majorities and wasting opportunities to make real change - changes that are must-haves, not nice-to-haves; changes needed to head off existential threats to the nation itself.

5/

Republican North Dakota legislators have introduced #SB2333, a bill that prohibits large tech companies from locking their users into a single app store or payment processor.

https://t.co/PgyhgOhFAl

1/

While his has implications for Android and other large tech platforms, its most immediate and far-reaching effects with be on Apple, whose Ios platform uses lock-in to monopolize both apps and payments (and another domain, not mentioned in the bill: repairs).

2/

Predictably, this has thrown Apple into a fury, with Apple's privacy chief @erikn telling the SD legislature that Apple uses its monopoly over the app store to protect its users' privacy and

Neuenschwander makes a good, but incomplete, point. To the extent that Apple has the same interests as its users, it uses its app store monopoly to lock out bad apps (to the best of its ability).

4/

But when Apple's interests diverge from its users' interests, the prohibition on sideloading apps actively harms those users' privacy and security. Think of how Apple caved to Chinese state demands to remove working VPNs from the Ios app store to facilitate mass surveillance.

5/

I got a Toshiba T1200, which has a bad screen, and a dead CMOS battery, and I thought the hard drive was broken too...

but I rebooted it and heard a KTHUNK and a really loud spin-up noise and holy shit, the hard drive works!

and it still has files on it. the newest date is January 1994.

It's a 21mb hard drive, with ~37k of bad sectors.

This fucker is never going to spin up again, so I better go find some serial cables and copy shit off now.

The backlight is fucked so I'm shining a flashlight on it.
without it, it looks like this.

Torn between "I think losing $100 million when someone beats you at security research is pretty much exactly what you signed up for doing yield farming" and "Maaaaaaaybe not the future of finance you were expecting, huh."

How to put this in regular finance terms...

Suppose hypothetically you have an account at a brokerage with some valuable asset in it. You take a margin loan against that asset to fund your normal spending, or pay a tax bill, or maybe buy something at another brokerage.

For reasons known only to the brokerage, they don't denominate your loan in dollars. They denominate it in shares of a money market fund, which are worth $1 +/- epsilon and basically never deviate from that.

And you think "Hmm, I have a large equity cushion against this loan."

One day, a computer system at the brokerage reports, sorta-kinda erroneously, that the value of the money market fund is actually $1.30 per share. The equity cushion is gone. Your valuable asset is sold, at timing you didn't choose, at wrong price, to pay an inflated phantom debt

And your recourse is... probably tweeting at patio11 saying he finds too much joy in this.

Which I don't; I just feel like this is why you don't trust a CPU built out of redstone to build reliable financial infrastructure on top of.

you know how Atari called the Jaguar as a "64bit system", because it had two 32bit CPUs? (or because it had a 64bit bus, but let's not worry about that)
we should apply that logic to the current generation of consoles.
So the Switch is a 256bit console. It's the Nintendo 256.

The Xbox Series X? terrible name.
Better call it the "Xbox 512 Blu-ray".
like the Jaguar CD, the Sega CD... the good old days when consoles had their media type in the name.

Boringly the PS5 is also a Playstation 512 Blu-ray, because both of them are using the same AMD Zen 2 CPU.

The Switch one is weeeird. It's built on an Nvidia Tegra X1, which is an 8 core 64-bit CPU, so that should be 512, right?

Well... no. Four of them can't be used. And later documentation doesn't even mention them.

it's some weird system where the system-on-a-chip has four Cortex-A57 cores and four Cortex-A53 cores but only the A57s are usable?

Next up in Privacy Technology at #enigma2021, Kelly Huang from @ethyca speaking about "GONE, BUT NOT "FORGOTTEN"—TECHNICAL & PRACTICAL CHALLENGES IN OPERATIONALIZING MODERN PRIVACY

Just imagine there's a global pandemic forcing everyone to stay home and buy their stuff over the internet. And you've been working on your sanitization-on-demand startup. You've got more users than you can count! ... literally, because your data's all over.

Now you're a multi-national international country with privacy issues because your information is all over the place.

Now a user writes to request you delete their data. Where is it? How do you do that? Who's responsible for privacy in your business.

How do you operationalize privacy rights?

Primary stakeholders:
* Legal
* Business
* Engineering

We spend a lot of time on Twitter analyzing the legal rulings, but it's harder where the "rubber meets the code" 🥁

@zkat__ I'm in the position that I actually find npm / yarn the best ecosystem. Whenever I use something else I always end up stubbing my toe into something thats missing / feels wrong.

Ex. Cargo seems to neither have a concept of devDependencies nor peerDependencies.

I also can't understand why it wouldn't have an "add" command to add a new dependency. And I'm no fan of Toml, json is greate (easy to parse and build tooling around), and the better option in my opinion would be json5.

C / C++ seems to just not have language package managers. The linux / bsd crowd seem to have decided that the system package manager also should be the language package manager. Which might have been fine if every Linux distro used the same system package manager.

Instead we end up with a N x M problem. Where we have a bunch of different operating systems and they all support multiple system package managers. So there's no easy way of distributing, referencing and updating C / C++ packages.

It is also my opinion that the compiler / runtime should be a package dependency. I don't like Rust's split between rustup and cargo (they should have been one tool). Similarly it would be better if you added Node as a dependency to package.json, that way we wouldn't need NVM.