Yote.zip

Yeah there’s a few ways they could be acquired. I don’t do Amazon or Kindle but they appear to be on Kindle Unlimited. They’ve also apparently been sent out for free a few times. I feel like it puts a bad taste in my mouth either way; even if I could sidestep the cost, by reading them it would still be supporting the books and therefore the gouging of others, in an indirect sense.

I haven’t read this series yet but it’s on my TBR. Is there some kind of actual justification for the price of these books? The combined total word count of all the books is ~350k, which is 50k words shorter than a few books I’ve recently read that cost $7-8 each. Meanwhile the entire Murderbot series costs $76 to purchase, most of them being 30k words for $12.

I’m lethargic on both getting around to reading it and not letting those hefty prices color my opinion if I were to read it, so I’m not sure if I ever will.

It has a very high opinion of itself.

JXL is the best image codec we have so far and it’s not even close. I did a breakdown on some of its benefits here. JXL can losslessly convert PNG, JPG, and GIF into itself, and can losslessly send them back the other way too. The main downside is that Google has been blocking its adoption by keeping support out of Chromium in favor of pushing AVIF, which started a chicken and egg problem of no one wanting to use it until everyone else started using it too. If you want to be an early adopter you can feel free to use JXL, but just know that 3rd party software support is still maturing.

Something you might find interesting is that the original JPEG is such a badass format that they’ve taken a lot of their findings from JXL and made a badass JPEG encoder with it named jpegli. Oddly, jpegli-based JPEGs are not yet able to be losslessly-compressed into JXL files, per this issue - hopefully that will be fixed at some point.

Syncthing - No introduction needed. Couldn’t live without it.

Healthchecks.io (you can self host this) - Dead man’s switch monitoring for all my automation. Most of my automated scripts hit up a Healthchecks endpoint when they run, and if they fail to hit the endpoint on a regular schedule I get notified. Mandatory for my anxiety.

I used to be on medication for depression until I got a high-paying job. Turns out being poor was the root to most problems in my life.

It’s really up to what you value most I would say. Personally I work to live, and all of my passions are outside of work, even if they are programming-related. I get paid ridiculous money doing BS work at some corporate company doing nothing for the world, and I’m okay with that. If you would rather do something cool and innovative for a company and put in a lot of effort that would potentially only be compensated by the knowledge and experience that you gain, that’s also an option. It all depends on what you want your career to look like.

Semi-related, please learn about Boglehead investing while you’re young and stuff all your phat programmer money into the right places. You could retire by the time you’re ~40, and that may shape your expectation of what you want your full career to be.

There has never been an official “global score” for users. If you ever saw one it was being calculated by your app/front-end.

Edit: per jet’s reply it looks like it actually was historically in the API but not exposed on most apps, so calculation was done by the instance and not the app/front-end. It seems like they’re being removed entirely from the API soon or already have been.

I’ve blocked all the news communities for a start. Maybe I’ll let one through eventually, but I’m sick of seeing 13 duplicate posts about how Elon Musk said that penguins can’t be trans or something equally useless.

As for getting more toxic in general I haven’t noticed anything drastic but my gut feeling is that as Lemmy grows, more people see a post, and as more people see a post, the better the odds that one person is going to start an argument. Even if 99.99% of the Lemmy community is not toxic, it only takes one person to reply.

Arch is bleeding edge and frequently has minor bugs as a result. This is probably fine for power users and people who want to learn Linux but I wouldn’t give an Arch distro to someone who isn’t techy. They also likely won’t appreciate the frequent updates to applications that they depend on to actually do work.

(I used Arch for almost five years and think it’s one of the best distros)

67. vote manipulation

Just 1 so far. In the future I might make an alt on another instance as a backup or something, but so far it doesn’t seem necessary. My current instance has a ridiculous amount of donations and a good sysadmin so I’m not worried about it disappearing at the moment.

It’s simple and solid enough to give to people who don’t know what they’re doing, and its Debian/Ubuntu base makes it flexible enough to not slow down power users who want to start modifying it. Other distros that might fit this bill keep shooting themselves in the foot and going off in weird directions, while Linux Mint has been a reputable no-BS distro for a very long time. It’s a workhorse distro without any gimmicks and that’s the point.

