Papermerge version 2.0, version 2.1 and version 3.0 are entirely different and incompatible applications.
That doesn’t exactly inspire confidence in the future versions of this application, given in particular the use case of long-term document archival :).
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.
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.
In other words, if all the billionaires just ceased to exist, it would result in the humanity achieving the emission goals?
Just keeping a single frame buffer image can take tens of megabytes nowadays, so 100MB isn’t all that much. Also 64-bit can easily double the memory consumption, given how pointer-happy the ELISP data structures can be (this is somewhat based on my assumptions, I don’t actually know the memory layouts of the different Emacs data structures ;)).
But I don’t truly know, though. If I start a terminal-only Emacs without any additional lisp code it takes “only” 59232 kilobytes of resident memory. Still more than I’d expect. I’d expect something like 2 MB. But I’ll survive.
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.
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.
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.
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.