I think I could easily enjoy the gesture, however it's way too easy to trigger. It's like a one centimeter movement on a tablet. E.g. the Android app switcher needs a much bigger movement to trigger app closing.
flux
joined 5 years ago
It comes from the words "Eight Megs And Constantly Swapping".
Yeah, the name hasn't aged well..
^Zkill -9 %1 is the only way.
kill -9 -1 if that doesn't work.
Do share if you have experiences using yabridge with the flatpak distribution of Bitwig! My existing setup did not work with that, but the deb version worked ok on Debian, so I keep using that.
One other thing is that you can bulk create your own instances, and that's a lot more effort to defederate. People could be creating those instances right now and just start using them after a year; at least they have incurred some costs during that..
I believe abuse management in openly federated systems (e.g. Lemmy, Mastodon, Matrix) is still an unsolved problem. I doubt good solutions will arrive before they become popular enough to attract commercial spammers.
There is the DJVU format for this exact use case, but you'd need to convert them to, say, pdf for many use case. Its also a bit old and perhaps not maintained, soo..
HEIF and other modern video encoders (HEIF=H265) should fare a lot better than JPEG, though.
I believe it's quite possible that there is no information where a removed file belonged to in exr4fs and it's ilk; after all they also have concept of "lost and found" files, and files there also don't have that information. If the directory they were contained in gets overwritten in a form that the file is not there, then the information is likely gone; along with the name of the file.
Just get a secondary device, recover everything you can, pick the files you needed. Consider yourself lucky if you get to restore the file you lost.
Good luck recovering your files! For future I recommend making backups. I use kopia, borgbackup is also popular.
No always-on display and waterproof rating only to 1m instead of 30m, though 😞.
Nevertheless, quite interesting. Maybe at some point new more capable hardware will arrive.
My main reason is that it's built for a single package repository -- basically making it a separate garden.
I mean you can change the "store", but let's say you do: then you cannot install packages from the first repo as you can only have one repository active at a time. And because Canonical's is the largest, it's not very feasible to provide an alternative.
Btw, can you find out how its changed? Last time I checked it wasn't too easy.
Contrast this with flatpak where basically anyone can provide packages. There are no walls between repos. It's the intended use case.
Indeed to me it seems Canonical is aspiring to become the appstore for Linux with Snap whereas flatpak implements the values of open source community, not monopolistic ones. I don't know of any technical benefits Snap has over Flatpak; perhaps there are some?
Though if I have some misconseptions about Snap, I'm happy to be educated :).
I doubt there would be a measureable benefit: after all, the kernel is already compiled without 32-bit support, and the code related to it just doesnt exist in the resulting binary. I assume there could be some small exceptions, though, like choosing to do something in a certain way so that the same approach will also work for 32-bit, and opting for another approach would perform better in 64-bit. That's just a guess, though.
It's mostly about maintenance load.
Btw, with PAE the host can have more than 4 GB of memory, so the limit would only apply to individual processes. Still quite feasible to use that kind of system even in the modern day--even if the browser can sometimes become quite large.. And then there are of course the numerous embedded applications.