That gets my normal GTK theme properly. I found a little more discussion on this here. Nothing very actionable but I did also confirm that my xdg-desktop-portal-gtk is running. It seems like this is supposed to be working, but I have a mostly stock Debian 12.1 KDE install and something seems to be wrong somewhere in the chain. I’ve also tried multiple GTK Flatpaks with the same results.

Edit: Also, I have both my themes folder exposed and the theme installed as a Flatpak via the linked script.

I do have xdg-desktop-portal-gtk on Debian Stable, which is currently at 1.14.1-1. I’ll look around to see if there’s more documentation on this method, because I would prefer to not use the debug variables if possible.

Edit: I launched with GTK_DEBUG=interactive and I can see the theme inside the Flatpak gets set to Adwaita-empty instead of my actual theme, which does get properly returned via gsettings get org.gnome.desktop.interface gtk-theme

Right, I understand it’s not supposed to be used in “proper” usage, but it does work for all my GTK apps and the gsettings method does not work for me. Unless I’m supposed to store it somewhere else because I’m on KDE.

I wasn’t able to get the gsettings method to work (I’m on Wayland KDE), and that article doesn’t say anything about theming QT Flatpaks. Also, after “installing” my GTK theme as a flatpak via the method described, it still wasn’t available to my GTK Flatpaks via the GTK_THEME method. The steps in the itsfoss.com article do work, though there’s been a lot of squabbles about the “proper” way to expose themes to Flatpaks. Regardless, this all goes back to my point that theming Flatpak is clunky and should be much smoother.

Aside from philosophical issues my experience with Flatpak has been excellent. There’s some theming steps you need to do to make them feel like regular apps, which I feel is clunky design. No Flatpak-induced instability from what I can tell. Setting up directory permissions is sometimes slightly annoying but Flatseal makes it trivial, and most Flatpak permissions are set up properly out of the box these days.

I haven’t noticed any start-time delays when launching Flatpaks as opposed to regular apps - I don’t know if they’ve fixed that or if my system is just too powerful. The only app that I’ve personally noticed is weird is VSCodium, which has trouble escalating to admin permissions when you’re trying to edit privileged files. I still use the regular version for that reason.

I use a few packages from Homebrew and don’t have any problems with it. By default it installs itself into /home/homebrew or something which I didn’t like so I put it into ~/Applications/Homebrew instead using these steps. It warns that you may be forced to compile software if you do it this way but I’m down to clown so whatever.

The biggest problem I have with it is that you’ll need to keep it updated alongside your regular packages, which I do by aliasing a simple upgrade command that runs all my package manager upgrades.

I would also recommend ungoogled-chromium as an alternative to Brave, which does have its own official Flatpak (not marked as such but it’s linked to in the ungoogled-chromium project github).

Mirrored vdevs allow growth by adding a pair at a time, yes. Healing works with mirrors, because each of the two disks in a mirror are supposed to have the same data as each other. When a read or scrub happens, if there’s any checksum failures it will replace the failed block on Disk1 with Disk2’s copy of that block.

Many ZFS’ers swear by mirrored vdevs because they give you the best performance, they’re more flexible, and resilvering from a failed mirror disk is an order of magnitude faster than resilvering from a failed RAIDZ - leaving less time for a second disk failure. The big downside is that they eat 50% of your disk capacity. I personally run mirrored vdevs because it’s more flexible for a small home NAS, and I make up for some of the disk inefficiency by being able to buy any-size disks on sale and throw them in whenever I see a good price.

The main problem with self-healing is that ZFS needs to have access to two copies of data, usually solved by having 2+ disks. When you expose an mdadm device ZFS will only perceive one disk and one copy of data, so it won’t try to store 2 copies of data anywhere. Underneath, mdadm will be storing the two copies of data, so any healing would need to be handled by mdadm directly instead. ZFS normally auto-heals when it reads data and when it scrubs, but in this setup mdadm would need to start the healing process through whatever measures it has (probably just scrubbing?)