Dan Kaminsky Profile picture
May 27, 2019 9 tweets 3 min read Read on X
twitter.com/i/moments/1132…

We need books.google.com actually working. If the "marketplace of ideas" is to work at all we can't be locking up everything *but* tech, and then wondering why *only* tech seems to vaguely function.

I adore Wikipedia, but it's not enough.
Let me be clear. I *absolutely* respect librarians. Not because they know how to maintain and locate physical sheets of paper, but because they are sherpas across vast tracts of not obviously connected human knowledge.
Books are not the most searchable resources things, particularly relative to digital search engines. Librarians were who you went to, to be productive anyway.

What, you think those skills don't matter in the digital era? We have *so much more* to archive, acquire, integrate.
I realized all this a while ago, when I tried to research a historical fact I saw mentioned on Wikipedia. All I could find, was that one paragraph from Wikipedia, over, and over, and over again.
Google built the new Library of Alexandria, with books.google.com. It hasn't been burned, but it's been locked up. At the end of the day, the resources do exist, but don't get to inform our debates.

So we're sounding pretty dumb.
We can find economics that work for books.google.com, and of course, for Sci-Hub. There are many capitalisms. Some of them deliver health care. Some of them deliver fake news.
Our civilization is based on the spread of ideas, and it also based on minimizing costs. Those can conflict, and are.

Well, there's a lot of cheap conceptual kit out there, and we're all paying the price. These debates are really stupid. Seriously. What the hell. Ouch.
Where there's openness -- which I'll say, tech has delivered, to itself, for itself, of itself, because *spreading quality knowledge of other fields was and is actively blocked* -- progress and innovation is real, measurable, probably impoverished.

We can allow better.
I think librarians can help us. We gave them something workable once. We can do that again. There's lots of capitalisms. There's lots of copyright systems. Some of them even work.

Not being a librarian (or a lawyer) I should defer to others on structure, but this could help.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Dan Kaminsky

Dan Kaminsky Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @dakami

Dec 19, 2020
The problem with algorithms is that abject stupidity can seem smart when separated from context.

Older COVID patients are ~100x more likely to die if infected. But the residents are spending *months* in COVID wards, *intentionally*.

They’re much more likely to get infected.
Now, these twenty something residents may not die quickly. But we don’t have the complete data on “Long COVID”. Hasn’t been long enough.

Early data is not good. Up to 30% are ending up with chronic respiratory disorders.

“It’s like if 40 pack-years of smoking was contagious.”
The algorithm that only looks at short term fatalities misses both the decidedly non-random exposure probabilities and the preliminary findings on Long COVID.

You know who did not miss those factors? The residents.
Read 9 tweets
Dec 19, 2020
@jeffiel Jeff,

Nobody stays where they’re hated. We are hated, taken completely for granted as tax dollars and despised as invaders otherwise. I’m an actual SF native who has spent most of his life here. It deserves to lose tech, full stop.

You know why we can go?

No mortgages. Oops.
@jeffiel Where was leadership when it came to letting tech put down roots?

The NIMBY bullshit here is so extraordinary, it can be seen from outer space. Literally. Here.
@jeffiel By comparison. Note how things change.
Read 11 tweets
Dec 18, 2020
wait for it
queen on a mean
Read 4 tweets
Jan 5, 2020
You can’t vouch for your own bug. You will always see it as the most beautiful bug that ever did bug. Doesn’t matter if you’re the one who does the thing, or even if you’re right. If it needs a vouch, recuse yourself. It’s ok. It’ll hold up on its own, or not. Learn either way.
On the flip side, be careful whose vouches you do trust. Review boards have drama that has absolutely nothing to do with you, starting from the reality that they can’t accept all the good talks. No room.

People in such situations sometimes get shitty. Don’t take it personally.
You absolutely need external calibration. You’ll eventually notice our culture (for *many* definitions of our) has a positive feedback problem.

A rule of thumb is, don’t seek approval from those who reject everything. What can you expect?

No easy answers here.
Read 48 tweets
Aug 25, 2019
If you want to understand why Linux achieved “world domination” — how it unambiguously wrecked, and rendered irrelevant — Windows and OSX in the cloud, it wasn’t exactly technical superiority.

You choose them, you spend all your time fighting fiddly licensing bugs.

Once.
Nothing is more expensive than having to ask permission.

Nothing is more desired, by some.

@nVidia, you don’t need to bind your ****ing control panel to a single motherboard. It’s ok.

I can hack around all this, and will.
Though repeatedly abandoning working APIs is also a thing.

Oh, Software.
Read 6 tweets
Jul 7, 2019
Hypothesis:

At the microprocessor scale, moving data and computation are not actually different things. You’re always moving bits. You’re sometimes changing them.

Bits may fly straight to RAM and back, or spin inside the CPU. Either way, distance traveled.

Coding is routing.
All models are wrong, some are useful. I think this unified view of computer engineering is interesting. Explains the enormous effects of locality, smaller processes, etc. Shorter distances.

Faster clocks? Bits don’t have to fly as far. Less power per bit. Lighter spins faster.
You could argue this is just another formulation of the time/memory tradeoff, but I think that says recomputing bits on demand is different than restoring them from memory.
Read 23 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(