AnyOldName3

That’s not relevant to being a tankie as the US, Israel, and other states backing Israel, aren’t claiming they’re building communism or are the successor state to another which claimed to be building communism. It’s the part where communism is an excuse that means the bad things didn’t really happen and would be fine even if they did that makes tankie-ism its own distinct thing.

Maybe XT-1 woke up with tattoos like this, but it said Dave the lab tech was here, and Dave was the only one to enjoy it.

It’s not Kessler Syndrome until it’s so bad that we can’t feasibly launch anything new. A single cascading collision chain might calm down again after breaking a lot of stuff without any catastrophic long term impact if all the debris ends up either in a stable orbit that can be predicted and avoided by other objects, or unstable orbits that decay until the debris falls out of orbit.

I’ve definitely noticed less shininess than the same filament was getting at the same temperatures on my previous printer, except for the first layer. As the first layer prints without part cooling, my guess is that the extra part cooling versus the other printer means it’s setting before it’s had time to self-level. If that’s right, then turning down the part cooling (and then also the speed so you can get away with the reduced part cooling) would make things shiny again. I’ve not bothered investigating that, as most of what I print is either functional, where I wouldn’t care about shininess, or gets painted, where any shininess would come from paint or clearcoat.

When they first started ramping up ads and demonetising more videos for being insufficiently advertiser-friendly, they probably still had enough goodwill from users that if they’d immediately launched YouTube Premium and presented it as a way to both remove ads, and support video creators that couldn’t rely on ad revenue, it would have been decently successful. A good number of YouTubers who had to switch to sponsorships and Patreon could have been pushing for people to subscribe to Premium instead of play Raid: Shadow Legends, which presumably would have boosted subscriber counts, and might have been enough to make YouTube profitable and much more pleasant for both free and premium users than it is today. Instead, they burned through a large amount of goodwill before implementing Premium, so people were already more reluctant, and for a long while it only shared revenue with a select few channels who were already raking in ad money, and was unaffected by view counts, so early Premium subscribers were paying Logan Paul even if they never watched that kind of video, but weren’t paying the channels they actually watched.

I ran the printer’s pre-sliced 12-minute benchy with cheap Geeetech PLA filament, and it didn’t come out great, but then realised that when I’d removed the nozzle clog that was there from the factory (apparently they test some nozzles during QA, so mine had some dregs of filament with a lump that needed a cold pull to shift it) I’d accidentally plugged one of the part cooling fans into the wrong header and it wasn’t running. After fixing that, it came out much better than what you’ve got here, despite a pause part way through due to trying to do it with the tail end of a roll.

I’ve read that the throat cooling isn’t great for PETG as the fan as it draws warm air from inside the toolhead shroud, and there’s an alternative one on printables that avoids this problem (although a duct to isolate the fan and its cutout in the shroud from the rest of the shroud interior might be simpler), so that could be related as you’re running PETG.

Upstream Firefox doesn’t comply with FDroid’s rules (thanks to the ‘proprietary bits and telemetry’ Handles mentioned), so is only available from the Play Store or as a loose APK that won’t auto-update.

A big part of the reason was that Facebook offered game studios a big upfront sum if they made their games work on whatever headset they were selling at the time in standalone mode with no major caveats. The headset only had an anemic mobile GPU, so was only capable of as much as mobile games were doing at the time. A bunch of studios took them up on this offer, and cut back their projects’ scope to be viable under the hardware constraints, so nearly everything that got made was gimmicky mobile-style minigames, and obviously that’s not what makes people want to drop hundreds of dollars on hardware, as they can get their fill by borrowing someone else’s headset for an hour.

Mobile GPUs have improved, so standalone headsets aren’t as terrible now, but we missed the expensive toy for enthusiasts and arcades phase and soured most people’s opinions by making their first VR experience shovelware.

It’s not realistic to demand to own games in the same way as a spoon any time soon. It is, however, pretty reasonable to demand you own games like you’d own a book. You can chop up a book and use it to make a paper maché dog, but you can’t chop up the words within to make a new derivative book (or just copy them as its to get another copy of the same book except for a single backup that you’re not allowed to transfer to someone else unless you also give them the original). The important things you can do with a book but not a game under the current system, even with Gog, are things like selling it on or giving it away when you’re done with it and lending it out like a library.

About a hundred years ago, book publishers tried using licence agreements in books to restrict them in similar ways to how games and other software are restricted today, but courts decided that was completely unreasonable, and put a stop to it. In the US, that’s called the First Sale Doctrine, but it has other names elsewhere or didn’t even need naming. All the arguments that applied to books apply equally well to software, so consumers should demand the same rights.

The vfs of MO2 isn’t the thing that’s hard to port. FUSE would make it fairly straightforward and the main reason USVFS is complicated in the first place is that there’s not a way to make a fast VFS under Windows due to the higher overhead of going back and forth between kernel and user mode, so it has to resort to hooking most of the multitude of functions in the Win32 and NT filesystem APIs instead of just providing about twenty callbacks like you’d do with FUSE.

A mod manager looks much simpler than it is as it looks like you’re just keeping track of lists of files, but mods come in the most insane packaging formats ever devised (e.g. with mad compression schemes and custom scripting languages) and mod managers need to selectively pretend to have all the bugs of every other mod manager as mods get made that rely on a particular bug in the mod manager their author used.

MO2 has a particular extra complexity when thinking about porting it to Linux in that it uses Win32 APIs in lots of places it doesn’t really need to, and also does so in a few places where it’s genuinely much more convenient that it does. It also uses a custom build system generator generator because its CMake and dependencies are too complicated for a human to practically deal with, so it would take loads of work to even build a completely unusable binary on Linux. We have people volunteer to do the work a few times a year and read a warning I write that looks like this comment and claim to have the willpower to do it anyway, but none of them have ever submitted a single commit.

As a counterpoint, I’ve had Ubuntu’s installer and grub’s updater overwrite and break Windows’ boot files several times, but never had the opposite happen (I’ve had both destroy themselves, though). Thankfully, I know how to rebuild the necessary parts of a Windows install, so it’s never been a catastrophe, but it’s irritating to see what’s always been the source of the problems I’ve had be held up as infallible. Possibly this is a problem unique to Ubuntu - I’m happy to blame Canonical - so maybe it could be entirely sidestepped with other distros.

Having the tinkerer options should come after making the software work. From my perspective, Thunderbird is a passable clone of a bad mail client. None of its tweakable options turn it into a good mail client, and so it would be a better mail client than it is had the effort spent on implementing the tweakable options instead been invested into making it generally better.