Actually, they were stored across the entire station’s computer systems; only part of them was in Quark’s holosuite. It basically took every bit of storage on DS9 to store them.

From what I can tell, their patterns are only on file during the transport, after which they are discarded. They imply it takes a lot of power and data storage to transport, meaning that they can’t just store everyone’s patterns.

There is an instance in beta canon, but just knowing that transporters and the title are related might spoil the entire plot. Thus, I am using nested spoilers so that people can check if it might be something they’re going to read without knowing exactly which thing it is.

However, you could probably try replicating the two containment beams thing that happened to Riker and Boimler, though, duplicating Tuvix and splitting one.

Not great. I even got GPU passthrough working once, but you get weird graphics glitches because it’s all being sent over RDP.

I think Cassowary might be better than WinApps, but honestly, at this point, I just gave up on those and just use the VM directly.

To clarify, what I mean is WebKit continued while Blink became its own thing. Factually, Blink is not WebKit anymore.

Replace “WebKit” with Linux and Blink with ELKS.

Honestly had better luck with DOSBOX-X.

For one, it explicitly calls itself a “subset”; a subset is not the whole set.

If we don’t want to go just off the pedantics of language though, then here’s the thing: it was forked a very long time ago, and both have diverged significantly, I think. It’s a bit like saying Blink (the rendering engine of Chromium) is WebKit; sure, Blink is a fork of WebKit, but the two are very different now.

Technically not the Linux kernel.

Just because they existed during the Linux era doesn’t mean they ran Linux; Torvalds was writing for the 386 from the beginning, and Linux has never been written for anything below 32-bit.

Now, it certainly has RAN on that hardware through emulation, such as on a 4 bit Intel 4004, but only for the heck of it.

When it freeze, after you’ve rebooted it, try running sudo journalctl -p 5 -b -1; you might see something in those logs.

Maybe also open a task manager before you do anything graphics intensive, just to see if there’s a process that rapidly increases its memory usage; while it might not be the cause, I’ve experienced similar freezes when I use all my memory (on a machine with 32GB of RAM).

FYI Don’t use this command. I think it was intended as a joke, but I just want to clarify.

Fun fact: you didn’t have to reinstall; you can actually boot up a live usb and chroot into your install to fix things.

Probably would work well on OpenTTD for similar reasons.

Honestly, there’s a bit of an “if I had a nickel” meme for open source reverse engineered clones of Chris Sawyer tycoon games, although it would be 3 nickels rather than the traditional 2 due to OpenLocomotion.

That is kind of awesome.

I wish Debian’s default Grub theme was less ugly; I know I could change it (and I have on other installs, but I’m quite lazy about theming these days. Part of it is I have a laptop that I rely on for college and don’t want to risk any theme glitches, so I keep its Debian install as vanilla as possible.

At least animated WEBP is kind of good; APNGs have huge file sizes and are not widely supported.

Still, this meme made me laugh.

Lossless webp actually has slightly better compression than PNG.

Most browsers support it, but most web apps, including some Google Suite stuff ironically, don’t support uploading a webp.

May I ask what your config was, such as distro, packaging format, and extensions were used? Also, what hardware?

Additionally, what issues specifically were you experiencing specifically? Were sites just loading slowly?

I ask because I’ve used recent versions Firefox on decently old hardware with 4 GB of RAM and 2 cores and had almost no problems. Everything rendered correctly and in a reasonable amount of time. I’d be curious to know why that isn’t happening for you.

Rubbing alcohol and a microfiber cloth.

Also, I feel like I’ve had good luck with k3b, though mainly for CDs.

As for drives, as others have said, USB ones tend to be janky; go for an internal. I like my LG WH16NS40 Blu-Ray drive.

If it’s a desktop, it should be easy to hook up with SATA, though if you have a newer case, you might need to dangle a cable out the side like I do.

If you have a laptop, though, you’ll probably need a USB adapter, though there might be a hack using an M.2 slot to hook up an SATA PCI-E card.

Huh. I guess 3 years of Debian usage has just gotten me used to stuff like that.

I can see where one might go wrong; there’s a lot of sections in that guide with contingencies only meant for specific situations, like upgrading from a USB or optical disc.

May I ask: when did you last try Firefox? There was a period during the 2010s when it has truly horrible performance, but they rolled out some major updates several years ago that greatly improved performance (though wouldn’t call some of the UI changes improvements).

Honestly, every major rendering engine is terrible in some way.

• Blink is resource intensive and has so many non-standard APIs for the sake of Google’s version of “Embrace, Extend, Extinguish”.
• WebKit takes 50 years to support the newest standards.
• Gecko (Firefox) is non-modular and is limited to being used in Firefox, Thunderbird, and forks and Firefox as a result. Its performance is also somewhat worse than Chrome’s, but not noticeable for daily use.

Ultimately, I choose Firefox because its issues are the least annoying to me. I do wish its structure was more community-based and less corporation-eating-its-own-hand, but whatever. So long as Debian sees it fit to keep in its repos, I’ll use it.