[-] Schmoo@slrpnk.net 2 points 1 hour ago

You can't take back what's already been given, so you just learn and move on. Whether to keep their art or throw it out is your choice, just don't support them in the future.

For example, I own a painting by Salvador Dali. Salvador Dali - if you don't know - is a fascist. I inherited the painting, and even the previous owner likely purchased the painting after Salvador Dali was dead. My owning the painting does not support Salvador Dali in any way, and the painting has nothing to do with his fascist views. Most people would not recognize that it is a Salvador Dali painting and even fewer would know about his political leanings. It doesn't bother me to hang the painting on my wall, and in the right context and company it can even make a good conversation piece.

[-] Schmoo@slrpnk.net 3 points 6 hours ago

Or you could do that by default while very selectively supporting specific artists. That way you can both stay within your means and exercise moral discretion over who you support.

[-] Schmoo@slrpnk.net 21 points 1 day ago

It's easy to talk out of your ass about how you would have done a better job, but you clearly have no idea what the circumstances were that the prosecution team was dealing with. This particular piece of evidence for example was attempted to be admitted but was denied by the judge for being "irrelevant to the case." The prosecution was fighting a court stacked against them and you would have had a hard time as well.

[-] Schmoo@slrpnk.net 3 points 3 days ago

his solution (for a class of "intellectuals" like him to take charge) however, are just neoliberal swill

This is such a common pitfall that even self-described communists fall into it as well. When you hear people talk about a "dictatorship of the proletariat," what they're describing tends to devolve into "a class of intellectuals needs to guide the working class to the correct decisions" when questioned about what a "dictatorship of the proletariat" actually entails. Often they'll try to justify it by saying it's only temporary, but we all know how that pans out (see the USSR). This is why I consider myself an anarchist rather than a communist and regularly critique marxism-leninism.

[-] Schmoo@slrpnk.net 7 points 3 days ago

I suppose I excluded some important detail. The reason I had wanted to read the Bible then was so I could better understand God's word and confront my family with that understanding. But reading the Bible didn't clarify things for me the way I thought it would, instead of clear instruction on right and wrong I found more hypocrisy and contradiction, as well as a disturbing focus on the appropriate conduct of slave-owners and the treatment of women as property.

Reading the Bible gave me the same whiplash I felt seeing the hypocrisy of the people around me, which made me realize that it wasn't in spite of their faith, but because of it.

[-] Schmoo@slrpnk.net 84 points 4 days ago

When I was young growing up Southern Baptist there was one time where the pastor preached about this verse, and the whiplash I felt when I heard family members bad-mouthing immigrants the moment they stepped outside is partly what led me to read the Bible myself, which led to me losing my faith.

[-] Schmoo@slrpnk.net 10 points 6 days ago

Accountability for actions that effect people other than yourself is necessary for a healthy democracy. Your problem is mistaking accountability for persecution.

[-] Schmoo@slrpnk.net 60 points 4 weeks ago

As an anarchist this is me on a good day. I more often find myself in the middle getting shit on from both directions.

[-] Schmoo@slrpnk.net 87 points 1 month ago

This is not terrorism, it's industrial sabotage, which in the context of the coal industry is based.

62
submitted 2 months ago by Schmoo@slrpnk.net to c/mycology@mander.xyz

Top

Bruising

The underside instantly darkens when scratched.

[-] Schmoo@slrpnk.net 87 points 5 months ago

Science is just the method by which technological advancements are achieved, it doesn't decide the priorities. That privilege falls to capital, and by extension, capitalists.

[-] Schmoo@slrpnk.net 68 points 6 months ago

I would suspect this is an intentional dark pattern. They're probably hoping most people will get tired of waiting and click cancel, which sets it back to the default of allowing all cookies.

[-] Schmoo@slrpnk.net 60 points 8 months ago

Remember everyone, media piracy is in the spirit of a tv show about a post-scarcity socialist utopian future.

35
submitted 11 months ago* (last edited 11 months ago) by Schmoo@slrpnk.net to c/piracy@lemmy.dbzer0.com

Edit: For those who stumble across this with the same issue, I eventually got it working by adding “default-runtime”: “nvidia”, to /etc/docker/daemon.json then restarting the docker service and Jellyfin container.

I am in the process of setting up a new media server on an old PC using Ubuntu Server and CasaOS and have run into my first major roadblock.

To give some background, I formerly had my media server running on my main gaming PC on Windows using Plex and the *arr suite. I’m now trying to do things the right way and set everything back up from scratch on some spare hardware with Jellyfin and all the rest in dockerized containers. I chose CasaOS because I’m not overly familiar with Linux and thought that would be a good way to ease into things.

