![](/static/0b35d4a1/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
But how many use it for browsing, which I imagine this data is from?
But how many use it for browsing, which I imagine this data is from?
Am I to understand correctly that if you are running Gtk+ apps in the Gnome compositor, you get this working, but if you are running non-Gnome compositor with Gtk+ apps, it will not work? Or is it independent of the compositor?
You should have backups. Preferably also snapshots. Then rm will feel less scary.
If you want to have multi-host redundant storage at home (via e.g. minio or ceph), S3 is a pretty good protocol to provide it.
S3 is nice in the way it’s not a file system so it can have relaxed semantics, while also providing secure access to individual files over HTTPS via URL signing.
Some people seem to be stuck in the idea that S3 means cloud hosting. Not sure if that was your view, but it’s worth spelling out sometimes.
Boox Tab Ultra
Looks pretty nice device! Even the camera makes a bit sense in the demo they give (though apparently in practice the scanning rarely works). And cheaper to boot as well. I might consider getting this one.
But is the display really better quality? Atleast the DPI is slightly higher at 219 on the Boox Tab Ultra vs 190 on the Daylight. And Boox weighs 70 grams less, and that’s the device some reviews call heavy (and some lightweight…).
These reviews mention the slow display speed:
So perhaps there is some room for improvement? That being said, some other reviews don’t mention it and one says it’s faster than typical e-ink display, though that doesn’t sound immediately purely praising.
In the end it probably comes to the software: how fast it is, it well it works, how nice it is to use. It seems both have customized the standard Android, so I suppose the difference is in which one has done it better and which one has better custom apps. Per the reviews Boox doesn’t fare too well in this aspect. Maybe someone will make a comparative review of the devices.
As opposed to buing a separate display for the computer?
I like to think this thing would be nice reading the news while having a breakfast or reading an e-book outside or at the bed, not near my computer. So it makes a lot of sense to build a tablet with this display technology.
Zooming and panning a pdf is arguably more comfortable with higher frame rate.
What a nice succinct explanation!
But also completely useless. Run0 ignores the suid bit for the same reason as 99% of command line apps do: it ignores because it isn’t relevant to its functionality.
Would that kind of provision allow me to have my code removed from a git repository history, if that git repository is hosted by a company?
I think the second point is the biggest for me: it’s almost like Canonical wanted to have a single dominant store for apps, as the ecosystem they are building supports only one. And, apparently, that one server is also closed?
So if you try to make an alternative source and give instructions to people how to configure their snap installation to use it (I found this information very hard to find for some reason…), your “store” probably won’t have the same packages Canonical’s has, so users won’t be able to find the packages and I imagine updates are also now broken?
Contrasting this with flatpak: you just install apps from wherever. Or from flathub. Or your own site. Doesn’t matter. No business incentive behind—built into the tools—to make everyone use flathub.org.
By that logic, is the compositor working any different than a trojan? Is there really a difference?
The Wayland compositor is always capturing all your keyboard and mouse as well. No permissions asked. Pretty sus.
I have 64GB RAM and my 64GB swap still gets filled to 60% over time.
It just happens so that apps end up touching some memory once that they never then use again. Better use some SSD for that instead of RAM.
I suppose it explains why people have a bad attitude about Wayland when tools providing useful functionality are described as trojans.
X11 can (…mostly…) have great security by just providing a suitable X Security module to it. It just seems it wasn’t considered that big of an issue that anyone bothered. Nokia Maemo/Meego used to rock such a module.
It’s two commands to grow the / fs on the fly:
lvextend -L+10G /dev/mycomputer-vg/root
resize2fs /dev/mycomputer-vg/root
So don’t worry about it. LVM is great :).
It doesn’t actually detect moved code, though, like git diff
can? I gave it a shot and also there’s a couple issues open about it, e.g. https://github.com/Wilfred/difftastic/issues/520 .
Other than that, difftastic is quite nice.
I use etckeeper to autocommit changes in /etc as git just has better and faster tools to look at the changes of a fle, compared to backup tools.
It’s just so easy to do that there hardly is any point in not doing it.
I was under the impression cross-site cookies are a standard feature per the RFC, though? Or is Patreon using some kind of non-standard extension?
Speed records aren’t usually representative of regular use top speeds, are they?
And how about the actual speeds they are used with? Another poster suggested the maintenance costs of traditional speeds skyrocket as speed increases, while maglev doesn’t really have a lot of stuff that wears down in the first place.
My /home is also on a separate filesystem, so in principle I don’t like to mounting data under there, because then I cannot unmount /home (e.g. for fsck purposes) unless I unmount also all the other filesystems there. I keep all my filesystems on LVM.
So I just mount to /mnt and use symlinks.
Exception: sshfs I often mount to home.