Exactly this. The entire market is held together by people who are willing to bend over backwards to keep it working. And all it takes is two or three of those to decide “enough is enough” at the same time, and suddenly all of the market’s sins are laid bare. And at that point, the investors panic and everything snowballs.

You can limit your battery charging, so it doesn’t charge to 100% by default. It’s better for your battery life, because Li+ batteries lose more capacity when they’re fully charged and discharged. So keeping them somewhere between the 30-85% range will dramatically extend the life of the battery.

Because there is very little overlap between “programmers who design the systems to be as efficient and reliable as possible” and “UX designers who consider elegance and ease of use, even if it means the install is a few extra MB in size”.

Tons of FOSS UIs tend to fall into one of three categories:

1. CLI. Maybe a third-party GUI exists.
2. Laughably horrendous monstrosities that make early 90’s websites look good
3. A direct ripoff of a paid software that has actual UX designers.

It’s because the people designing the FOSS aren’t UX designers, so they either make their best guess at it (the laughably horrendous choice) or they just copy whatever paid software they’re trying to replace.

The unlicensed suppressor will get you into just as much trouble as destroying the camera. Plus, suppressors don’t eliminate sound. It’s not like in the movies where you get a quiet “thwip” noise. The suppressor simply takes the gun from “almost guaranteed hearing damage without proper PPE” to “was that a firecracker? Or someone hammering a nail?” Sure, there can be quiet shots with the proper suppressor and ammo. But if you’re bootlegging it to avoid licensing requirements, you’re probably not using the optimal setup.

And this is why calling them “license plate readers” is hugely disingenuous, to the point of being straight up propaganda. The term vastly downplays what they can do. They don’t just scan license plates. They scan nearby devices’ Bluetooth and WiFi signals. They scan faces. They scan gait to determine specific limb proportions. They scan tattoos and birthmarks. They scan bumper stickers, dings/dents, etc… If you walk in front of a camera, it will use every trick in the book to try and figure out who you are specifically.

People also shouldn’t pair those masks with infrared-blocking sunglasses or goggles. Because the cameras can see in infrared, and will see straight through regular darkened lenses.

Only the most dastardly vandals would leave their phone (and all other Bluetooth devices) at home, plugged in charging, auto-lock fully disabled, on their home WiFi, with YouTube set to auto-play a playlist. That would create a watch history that the vandal could later use to prove that they were active at home at the time of the crime. Again, you definitely shouldn’t do that.

It can be, yes. One of the largest complaints with Docker is that you often end up running the same dependencies a dozen times, because each of your dozen containers uses them. But the trade-off is that you can run a dozen different versions of those dependencies, because each image shipped with the specific version they needed.

Of course, the big issue with running a dozen different versions of dependencies is that it makes security a nightmare. You’re not just tracking exploits for the most recent version of what you have installed. Many images end up shipping with out-of-date dependencies, which can absolutely be a security risk under certain circumstances. In most cases the risk is mitigated by the fact that the services are isolated and don’t really interact with the rest of the computer. But it’s at least something to keep in mind.

Or just get into CB radio. You can get a unit for like $100. No license required, and it makes road trips much more interesting, because it’s still used by a lot of truckers. Channel 17 for north/south travel, and 19 for east/west.

I mean, he switched to Linux and has advocated for gamers to do the same. So… Maybe?

Yeah, I love my catch-all email domain. If I start getting spam addressed to “Target@{my domain}” then I know Target sold my data; I can burn the account by auto-spamming everything addressed to it, and move on.

Yeah, this can be an unpopular opinion on Lemmy, because there’s a giant Linux circlejerk. But the unfortunate reality is that changing to Linux does have some major stumbling blocks. The “switching is so easy, just do it” crowd totally glosses over it, but that’s kind of rhetoric doesn’t help long term adoption. Because if some new user has only heard “switching is so easy” and immediately runs into issues, they’ll be more likely to go “well if it’s super easy and I can’t figure it out, I guess it’s just not for me” and abandon things.

