404 karma · joined March 30, 2018
https://meet.hn/city/gb-London
Socials: - github.com/liskin - linkedin.com/in/pivnik - reddit.com/user/Liskni_si
Interests: Cycling, Fitness, Gaming, Hacking, Hiking, Open Source, Outdoor Activities, Programming, Remote Work, Running
---
This is not accurate. It runs quite a lot of legacy Xorg code actually, just without the input and video drivers.
I'm asking in the context of installing a single CLI tool into ~/bin or something. There's no requirement to satisfy all dependencies, because the only dependency I care about is that one CLI tool. All I want is an equivalent of what `cargo install --locked` does — use the top-level lockfile of the CLI tool itself.
Rust has `cargo install --locked`, which will use the pinned versions of dependencies from the lockfile, and these lockfiles are published for bin packages to crates.io.
But it seems npmjs doesn't allow publishing lockfiles, neither for libraries nor for CLI tools, so if you try to install let's say @google/gemini-cli, it will just pull the latest dependencies that fit the constraints in package.json. Is that true? Is it really this bad? If you try to install a CLI tool on a bad day when half of npmjs is compromised, you're out of luck?
How is that acceptable at all?
xrandr --delmonitor screenshare
before this to seamlessly update the shared region — Chrome will immediately pick up the change and continue sharing the updated virtual monitor.
geo=$(slop -f '%w/1x%h/1+%x+%y') && xrandr --setmonitor screenshare "$geo" none
So… you can expect apps developed by engineers in London to get much worse on slow internet in 2025. :-)
Oh, and speaking of responsiveness, I found that it depends on temperature a lot. E-ink apparently has a sweet spot at room temperature, but when I use the device outdoors, in either sub 10 ˚C temperatures or over 30 ˚C the screen changes noticeably slower.
If the "keepassxc" package is to be replaced by the two alternatives ("keepassxc-full" and "keepassxc-minimal"), you'd still need a transitional dummy package named "keepassxc". That package would depend on "keepassxc-full | keepassxc-minimal", giving the user a choice to satisfy the dependency by installing either of those. So far so good. What if the user doesn't explicitly choose, though? The idea is that an upgrade would keep the "-full" variant but "apt install keepassxc" would pull in the "-minimal" variant. How do you encode this in Debian package metadata?
I think both "apt install" and "apt full-upgrade" will simply choose the first alternative, so you get either "-full" in both scenarios, or "-minimal" in both.
The original post is just a badly written clickbait. Nothing was removed, it was just moved to the keepassxc-full package.
Running an IRC server is absolutely not as difficult as running a Matrix server.
There is no state, so you can literally build a tiny Docker image with the config baked in, run it on a VM with the specs of a cheap computer from the 1990s, and then forget about it for years. If it gets hacked (which I think isn't super likely as it's a small codebase that's been out there for decades), you build a new image with a more recent version of ircd.
Google Play in a browser: "This app is not available for your device"
Google Play app: "This item is not available in your country."
Aurora Store: "Download Failed. App not purchased"
Great launch indeed. Bravo.
They do, but the fonts are visibly blurry on those, as they did indeed remove the subpixel antialiasing. Thankfully, the Gtk4 developers removed it as well, so Linux (or at least the GNOME desktop) will soon look like crap as well.
I've had artists send me mp3 in the morning after I gave them cash at a concert the night before. :-)
Not really in "production", but I have a lot of small-ish shell scripts all over the place, mostly in ~/bin, and some in CI (GitHub Actions) as well.
> 1. … You'll need some rebase-fu to handle that, and the pain is significant if the chain is long.
`git rebase --update-refs` on the last branch will handle updating of all the intermediate branches in the stack, you just need to force-push them all at the end.
It does help with 2. as well, but you will indeed need to manually update the target branch of a single PR on GitHub.