Is it “fair”? I’d say no, but the world isn’t a fair place. Enormous, unscrupulous corporations are to blame for the untenable situation we collectively find ourselves in. And those corporations aren’t going to be rectifying their behavior any time soon unless forced to.

That being said, asking individuals to take steps to reduce climate change isn’t an unreasonable thing in my eyes. Because, until corporations are held accountable, asking individuals is the only thing that can possibly improve the situation. Even though it’s like throwing a cup of water on a forest fire.

The second that Amazon, Shell, BP, ExxonMobil, Chevron, Coke, Pepsi, et al are forced to do their part, I will start throwing my trash out the window again like a proper American. Until then, I’m gonna recycle and encourage my friends and family to do so as well.

“Sons of Texas” reminded me of this tune I enjoyed a while back from Maylene and the Sons of Disaster:

“Step Up (I’m On It)”

The official documentation has some guides on setting it up in a few different ways, although they assume the user is decently familiar with Linux/terminal commands and such. There might be some more beginner-friendly guides out there, though.

https://jellyfin.org/docs/general/installation/container/

I switched from Plex to Jellyfin a while back and I’ve been very happy with it.

Hmm, have you made any changes to the firewall on the system hosting the Docker container?

You might need to edit the firewall with a something like this:

sudo ufw allow from 192.168.1.0/24 to any port 8096

Are you using docker-compose to run the Jellyfin service? If so, you might need to add something like this to the docker-compose.yml file:

network_mode: 'host'
extra_hosts:
      - "host.docker.internal:host-gateway"

I’m no expert at Docker or UFW, but these are part of my Jellyfin setup, which I’m running on Ubuntu LTS in a Docker container.

Are you putting the port number at the end of the local IP? Jellyfin defaults to port 8096 iirc. So the server URL should be 192.168.0.5:8096. What happens if you input that?

Are you able to connect to the server via web browser? e.g., typing http://192.168.0.5:8096 into Firefox

And as a quick sanity check, is your phone connected to the same wifi network as the Jellyfin server?

Well, that was fast, lol.

Thanks!

We need @SorteKanin@feddit.dk to dive in and tell us how these numbers work!

Guy seems like he has a bit of a chip on his shoulder (or maybe his character does?), but hey, congrats on the weight loss. That’s a hell of a transformation.

Depends on the particular device. LDAC has been around for years and supports higher bitrates than mp3s (assuming we’re putting 320kbps mp3s in the “higher quality” category)

You are wrong =)

I’m not vegan, clown.

Nice argument, though 🤡

That isn’t evidence that the aforementioned cat food will cause cats to become malnourished. That’s just you speculating to confirm your existing biases.

AAA’s seem really common in my neck of the woods.

I got a Coast headlamp a couple years back that has a rechargeable battery pack, but can also take regular AAA’s, which is a handy feature if I happen to need an immediate recharge.

So you have no evidence at all and are purely speculating. Gotcha

So, by your logic, shouldn’t there be a bunch of malnourished and dying cats as a result of people buying this food and only letting their cats subsist on it?

Where are the outraged customers? Where are the lawsuits?

I appreciate your comments here, even if the people you’re trying to educate completely ignore you and downvote you because they have no response to the fact that vegan cat food exists.

I’m not vegan, but the hysterical ignorance espoused in this comment section is bewildering.

I don’t think Reddit-for-nerds (Lemmy) is that great of a place to ask this.

Ouch

Ah, darn. Unfortunately I have no additional help to offer since that particular issue was fixed for me after changing those options in Flatseal.

I’d try running Firefox from the terminal to see what error message you’re receiving when the crashes occur; the unique error message was what led me to this workaround when I was originally troubleshooting.

In Bazzite, you should just need to open the Discover package manager and click “Refresh” and then “Update All” in the top right. Although these drivers don’t appear to be available through the package manager yet; mine is still on version 560.31.02.

If your Firefox crashes are anything like mine were, it should be solved by opening up Flatseal and disabling Wayland rendering for Firefox. See the screenshot shown here: https://universal-blue.discourse.group/t/nvidia-555-drivers-incoming-important-information/2554

When I first installed Bazzite on my Intel+Nvidia laptop, the Firefox crashes were constant. The workaround here fixed the issue for me.

That’s hilarious