xXthrowawayXx [none/use name]

I’m with you especially on that last part. My most insane privately racist lug-mate called it modding or customization. Even in the windows shell hacking scene no one described it like that.

I do like using “tuning” though, fond memories of import tuner magazine and my dearly departed first car and first computer.

Lay off. This person is right.

We here at hexbear are concerned about protecting people from seeing csam. That’s good. The rest of lemmy is concerned about that and the very real consequences of csam uploads for the sites, which is getting dropped by hosting and registrar and prosecuted for distributing.

There are already cases where that kind of legal dos attack has worked, there’s even cases of anti csam organizations uploading it to reverse image search sites and then serving them papers when the reverse image search site displays the uploaded image to compare with nonexistent results.

The person you’re replying to isn’t trying to fuck shit up, they’re telling you that this tool won’t actually solve the problem it’s marketed for.

E: edited for clarity and kindness

Because those laptops suck.

Thinkpads are good and cheap. If someone has a bunch of money to spend on a computer they buy a Mac.

Also if the normal invocation of your program produces more than 3k lines of stdout, sanitize it and default to a file.

I think you’re off base here. The utopian socialists were arguing against the methods and outcomes of revolutionary socialism, this person is trying their best to explain that this particular tool has serious legal repercussions within the framework we all live under. Those are pretty different.

The reason I see the logic in their arguments is because there’s longstanding legal precedent for misuse of a tool or material because it’s better than nothing to not be a defense even if there are no other options available.

So if you built a car so big no type of shock absorber could handle it cornering at speed and you knew it, using some amazing whiz bang material for shocks isn’t a defense because even though it’s the best thing you knew it wouldn’t work.

Legally speaking, the right choice there is not to make an excessively dangerous vehicle if you don’t want to be held liable for negligence.

It’s also the argument throughout unsafe at any speed although the courts always seem to side with the automakers 🤔

Or if one were to get sued for hosting csam, using the latest whiz bang ai system for detection wouldn’t be a defense or even a point in your favor because you knew it wasn’t a reasonable use of the underlying technologies. You can’t say “judge, I was relying on the ai csam detector!” When the component parts of the ai csam detector have big “prototype, do not use in production” stickers all over them.

Ultimately while these tools might protect mods and users from having to view csam in the moderation process, that’s just one side of the struggle and on its other side they’re a paper shield at best and proof of negligence at worst.

Hoes mad (x24)

You’re cutting off your nose to spite your face under the mistaken belief that voting with your dollar is effective.

Consider tracking mitigation techniques as opposed to the boycott.

I uh actually agree with you almost entirely. Except at the end I’m like “and that’s why it won’t work as protection”.

Software hasn’t been treated like other fields of engineering and all operators have needed for protection from liability was the twin shields of “nothing I could do” and “I was doing nothing” to come out of any courthouse relatively unscathed.

That type of “aww shucks technocracy” is only possible if you do the bare minimum or nothing at all. Once an operator implements some kind of protection (yes, even one with warning labels all over it), both defenses are rendered unusable.

Now that you’ve done something you’re able to be held liable for the effects of what you’ve done and for knowing there was a problem.

The picture gets even murkier when we look at how things are going! Lawsuits against Tesla for their self driving deaths are making waves not because they impugn the dignity of Americas biggest car manufacturer by market cap but because every judge who sees one raises the biggest eyebrow possible at software engineering not being held to the same standard as any other type, both in a court of law and within its own process.

There’s a good chance that software PEs will become a thing (again?) as a result.

The long and short of it is that because the only reason monsters like moot are able to exist is their sly lethargy and looking at the legal storm rolling into software engineering, having something bolted onto the backend like this would be a bad idea.

I think automated tools like this can be put to use though if they were hosted separately and provided with an api that linked up nicely with some moderation queue standard and returned something like “entries 1,5 and 9 are likely csam” back to the moderator. It would at least save the mod from dealing with the material directly.

So I guess I agree but come to the opposite conclusion.

Yeah. It’s real good. I wish we were federated with more instances, but thats a process and will take time.

Couple hundred gigs. Everything else is on the server.

Eh, none of this is really addressing the fundamentals of getting comfortable figuring out how to do what you wanna do, which is what in my experience leads to people seeing command line use as magic incantations.

Like, if you’re on windows you know how to figure out how to do what you wanna do, right click a file, look for entries in the context menu, look at the properties, open with, etc.

This works because people fundamentally understand the metaphor behind the operating system.

If you’re in bash and don’t know how to do what you wanna do you don’t need any of this fancy zoomer shit, just use “which”, “man”, whatever your package manager offers and the other commands that had big oriley books written about em.

People need to develop the command line equivalent of the “click around and see if you learn anything” skills.

E: I gave the linked article another read and it really is about setting up a production environment in the command line and not about getting people comfortable with the command line at all.

Like, if someone needs to cut down a tree in their front yard they don’t need to know how to operate a felller-buncher, they need to know how to use an axe handle to judge where the tree will fall and what it will fall on.

No it’s bad.

E: anti wayland, anti pulseaudio, anti systemd, pro xscreensaver.