Shoko + shokofin is a great solution for anime, but if you get most of your stuff from streaming sources you might have to manually link almost everything (or add it to AniDB). I could be wrong and it wouldn’t hurt to check first with some of your catalogue. You could even just log into AniDB and look at the releases for an anime you have, maybe compare file hashes or test it with shoko desktop if that still exists.

I don’t know if it is. The tweet message seems to be the only sexist part of this equation and yet people are overanalyzing the shit out of that picture.

I haven’t heard about all of these flatpak malware incidents.

Unfortunately it’s more of a poorpocalypse, which is why I find this attitude morally reprehensible, even though I don’t have a particularly positive opinion about the average US citizen.

AI generated image with a garbage ass headline on a garbage news site. Man people on lemmy must just hate technology.

Where does this myth come from that Plex is secure to share over the open internet?

Omg it’s HE MANDALDRIAN! Hi!

If I’m gonna buy an authentic baguette, the baker could at least have the decency to wear a beret and a twirly moustache, regardless of their ethnicity.

Get in the fucking PC braixen.

It is, but suboptimal driving behaviour of your fellow drivers is never an excuse to consciously make road traffic even more dangerous or behave aggresively.

For all intents and purposes I don’t have a desktop. It’s just a wallpaper and canvas for the actual workflow. The app drawer is one keypress away, as is the terminal (and I prefer to have separate sessions for different tasks anyway). I usually see my desktop for about five seconds after bootup per day so there’s not much reason to put anything else there. Think of it like the wallpaper or black background of a tiling window manager. I really don’t get how this is such a crazy idea to some people. I’ve subconsciously used the exact same workflow since before Gnome even implemented it, just without explicit support from my desktop environment.

Probably, yeah? I mean I’d hope they’re not still using Gnome if desktop icons are their one wish in life…

Whatever floats your boat. I’m using my keyboard probably 90% of the time and hitting super and typing in one to three letters followed by enter is the fastest way for me to navigate to pretty much anything including system settings and documents. Finding stuff on a desktop with more than a dozen icons is annoying to me. I move windows and switch focus with the standard keyboard shortcuts etc. It’s a familiar workflow for tiling WM users and works that way out of the box, yet Gnome has been catching shit for it since v3. It used to be the disgruntled Gnome 2 userbase but nowadays it seems to be mostly people who don’t use Gnome at all lol.

Icons on the desktop is a non-feature for most gnome users. Even my Windows desktop has been empty since XP released. If you really want desktop icons then using an extension for that should be fine, but it’s silly to frame this as a failing of the “Gnome people” just because Gnome doesn’t replicate the classic Windows desktop experience.

The opinions of a christian youth pastor who loves claude code.

I’m pretty sure it’s both.

Type of shit that jerma985 would write down on a whiteboard while high.

There are some good points in it, though I wouldn’t really consider go dependencies all that decentralized in practice and I don’t understand how checksum db will protect against supply chain attacks with stolen credentials, but I admit I haven’t looked into the details.

But why hasn’t JavaScript established a defacto stdlib to replace ask the left pads and is even type packages?

I’m guessing things were working out pretty alright, even with the insane amount of dependencies per project. The awareness and the increasing frequency of supply chain attacks is relatively recent for npm. But who knows, maybe the tech giants in control of the web standards are happy to keep using their own vendored registries.

Npm probably has the biggest attack surface and many of the libraries hosted there are in extremely widespread use. They’ve taken some steps to mitigate these supply chain attacks, but as we’ve seen with more recent examples, it’s unrealistic to think they can be prevented completely. Most of these attacks use stolen developer credentials, which invalidates almost all potential security measures on the registry side and the best you can hope for is catching a malicious package quickly. To be clear: I think the JS ecosystem is uniquely positioned to be the prime target of supply chain attacks and while that doesn’t excuse the slow implementation of security measures from the npm team, the people arguing that other package managers and registries aren’t vulnerable to this have to be huffing fumes.