BrianTheeBiscuiteer

I've looked at a lot of other immutable distros and I might just end up using one of those, but I feel like taking on a bit of a challenge and there's a few things I'm not very keen on with existing solutions (last paragraph is my idea if you want to skip the context).

Most immutable systems I've seen require a reboot in order to apply system changes. What is this, Windows? Yeah, reboots are quick but restoring my windows and getting back into my groove is not quick. Also, every immutable OS I've seen wants you to opt-in to a rollback. Rarely do I see the full effects of installing a package or altering a config immediately. By the time I notice an issue maybe it's too late to rollback to before the change or maybe I've done a few other things since and I don't want to rollback everything. I would much prefer to make "rolling forward" or persisting changes to be a very conscious process.

I started messing with BTRFS and I think I've come up with a process that will get me what I want, no matter the distro. Please poke holes in my idea. So I think I can use BTRFS to hold data for the rootfs in three different subvolumes (at minimum): root-A, root-B, root-Z. root-Z is my golden image and it represents what I want root to look like after reboot. root-A and root-B are the active and passive instances of rootfs, but which one is active will flip-flop after every reboot. So if I boot with A, B gets replaced with the contents of Z. In the meantime I can do whatever I want with A. Not sure how I'll update Z (chroot or "promote" the active subvol to be Z) but without an update every reboot is an automatic rollback.

Thoughts?

This stuff moves so fast I really can't keep up and a lot of the research posted here goes a bit over my head. I'm looking for something that doesn't seem too out of the question given things like CLIPSeg. Is there some tool or library out there that will accept an image and a prompt and then generate a mask within the image that generally corresponds to the prompt?

For example, if I had a picture of an empty park and gave the prompt "little girl flying a kite" I should get back a mask vaguely in the shape of a child with a sort of blob mask in the sky for the kite. Of course from there I could use the mask to inpaint those things. I would really like to be able to layer an image kind of like Photoshop so it's not all-or-nothing and focus on one element at a time. I could do the masking manually but of course we all want fewer steps in our workflows.

Couple of things for me.

One is tiny croutons. I don't see them anywhere anymore. They taste the same but it's kind of a pain sometimes to keep the big ones on your fork. The small ones were a little more satisfying to snack on too.

Second is Blue Nehi. Never met anyone else that's tried or heard of it. Damn it was good though. Big Blue is kinda similar but those always taste under carbonated.

Official docs say it's for

Packages that are only needed for local development and testing.

Umm, okay. Not 100% clear there. Some articles mention things like ESLint or Jest (k, I'm onboard there) but others mention Babel or WebPack. I get that you don't need WebPack libraries to be loaded in the browser but how the hell do you bundle up your code without it? When you use npm ci or npm install you'll get all dependencies but isn't it good practice (in a CICD environment) to use --omit=dev or --only=prod?

Do I have to do some special search query? My favorites tab shows posts only.

I just went through airport security and was quite surprised how easy it was (relatively speaking). Didn't have to go through a body scanner, didn't have to separate liquids, didn't have to take out my laptop, and my boarding pass wasn't even scanned. Did some rules change? Is their thoroughness related to terrorist threat levels?

I've seen FAQs and troubleshooting pages that say clean the contacts with alcohol, and that works, but I seriously have to do that every time I run it. The only other thing that will work is jamming something under the Roomba to lean it onto the charging contacts. Is it a crappy base? Are there any diy tricks to give the base better contact?

My son dropped his Switch Lite in the toilet and the battery life seems worse than before. I'm thinking of doing the replacement myself but I'm curious how hard it is or if there are gotchas. I've replaced "non-replacable" batteries in phones before and I usually break some plastic tabs or (one time) pierce the battery. I'm totally fine taking it to a shop if it's moderate to hard.

What I mean by n-to-n sharing is that I have all of my devices sharing the same folder with every other device. This has definitely been a bit of a pain to set up and manage (moreso because a few machines use Docker so they're basically double-NAT'd). My biggest concern is having conflicts out the wazoo and losing data. The most important thing to me is my KeePass vault.

I had to read like half the article to be sure she wasn't saying that slavery having no benefits is "ridiculous".

Amidst all the SDXL stuff I'm sure this will get overlooked but I've been trying to share more of my gens and my code instead of keeping it all to myself.

I made a downloader for models. Now that I'm posting it I do kinda of wonder how useful it is but at one point I thought it was a great idea. I suppose I didn't like the idea of not being able to wipe the installation and start fresh with minimal effort (or if I one day have a new main for SD stuff).

Anyway, here it is as a Gist: https://gist.github.com/MalikKillian/2be8af358111049848139d95abddee64

Just tried using it for the first time. I wrote some text, highlighted it, then hit the spoiler button. What I saw was this:

Don't show this