If you look at it from a different angle and ask: who might be interested by a user being reported, given that each instance operate independently? The answer is all of them.

• The instance you're on could be interested because it might violate the local instance's rules, and the admin might want to delete it even if from just that instance.
• The instance hosting the community, because regardless of the other two instances they might not want that there.
• The instance of the user being reported, because it's their user and if they're causing trouble they might want to ban the account.

The rest comes naturally: obviously if the account is banned at the source it's effectively banned globally. If it's banned on the community's instance, then you won't see that user there but might on other instances. And your instance can ban the user, in which case they're freely posting on other instances but you won't see it from your perspective.

I'm concerned about DRM violating my rights. But apart from that, media is largely for consumption, there's very few reasons to need to edit a movie or something, and the laws at least attempt to cover fair use. DJs remix songs and stuff just fine. Or news article, you'd mostly want to quote them which is well defined in the legal framework. It's important to remember that open-source doesn't imply free of charge: there is paid GPL software.

Open-source is important in software because it's much more complex, and you can end up in a situation where software you bought doesn't work because the company refuses to fix it, or straight up stops working because the company went bankrupt 10 years ago and things have changed too much. Proprietary software is a black box that can be doing literally anything, and legally, you're not even really allowed to reverse engineer it to even make sure it does what it says it does.

Stallman started the free software movement out of frustration with a printer driver that he knew how to fix, but the company wouldn't give him the source code so he could fix it, and I believe at the time it would also have been illegal to reverse engineer it and patch it, or at the very least it was against the license. And that's also my reason for using open-source software: not because I want free stuff, but because I want libre stuff that I can fix and maintain. Most people won't, and that's where the sharing clause comes in: someone else that can patch it will, and everyone can just use that.

Ideally things would be free and widely available but that's too commie for most people and we're headed in the polar opposite direction. Buuut there's always the high seas where you can set your own moral compass.

They'd get sued whether they do it or not really. If they don't they get sued by those that want privacy invasive scanning. If they do, they're gonna get sued when they inevitably end up landing someone in hot water because they took pictures of their naked child for the doctors.

Protecting children is important but can't come at the cost of violating everyone's privacy and making you guilty unless proven innocent.

Meanwhile, children just keep getting shot at school and nobody wants to do anything about it, but oh no, we can't do anything about that because muh gun rights.

And the same people are the loudest complainers when bike lanes are installed so this doesn't happen.

Seems a bit harsh considering single user instances or very small ones. I can be away for a week but not dead.

You could also push the EFI partition at the very end of the disk whenever you resize the volume. A bit more annoying but can be done live at least. Or at the very least, moving a 500MB partition is a lot faster than moving GBs of C drive, so less time spent on GParted.

Not safe for them because the US can just cut off their supply, and of course if that happens they won't be able to reliably source them to replace them when they die.

And when I was going to the library, asking questions online, and then printing the answers a week later, everyone was saying "Oh, try these other disros...."

It is ASTOUNDING to me how linux users think. The answer to every problem someone else is facing is "Your way is stupid, that's why it doesn't work. Do it MY way, on MY distros"

So, this isn't a very fun advice, but a big part of a Linux distro is changing your starting configuration and dependencies and everything. So it is true that changing your distro can make a whole bunch of things work out of the box that didn't before, especially if it's a weird distro. Now, can you make it work on any distro? Also yes, but it's more effort, and if you're printing help at a library, yeah it might be a better choice to just try a bunch of distros and at least try to find the one that gets you on the Internet out of the box. Bazzite for example literally ships with Steam, Wine, and a whole bunch of gaming utilities out of the box, so for a gamer that means more stuff works out of the box, and that's great if you hate tinkering.

There's a lot of complicated legal and philosophical stuff in the Linux world where some drivers are either not shipped by default because it's proprietary and it makes puritans angry, or legally, the firmware just cannot be distributed by the distro.

And sometimes, you really just don't vibe with the distro. Ubuntu has a way of doing things, so if you hated Ubuntu (2013 would put you in the Unity era which was pretty terrible, it was wildly hated for that reason). Fedora has a different way of doing things. Mint takes a bunch of stuff people hate with Ubuntu and fixes it. Pop_OS takes stuff they hate from Ubuntu and fix it. If you hated Ubuntu, why bother trying to fix it?

And when picking niche distros like Zorin you also significantly reduce you help pool, because it's not that popular so people don't know how it works. You ask me something about Void Linux and I'm gonna be like, I don't know man, I have no idea how to solve you problem on that distro. But I do know how on Arch and Debian based distros. Niche distros are sharp double-edged sword: it can be very nice because it lines up exactly with what you want, or you could be fighting endlessly with the distro because you're trying to do the polar opposite of what it wants you to do.

You can go beyond that obviously, Linux is endlessly customizable, but that takes experience and skill with Linux to do successfully because it might involve compiling stuff from source and whatnot. It's not hard, but it does come with a lot of pitfalls on its own.

Everything went fine until the actual install at 5:59 of the video. At 6:00 he jump cuts to after the installation. The installation itself took roughly 5 hours.

And then it took roughly 30 minutes to boot. I googled it, and it should only take 15-20 minutes to install, and boot almost instantly.

