Thanks, I see that sdl2-compat-2.30.51-1 has landed in Arch since.

I’d start by comparing the following in the working vs non-working cases:

1. Is there a corresponding /dev/input/js* device?
2. If it’s there in both cases, any difference in permissions? Check both regular Unix perms using ls -l or stat and ACLs using getfacl

deleted by creator

1. The basics: high quality terminal emulation with utf-8 and directcolor support
2. Customization is by simple git friendly text config. Build time config (ala st) is acceptable if done in a reasonable way.
3. A way to pipe panes into external commands to allow for customized url and other other data extraction. Built-in regexs are not always enough and doing it on the tmux side is not always ideal.
4. Control over key bindings and mouse behavior
5. Small, very fast, instantaneous startup
6. Very predictable behavior, no surprises
7. Minimal dependencies (including build time) are a plus. Definitely no 100MB+ electron beasts.
8. Support X11 since I am sticking with that for now
9. A codebase I can understand in case I need to change it. Simple and fast build. For core tools like terminal emulators I must be able to build or modify them without much trouble.
10. Not too much extra junk. I don’t use menus, tabs, scrollbars etc so I don’t want the terminal to be huge or slow to support every feature others might want. I will put up with some extras if they can be completely disabled and don’t significantly affect performance or startup time or code complexity.
11. Absolutely no network service integration, no matter how well intended. The only acceptable network activity is talking to the X11 socket.
12. Longevity. I like to use my tools for years and years. I am interested in new tech of course but I don’t hop from one hype train to the next.

I know this is not everyone’s cup of tea but you asked what I want. And nowadays it’s at least as much about do not wants as wants.

I briefly tried ghostty when it was going around earlier. Slow startup time (~250ms if I remember right), the gtk-4 dependency and some weird defaults like the client side decoration (which I gather can be turned off in config) made me pass on it for now but might take another look in a few months. It didn’t seem particularly revolutionary to me either but there are plenty of much worse options out there too.

Any naming convention is fine as long as it’s meaningful to you. But it’s a good idea to keep your own repos separate from the random ones you clone from the internet.

What I see is an inexperienced developer who instead of systematically debugging the issue keeps trying random stuff hoping that it will somehow work.

It depends. If there is any money on the line or don’t want to burn bridges then I’d do the smart thing, whatever that is. Otherwise I’d just skip it.

If you have an email workflow that you like then something like rss2email might be an option. You simply feed your incoming rss into your email. You’ll want to auto-tag (or otherwise organize) these emails to keep them separate from regular emails. Then you use your usual email tools to organize them further.

I’ve been using such a setup for the past 15 years.

I’ve done many hours of phonecalls on mine. Mic quality is acceptable, slightly mushy. Wind is an issue for example when riding a bike at higher speeds. Wearing a hoodie over them can block the mic too.

I’ve been using various Aftershokz/Shokz models for many years and well over a thousand hours. They are a great option for speech-focused contents like podcasts, audiobooks and that’s what I use them for. I almost never use them for music, the lack of bass (even with earplugs) just doesn’t do it for me. But I don’t find any earbuds satisfactory for music either so maybe I am more picky than most.

I agree with OP about the controls. They are workable but could be much better even considering the limited inputs. I particularly hate the choice of triple-click for backwards-seek and I mess up the timing half the time. Another pet-peeve is the loud beep on play/pause that cannot be turned off. Using the phone/computer controls instead of the on-device ones avoid these issues.

As far as models I originally got the Aeropex and later on “downgraded” to the OpenMove. The audio quality is comparable between the two, the only thing you are missing with the lower end model is comfort - but that is highly subjective! I actually prefer the way the OpenMove feels.

I really wish that there was more competition in this space. The Shokz products are a bit overpriced and slow to evolve and the rest of the options I’ve seen seems lower quality and worse form factor. Would love to hear if anybody has found a different brand that they prefer over the Shokz models.

SearXNG is great at what it does but it falls into the Bing/Google/etc-frontend category since it just forwards your query to one of the search engines it has modules for. It doesn’t have its own crawl and index.

I wish that was the case but sadly most of them are basically Bing or Google frontends or belong to entities that I trust even less. As far as I can tell there are very few independent crawls out there.

Roguelikes: DCSS, Shattered Pixel Dungeon, Nethack

Costs a lot less than therapy too.

They federate because it’s the most efficient way to scrape fediverse instances and build profiles on fediverse users.

That’s not true. Quiet scraping is much easier to implement than integrating AP into your platform.

And keeping the v2 (or v3+WebRequest) support in the browser is not enough, they’d also have to start running their own extension store since presumably the Chrome one will no longer carry such extensions.

Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).

These tools work by creating a virtual keyboard so they don’t let you send input to a specific window. The input goes to whatever happens to be focused at the moment. This makes them less reliable than the X11 equivalents and unusable for tasks where you need to guarantee that the right window gets the input.

Those of us who use the autocd feature of shells “execute” directories all the time. For example I’d type just /usr/bin RET if I wanted to cd to /usr/bin.

not having kludges 42 levels deep

There are already almost a hundred extension protocols and you need dozens of them to implement just barebones desktop functionality. If you look under the surface the Wayland ecosystem is arguably already more complex than X11 ever was and it’s only going to get worse.

There is a fairly compact Thinkpad USB keyboard which would be much easier to connect if you can make it fit somehow. It has the trackpoint but no trackpad.