• 5 Posts
  • 253 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle
  • It was my first time using a Linux GUI. I was comfortable with CLI, but it was my first time having it installed on a laptop instead of just sshing into a server somewhere.

    So naturally, instead of learning how the GUI worked, I tried changing it to be exactly like Windows. I was doing things like making it so I could double click shell scripts and other code files and they would run instead of opening them up in an editor. I think you see where this is going, but I sure as hell didn’t.

    Well, one of my coworkers comes over and asks me to run this code on this device we were developing. We were still in the very early stages of development, we didn’t even have git set up, so he brought the code over on a USB stick. I pop it into my laptop. I went to check it once by opening it in an editor by double clicking on it… Only it ran the code that was written for our device on my laptop instead of opening in an editor.

    To this day, I have no idea what it did to fuck my laptop so bad. I spent maybe an hour trying to figure out what was wrong, but I was so inexperienced with Linux, that I decided to just reinstall the OS. I had only installed it the day before anyway, so I wasn’t losing much.
















  • I actually contributed to this repo! But I was still too spooked to use pictrs, even with this. Also, I’m no lawyer, but I think using that repo might be illegal in my country. I’m not 100% sure, but I saw some people saying that in my country I have an obligation to report CSAM images to the government, and deleting them could get me charged with obstructing justice or destroying evidence.

    Though it looks like pictrs now has an option to set the amount of time pictrs holds on to proxied images. I think if I just add the option “PICTRS__MEDIA__RETENTION__PROXY=0m” to the pictrs container in my docker-compose.yml file, it shouldn’t hold on to the images from other instances?