How is it political to talk about yourself in vague terms when introducing yourself to a group!? Would it be political if he said his hair is brown? How about if he mentions the color of his skin, is that political?

You make the statement political when you try to ban certain people from talking about who they are, if only white people talk about the color of their skin it’s not political to say you’re black, it’s political to try to block people from saying it. Saying you’re queer is on the same level of mentioning you have a wife/husband, in fact it’s even more vague, it’s in the same level of saying “since I was a boy/girl”, because queer does not necessarily mean non-heterosexual it can also mean non-cisgender so it’s an umbrella term to mean member of the LGBTQ+ community, if being queer is political then being heterosexual or cisgender also has to be, and I doubt people would be okay with having to step on eggshells not to mention anything that could make someone deduce their sexuality or gender. Hell, the same people who claim Queer is political are the ones who have the most problem with gender neutral language.

First of all, this is not a professional setting, he’s not an employee there, and that forum is open for everyone.

Secondly, and way more important, people do that daily and no one cares especially when introducing oneself it’s common to mention stuff like your wife/husband and your preferred pronouns, hell, my corporate slack profile has my pronouns and those of everyone else. I’ve worked with trans people who introduced themselves as trans on the first day, and no one cared. So no, it’s perfectly okay for people to talk about themselves during an introduction even in professional settings.

Last but not least, people being uncomfortable is not a good reason to ban something, members of the KKK might be uncomfortable about working next to a black person, so what? Should the black person hide that he’s black to not make the others uncomfortable? That’s bullshit. If a person is uncomfortable by another one saying they’re queer, then that first person needs to deal with it, being queer is part of who the other person is and he shouldn’t have to hide who he is because someone might be uncomfortable about it. You mentioned religion, which I don’t think falls into the same category because religion is a set of beliefs that many people change through their lives, but still, people wear crosses daily in professional settings and no one cares.

Regardless of how impartial the source might be, there are facts there:

• Fact 1: Someone made an introductory post in which, among other things, they mentioned “I am queer”.
• Fact 2: A moderator working for Canonical deleted that part, and only that part, of that post.
• Fact 3: Another moderator re-added that and claimed the first one acted erroneously.

While Fact 3 is a bit of a relief, they still haven’t communicated what they intend to do to prevent this from happening again.

What are you talking about? Middle click on links opens them in new tabs, middle click on tabs closes them, always has been, and works on both windows and Linux, both chrome and Firefox.

Ok, lots of answers focusing on the game, so I think you have plenty of suggestions on what to try there. That being said I have never heard of bottles, I’ve used raw wine and PlayOnLinux before Steam integrated Proton so now I just use that.

For docker it can be daunting, and home assistant is not an easy thing to setup. The thing with docker is that it can be very complex, but you don’t have to worry about the majority of it. I assume you have docker installed, enabled and your user is in the correct groups. Unfortunately Mint/Ubuntu don’t have docker in their normal repos so you probably had to add the docker PPA and install from there. Let’s run a couple of commands to ensure all went well:

sudo systemctl status docker

This should show you the status of the docker daemon, and it should say that it is Active. If you get a no such service type error then docker is not installed, if it’s not shown as active then the daemon is not started and can be done so by running sudo systemctl start docker (and you can replace start with enable for it to happen at boot). If it’s Active then awesome, let’s check that your used can run docker commands, try running this: docker run hello-world if that fails but sudo docker run hello-world works then your user doesn’t have access, you want to add your user to the docker group sudo usermod -aG docker $USER and reboot.

