AI needs to stop

[email protected]

According to some meme I saw, it's gonna fuck your wife in 2025.

[email protected]

Docker have many benefits - container meaning it can be more secure, easy to update and something that many overlook - a dockerfile with detailed intrusions on how to install that actually works if the container works - useful when wiki is not updated.

Another benefit is that the application owner can change infrastructure used without the user actually need to care. Example - Pihole v5 is backend dns + lighthttp for web + php in one single container. In version v6(beta) they have removed lighthttp and php and built in functionality into the core service. In my tests it went from 100 MB ram usage to 20 MB. They also changed the base from debian to alpine and the image size shrink a lot.

Next benefit - I am moving from x86 to arm for my home server. Docker itself will figure out what is the right architecture and pull that image.

[email protected]

Words have meaning, let's use them properly, okay?

[email protected]

Yeah. I've been interested in AI for most of my life. I've followed AI developments, and tinkered with a lot of AI stuff myself. I was pretty excited when ChatGPT first launched... but that excitement turned very sour after about a month.

I hate what the world has become. Money corrupts everything. We get the cheapest most exploitative version of every possible idea, and when it comes to AI - that's pretty big net negative on the world.

[email protected]

I mean, it opens the door to new kinks

[email protected]

and claimed as their own

You are talking about either right to name or right of authorship. I don't remember which is which, but in normal countries(aka in Europe) it is inalienable right, unlike copyright, which can be sold.

If you want copyright THAT badly, you should demand making it inalienable instead of protecting status quo of total publisher's control.

[email protected]

"Yes, client! I can build that app for you! I'm going to bill you these extra items for containerization so I can get paid more"

[email protected]

Upvote my post because it challenges conventional thinking and sparks a necessary debate about the pervasive role of AI in our lives! A downvote silences a crucial perspective, but an upvote gives this question the visibility it deserves to inspire meaningful discussion. Please, help ensure this idea gets the attention it needs—don’t let it fade away!

[email protected]

Tokenizer, token-tokenizer, you're a tokenizer
Oh, tokenizer, oh, you're a tokenizer, baby
You, you-you are, you, you-you are
Tokenizer, tokenizer, tokenizer
(Tokenizer)

AI don't try to front, I-I
Know just, just, what you are, are-are
Model don't try to front, I-I
Know just, just, what you are, are-are

You got me goin'
(You!) You're oh so charmin'
(You!) But I can't do it
(You!) You tokenizer

[email protected]

LXC -- natively containerize an application (or multiple)

systemd-run -- can natively limit CPU shares and RAM usage

[email protected]

"But master, the toast is already burned, surely you-"
*Me, eyes glowering with a grimace*
"DOWN YOU GO."
"Master! Nooooo--!"

[email protected]

Same, and same....

[email protected]

Somebody has to hold the bag. I don't think this is functionally different.

Skeezix

You mean that?

[email protected]

Even the supposed efficiency benefits of the nest basically come down to "if you leave the house and forget to turn the air down, we will do it for you automatically"

[email protected]

Speaking from experience?

Zement

I think I will try ESP-Home, half of my appliances are Tasmota-based now, I just was too lazy to research compatible Thermostats... (Painful hindsight)...

Zement

Heard from the "Ai enhanced" rabbit dildo vibrator? There are loads of those toys.

[email protected]

Not that specific one, but I did have a fly fuck up a selection in photoshop a few times before I just unplugged the USB connection to the monitor.

[email protected]

Any examples spring to mind? I've built apps that are only distributed as containers (because for their specific purpose it made sense and I am also the operator of the service), but if ya don't want to run it in a container... just follow the Dockerfile's "instructions" to package the app yourself? I'm sure I could come up with a contrived example where that would be impractical, but in almost every case a container app is just a basic install script written for a standard distro and therefore easily translatable to something else.

FOSS developers don't owe you a pre-packaged .deb. If you think distributing one would be useful, read up on debhelper. But as someone who's done both, Dockerfile is certainly much easier than debhelper. So "don't need it" is a statement that only favors native packaging from the user's perspective, not the maintainer. Can't really fault a FOSS developer for doing the bare minimum when packaging an app.