Everything was going well until I tried to get hardware acceleration enabled in Jellyfin. For the life of me I cannot seem to get the Nvidia drivers properly installed, much less give Jellyfin access to the device. I’m using a GTX 960.

I’m not sure exactly what additional info I need to give here, but here’s something I hope helps:

*****@home-server:/$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
*****@home-server:/$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Thu_Nov_18_09:45:30_PST_2021
Cuda compilation tools, release 11.5, V11.5.119
Build cuda_11.5.r11.5/compiler.30672275_0
*****@home-server:/$ ls /usr/src | grep nvidia
nvidia-srv-535.104.12
*****@home-server:/$ sudo dkms install -m nvidia -v srv-535.104.12
Error! Could not locate dkms.conf file.
File: /usr/src/nvidia-srv-535.104.12/dkms.conf does not exist.

If there’s anything important I’m leaving out - and I probably am - let me know. Also if there’s anywhere else you recommend I post this let me know that as well.

13
submitted 11 months ago* (last edited 11 months ago) by Schmoo@slrpnk.net to c/opensource@lemmy.ml

Edit: For those who stumble across this with the same issue, I eventually got it working by adding “default-runtime”: “nvidia”, to /etc/docker/daemon.json then restarting the docker service and Jellyfin container.

I am in the process of setting up a new media server on an old PC using Ubuntu Server and CasaOS and have run into my first major roadblock.

To give some background, I formerly had my media server running on my main gaming PC on Windows using Plex and the *arr suite. I’m now trying to do things the right way and set everything back up from scratch on some spare hardware with Jellyfin and all the rest in dockerized containers. I chose CasaOS because I’m not overly familiar with Linux and thought that would be a good way to ease into things.

Everything was going well until I tried to get hardware acceleration enabled in Jellyfin. For the life of me I cannot seem to get the Nvidia drivers properly installed, much less give Jellyfin access to the device. I’m using a GTX 960.

I’m not sure exactly what additional info I need to give here, but here’s something I hope helps:

*****@home-server:/$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
*****@home-server:/$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Thu_Nov_18_09:45:30_PST_2021
Cuda compilation tools, release 11.5, V11.5.119
Build cuda_11.5.r11.5/compiler.30672275_0
*****@home-server:/$ ls /usr/src | grep nvidia
nvidia-srv-535.104.12
*****@home-server:/$ sudo dkms install -m nvidia -v srv-535.104.12
Error! Could not locate dkms.conf file.
File: /usr/src/nvidia-srv-535.104.12/dkms.conf does not exist.

If there’s anything important I’m leaving out - and I probably am - let me know. Also if there’s anywhere else you recommend I post this let me know that as well.

14
submitted 11 months ago* (last edited 11 months ago) by Schmoo@slrpnk.net to c/selfhosting@slrpnk.net

Edit: For those who stumble across this with the same issue, I eventually got it working by adding “default-runtime”: “nvidia”, to /etc/docker/daemon.json then restarting the docker service and Jellyfin container.

I am in the process of setting up a new media server on an old PC using Ubuntu Server and CasaOS and have run into my first major roadblock.

To give some background, I formerly had my media server running on my main gaming PC on Windows using Plex and the *arr suite. I'm now trying to do things the right way and set everything back up from scratch on some spare hardware with Jellyfin and all the rest in dockerized containers. I chose CasaOS because I'm not overly familiar with Linux and thought that would be a good way to ease into things.

Everything was going well until I tried to get hardware acceleration enabled in Jellyfin. For the life of me I cannot seem to get the Nvidia drivers properly installed, much less give Jellyfin access to the device. I'm using a GTX 960.

I'm not sure exactly what additional info I need to give here, but here's something I hope helps:

*****@home-server:/$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
*****@home-server:/$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Thu_Nov_18_09:45:30_PST_2021
Cuda compilation tools, release 11.5, V11.5.119
Build cuda_11.5.r11.5/compiler.30672275_0
*****@home-server:/$ ls /usr/src | grep nvidia
nvidia-srv-535.104.12
*****@home-server:/$ sudo dkms install -m nvidia -v srv-535.104.12
Error! Could not locate dkms.conf file.
File: /usr/src/nvidia-srv-535.104.12/dkms.conf does not exist.

If there's anything important I'm leaving out - and I probably am - let me know. Also if there's anywhere else you recommend I post this let me know that as well.

view more: next ›

Schmoo

joined 1 year ago