I note that Linode will still let you run exit nodes on their infra (though they may ask you to respond to specific complaints to reduce the exit policy).
The comic satirizes the 2026 US tariff rationale, vs. worker protection tariffs. But I do often think about Noam Chomsky's opposition to NAFTA[0] when talking heads explain why tariffs are bad.
One of the ironies of a vibe coded VHF teletext is that the LLM-pocalypse prompted dropping low-level network support (AX.25) from the Linux kernel, which is the basis of a lot of ham networking experiments.
There are userspace workarounds for much of what was dropped, there were no real upstream maintainer of this stuff, and it was justifiable to drop AX.25 support. I don't really understand any of it, nor am I in the unenviable position of keeping it around/working. But a real mixed bag of ham news, AFAICT.
I didn't see it got dropped, that is very unfortunate but also understandable. It's been a few years since I last messed around with it. If I recall, what was in the kernel at the time had a few issues and hadn't been touched in a very long time. It was a huge hassle to get working, there wasn't much up to date documentation.
I made back images and kept a lot of the documentation in case I needed to go back since it was tricky to find the first time.
However once you do get it working it's very satisfying to see a connection through a VHF radio appear in the native linux networking stack. Opens doors to a lot of goofy and fun ideas.
Zoning is likely a big part of what causes people to become medium wealthy. Making it legal to build on every parcel also helps avoid concentrating wealth.
I hate this thing where we can't do a thing that helps a ton of people, because it also helps people we hate.
It's so poisonous to politics, and everyone does it for their pet peeve.
Can't do permitting reform, can't fix education, can't loosen bad regulation, all of it because someone you don't like might benefit and fuck that guy.
Los Angeles, whose population is only 50% higher than Houston, has 25x as many people who are homeless (75k vs 3k).
If people couldn't afford food because there wasn't enough food grown, no one would think handing out food stamps would work. It's silly to think that doesn't work for housing.
These may be accurate and real, but I also wonder if this might partially be because Houston sucks in terms of lived experience for the homeless so they tend to end up elsewhere?
Texas has a recent and storied history of just busing people out of state or into other cities for people it deems are problematic or they don't want to deal with. So it would not surprise me if some of the stats are cooked or they've partially swept the problem under the rug.
I gave actual stats. They also match my impressions driving around both cities. If you have stats about the scale of busing people out of state please do share.
What you've suggested may account for some of the difference. But "Houston has liberal zoning and builds more houses" is a far simpler explanation for the staggering 25x difference in homeless population between the cities.
Very cool that GitHub actually put stacks in the UI vs. GitLab's `glab stack`[0] (which looks just like the `gh stack` part of GitHub's thing).
One part that seems like it's going to feel a little weird is how merging is set up[1].
That is, if I merge the bottom of the stack, it'll rebase the others in the stack, which will probably trigger a CI test run. So, if I have three patches in the stack, and I want to merge the bottom two, I'd merge one, wait for tests to run on the other, merge the second vs. merge just those two in one step (though, without having used it, can't be sure about how this'd work in practice—maybe there's some way to work around this with restacking?)
> So, if I have three patches in the stack, and I want to merge the bottom two, I'd merge one, wait for tests to run on the other, merge the second vs. merge just those two in one step
As we have it designed currently, you would have to wait for CI to pass on the bottom two and then you can merge the bottom two in one step. The top of the stack would then get rebased, which will likely trigger another CI run.
Thanks for the callout - we'll update those docs to make it clear multiple PRs can be merged at once.
I’ve been using Ctrl-s for years. Nothing else uses it because it’s historically been used for terminal flow control, but that doesn’t really have much use in a graphical terminal with history and scrollbars and so I’ve never missed it. Has similar two-finger ergonomics to the Ctrl-a bind as well.
edit: oh, and I think Ctrl-space is the keystroke to get a nul character, and vi uses that character to insert the last entered piece of text in insert mode. It looks like Ctrl-@ does the same things, but tmux might not be able to tell the difference either.
Ctrl+s is evil. I can't count how many times I froze my terminal by accident before realizing that Ctrl+q "unfreezes" it. I absolutely support rebinding it.
Same, I used C-a for a while until I found out its default mapping is jumping to the beginning of the line so I rebound tmux prefix to C-Space. Now my only problem is on a few servers where I haven't copied my dotfiles.
reply