@lanodan@smlavine@navi It’s clear that we’re from wildly different economic backgrounds. Keyboards are not only cheaper than game pads, but a necessity to use the computer. Game pads are an expensive add-on. Gaming keyboard are an expensive upgrade.
@sebastian Don’t threaten me with a good time. I *wish* package registries didn’t exist. Centralised package registries of this kind are an absolute terrible idea.
@navi@smlavine Using a controller on PC is mainstream now? I’ve always seen people use mouse + keyboard (and I worked at LAN gaming venues and gaming hardware stores during the 2000’s).
I thought game pads on PC were kind of a niche thing and mostly used with emulators.
@lanodan It's true that distros rarely check signatures, but I still want to provide the means for them to do so, because they most definitely SHOULD be checking them.
What are general thoughts on signing #git tags with #ssh keys instead of #gpg keys?
I can't say that I'm a huge fan of GPG, and I'm considering whether using SSH keys to sign releases is more convenient and equally valid for downstream.
@lanodan Touchpads without clickable buttons (e.g.: where only tap clicks) are pretty common in my experience. IIRC many Dell models are like this. I think the Framework laptop too? I'm sure most of the ones I see at local electronics stores don't have clickable buttons.
Of course, there might be a huge mismatch between "laptops used by libinput devs" and "laptops out there wild".
@lanodan I prefer touchpad with no buttons to be honest. It's easier to just tap where my finger is rather than click a button elsewhere. I do hate those where there's an unmarked region for left click and another for right click. One finger for left click and two finger for right click makes more sense to me.
Regardless of taste (where we can agree to disagree), touchpads with no buttons should be usable out of the box, not behind a software toggle.
The fact that "tap to click" is disabled by default on most compositors (including so-called "user friendly" ones like KDE) drives me completely crazy.
Picture this: someone doesn't have a physical mouse, and isn't a keyboard-driven person. They want to click somewhere, but clicking with their trackpad is disabled by default. To enable it, they have to enable a checkbox in settings.
I just learnt to use `git checkout --theirs` during a conflict resolution. My first impression is that --our and --theirs have the exact opposite meanings of what one would intuitively expect.
The documentation actually points out that these names "may appear swapped", which further reflects that the names are poorly chosen (why not pick different names).
Tip: --their and --ours only make sense if you're rebasing someone else's work onto your own branch. The opposite of the typical usage.
Is there any lightweight #mqtt server which I can use on a production host? I don't need ultra-high scalability; I'll have less than a dozen clients, pretty low scale.
I want to avoid rolling my own, but can't find anything lightweight and simple.
@nobodyinperson mosquitto is too immature and full of bugs. Example: any time a client disconnects, its CPU usage jumps to 100% *forever* (see: https://github.com/eclipse-mosquitto/mosquitto/issues/2807 ). I can reproduce this 100% of the time; has this not been an issue for you, or do you just have a dedicated host for it?
Having used git before forges were so popular was really a blessing. I don't think I'd properly understand how git works if I had to learn it today. All of it is too entangled with coding platforms, the most popular ones proprietary black boxes.
TechsmithInterested in #SelfHosting, #OpenSource, #Sustainability, #DigitalRightsUser of #AlpineLinux and #OpenBSD.xmpp://hugo@whynothugo.nl or #whynothugo on irc.libera.chat