If not DT Jan 6 attack on US Capitol fits under:
TREASON, SEDITION, & SUBVERSIVE ACTIVITIES
2381.Treason.
2382.Misprision of treason.
2383.Rebellion or insurrection.
2384.Seditious conspiracy.
2385.Advocating overthrow of US Gov.
2389.Recruiting for service against US.
1/

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.

1. I was walking in the woods yesterday and I had an epiphany. It wasn’t one I wanted to have. I was thinking about today’s class, where we are reading Kimmerer’s ‘Gathering Moss’. I’ve taught Braiding Sweetgrass in multiple classes every year since 2016. It’s eminently teachable

2. Both books are beautifully written. Students uniformly enjoy them as assigned reading. They do a great job communicating to non-Indigenous folks the contours of basic Indigenous relationships to more-than-human beings. They’re wildly popular with white readers.

3. I’ve found Braiding Sweetgrass to be a great entry point for non-Indigenous folks to Indigenous scholarship. But this is where yesterday’s epiphany comes in. Neither Braiding Sweetgrass or Gathering Moss tends to the deep deep lineages of Indigenous scholarship in Canada or US

4. As the popularity of ‘Braiding Sweetgrass’ has soared, I’ve seen more and more white folks wax on about ‘braiding knowledge’. But they often don’t know any of the lineages of these concepts beyond what is presented in this one book. They confidently run with this.

5. Kimmerer does a commendable job of weaving in her own experiences, her family stories+nods to some very important knowledge keepers who deserve to be celebrated for their work. But Braiding Sweetgrass does not tend to the citational politics Sara Ahmed & others teach us about

THE LESSER KNOWN MAHARANA OF MEWAR:RANA KUMBHA
Kumbalgarh Fort is one of most spectacular sites of India,atop a hill abt 3600ft above sea lvl in the https://t.co/LkjmzzBhE2's second largest wall is surrounding it.A fort wall second only to Great wall of China,still not so famous.

This longest wall of India stretches to almost 36Km and encompasses a few hills, many step wells and over 360 temples and palaces. Birth place of the Great Maharana Pratap, this fort is named after another Great Maharana of Mewar, who is not given his due in the History.

Builder of many architectural marvels like the Kumbhalgarh Fort, an erudite scholar, a patron of arts, music, culture & a great warrior was the Great Maharana Kumbha. Yet we don't know much about him. Let's get to know him a little.

Maharana Kumbha was the undefeated King of Mewar from 1433-1468CE.He never lost any battles &kept Mewar out of the reach of Islamic Invaders till the time he was alive. Born on Makar Sakranti to Maharana Mokal & Saubhagya Devi, Rana Kumbha was only 13 when he ascended the throne.

His father was killed by his own relatives in a political conspiracy. He was a powerful King about 8ft tall &charismatic personality,a hardcore Hindu Rajput who could shed his life for Hindu honour without thinking twice.He was an ardent skillful warrior who never lost a battle.

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.