What's the performance of your USB stick? You can check with utilities like CrystalDiskMark on Windows, so you get the Windows numbers. My guess is your USB stick is a USB 2.0 stick and is horribly slow at anything other than bulk file reading and writing. That could explain why it was so bad and that'd make it not Linux's fault. The live USB would decompress into RAM, so it's faster because it's compressed (less data to read), and the data is then in RAM where it's very very fast to access.

I actually had the same issue but in reverse: I needed to run motherboard software just once on Windows to configure a few features once forever. I installed it on the only USB stick I had, a 32GB Verbatim from Microcenter. It took hours to install, a solid half an hour to make it to the Windows desktop, and probably like an hour to manage to open up Edge, download the software, install it and run it. It was absolutely horrible.

I tried sudo mount /dev/sdc/ but terminal spit out an error.

That's not a valid command because /dev/sdc/ isn't a folder, it's a device file. It probably would have worked with sudo mount /dev/sdc, without the trailing /. But that still would only work if the drive is listed in /etc/fstab as to where it should be mounted. You ideally want sudo mount /dev/sdc /some/other/path so it ends up mounted where you want it. Or just mount it from the file manager which will do it for you in a temporary location.

I don't really have better advice for you and Linux. For some people it just works out of the box, some other people have more annoying hardware that's a pain to get working. With the attitude you have, you don't seem like you want to take the time to learn how Linux works and get used to it, so you end up frustrated and you just go nowhere. Sometimes it really just takes persistence to get through it.

You're not helping yourself at all doing weird setups like temporarily installing it on a USB stick. As I said in my other comment, you started off with an impossible task (that app will not work in Wine), so you're also thrown into a rabbit hole of commands and troubleshooting that has no chance of succeeding. That is very demotivating in itself.

The "easy" Linux distros can be convenient but ultimately if you want to have a good Linux experience you must be willing to learn how it works and get familiar with how things are done. You're relearning to use a computer all over, it's not an easy task, it takes persistence. The issues must be turned into learning experiences, not frustration and points towards "I'm done with this stupid OS".

8BitDo Ultimate Software V2

There's no way this app runs on Linux under Wine, because Wine can't do direct USB yet, and also if the key mappings rely on a Windows driver to do that, that obviously won't work either.

Pretty sure there's pretty decent apps that can do similar things on Linux.

Epic is anti-consumer and also anti-Linux, they don't make any effort to support other platforms, the app is shit.

Meanwhile, Steam is

• Actively working with the FOSS community to help preserve old games
  • Kernel improvements for better graphics performance
  • Lots of VR and HDR work
  • Many contributions to the open-source AMD drivers
• Has been supporting Linux gaming for a decade with no signs of backing down
• They have a portable Linux gaming console experience, and it's intentionally left wide open for users to mess with
  • They've taken several community features and built them into the OS
• Their DRM is weak and unintrusive
• Their anticheat is ununtrusive
• The sales are pretty good
• They have tons of features for users:
  • Family sharing
  • Remote Play Together
  • Remote Play
  • Streaming
  • Community forums for every game
  • Mod workshop
  • Matchmaking
  • Steam Chat / Voice Chat / Streaming

The only appealing thing for EGS is, EGS takes a lower cut from the developers who just pockets it and doesn't even result in lower prices for users. As a Linux user, praise our Lord GabeN for all the good Valve has done for gamers. Even for the developers, most are quite happy with the services they get back from that 30% cut.

I'd say the dislike is mainly that for the users, EGS doesn't bring in anything new or interesting or useful that Steam didn't already do well, and goes directly against a lot of the good Steam has been doing. It's just a store that makes big developers slightly more happy.

Isn't he the same person who calls adblocking piracy?

He's also got a generally nuanced opinion of piracy, in that it's justifiable in some situations. If you call it piracy and you're okay with piracy then it's not really a contradiction.

Being willing to talk about it despite working against your interests isn't always bad depending on context.

Basically, the SUID bit makes a program get the permissions of the owner when executed. If you set /bin/bash as SUID, suddenly every bash shell would be a root shell, kind of. Processes on Linux have a real user ID, an effective user ID, and also a saved user ID that can be used to temporarily drop privileges and gain them back again later.

So tools like sudo and doas use this mechanism to temporarily become root, then run checks to make sure you're allowed to use sudo, then run your command. But that process is still in your user's session and process group, and you're still its real user ID. If anything goes wrong between sudo being root and checking permissions, that can lead to a root shell when you weren't supposed to, and you have a root exploit. Sudo is entirely responsible for cleaning the environment before launching the child process so that it's safe.

Run0/systemd-run acts more like an API client. The client, running as your user, asks systemd to create a process and give you its inputs and outputs, which then creates it on your behalf on a clean process tree completely separate from your user session's process tree and group. The client never ever gets permissions, never has to check for the permissions, it's systemd that does over D-Bus through PolKit which are both isolated and unprivileged services. So there's no dangerous code running anywhere to exploit to gain privileges. And it makes run0 very non-special and boring in the process, it really does practically nothing. Want to make your own in Python? You can, safely and quite easily. Any app can easily integrate sudo functionnality fairly safely, and it'll even trigger the DE's elevated permission prompt, which is a separate process so you can grant sudo access to an app without it being able to know about your password.

Run0 takes care of interpreting what you want to do, D-Bus passes the message around, PolKit adds its stamp of approval to it, systemd takes care of spawning of the process and only the spawning of the process. Every bit does its job in isolation from the others so it's hard to exploit.