I have a canned reply to these to try to get them fixed, so there’ve been many opportunities for someone to communicate back.
8,758 karma · joined February 5, 2012
I have a canned reply to these to try to get them fixed, so there’ve been many opportunities for someone to communicate back.
People will forget their middle initial in their email (or others won’t notice it), or they’ll add firstlast as a recovery email or something.
Receiving other people’s email never stops being funny to me. Some of them are grumpy about it (especially the one who paid for and distributed “thousands” of poorly designed business cards.)
More have a sense of humor, and I’ve enjoyed getting to know a few of the other guys with the name over the years.
Calling out some specific popular extensions that overreach for permissions would be a nice addition or followup to your post.
A scheme to be able to show coercive parties fake votes would be known to them immediately.
(I paid for Current to try it when it came out.)
Someone talking on the phone but facing away from the room isn’t usually considered rude, either.
In a waiting room or train car, if you’re sitting and talking on the phone or Zoom, you’re broadcasting into the room with your posture. Your voice tends to broadcast as well with no wall or other conversant as an immediate barrier.
I auto-run the skill when certain changes are detected in a branch and it takes just a few minutes. Recommended if your work shows up in browsers.
If the app is offering what appears to be momentum, it's implemented its own acceleration/deceleration algorithm. That's a lot to ask of an app, and they aren't equally good.
Detecting a wide range of underlying terminal support for a CLI app is a pain and prone to errors/drift.
There are various plugins that attempt to solve this, but it'd be nice for someone to solve it once and for all, and then upstream those layers into open source as this project is promising to do.
Multiplexers have a lot of little papercuts and limitations when you want consistent and native-to-the-OS behavior to flow all the way between the OS and the apps and connections in the multiplexers. For example, gesture scrolling in a tmux/zellij pane is hard because the right events don't flow through. It's an itch to scratch like designing a good terminal lib (like ghostty.)
And then, there's all the unifying and smoothing out of data connections--I imagine they'll be a lot to make sure that, e.g., an ssh session or a Claude code session in a pane can be seamlessly reconnected or never drop when the pane is closed. This takes a lot of hacking to make look seamless in most setups right now.
Like mitchell, I write a lot of software around multiplexers, and I've thought about making something similar, but I don't have quite the same level of personal wealth or angel investor connections. :)
herdr and mosh are a couple of reference points for this, there are others.
Messing around with ground panels is lower risk and safer than roof panels where tool extenders and ladders start to become involved. If you have roof panels, you are the biggest danger to your panels (and yourself.) Don't try to clean them, spray them, knock snow off of them. I was told this multiple times by my installer. :)
- Less training; org probably has someone who’s used Wordpress before. (Yes, training. You must deal with the reality of the typical user.)
- In the developing group or agency, anyone can work on the theme if you install a theme builder. An agency can put a cheaper content marketer or designer on it, rather than a developer.
Pointing out they generated it at least encourages them to write a shorter article that says what they meant.