Is it possible to make faceless Youtube channel with the help of LLMs and Claude code?

Voss — Sun, 12 Apr 2026 00:13:45 +0000

Hy everyone! Hope y'all doing well.

After being broke and nerd for few months I am thinking to finally do something to make money while not showing my face.

I'm trying to create a full 60 follow up plans to make AI video to publish on YouTube but wait not just brainrot video I am talking about but Educational video which will help the growing youth.

I have done a lot of research about creating and growing faceless youtube channel but I think I still need some tips and tricks to use.

I am going to use Claude Code, Gemma 4, Qwen 2.2, Pika 2, LTX and other LLMs. Is it enough? Maybe not because AI characters need finishing, lip-sync etc.

I don't have powerful GPU but I am thinking to rent like RTX 3090 or the lastest model which will cost me 0.50-3$/h

Each day I am gonna talk about where I am, how it's going, what will be the next your support will be appreciated in any way.

Any advice or help will be really appreciated.

Thank you.

I started Linux with Parrot OS. Here are every stupid thing I did that forced me to reinstall — so you don't have to.

Voss — Sat, 11 Apr 2026 22:22:18 +0000

Parrot OS is a Debian-based distro built for security and privacy. It looks slick, ships with hacking tools pre-installed, and pulls in every curious 18-year-old who just watched Mr. Robot. I was one of those people.

Here's every dumb thing I personally did — or watched others do — that ended in a full reinstall and a quiet moment of shame.

💣 The "sudo" Disasters
☠️
Running
sudo rm -rf /
"just to see what happens"
YouTube "pranks" and forum trolls have killed more Parrot installs than any bug. This command deletes your entire root filesystem. No prompt. No undo. Done in seconds. Some versions now block it but never rely on that.

sudo rm -rf / # instant death. your OS is gone. sudo rm -rf /* # same thing. don't. rm -rf ~/some_folder # this is fine — only deletes that folder.

🔥Messing with
/etc
without a backup
New users love editing config files in /etc/ — network configs, sudoers, fstab — without making a copy first. One wrong character in /etc/fstab and your system won't boot. One bad edit in /etc/sudoers and you lose sudo access permanently.

✅ ALWAYS backup before editing anything in /etc
sudo cp /etc/fstab /etc/fstab.bak sudo cp /etc/sudoers /etc/sudoers.bak
⚠️ Use visudo for sudoers — NEVER edit it directly with nano/vim
sudo visudo
💀
Chowning the wrong directory as root
Tried to fix a permission issue and ran sudo chown -R youruser / instead of sudo chown -R youruser ~/yourfolder. This recursively changes ownership of your entire system. GUI breaks. SSH breaks. System is unusable.

📦 The Package Manager Chaos
🤡
Mixing apt with random .deb files and PPAs
Parrot is Debian-based. Adding Ubuntu PPAs or random third-party repos will eventually break your package manager. You'll get dependency conflicts so deep that even apt --fix-broken install gives up on you.

sudo add-apt-repository ppa:some-random/ppa # dangerous on Parrot sudo apt update && sudo apt install package # stick to this
🧨
Running
apt dist-upgrade
or
full-upgrade
blindly
Parrot is a rolling-style distro. Running a full dist-upgrade without checking what's being removed can pull out critical system components like your display manager, kernel, or desktop environment. System boots to a black screen. Reinstall time.

✅ Always check what will be removed BEFORE confirming
sudo apt full-upgrade --dry-run # simulate first
🛑 If it says "removing 200 packages" — DO NOT PROCEED
😵
Removing packages that "sound unnecessary"
Beginners see packages like libx11-6 or xserver-common and think "I don't need this." Wrong. These are core display libraries. Uninstalling them cascades into removing your entire desktop environment silently.

🔧 The "I'll Fix It Myself" Kernel Disasters
👻
Deleting old kernels and accidentally removing the only working one
Trying to clean up disk space, you remove what you think are "old" kernels. You accidentally remove the active one or all of them. System won't boot. GRUB stares at you. Reinstall.

✅ Check your current kernel BEFORE removing anything
uname -r
⚠️ Only remove kernels that are NOT the one currently running
sudo apt remove linux-image-X.X.X-XX-generic # where X ≠ uname -r output
🪦
Installing a custom kernel without testing it
Wanted better GPU/WiFi support and installed a mainline kernel. It broke hardware drivers. WiFi gone. Sometimes display gone. Never install a new kernel without keeping the old one in GRUB as a fallback.

🖥️ Display & GPU Carnage
⚫
Installing NVIDIA drivers the wrong way
This is the #1 most reported black screen of death on Parrot forums. People download the .run file from NVIDIA's website and run it directly. It conflicts with the existing Nouveau driver. Black screen on next boot.

sudo sh NVIDIA-Linux-x86_64-XXX.run # DO NOT do this sudo apt install nvidia-driver # use the repo version instead # Or use the hardware manager on Parrot: sudo parrot-drivers
🌑
Editing
/etc/X11/xorg.conf
without knowing what you're doing
Trying to fix screen tearing or resolution issues by manually editing Xorg config. One wrong line and X server refuses to start. You boot to a blinking cursor with no GUI. Recovery mode is your only friend.

🧠 The "I Read It On StackOverflow" Mistakes
📋
Copy-pasting terminal commands you don't understand
The most dangerous habit in Linux. Someone on a forum posts a "fix" and you run it without reading. Could be deleting system files. Could be adding a malicious repo. Could be disabling critical services. Always read every command before you run it.

🔓
Running
chmod 777
on system directories to "fix permission errors"
Got a permission denied error? New users just slap 777 on everything. sudo chmod -R 777 /var, sudo chmod -R 777 /usr. This makes your system a security disaster and can break apps that specifically check for correct permissions to run.

sudo chmod -R 777 /usr # breaks package manager, SSH, and more chmod 755 ~/my_script.sh # this is fine — only your personal script

🔁
Killing processes by name with
killall
recklessly
Typed sudo killall python to stop a hung script and killed 4 system processes running Python in the background. Desktop environment crashed. Had to hard reboot.

⚠️ The real pattern behind all of these:
Every single one of these disasters has one thing in common — running powerful commands with root (sudo) privileges without understanding what they actually do. Linux gives you complete control. It will not stop you from destroying yourself. That's the deal.

✅ Survival Rules for Every New Parrot OS User
Snapshot or back up your system before doing anything major — use Timeshift
Never run a command you copied from the internet without reading it word by word
Before removing anything: Google what it is first
Keep at least one extra kernel in GRUB at all times
Learn recovery mode and chroot — it will save you from reinstalling 80% of the time
Use a VM (VirtualBox/VMware) for experimenting before touching your real install
TL;DR: sudo rm -rf, bad GPU drivers, mixing package sources, editing fstab/sudoers without backups, and chmod 777 on system folders. All of them end the same way — you staring at a Parrot OS live USB wondering where your afternoon went.

DEV Community: Voss

Is it possible to make faceless Youtube channel with the help of LLMs and Claude code?

I started Linux with Parrot OS. Here are every stupid thing I did that forced me to reinstall — so you don't have to.