There’s also a very vocal (and toxic) part of the Linux community that basically just screams “RTFM” at every newbie question. New users shouldn’t be expected to dig into a 350 page technical document just to learn the basics of their new OS.

This is actually why I’d be in favor of AI generators creating a hash database of their generated images. If legalized, they should be required to maintain records of the images they have produced. So that if those images appear elsewhere, they can be verified as AI generated.

It would be a monumental effort to actually get the AI companies to agree to it willingly. But that’s why legislation exists.

The fact that you don’t need to actually supply any real CSAM to the training material is the reasoning being offered for supporting AI CSAM. It’s gross, but it’s also hard to argue with.

Yeah, this is basically the crux of the issue. When you get into the weeds and start looking at more than just surface-level “but it needs CSAM to make CSAM” misconception, arguments against it basically boil down to “but it’s icky.” Which… Yeah. It is. But should something being icky automatically make it illegal, even if there are no victims?

I hate to make the comparison (for a variety of reasons) but until fairly recently homosexuality was psychologically classed as a form of destructive/dangerous kink. Largely because straight people had the same “but it’s icky” response whenever it got brought up. And we have tried to move away from that as time has passed, because we have recognized that being gay is not just a kink, it’s not just a choice, and it’s not inherently dangerous or harmful.

To contrast that, pedophilia has remained stigmatized. Because even if it passed the first two “it’s not just a kink/choice” tests, it still failed the “it’s not harmful” test. Consuming CSAM was inherently harmful, and always had a victim. There was no ethical way to view CSAM. But now with AI, it can actually begin passing that third test as well.

I don’t know how I feel about it, myself. The idea of “ethically-sourced” CSAM doesn’t exactly sit right with me, but if it’s possible to make it in a truly victimless manner, then I find it hard to argue outright banning something just because I don’t like it.

This is really the biggest hurdle. To be clear, I’m not arguing that being an active pedo should be decriminalized. But it is worth examining whether we’re basing criminality purely off of the instinctual “but it’s icky” response that the public has when it gets discussed. And is that response enough of a justification for making/keeping it illegal? And if your answer to that was “yes”, what if it could help pedos avoid consuming real CSAM, and therefore reduce the number of future victims? If it could legitimately help reduce the number of victims but you still want to criminalize it, then you are not actually focused on reducing harm; You’re focused on feeling righteous instead. The biggest issue right now is that harm reduction is very hard to study, because it is such a taboo topic. Even finding subjects to self-report is difficult or impossible. So we’ll have no idea what kinds of impacts on CSAM consumption (positive or negative) AI will realistically have until after it is widely available.

If you already have a Plex instance running, Prologue is an app that turns it into an audiobook host as well. Plex doesn’t natively support audiobook metadata like chapters, but Prologue simply uses Plex’s remote access to reach the files.

All you do is throw the .m4b audiobook files into a music library on Plex, sign into your Plex account on Prologue, and Prologue handles all of the metadata for the audiobooks instead of using Plex’s built-in music player.

I mention this because I had massive issues trying to get ABS to work on my setup. It simply refused to read or write any data from my NAS. After a day or two of throwing myself at it to no avail, I found Prologue and haven’t looked back. I already had Plex running for some friends and family, so setting up the music library was as easy as dropping the audiobooks into a folder.

Hah yeah, Lemmy is a much smaller community than Reddit. I have started tagging users, and it’s surprising how often I see the same tags in the comments sections.

This is true in America. In the EU, Apple was recently forced to allow third-party browsers. But even in the EU, developing those third-party browsers will take time and money.

That’s largely because the companies want to grab all of your telemetry data, which they can’t do in a browser. Putting it in an app allows them to gather whatever info they want, instead of being siloed inside of a browser.

Yeah, people complain about roombas not giving a super deep clean… But they’re really not intended to do so. They’re meant to be a daily maintenance clean. They may not be great for when you dump an entire can of coffee grounds in your carpet… But they’re wonderful when you have a big dog with lots of fur that needs to be vacuumed every single day.

Yeah, you always have to account for the Wife Factor with things like this. Good luck convincing your wife to stop clicking on sponsored links on Google, especially when it’s what she’s searching for.