From experience, dont do this unless you have a very good desoldering setup. The joysticks have 14-16 pins and you need to be able to desolder every single one perfectly to get it off the board. Getting the new one on can be similarly difficult.

I have seen some custom tips for these but haven’t tried them yet.

If that hasn’t dissuaded you, then calibration itself is easy. Just connect it to a computer and go to the calibration website (it’s a GitHub page that does it all in JS).

Your readline config sucks because the default sucks.

Add this to your .inputrc:

"\e[A": history-search-backward
"\e[B": history-search-forward

BGP isnt just Turing complete, It’s Cthulhu complete

real men write their code one bit at a time with a laser pointer and a fiber optic network cable

Or you could just use zig which is better at compiling C than C (the second it supports the espressif chips I’m never touching C again)

Squirrel vs snail - who wins?

I get very far by just keeping a set of folders for each piece of equipment in a git repo.

Pictures, etc, and sometimes the PDF manual if I bother.

The difficult part here is being consistent over time - making sure you mark down when you bought things, serial numbers, etc. a proper website/app will force you to do this, but there is flexibility in having whatever convention you like most

Strongly agree. A guide for dead simple setups would be incredibly useful (e.g. gsuite as idp, oauth for a single app).

It took me a few days to get that basic setup working, and a few days more to improve it. But once it was up, it was rock solid.

Keycloak might seem a little daunting to start with, but is basically glue between your idp (ldap) and whatever apps need to authenticate.

Many cloud providers (the cheap ones in particular) will put patches on top of the base distro, so sometimes root always gets a password. Even for Ubuntu.

There are ways around this, like proper cloud-init support, but not exactly beginner friendly.

Struwwelpeter

Edit: spelling

Once upon a time, I accidentally created a folder named “~” in my home folder (the company provided scripting framework would inconsistently expand variables, so the folder had a ton of stuff inside it).

I ran “rm -rf ~” and only panicked when I started to wonder why it wasn’t taking too long.

Good news is that it only managed to get halfway through my local checkout of aosp before I stopped it. Bad news was that it nuked most of my dotfiles.

The original article smelled wrong when they claimed to have broken AES. Thankfully, Bruce Schneier is far more authoritative than I ever will be and gives a short and succinct list of links to debunkings of this.

Those young machine spirits need their rest

Yes. I’ll read the content, but I try to avoid interacting.

Mind you, db0 himself is a tankie, although he doesn’t seem to insist on imposing that on the users or communities on his instance.

EDIT: I stand corrected. Apologies to db0 for lumping him in with that crowd.

Only on signup

Anything using Blind as a “verified industry source” is going to be skewed to the type of person who uses Blind. Beyond that, it’s low sample size, and there are suspiciously round fractions for some of the larger companies. Worse, because Blind is blind - this doesn’t represent current employees, but merely people who worked at some point in the past at those companies.

Not saying it’s not good - just saying not to get overly excited over a badly done survey

Nope. Bitkeeper used it in the master-slave pairing and the term was carried forward. Gitlab did a whole writeup about it.

TCP Selective Ack is very much a thing, but it does take extra memory so lots of TCP stacks exclude it or disable it by default.

TCP was never designed with wifi in mind. TCP retransmission was only ever meant to handle drops due to congestion, not lossy links.

Tmux is a wonderful complement to mosh. Together you get persistence even when your local client loses power (speaking from experience)

I worked with mosh for years to connect to servers on other continents. It was impossible to work otherwise. It only has two small warts: forwarding, and jump hosts.

The second is fixable/ish with an overlay network, but that isn’t always an option if you don’t control the network. I tried to solve this with socat but wasn’t able to configure it correctly - something about the socket reuse flag was very unhappy.