I didn’t think the project was about independence from Valve, moreso about avoiding duplication of effort among Bottles/Heroic/Lutris and Linux gaming support in general.

I think with a self-hosted mastodon instance, the main downside is poorer discovery across the fediverse as a whole.

When you scale up to the thousands of users something like mastodon.social has, it’s not really an issue because other users have already established connections between instances by following or replying… but if your instance only has a single user, you only see and share posts with the instances you’ve directly interacted with, and it can be really isolating. You have to already know what external accounts you want to follow, because your instance is initially blind to them.

I feel like more instance connections leads to way larger amounts of data consumption too. I follow 120, and am followed by 12… my instance is currently using 24.1 GB for Media Storage.

PCPartPicker can filter for card length (in millimeters as opposed to inches, but still) and that should help with narrowing down your choices. Most GPUs have some variant that’s shorter in length, but they might just charge a bit of a premium for it.

What I feel would be acceptable:

If you’re proud of your Framework laptop and want to brag about it, we’ll give you some swag for free that you can show off with when you’re out and about!

What this looked like to me:

If you’re attending a conference we’d be paid to attend, but can’t go to, will you show off your Framework laptop to attendees in an effort to convince them to buy one from us too, and we’ll send you some stickers?

The issue isn’t even what they’re asking for, but how their asking it.

When I last had an everyday carry USB stick (5+ years ago) I found I never actually used it for anything.

I had Ventoy and some practical ISOs, and PortableApps with a bunch of useful software (firefox, foobar2000, GIMP, notepad++…) for when I was using someone else’s Windows PC.

…think I stored like two word documents on it, ever.

did you find any solution for this?

The usual fix from the Jellyfin docs would be to check you file naming conventions, and add the TVDB or TMDB show ID to the folder so that it scrapes it correctly, or use the Identify option like @Rudee mentioned to select a better match from the UI after import.

Both TVDB and TMDB consider Pokémon Journeys to be Season 23 of the original Pokémon show, the OMDB seems to list it as a standalone show though, so you could import and match it against that metadata.

I think we Fedora users just have to wait for RPMFusion to roll out the updated driver. Not entirely sure if they only use Stable branch drivers or not though. I’m used to Arch where it would just be in the AUR within the hour…

I’ve been refreshing half the uBlue repos a lot today in the hopes there’s some commits showing they’re rolling the drivers out for Bluefin quickly 😂

• For what I assume is a security precaution, SysRq is disabled by default in Fedora, and you need to go enable it if you want to be able to recover when shit like this happens - the link shows how, and explains what each letter does.
• It’s honestly hard to say what caused it, but you could check your system logs and see what looks suspicious around the time of the crash. journalctl, dmesg and your steam logs (in ~/.steam/steam/logs usually) could be worth a look, or worth showing someone else at least if you aren’t sure whats going on in there.
• I’d avoid actively trying to cause it, but if it happens again you handled it exactly how I’d try handle it. Having SysRq enabled would let r-e-i-s-u-b handle it more gracefully than a forced shutdown at least!

Regardless of what distro you do end up using, the Arch Wiki is a great bookmark to have. The info is like 90% relevant to Linux in general, and at worst you might need to figure out what a file path or package might have changed to in the likes of Ubuntu or Fedora.

and a Nvidia 2080ti

Do you know which Nvidia driver you’re using currently?

There’s an established open-source Nouveau driver that Ubuntu & Mint probably defaulted to, a bleeding-edge open-source NVK driver that is still very early in it’s development, and a proprietary Nvidia driver that Nobara probably tried, as it’s kinda what you’d want for gaming.

The other question would be if you’re using Wayland or X11 underneath your desktop environment?

It should be listed in Settings > System > System Details, under the heading “Windowing System” if you’re using GNOME.

Wayland has better multi-monitor support than X11, but the proprietary Nvidia driver has a few teething problems with Wayland at the moment - a new 555 beta driver update should be coming this week with proper fixes for the sync/screen-tearing issues people have been experiencing.

I’m roughly 6 episodes into the original Cowboy Bebop, and about halfway though a re-watch of Dragon Ball.

Honestly, I’m enjoying Mastodon more because it hasn’t replaced Twitter.

It’s not full of spam and arseholes, it’s not trying to bruteforce shite takes or adverts into my feed, and I can self-host the whole thing while still interacting with the platform as a whole.

This one is edgy.

Thats great.

I’d still like my Nvidia card to work so I’m happy about this, and when AMD on Linux eventually starts swapping over to explicit sync, I’ll be happy for those users then too.

I thought Lawnchair died off a looong time ago, Glad to hear it’s still going.

• Arch Linux announcement
• Ubuntu discourse announcement
• RedHat/Fedora security alert
• Debian security announcement

I set up a wiki.js docker container for myself, mainly for keeping track of video game achievement lists in things I’m playing, but I’m probably gonna plop all my docs into it at some stage. It does basically use folder hierarchy, and I have it set to backup to a self-hosted Gitea git repo every 24hrs as well, so I have somewhere to pull all the markdown docs (and their edit history) from if needed, too.

I’m usually using nvidia-beta drivers from AUR because they’re newer, so I just added the hook as an insurance policy.

The DKMS drivers are probably the safer option because they’ll handle rebuilding the kernel modules. Even though (like EddyBot said) the kernel and nvidia packages are supposed to get updated together, sometimes you can spam pacman -Syu at the wrong time and only one package is updated and things go wonky…

Nvidia Arch user here, are you just forgetting to rebuild your kernel modules after a kernel or nvidia driver update?

You can just add a pacman hook that triggers mkinitcpio -P after the linux or nvidia packages are updated. I’ve never had a no-GUI situation from a stray update… maybe one or two that were my own doing when trying to set up UKI’s though.