Ok, docker hello world is working, what now? Now, I assume you have some idea of what docker is, but in a (wrong but simple) way you can think of it as virtual machines. Let’s try to run some cool stuff in it, there are two main ways, running a long complicated command, or writing those parameters on a file and running a simple command. This file is called a compose file, and should be named compose.yaml or docker-compose.yaml. let’s try that, create a folder called silverbullet (just because that’s the service we will try, it is a note taking app that I really like) and in there create a file compose.yaml and write the following content there (everything starting with # is a comment I added explaining what that does, and can be removed if you don’t want it):

# This defines all of the services we want to run
services:
  # This is the name of the service, it can be whatever you want
  silverbullet:
    # The image is the actual thing you want to run
    image: ghcr.io/silverbulletmd/silverbullet
    # This tells docker to restart the service if it closed for whatever reason, unless you specifically tell it to stop
    restart: unless-stopped
    # This will set environment variables inside the docker.
    # different services might require different environment variables set
    environment:
      # silver bullet uses SB_USER environment variable to set user/password for the main account. We're setting user to admin and password to 123 here
      - SB_USER=admin:123
    # This maps outside folders to inside folders so that your docker container can access them
    volumes:
      # Here we're telling it that the ./data folder should be accessible in the /space folder inside the docker
      # silver bullet stores stuff in the /space folder, so by mapping it to the ./data folder we can keep that data between runs
      - ./data:/space
    # This tells docker to map ports from the inside to your host machine, this allows you to access the docker container as if it were running on your machine
    ports:
      # This tells it to map the internal port 3000 to the external port 5000, so accessing http://localhost:5000/ from your machine will in fact access the same as http://localhost:3000/ inside docker
      # Silver bullet runs on port 3000, so we need to expose that port
      - 5000:3000

Uff, that was a lot, but we’re done, now just run docker compose up -d (up to start -d to run as a daemon, i.e. in the background) and you should be able to access http://localhost:5000/ and get to Silver bullet logging in with admin 123, then if you write about something you will see files appearing in the silverbullet/data folder.

I know that this was a lot in one go, but I chose Silver bullet because it touches all of the most common stuff you’ll need and it’s easy to get going.

Good luck with your self hosting journey, and don’t hesitate to ask if you have any questions.

That’s interesting, I don’t remember which implementation I’m actually using, possibly RADV, but don’t remember having any issues, unfortunately I don’t have Indiana Jones to try to independently confirm that the driver is indeed causing a problem there. Have you seen issues in other games?

No it hasn’t, Nvidia usability in Linux now is the same as it was 10-15 years ago, and that’s sort of the problem. What do you think has improved since then? I remember ~18 years ago getting Nvidia to work with the proprietary drivers on my Mint was just a couple of clicks away and I could play oblivion and many other games that ran on Wine (and the very few natives we had) just fine. The majority of the Nvidia issues are self-inflicted, always have been, the problem is that because you have to use the proprietary drivers it’s very easy to shoot yourself in the foot, and inexperienced people tend to do it very often, so my guess is that 10-15 years ago is when you started using Linux, and broke stuff with the Nvidia driver, nowadays you don’t break that stuff and you think the driver has changed, when what has changed is you.

Yes, I have a near flawless experience with Linux, but it was years in the making. One thing people don’t realize when they switch over is the amount of time you’ve spent in dealing with similar issues on Windows, but you did it so long ago and so often they’re second nature to you, so you don’t perceive them as problems. But when you start from scratch on Linux they’re daunting problems because they force you to learn new stuff.

The same will happen to Linux over time, some stuff you’ll fix once and forever, others you’ll learn to work around and be okay with it. For me nowadays whenever I have to use Windows for something more than simple stuff it’s death by a thousand cuts, because I haven’t used windows in so long that my muscle memory for those caveats and weirdness (that I didn’t even noticed before switching) is completely gone.

As for the specific things, you’re using an Nvidia card, which is known for not playing nice with Linux, you haven’t mentioned drivers but you have two options here, open source and very poorly performative Nouveau driver or the proprietary and doesn’t play nice with other stuff Nvidia one. Both are bad, but probably you want the Nvidia one.

Also I don’t know how Ubuntu studio is, but I would recommend you try other distros, maybe Mint or I’ve heard wonderful stuff for Bazzite. Any way you can have your /home be in a different partition so you don’t lose your data when switching over and trying stuff, eventually you might find something that clicks for you, and it’s smooth sailing from then on. Good luck.

Depends on what you work for specifically, at my current job most people use Windows, and it makes sense because our product will mainly be used on Windows, and some of them are windows only. But I also worked in many other places where we were deploying to Linux servers but the majority of devs were on Windows.

At my current job they asked what OS I wanted for my laptop and Linux was an option. I do have a Windows desktop at the office that I remote to that needs to be Windows for technical reasons, but my main device is Linux.

At my job before this I worked for one year on my own Linux laptop, until one day I asked for a laptop lent temporarily because I was going to travel and my wife needed mine, and it had to be Windows. I never minded much because it was temporary, but when I came back I was told that I was supposed to always have been using a Windows machine and that I shouldn’t use a Linux machine anymore (even though our product was a website deployed to Linux servers). That was one of the reasons I eventually took another job, not the main one, but an important one nevertheless.

Before that the company also offered Linux.

And before that it was a very small company when all of the owners were software engineer guys using Linux themselves. I remember one day we were discussing OS and someone said “can we take a moment to recognize we’ve been talking about this for 15 minutes and no one even considered Windows as an option”.

Nope, they complement each other, you can have workspaces in non tiling window managers, but they’re a must in tiling ones. But the tiling does play a very crucial part, for example my workspace that has the terminals can have several terminals depending on what I’m doing, and being able to open/close terminals and having the remaining adjust is a big part of why I use a tiling window manager. It’s just efficient because 99% of the time when you have 2 apps open you want to look at both simultaneously, so not having to move stuff around with the mouse makes that easier, and for the remaining 1% you just move the app you don’t currently care about to another workspace, so it’s somewhere easily accessible when you want to.

How to make the most of it?

Use workspaces, I almost never used it before because I was set in my ways, but after switching to tiling WM it’s a must and increases productivity by a LOT, I’ve grown so used to it that using windows with a mouse feels super clunky and cluttered.

That’s where workspaces come in place, I usually have a single full screen application per workspace, so Meta+1 is my browser, Meta+3 is my IDE, Meta+4 is slack, etc. Some workspaces have more than one application, e.g. I usually keep a few terminals in Meta+2.

This means that I usually work with things occupying all of my screen and in a short keystrokes I’m in whatever I want to be. But if I ever need to open a terminal or a random application it will occupy half my screen and whatever I was doing would resize to the other half, so I never have to grab my mouse to move stuff over to be able to see what I was doing.

On paper I should love Authelia, I’m a sucker for y’all configured services, I can write a couple of files on my Ansible and boom, everything works… However I never had much luck setting Authelia up, Authentik on the other hand was very painless (albeit) manual (via UI) configuration. I don’t do anything crazy, so any of them would work for me though, I just failed on setting Authelia and tried Authentik and had had no reason to change.

That is sound advice, the AUR is most definitely not a trusted source though. For the normal arch repos the people who put the stuff there are known, they work for the project, you’re as likely to get malware from one of those as you are to read an article bashing gamespot in gamespot, the people in charge of putting the packages there are the ones with more vested interest in things working so they won’t knowingly introduce malicious code (plus it’s a handful of people who know each other by first name).

The AUR is a different story, because anyone can put stuff there it’s very easy to have malicious code end up there. It doesn’t happen that often because most of the time it’s fairly obvious and it gets flagged straight away, plus if people start doing that people will migrate away from the AUR, so it’s a high risk low reward situation. But as more and more people start to use Arch derivatives that come with the AUR enabled without understanding any of this it becomes a more rewarding thing to exploit.

Yes, that’s what I said, but AFAIK the only way to achieve that is to make it a mandatory dependency.

I was going to say that Manjaro will have the same issue in a short while because they delay the updates a little bit but follow them, so VLC will get split in Manjaro too, but someone already commented that it has already happened

I had the same issue, hadn’t found the solution yet (also didn’t looked too hard) and while I sort of agree that it should have been in the news I also understand why it’s not (it only affects people with VLC, and not everyone uses VLC, if every time a package gets split it was in the news the news would be all about that). That being said I think that there were other solutions that would have been much better, namely split the package with a mandatory dependency on vlc-plugins-all and convert that to optional dependency in a month or two, that way everything keeps working as is for people during the transition, but after a short while it can be modularized.

This might be the answer really, Gentoo is my favorite distro in theory. In practice I’m a lazy ass that just ends up installing binary packages for everything and missing the AUR.

Ok, I think I can provide some insight into this that I think it’s missed on other replies.

I switched to Arch back when Arch had an installer, yup, that’s right, Arch used to have an installer, then they removed it and you had to do most of the process manually (yes, I know pacstrap is technically an installer, but I’m talking about the original ncurses installer here).

After Arch removed its installer it began to attract more purists, and with that the meme was born, people online would be discussing stuff and someone would explain something simple and the other would reply with “I use arch BTW”, which meant you didn’t need to explain trivial stuff because the person had a good idea on how their system works.

Then Arch started to suffer from being too good of a distro, see those of us that were using it consistently saw posts with people complaining about issues on their distros that never affected us, so a sort of “it doesn’t happen on my distro” effect started to grow, putting that together with the excellent wiki that people were linking left and right (even for non Arch users) and lots of people became interested.

This new wave of users was relatively new to Linux, they thought that by following a tutorial and running a couple of command lines when installing arch they had become complete experts in Linux, and they saw the “I use Arch btw” replies and thought they meant “I know more than you because I use Arch”, so they started to repeat that. And it became common to see posts with people being L337 H4ck3r5 with no clue whatsoever using “I use Arch btw”.

That’s when the sort of cult mentality formed, you had experienced people who liked Arch because it was a good distro that didn’t break on its own with good documentation to help when you screw up, these people suffered a bit from this and told newbies that they should use Arch. Together with that you had the other group who thought because they installed Arch they were hackers telling people Arch was waaaay too hard, and that only true Linux experts should use it. From the outside this must have felt that we were hiding something, you had several people telling you to come to our side or they couldn’t help you, or pointing at documentation that looked specific for their distro, and others saying you weren’t cool enough for it probably felt like a cult recruiting.

At the end of the day Arch is a very cool distro, I’ve tried lots of them but prefer Arch because it’s a breeze to maintain in the long run. And the installation process is not something you want to throw at a person who just wants to install Linux to check it out, but it’s also not complicated at all. There are experts using Ubuntu or other “noob” distros because at the end of the day it’s all the same under the hood, using Arch will not make you better at Linux, it will just force you to learn basic concepts to finish the installation that if you had been using Linux for a while you probably already know them (e.g. fstab or locale).

As for Ubuntu, part of it stems from the same “I use Arch btw” guys dumping on Ubuntu for being “noob”, other part is because Canonical has a history of not adoption community stuff and instead try to develop their own thing, also they sent your search queries to Amazon at some point which obviously went very badly for their image in the community.