catatonicprime

@catatonicprime@defcon.social
69 Followers
78 Following
1.5K Posts

I like hacking, and learning, and jiu jitsu.

favorite biome: high desert

he/him/they/them

LocationArizona, USA

look I'll be the first to admit that fedi has problems and that the world is kind of falling apart around us

and it's easy to forget or overlook

but ... we built this place

we don't need Them, we have this place that's For Us, and we fight to keep it that way, and mostly? mostly we fucking win

don't forget what we can do, together

@mos_8502

"I set up Claude to eat ChatGPT's ass and now I get so much housecleaning done"

stop using twitter.

there are no more excuses.

get your news and your cti elsewhere.
the only reason the news and cti vendors stay on twitter is because you, the audience, are still there.

so leave.
take your clicks and your eyeballs to another platform.

it will make them leave.
dont wait for the critical mass to form

BE THE CRITICAL MASS

your body is a vote.
choose wisely.

You aren't going to get owned by quantum dark blockchain AI, you're going to get owned by somebody with a British accent phoning up your Service Desk at 2pm on a Friday with a kebab in their mouth. www.ncsc.gov.uk/guidance/mit...
This is exactly what the internet is for.

Hey, please stop repeating the misinformation that corps are legally required to maximize profits or your shareholders can sue you. It's propaganda promoted by a handful of huge fund managers because they'd *like that* to be true.

Even SCOTUS agrees “Modern corporate law does not require for-profit corporations to pursue profit at the expense of everything else, and many do not.” (Burwell v. Hobby Lobby)

Ahh, the cliche technology problem solving process:

1) Write a thing
2) Thing doesn’t work
3) Iterate on thing
4) Read documentation to try and fix last broken thing
5) Realize documentation is wrong and/or outdated
6) Check GitHub to see how others solved your problem
7) Realize they did not actually solve your problem, just their problem
8) Rewrite thing from scratch using documentation
9) Now everything is broken, huzzah!
10) Start yanking features until thing works
11) Question your technical expertise in thing you’ve managed before
12) ???
13) Thing is fixed, code looks identical to before in concept but different in structure
14) Scream at the Gods, who will neither hear nor respond to your anguished sobs.

SD cards are a technology taken right out of early Gibson, real neuromancer shit. Incredible trash tech. Gigabytes of low quality abundance. Small enough to lose even when you're paying attention. Extraordinary but embarrassingly low grade.

There's very nice classy ones from SanDisk but there's so many more from nameless foundries for sale on AliExpress and a tenth the price, that mostly work.

(Chairman George Morrow would shit bluebirds: "never underestimate the bandwidth of a station wagon full of floppy disks", two obsolete things in one sentence.)

I'm using the big ones in my cp/m machine. Doing serious endurance testing and marginal testing. The really cheap ones do _weird_ things sometimes but work ok, mostly. I now have some good test code, ask me in a week....

With two cards installed, on the same SPI buss, doing random disk random block random read/write I *suspect* there is some odd stuff going on, but it's hard to separate code from electronics from the cards' various effects.

Pretty fucking interesting though.

I want to make the cheap cards as usable as the good ones. I think tristate buffers will do that.

Rooting for the underdogs.

Its damn near impossible to work all week, work on your side projects, invest time into hobbies, spend time with loved ones, work out every day and eat properly.