28F, she/her - Seattle - Drive stick, use Linux, do praxis. Don’t call me unless I gave you my number

  • 2 Posts
  • 477 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle
  • If you’re on a Mac, you can likely use an app called “Balena Etcher” to create a bootable Linux USB… if it’s an Intel mac, you can just boot that right up by holding option at boot-time. If you’re on an Apple Silicon Mac, you are not going to be able to boot most Linux distros there. If you’re on PC, you can usually stick the flash drive in and mash F12 at boot-time to get into a menu, select the USB stick, and then it’ll boot you into a “live environment” to test with. That way you can just poke around and see if you like it. Almost all distributions come with a live environment by default.


  • There are a lot of differences and a lot of similarities between the operating systems here. It will take you time to get used to no matter what you do. Start by swapping your apps on your existing Mac, trade out any apps that you know won’t work on Linux with apps that do. That way, you spend some time in your existing environment with the new apps you’re going to need going forward.

    Next, make sure to test out your peripherals in a live environment. Does everything you use with your computer work correctly? If not, find out why. See if you can mitigate it, or if you’ll need to replace stuff.

    Finally, be willing to experiment. I know others in this thread will recommend various desktop environments and distributions to you. Try many of them. GNOME is good and simple out of the box, feels kinda mac-like, but if you want to completely replicate the functionality of macOS, KDE Plasma has more options for that like global menus and the file management app (Dolphin) is incredibly extensible and customizable.

    Try to have fun with it, and don’t give up. It takes time to learn a new way of working, and you will likely have frustrations along the way, but ultimately the goal is to learn and figure out what works best for your needs.



  • This is just TOS enforcement, they updated their TOS in October. From the article:

    Github updated its acceptable use policies in October 2025 to forbid “sexually themed or suggestive content that serves little or no purpose other than to solicit an erotic or shocking response, particularly where that content is amplified by its placement in profiles or other social contexts.” This include pornographic content and “graphic depictions of sexual acts including photographs, video, animation, drawings, computer-generated images, or text-based content,” according to the terms.








  • Developers very seldom communicate in a way that pleases their company leadership. There’s a reason support, sales and marketing people have jobs. If companies didn’t need them, they would cut them to save cost.

    However, the developer should be able to put down their changes and whomever is in charge of communications should be using the change log as a chance to communicate to end users the changes in a friendly way. Not this nonsense. LLM could do it but it, but it’s best to have it written by a person.






  • I think the point here is that Jellyfin doesn’t have a centralized login or website like Plex does. An attacker would have to know about your server and log into it directly to get access. If you run it in a container, there isn’t a lot they can do other than trashing your media library, which you should have protected with filesystem snapshots anyway.