

Bang bang, shoot shoot.
Bang bang, shoot shoot.
Real printers used real paper…
I would say that the software side all qualifies. You’re setting up the full software stack; that’s definitely self-“something”.
I, personally, would only consider it “self hosting” if I can take a sledge hammer to the bare metal without getting arrested.
But, I acknowledge that is an arbitrary, puritanical distinction. I don’t look down on VPS; they have specific pros and cons, and I use them myself. I just think that “self hosting” includes hardware factors, not just the software.
they don’t want to mess with the terminal to troubleshoot any errors.
I reject your premise that the purpose of the terminal is to troubleshoot errors. That is part of the widespread misconception I am talking about.
The terminal is simply for using the computer. With all the command line utilities available, and their widespread interoperability, the terminal should be one of the first tools a user looks for.
A GUI is a hammer. The CLI is the Snap-On tool truck.
EVERYTHING? I enjoy doing things that aren’t eating and sex on a intrinsic level that I was never trained to enjoy.
No, not “intrinsically”, you don’t. Food, fuck, sleep, that’s about it. You likely enjoy other things as well, but not intrinsically. I enjoy Sudoku, but that is something I learned. There is no “enjoy sudoko” element within me that I did not put there myself.
Why didn’t people adopt personal computers en masse before Windows came to be then?
They did. Everyone I knew back in the Windows 3.1 days already had computers. Most of those people didn’t have Windows, and used standalone applications. The increase in ownership came when hardware prices finally fell enough for them to be affordable. Windows development was a result of that uptick, not the cause.
Do you also think that anyone that wants a car should be a mechanic?
I reject the premise.
I think that anyone who wants to be a driver should be able to understand that the brake pedal squeezes the pads against the rotor.
I don’t think that everyone who can identify a brake rotor is a mechanic.
Anyone that wants a drug should be a pharmacist?
I think that anyone who wants any sort of medicine should have enough medical, mathematical, and statistical knowledge to understand that vaccines don’t cause autism. I don’t think that everyone with such knowledge is a pharmacist, mathematician, or statistician.
The idea that the command line is “unfriendly” and that decelopers should hide it away is, in my opinion, the computer equivalent of the antivax movement.
Most people do not intrinsically desire that.
The only things that people “intrinsically” want are food and fornication. Everything else, they have been taught and trained. The training they have received from Microsoft domination has been “don’t learn how to use a computer”.
That training is something to despise and reject, not incorporate into Linux.
Most people don’t care about automation. They just don’t.
Microsoft would certainly have us believe that. Decades of operant conditioning by Microsoft and Apple have given us that attitude.
Most people certainly do want automation; they don’t know how to automate. There was a meme floating around recently about a temp who replaced hours and hours of tedious, daily transcription between two applications with ctrl-c, ctrl-v.
We have all seen plenty of examples like this, with users doing excessive manual labor out of simple ignorance of absurdly simple automation.
And your still refusing the point.
The point arises from the very attitude I am challenging, so yes, I am refusing the point. We should not be encouraging or supporting the behaviors you describe, but should instead be promoting the tools that allow the average user to identify menial tasks and relegate them to the machine.
In my opinion, Linux and its various distro’s main goal ought to be to undermine for-profit OS. Not to turn everyone into computer techs.
Turning everyone into “computer techs” is how we undermine for-profit OS. The command line is a spoon. In the hand of a toddler, it goes flying across the room, along with the mashed potatoes it held. Microsoft’s answer to that flying spoon is to teach the kid that they can never touch the spoon; they must let mommy do it for them (and here is “mommy’s” bill for that “service”).
Microsoft teaches that it is a “pipe dream” for the average person to ever have sufficient mastery over the spoon to be able to feed themselves. They taught us that spoons are scary and dangerous.
Linux keeps putting that spoon on her tray, and encouraging her to use it.
My “goal” has less to do with bringing Linux to the masses and more with bringing the masses to Linux. The “pipe dream” argument you presented should not be ported in. The “normie” should be taught from a very young age that the command line isn’t “unfriendly”, but wildly powerful, and well within their capacity to wield.
if my whole family is to use a Linux environement thet moment they will see a consol they will run away.
Then they will never script anything. They will never automate a task themselves. They will only ever operate a computer manually, interactively, rather than programmatically.
Windows pushed users to remain toddlers their entire lives. They charge us for the privilege, so they want to keep spoon feeding us for our entire lives. When we see a spoon anywhere but in their hands, they want us to throw it across the room rather than pick it up and try to use it.
Microsoft wants your family to run away screaming, rather than asking what that console is and what it can do.
The objective of Linux is to put the spoon on the tray of your toddler’s high chair. Linux encourages her to pick it up, poke it at her food, and keep encouraging her to learn, to develop and build on her skills, until she is asking for the fork, the knife.
Yep. Every Linux problem has the exact same solution: ctrl-c, ctrl-v.
The user is never be expected to type a command into a terminal.
Nope! Absolutely not. This is where Windows 95 fucked us all over. Prior to 95, windows was an application executed from a DOS prompt. Users may not have known many commands, but they learned that commands could be given.
Windows 95 tried to convince us that a GUI developer knew better than the user everything the user wanted to be able to do with that computer. It did make simple use easier, but the way it did it was by hiding the average user away from any simple ability to automate. It took away virtually all command line utilities that could be scripted to run themselves, and replaced them with GUI-driven applications that required the human’s time and attention, repeatedly and monotoniusly sorting through graphical menus and prompts to achieve a task that the computer could easily be “trained” to do itself. It did it by dumbing down the user, reducing their expectations to the few idea the GUI allowed them to express.
GUIs are Fisher-Price toys. They are the bright and shiny, but functionally crippled. There is no need for a distro that deliberately impairs the user in the way that you describe.
Parent comment is on mander.xyz. You are on dbzer0.com. The admins for either instance can prevent your account from interacting with the other.
If you start lemmy.ddash.com, the other admin can still block you, but you are the admin of your own instance. You are the second admin.
I don’t know what should be done, but I’m pretty sure whatever it is will involve a Guy Fawkes mask and a green newsboy hat.
https://jontic.com/two-ais-realize-theyre-talking-to-each-other-and-switch-to-a-secret-language/
Prior to the two AIs switching languages, this was two machines using “voice” to convey data.
Technically, they weren’t using “Internet Protocol” over that voice link.
https://jontic.com/two-ais-realize-theyre-talking-to-each-other-and-switch-to-a-secret-language/
Technically, it’s not internet protocol over voice, but the two AIs are initially using voice to convey (meta) data.
I never got beyond proof of concept, and definitely didn’t keep any documentation.
I used voip.ms as a VPN trunk provider. They handled the incoming and outgoing calls to/from the PSTN, connecting them to my server.
If you’re not familiar with Tasker, I wholeheartedly endorse it. I thought it was a little unintuitive at first, but I use it for all kinds of things now.
I had a setup with a remote Asterisk server, and a Tasker app on my phone.
If I pressed a button on the phone, it placed a call to the Asterisk server, which dumped the call into a recorded conference room.
That was simple enough. The fun part happened next. The cops are always shown telling stopped subjects to stop recording and hang up phones. They’ll take the phone out of your hand, and attempt to delete recordings. I wanted to address that.
I worked out a script on the Asterisk server where if the phone hung up, it would immediately dial back, and dump the call right back in the recorded conference room. Tasker on the phone would silently answer a call from that number.
That was about as far as I got. I had planned on some way of the asterisk server dialing a contact list and adding them to the conference.
I didn’t even know I needed to edit my prompt, but now I don’t know how I have lived with it for so long.
“Fair Use” doesnt even enter into the equation: copyright protects distribution, not reception. It is illegal to send the data; it is not illegal to receive it. It is not illegal to read something you didn’t pay for. It may have been illegal for someone to provide you with that content, and it may be illegal for you to share that content with others, but it is not illegal for you to receive it and to read it.
It is the copyright-trolling “you wouldn’t download a car” types that have spread the propaganda that downloading is somehow illegal. It is not. Uploading is the illegal part: distributing without permission is the violation of copyright. There is nothing illegal in asking for a copy, nor in receiving an unauthorized copy.
Don’t let the zealotry against AI lead you to fight against your own interests.