If this is a hard requirement for federation, then I guess federated services are not for me, as I value my privacy more than I care to use them.

How do you know who you’re defederating with? When I set up my instance, the list of federated instances was thousands. How do you know which one is scraping the data?

Admin access means nothing if you can set up your own instance in an afternoon, federate with everything, then get all the votes copied to your database. I have done this just to prove it could be done, btw.

sudo systemctl restart vaultwarden.service

Done. :)

Thanks for the heads up.

That’s a satire article

That’s a satire article

So if I don’t have a camera on my laptop, I’m good?

Well, I reinstalled this morning and I’m keeping the nouveau driver this time instead of going with the proprietary. I don’t play play games on this laptop anymore since I set up sunshine/moonlight, so it shouldn’t be a problem.

I will try this once I get my system back up and running tomorrow! I’m going to install the distro on a new SSD and see what happens.

Yeah, I just ordered a new SSD. I’ll give that a try when it arrives tomorrow. Smart says it passed, but suspect my SSD enough that I think it’s worth it to just try another SSD.

I have 16GB of RAM and 16GB of swap as a swap partition. Though I have also tried a 16GB swapfile and saw no difference. I don’t know about zram.

It’s a 2021 Asus Zephyrus G15 with an AMD CPU and an Nvidia GPU. I got an aftermarket SSD off of Amazon so I could dual boot with Windows, but I haven’t booted back into Windows a single time since installing Linux. Though that might be a good test.

I can try set -x once I reinstall my distro and get it back up and running tomorrow, as it is currently borked. Since zypper does all the downloads then all of the installs, I was able to see that it always happened during the install phase, not the download phase.

I am definitely interested in the possibility of it being related to the proprietary Nvidia driver. When it happened yesterday, the proprietary Nvidia driver was being updated (not sure at that exact time. But it was in the list of packages to be updated). I’ll keep an eye on that for sure.

1. Already done. :)
2. It started with GUI, but I switched to command line, and even did it in a separate TTY to make sure it wasn’t something weird going on with updating plasma from plasma. After switching to Arch-based distros, I have only use CLI.
3. Currently I’m on EndeavourOS, but after the most recent time this happened, it won’t boot, and I can’t even mount and chroot to it (I get an I/O error message)
4. No, I’m at about 1% capacity.
5. I ran this from a live USB, and it came back with no errors detected, but returned instantaneously, so I’m not sure if it ran the right thing. Doing more research on it now. (Edit: I did it wrong. The test is running now)

Thank you for the suggestion. I am unfamiliar with this, but I am reading about it now.

Just this weekend I installed Manjaro after having tons and tons of issues with SUSE since the Plasma 6 upgrade. I have a laptop with AMD integrated graphics, which Plasma is running on, so your issues may not apply to me. But if I run any apps on the Nvidia GPU in full screen, I do get the flickering issue.

My biggest issue I have is that no matter what distro I use, as soon as I install the proprietary Nvidia driver, my system fails to boot like 20% of the time. It just freezes during boot with no error messages or warnings that I can find. But once it boots, it works.

I’m not sure how to run Plasma on my dedicated GPU so I can see if I have the same issues you have. But with my current setup, it works.

I have tried KDE connect, and it never works when I need it to. I just send it to myself on Signal. It’s the easiest, most non-bullshit way.

I guess I’m a dummy, because I never even thought about this. Maybe I got lucky, but when I did restore from a backup, I didn’t have any issues. My containerized services came right back up like nothing was wrong. Though that may have been right before I successfully hosted my own (now defunct) Lemmy instance. I can’t remember, but I think I only had sqlite databases in my services at the time.

I imagine people who care about this sort of thing are more likely to report it. And people who care about this sort of thing are also more likely to be early adopters and go through the effort of switching to Wayland.

The way to get a more random sample is not something I want (built-in, automatic telemetry by default). So I’m fine with having skewed data for something like this.

That’s a really interesting thought. We do still have issues where we get like Ken then Terry (or Mii Gunner then Mii Brawler) back to back, and for people who don’t like that type of characters, its a bummer.

Each character having a list of groups that they belong to, then not allowing players to play a character in the same group consecutively would probably be a huge improvement. I would need to be careful to make sure too many characters aren’t excluded, though. It would be tough to get right, but I think it would be really good.

I made a random character selector app for super smash bros that makes you play through every character before it lets you repeat a character. And it won’t let two people play the same character at the same time. My friends and I like playing random characters, but we kept getting the same characters over and over again, sometimes even in the same colors (online only). I got frustrated one day and made the app.

It definitely livens up our game nights.