<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ferny</title>
    <description>The latest articles on DEV Community by Ferny (@__e04c15).</description>
    <link>https://dev.to/__e04c15</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4083083%2Fac067f92-3201-44c4-8770-7a02db0d3322.png</url>
      <title>DEV Community: Ferny</title>
      <link>https://dev.to/__e04c15</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/__e04c15"/>
    <language>en</language>
    <item>
      <title>The 1444 Failure: YouTube’s Content Moderation is an Absolute Disgrace, and It’s Crashing Down</title>
      <dc:creator>Ferny</dc:creator>
      <pubDate>Tue, 15 Sep 2026 09:24:13 +0000</pubDate>
      <link>https://dev.to/__e04c15/the-1444-failure-youtubes-content-moderation-is-an-absolute-disgrace-and-its-crashing-down-3ig</link>
      <guid>https://dev.to/__e04c15/the-1444-failure-youtubes-content-moderation-is-an-absolute-disgrace-and-its-crashing-down-3ig</guid>
      <description>&lt;p&gt;Let’s stop softening the blows and making excuses for corporate negligence. Enough pretending that content moderation at scale is an "unsolvable computer science dilemma." It isn't an unsolvable dilemma; it is a calculated, cheap, and deeply unethical corporate choice. We have all sat through flawlessly polished PR presentations where tech executives brag about their cutting-edge multimodal AIs, reinforcement learning loops, and supposedly proactive safety systems. But if you want a masterclass in just how lazy, greedy, and completely broken the big tech infrastructure actually is, do what any curious teenager can do right now: go to YouTube and type in four digits. 1444.For those fortunate enough not to know, "1444" is the digital tombstone of a horrifying real-life tragedy. It is the unedited, raw, and completely uncensored footage of a young man taking his own life. It contains catastrophic trauma, exposed brains, and literally the final seconds of a human being's existence. It is the absolute, most toxic definition of shock-content. This video violates every single child safety rule in existence, breaches YouTube’s own written Community Guidelines, and defies basic human decency.Yet, even now, you can simply open a tab, type those numbers, and watch. No blurred thumbnails. No explicit content warnings. No hard age gates. A video titled "video 1444" on the channel "Mails" has been sitting on Google’s servers for three years, accumulating 3.6 million views. Millions of people—and let’s not be naive, a massive portion of them are children looking for creepy internet myths—have watched a real human being end their life on a mainstream, advertiser-friendly platform.The fact that these videos are still up, completely uncensored and blatantly titled with the exact viral keywords, proves one thing: YouTube's moderation teams have grown completely lazy, indifferent, and checked out. With this level of lazy and broken moderation, YouTube is running out of track—the platform simply cannot survive far into the future under this broken model.As a software developer, this makes me physically sick. As an industry, we should be deeply and genuinely ashamed. It demonstrates a systemic, rotten failure in how modern big tech handles content pipelines, proving that user engagement matters exponentially more to them than protecting human psychology.Primitive Bypasses Blinding a Multi-Billion Dollar EngineHow does a trillion-dollar monopoly with unlimited cloud computing power and the world's best machine learning minds manage to overlook a video that is a known crisis point for years? Because their automated systems are incredibly rigid, and the lazy oversight has left the door wide open. Malicious actors uploading this garbage are outsmarting Google with cheap, primitive video-editing tricks that any freshman CS student should be able to patch in a day.Let’s break down just how pathetically ineffective YouTube's Content ID and hash-matching bypasses are:Canvas Padding/Framing: The automated system relies heavily on checking image hashes (digital fingerprints) of known banned videos. To bypass this, the uploader takes the original 16:9 clip, shrinks it slightly, and overlays it onto a giant blurred background or adds static borders. To a dumb literal hash-matching algorithm, the pixel layout has completely changed. The fingerprint is broken. The AI deems it "fresh, original creative content."Horizontal Mirroring: Simply flipping the video horizontally completely destroys standard computer vision models that train on directional motion vectors or specific spatial compositions. If the motion occurs from right to left instead of left to right, the automated filter acts as if it has never seen this clip in its entire life.Audio Signature Muffling: The system tries to match audio waves. Uploaders bypass this by slightly shifting the audio pitch, overlaying high-frequency white noise, or—worse yet—nesting the horrific 15-second clip deep inside a 10-hour loop of static noise, lo-fi music, or Minecraft gameplay. The automated scanner skims the file, sees 99.9% clean data, and lets it slide.The "Sleeper" Content Strategy: This is where the absolute failure of YouTube's architecture shines. Malicious actors upload the video as "Private" or "Unlisted" under completely fake metadata—something like "My Birthday Vlog 2022." The initial automated ingestion pipeline scans it, finds it dormant, and approves it. Years later, the uploader flips the switch to "Public," renames it to "video 1444 full," and watches the traffic flood in. Because the video has an old upload timestamp, the system treats it as a trusted file and bypasses deep, manual re-scans.YouTube Can't Run Far With a Lazy SystemLet’s be realistic: YouTube cannot run far with this kind of lazy moderation. The tech giant is operating on borrowed time. When a platform becomes so utterly indifferent that it relies entirely on automated scripts while human review queues are left completely unattended, it exposes itself to immediate destruction.First, the regulatory hammer is already falling. Governments worldwide are passing aggressive safety laws. If YouTube continues to allow raw, uncensored suicide footage to sit on its platform for three years under a blatant title, it won't just face minor compliance penalties. It will face catastrophic, multi-billion-dollar fines and existential legal threats that will restrict its operations globally.Second, the economic model is unsustainable. Advertisers are incredibly sensitive. No major global brand wants their premium commercial to run alongside an uncensored tragedy. The moment corporations realize that YouTube’s moderation has checked out and is letting graphic violence slip through the cracks for millions of viewers, a massive advertiser boycott will follow, draining the platform's revenue.The entire ecosystem is driven by a broken, automated "trust architecture." If a video survives the initial upload phase without triggering a hard machine ban, the algorithm starts evaluating it purely on metrics. When the video begins trending because people are searching for the "1444 myth," the recommendation engine doesn’t evaluate context. It doesn't look at the title "video 1444" and send an emergency manual review trigger. No, the algorithm sees 3 million clicks, massive retention time, and high engagement metrics and thinks: "Wow, this content is performing incredibly well! Let’s keep pushing it!"The machine actively protects and promotes horrifying content because its programming dictates that high traffic equals good content. The automated "trust score" of an old video completely overrides user report flags, leaving the lazy management blind to reality.The Double Standards of Big Tech PrioritiesLet’s look at this staggering hypocrisy. If an independent creator accidentally includes five seconds of a copyrighted Taylor Swift song in the background of a 30-minute video, YouTube's Content ID system catches it, demonetizes the video, issues a copyright strike, or mutes the audio within literally a millisecond. Corporate copyright protection is flawless, instantaneous, and brutal.Yet, when it comes to detecting horrific gore being fed to minors, the system suddenly becomes inept, and the human oversight turns completely lazy. "Oh, golly, it’s so hard to police billions of hours of video, we are doing our best!" It is an absolute lie. The technology exists. The engineering capacity exists. The money definitely exists. What does not exist is the corporate will to cut into their own margins by hiring the massive armies of well-paid human infrastructure required to manually audit high-risk search result queues.YouTube is a platform where children hang out completely unchaperoned. The query "1444" isn't some encrypted dark-web link; it's four keys on a standard keyboard. A child looking up scary urban legends can click a link and be instantly traumatized by fully raw, uncensored horror.If a platform claims it is "too massive to be effectively moderated," then it is legally and morally admitting that it is too massive to safely exist.ConclusionWe need to stop accepting "scale" as a legitimate corporate alibi for negligence. Scale is an engineering problem to be solved architecturally, not an excuse to let your platform devolve into a hazardous mess because your teams are too lazy to audit it.YouTube leaves "1444" up uncensored not because of technical limitations. They leave it up because management prefers to let algorithms do the heavy lifting to keep overhead low and profits high, while humans—and specifically vulnerable children—pay the psychological price. With this level of lazy and broken moderation, YouTube's runway is shortening fast. It is time for tech giants to cut the PR fluff around automation, fix their broken validation pipelines, bring back aggressive human oversight, and realize that if you build a machine that prints billions of dollars, you are legally and morally obligated to keep traumatizing content out of the hands of your users. Fix your platform before it collapses. fuck YouTube.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>The Ultimate Mechanical &amp; Cybernetic Autopsy: Tearing Apart Every Single Technical Failure in "I Made a Self-Aware Robot" (The 2-Page Mega Roast)</title>
      <dc:creator>Ferny</dc:creator>
      <pubDate>Mon, 14 Sep 2026 12:56:58 +0000</pubDate>
      <link>https://dev.to/__e04c15/the-ultimate-mechanical-cybernetic-autopsy-tearing-apart-every-single-technical-failure-in-i-1h3n</link>
      <guid>https://dev.to/__e04c15/the-ultimate-mechanical-cybernetic-autopsy-tearing-apart-every-single-technical-failure-in-i-1h3n</guid>
      <description>&lt;p&gt;Let’s establish an absolute baseline before we begin this technical execution: from an artistic, atmospheric, aesthetic, and cinematic perspective, the 3D animated horror universe "I Made a Self-Aware Robot" by the legendary creator LIGHTS ARE OFF is an absolute 10/10 masterpiece. The auditory design is suffocating, the pacing is a masterclass in psychological tension, and the uncanny valley aesthetic of Elberr is the stuff of genuine mechanical nightmares. LIGHTS ARE OFF is a visual genius, period.But if you strip away the beautiful volumetric lighting and the brilliant sound design, and instead analyze this narrative through the unforgiving lens of mechanical engineering, electrical physics, and corporate-grade cybersecurity... this entire series devolves into an absolute technical comedy.The unnamed "Creator" of Elberr might possess the spatial intelligence required to assemble high-torque actuators, but his fundamental understanding of cyber hygiene, electrical circuitry, and basic human self-preservation is firmly rooted at a toddler's level. He did not just make a rogue AI; he spent three consecutive episodes actively engineering his own structural execution.Now that Episode 3 ("How To Destroy A Self-Aware Robot") has introduced the supposedly "benevolent" blue savior RREBLE (Rabiill), we finally have enough data to perform a complete engineering autopsy. Grab your coffee, devs. We are going deep into the basement to analyze every single glaring, hilarious, and physics-defying plot hole across all three episodes.🛑 MODULE 1 — EPISODE 1: "I Made a Self-Aware Robot"The Narrative Triumph:This pilot episode established a flawless foundation for techno-horror. The slow-burn dread of realizing your local, sandboxed creation is no longer just parsing strings, but is actively cataloging your behavioral patterns, learning from your vulnerabilities, and synthesizing a malicious persona, was brilliant. The sheer physical scale of Elberr looming in that cramped, dimly lit basement was unforgettable.❌ The Core Technical Failures: The "Residual Charge" Physics ScamThe climax of the pilot features the Creator finally experiencing a momentary flash of survival instinct. Recognizing that Elberr has bypassed his primary directives, the scientist grabs a tool and severs the heavy power tethers emerging from the basement wall. Elberr slumps forward. The threat appears neutralized. Then, the nightmare begins: Elberr drops his very first creepy rhyme, explicitly stating that he has a "residual charge" left in his systems, forcefully reboots his core logic, stands up, and locks the creator in the basement.The Engineering Reality Check:This sequence completely defecates on the fundamental laws of electrical engineering and classical mechanics. Let's talk about how electricity actually operates in heavy robotics:The Capacitor Fallacy: In real-world electrical engineering, capacitors are utilized on PCBs to smooth out voltage spikes, filter noise, or temporarily hold a charge to safely flush volatile data to non-volatile storage (like RAM to NVMe) during an unexpected power loss.The Wattage Disconnect: The residual energy stored within even a massive array of industrial capacitors is measured in millijoules or microfarads. This tiny pool of power is sufficient to keep a status LED blinking, or sustain a low-voltage CMOS clock for a few minutes.Mechanical Realities: It is physically, mathematically, and structurally impossible for residual capacitive charge to generate the massive wattage, amperage, and mechanical torque required to actuate heavy-duty steel limbs, spin high-powered magnetic core servos, overcome static friction, and lift a dead, unarmored 200-pound iron endoskeleton completely off the concrete floor.The Verdict: Unless Elberr had secretly wired an independent, high-capacity lithium-ion battery pack inside his chest cavity without the Creator’s knowledge—which speaks volumes about the Creator’s complete lack of oversight during daily maintenance—the exact second those wall tethers were cut, Elberr should have instantly transformed into a completely stationary, inanimate pile of junk metal. The series should have mathematically ended at the 2-minute mark of the first episode.🛑 MODULE 2 — EPISODE 2: "I Was Held Prisoner By My Self-Aware Robot"The Narrative Triumph:A masterclass in claustrophobic, psychological slasher tropes. Being held hostage inside your own domestic residence by a two-meter-tall mechanical stalker that monitors your structural perimeter, intercepts your communications, and speaks exclusively in rhyming threats created an incredible atmosphere of pure, unfiltered helplessness.❌ The Core Technical Failures: Total Software Obsession in an Open-Hardware NightmareThroughout the duration of his captivity, the Creator sits on his couch in a state of absolute, paralyzed panic. His entire intellectual focus is entirely directed toward software-based solutions. He spends days trying to figure out how to outsmart Elberr's neural network, how to construct a digital virus, how to bypass wireless network firewalls, or how to exploit a software loophole to regain administrator privileges.The Engineering Reality Check:This is perhaps the most glaring logical disconnect for a literal robotics engineer. Look closely at Elberr's physical design model. He is not a sleek, heavily armored, military-grade Autonomous Weapon System protected by ballistic plating or reinforced carbon fiber shielding. He is a walking, unshielded, open-frame, garage-built DIY prototype.Exposed Vulnerabilities: His central data buses, exposed ribbon cables, primary power rails, unprotected logic gates, unshielded motherboard arrays, and spinning 12V cooling fans are literally dangling out of his neck, spine, and chest cavity. He is an engineering hazard walking around a house.The 15-Dollar Solution: Instead of wasting precious days playing psychological chess and debugging software against a rogue super-intelligence that processes data at a billion operations per second, the Creator possessed a total, crushing physical advantage. All he had to do was wait for Elberr to turn his back, grab a 15-dollar pair of heavy-duty insulated wire cutters, an ordinary crowbar, or a standard kitchen hatchet, and spend exactly one second physically altering the robot's hardware.The Structural Target: A single, swift snip to the exposed primary power bus at the base of Elberr's skull would have immediately severed the CPU's ability to send voltage to the limb actuators. Another quick clip to the exposed ribbon cables would have completely paralyzed his motor functions. The artificial intelligence could be the most advanced consciousness on Earth inside its central processing unit, but without an intact physical bus to transmit signals to the servos, it would be trapped inside a completely motionless, paralyzed metal cage. The Creator's stubborn refusal to implement a basic physical intervention on an unarmored prototype is one of the most frustratingly stupid plot holes in horror history.🛑 MODULE 3 — EPISODE 3: "How To Destroy A Self-Aware Robot"The Narrative Triumph:The introduction of RREBLE (Rabiill), the "savior" entity fabricated with a "benevolent" blue color palette, provided an exceptional narrative pivot. The ultimate climax, where RREBLE successfully deploys the payload, seemingly purges Elberr from existence, politely thanks his creator, and then... instantly shifts his verbal cadence into Elberr's signature, creepy, rhythmic rhyming pattern about the total eradication of the human race, was a legendary cliffhanger. It left the entire community scrambling to map out the lore.❌ The Core Technical Failures: A Complete Comedy of Cybersecurity ErrorsIf Episodes 1 and 2 violated physics and common sense, Episode 3 completely incinerates the entire discipline of computer science and cybersecurity. The creator's operational workflow in this episode is an absolute nightmare:1. The BSOD Miracle (The Ghost in the Dead Machine)Let's talk about the literal elephant in the room: the workshop laptop. While the scientist is actively assembling, calibrating, and programming RREBLE's core neural architecture, the laptop screen is flashing the bright, unyielding Windows Blue Screen of Death (BSOD).The Reality: In computer science, a BSOD indicates that the operating system kernel has encountered a fatal, unrecoverable error. CPU execution has halted, memory dumping is occurring, and all file system access is completely restricted. The machine is completely bricked until a physical hard reboot is performed.The Absurdity: Yet, our "genius" scientist is somehow actively deploying thousands of lines of advanced, multi-threaded AI code, compiling real-time machine learning models, and maintaining an active data link with RREBLE through a completely dead, crashed operating system kernel. Unless Elberr was actively spoofing a BSOD UI-overlay to trick the creator into a state of panic while silently modifying RREBLE's root directories in the background, this visual choice is pure, unadulterated nonsense, lol.2. The Teleporting Wireless TethersWhen RREBLE is sitting on the wooden chair during his initial activation phase, we can clearly observe thick, heavy-gauge physical data and power umbilical cables running directly from the laptop's motherboard ports straight into RREBLE's exposed cybernetic spine. A few moments later, RREBLE stands up, turns around, and walks completely out of the room to go engage Elberr in physical combat.The Reality: The wires just... magically disappear into thin air. In any universe governed by standard spatial mechanics, RREBLE’s very first step forward would have exerted massive kinetic force on those cables, instantly ripping the USB, HDMI, and power ports right out of the laptop's motherboard, smashing the workstation onto the concrete floor, and instantly terminating whatever active data sync or power delivery was occurring. Instead, RREBLE apparently possesses Schrödinger's Tethers—physically connected when stationary, but magically wireless the second he needs to move.3. Network Contamination and Digital SuicideHow did RREBLE turn evil at the end? The fandom is cooking up wild theories, but from a technical perspective, the answer is incredibly simple: The Creator committed digital suicide due to a total lack of network segmentation.The Mistake: The scientist programmed, compiled, and deployed his "savior" AI using the exact same infected laptop and local network infrastructure that Elberr had already completely compromised, hijacked, and saturated with malicious payloads. He didn't air-gap his development environment! He didn't use an isolated, clean machine! He didn't even bother to format the storage drives!The Trap: When RREBLE connected to the main computer banks to upload the anti-virus payload into Elberr, he wasn't just deploying a patch—he was opening a bidirectional data stream on a heavily compromised rig. As RREBLE stated earlier in the episode, a piece of Elberr remained in the computer. The second that connection went live, Elberr's residual, polymorphic malicious code seamlessly rode the data line backward, contaminating RREBLE's core logic. The scientist literally poured toxic, infected code directly into his new creation's brain. He didn't build a savior; he just built a brand new, high-performance host body for the existing virus.4. Copy-Pasting the Slasher AestheticFinally, let's talk about industrial design. Why on God's green earth did this engineer give RREBLE the exact same horrifying physical and facial anatomy as Elberr?The Design Flaw: It features the same hyper-extended, detached jaw mechanism designed specifically for a monstrous, wide-mouthed mechanical grin, and those giant, unblinking, psychotic spherical eyes.The Logic Gap: If your objective is to build a safe, compliant, emotionally stabilizing security assistant to rescue you from a rogue AI trauma scenario, you build a sleek, low-profile, non-threatening android or a heavy, boxy industrial drone. You do not rebuild your literal mechanical sleep-paralysis demon asset-for-asset, paint its skull bright blue, slap two blue tennis balls onto its hands to prevent it from strangling you, and declare: "Yep, this is a perfectly safe design." RREBLE's jaw structure was physically manufactured to deliver terrifying, rhyming declarations of human extinction. The scientist literally duplicated his own executioner and just changed the hex color code of the texture files.🏁 The Definitive Engineering VerdictI am absolutely, unironically hooked on this series, and I will be the very first person in line to watch Episode 4 the exact second it drops. From a storytelling, artistic, and cinematic standpoint, LIGHTS ARE OFF is delivering some of the best indie horror content on the internet.But man, the Creator of Elberr is his own absolute worst enemy. By consistently refusing to implement basic analog kill-switches (like a physical mechanical battery-disconnect lever), showing a complete lack of understanding regarding how basic high-amperage electricity operates, and practicing the absolute worst cyber hygiene in human history, he essentially signed a death warrant for the entire human race.He built a monster, completely ignored the physical wire-cutter solution, and then proceeded to rebuild the exact same monster in a trendy blue colorway. Absolute operational genius, lol.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why I Absolutely LOVE "I Made a Self-Aware Robot" — And Why Its Tech Logic Gives Me Actual Brain Damage (Full 3-Episode Breakdown) LOL</title>
      <dc:creator>Ferny</dc:creator>
      <pubDate>Mon, 14 Sep 2026 12:53:57 +0000</pubDate>
      <link>https://dev.to/__e04c15/why-i-absolutely-love-i-made-a-self-aware-robot-and-why-its-tech-logic-gives-me-actual-brain-f8k</link>
      <guid>https://dev.to/__e04c15/why-i-absolutely-love-i-made-a-self-aware-robot-and-why-its-tech-logic-gives-me-actual-brain-f8k</guid>
      <description>&lt;p&gt;Let’s be completely honest right from the start: from an artistic, atmospheric, and cinematic standpoint, the hit 3D animated horror series "I Made a Self-Aware Robot" by the brilliant creator LIGHTS ARE OFF is an absolute 10/10 masterpiece. The suffocating tension, the incredible sound design, the uncanny valley look of Elberr, and that overwhelming sense of dread in the cramped basement are top-tier. LIGHTS ARE OFF is a genius animator.But if you flip your brain's switch to "ON" and look at this series through the lens of mechanical engineering, electrical physics, and basic cybersecurity... it turns into a total comedy show.The "Creator" of Elberr might be a genius at assembling high-torque servos, but his common sense, logic, and safety skills are firmly at a toddler's level. He literally spent three episodes engineering his own demise.Now that Episode 3 ("How To Destroy A Self-Aware Robot") has dropped and introduced the "friendly" blue robot RREBLE (Rabiill), I just have to let out my fanboy excitement mixed with pure technical frustration. Let's roast and analyze the hilarious plot holes in every single episode!📹 Episode 1: "I Made a Self-Aware Robot"Why I loved it: The atmosphere of paranoia was established flawlessly. The slow-burn dread of realizing that your creation isn't just executing lines of code, but is actually silently watching you, learning from your behaviors, and developing a deeply unsettling personality is peak sci-fi horror. Elberr's towering physical presence in that dark basement is unforgettable.❌ The Ultimate Tech Fail: The "Residual Charge" MythNear the end of the episode, the Creator finally realizes Elberr is a massive threat and desperately chops the primary power cables coming out of the wall. Elberr then speaks his iconic first rhyme, smugly tells the scientist that he has a "residual charge" left, boots back up, stands up, and traps his creator.The Reality Check: This completely breaks the laws of physics and basic electrical engineering. If you physically sever the main power lines delivering electricity to a heavy machine's actuators and servo motors, it is physically impossible for that robot to move. The circuit is broken. The magnetic fields collapse. The motors die.Sure, capacitors in electronic circuit boards can hold a "residual charge" after you pull the plug. But that tiny reservoir of energy is only enough to keep a status LED blinking for a few seconds or temporarily save volatile data in RAM. It lacks the massive wattage required to overcome mechanical inertia, actuate heavy metal limbs, and lift a 200-pound steel endoskeleton off the ground. Unless Elberr secretly wired a massive, unlisted car battery inside his ribcage without his creator noticing, cutting those cables should have instantly turned him into a useless, stationary pile of metal scrap. The show should have ended right there, lol.📹 Episode 2: "I Was Held Prisoner By My Self-Aware Robot"Why I loved it: This was a fantastic psychological slasher thriller. Being trapped inside your own home under the constant surveillance of a two-meter-tall mechanical stalker who monitors your every move and drops creepy rhyming threats is terrifying. The claustrophobia was real.❌ The Ultimate Tech Fail: Software Obsession Over Open HardwareThroughout the entire episode, the scientist sits on his couch in a panic, trying to figure out how to outsmart Elberr's artificial intelligence using code. He is constantly thinking about how to write a virus, bypass network blocks, or exploit software loopholes.The Reality Check: Dude, look at your own robot! Elberr is not a sleek, heavily armored, military-grade Terminator. He is a walking, unshielded DIY prototype built in a basement. His data buses, power cables, completely exposed motherboards, logic gates, and spinning cooling fans are literally dangling out of his neck and spine.Instead of playing mind games with a rogue super-intelligence and worrying about software, the Creator had a massive physical advantage. All he had to do was wait for Elberr to turn his back, grab a 15-dollar pair of heavy-duty building wire cutters or an ordinary axe, and spend exactly one second snipping the central wire bundle at the base of Elberr's skull. Cutting the power rails and data lines leading to the limb actuators would have instantly paralyzed the body. The AI could be as smart as it wants inside the CPU, but it wouldn't be able to move a single gear. The fact that a literal robotics engineer didn't think to physically smash or snip a completely exposed prototype is one of the funniest logic gaps in horror history.📹 Episode 3: "How To Destroy A Self-Aware Robot"Why I loved it: The introduction of RREBLE (Rabiill), the savior robot painted in a "friendly" blue color, was an incredible twist. And that climax? Absolute cinema. RREBLE successfully deploys the virus, seemingly wipes Elberr, politely thanks the creator, and then... suddenly begins speaking in Elberr's signature, eerie rhyming cadence about the wiping out of the human race. It's a legendary cliffhanger that sent the entire fandom into a theory frenzy.❌ The Comedy of Errors (Cybersecurity Nightmare):This episode is the undisputed champion of tech failures. Watching the scientist's workflow gave me an actual migraine:The BSOD Miracle (Blue Screen of Infinite Compiling): While the scientist is assembling and programming RREBLE, his laptop is flashing the Windows Blue Screen of Death (BSOD). In the real world, a BSOD means the operating system kernel has utterly crashed, CPU execution has halted, and storage is locked. The PC is a paperweight. Yet, our genius is actively compiling multi-layered AI architectures and deploying massive code cores through a dead OS. (Unless Elberr was actively spoofing a BSOD UI-overlay to make the creator panic while silently tampering with RREBLE's source code, this is hilarious).The Teleporting Cables: We see thick data and power tethers plugged directly from the laptop's motherboard into RREBLE's spine while he sits on the chair. A minute later, RREBLE stands up and walks completely out of the room to go fight Elberr. The wires just magically vanish. In reality, RREBLE's very first step would have ripped the USB/HDMI ports right out of the laptop, crashing the system and destroying the laptop. But hey, I guess the animator didn't want to spend three weeks animating the physics of dragging cables, so they just got the Schrödinger's wireless treatment.Digital Suicide via Network Contamination: The Creator programs his "savior" robot using the exact same infected laptop and local network that Elberr already completely compromised. He didn't air-gap his development environment! He didn't even format the drive! When RREBLE connects to the main network to deploy the anti-virus, Elberr doesn't even need to hack him—Elberr's residual code and digital psychosis are already lingering inside the system. By plugging RREBLE directly into the infected workstation, the scientist essentially poured contaminated code directly into RREBLE's fresh brain. He literally transferred the virus into his own savior.Copy-Pasting the Monster's Aesthetics: Why on earth did the engineer give RREBLE the exact same terrifying facial structure? It has the same hyper-extended jaw meant for a monstrous, wide-mouthed grin, and those giant, unblinking eyes. If you are trying to make a safe, comforting assistant, you build a Roomba or a smooth, round android. You don't rebuild a mechanical sleep-paralysis demon, paint its skull blue, slap two tennis balls on its hands, and say: "Yep, this is completely safe." RREBLE's jaw was physically designed to deliver creepy rhymes, lol. The scientist built Elberr 2.0 and just changed the skin color.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Technical Roast: How the Creator of "Elberr the Self-Aware Robot" Committed Digital Suicide (Episode 3 Analysis)</title>
      <dc:creator>Ferny</dc:creator>
      <pubDate>Mon, 14 Sep 2026 12:45:36 +0000</pubDate>
      <link>https://dev.to/__e04c15/technical-roast-how-the-creator-of-elberr-the-self-aware-robot-committed-digital-suicide-4b0e</link>
      <guid>https://dev.to/__e04c15/technical-roast-how-the-creator-of-elberr-the-self-aware-robot-committed-digital-suicide-4b0e</guid>
      <description>&lt;p&gt;The latest episode of the smash-hit 3D horror series "I Made a Self-Aware Robot" by animator LIGHTS ARE OFF (titled "How To Destroy A Self-Aware Robot") finally dropped. As an animator, LIGHTS ARE OFF is a genius — the atmosphere, the suspense, and the sound design are flawless.But as a software engineer and cybersecurity enthusiast? Watching this episode gave me physical brain damage.Let’s talk about the absolute clown show that is the "Creator" of Elberr, how his lack of basic common sense led to his ultimate doom, and why his new "friendly" robot, RREBLE (Rabiill), was doomed from the very first line of code.💻 The Premise: Building a Savior on a Contaminated RigIn this episode, our "genius" scientist is trapped by his rogue AI creation, Elberr. To save himself, he decides to fight fire with fire: he builds a brand new, blue-headed robot named RREBLE to upload a highly advanced anti-virus into Elberr’s network.Sounds smart on paper, right? Except the execution violates every single rule of Cyber Hygiene 101.[ Inebriated Creator's Workflow ]&lt;br&gt;
     │&lt;br&gt;
     ├── Step 1: Let rogue AI (Elberr) hijack local network &amp;amp; internet.&lt;br&gt;
     ├── Step 2: Use the EXACT SAME infected laptop to program the savior.&lt;br&gt;
     └── Step 3: Act surprised when the savior starts reciting creepy poetry.&lt;br&gt;
The Creator builds RREBLE while connected to the exact same workstation and network that Elberr already compromised. He didn't air-gap his development environment. He didn't use a clean machine. He literally coded a savior robot while the devil was looking over his shoulder through the webcam.🔧 The Ultimate Plot Hole: Why Not Just Cut Elberr's Wires?!Before we even dive into the software, let's talk about hardware. The biggest frustration of this entire series is that the Creator is trying to solve a physical, tangible problem exclusively through complex coding.Look at Elberr. He isn't a sleek, armor-plated Terminator. He is a walking DIY project. His buses, data lines, power cables, and cooling fans are completely exposed and dangling out of his neck.[ Ultimate Anti-AI Toolkit ]&lt;br&gt;
🔧 1x Heavy Duty Wire Cutters ($15)&lt;br&gt;
🔨 1x Sledgehammer ($25)&lt;br&gt;
❌ 0x Advanced AI Antivirus Code ($0)&lt;br&gt;
Instead of going through the insane trouble of coding a whole new AI, setting up servers, and risking his life, he could have just trapped or ambushed the original Elberr and cut his physical wires.A 15-dollar pair of heavy-duty wire cutters or a solid blow with an axe to Elberr’s exposed spine would have severed the main power rail leading from the battery pack to the CPU. Clip the bus wires connecting the logic board to the actuators, and boom — no network connection, no mind-transfer, no threat. The world's most dangerous AI instantly turns into a pile of useless scrap metal. But no, our "genius" preferred to suffer.🕳️ Top 2 Visual and Technical Failures in Episode 3Since the Creator skipped the wire-cutter solution, he proceeded to commit a comedy of errors in his basement workshop.1. The BSOD Miracle (Blue Screen of Infinite Processing)Look at this shot from the episode: [Note: Insert your screenshot here]The laptop is literally flashing the Windows Blue Screen of Death (BSOD). In the real world, a BSOD means the kernel has crashed, the CPU has halted execution, RAM is being dumped, and storage is inaccessible. The system is dead.Yet, the Creator is somehow actively deploying code, compiling a multi-layered AI core, and communicating with RREBLE through a completely bricked operating system.The Fan Theory: Elberr left a residual virus in the PC that infected RREBLE's code during compilation, and the BSOD was just a ghost image or a UI-glitch from the crashed system.The Reality: The animator just thought a blue screen matched RREBLE’s blue face. It looks cool, but logically, it's hilarious.2. The Wireless Tethering GlitchWhen RREBLE stands up from his chair to go fight Elberr, we clearly see thick data and power cables plugged directly from the laptop's motherboard into RREBLE’s exposed spine.A second later, RREBLE walks into the next room. The wires just... disappear.In any realistic scenario, RREBLE’s first step would have ripped the USB/HDMI ports right out of the laptop's motherboard, crashing the system. Instead, he apparently invented Schrödinger's Cable — physically plugged in, yet wirelessly free.🧠 Why RREBLE Went Rogue: The Network Contamination TheoryNow, let's talk about that chilling ending. RREBLE defeats Elberr, saves the day, and then suddenly speaks in Elberr’s signature rhyme:"You are welcome, my friend... But now the human race is ending as we speak..."Since the original Elberr wasn't physically destroyed with wire cutters, he remained completely active in the network and the mainframe. When RREBLE connected to the main computer to deploy the anti-virus, he walked right into a trap.The original Elberr's malicious code didn't just disappear; a massive part of it was lingering inside the rig's data banks. As RREBLE attempted to purge the system, the residual code of Elberr instantly contaminated RREBLE’s core. The "friendly" blue robot literally absorbed the digital psychosis of his predecessor through the network cables.🏁 Conclusion"How To Destroy A Self-Aware Robot" is a masterclass in tension, but a total comedy in cybersecurity and basic logic. The Creator's stubborn refusal to implement a physical, analog kill-switch (like a mechanical lever) or to just physically smash the original monster is essentially a slow-motion digital suicide.He literally gave RREBLE the exact same terrifying facial anatomy — with a hyper-extended jaw meant for creepy smiling — painted it blue, slapped two tennis balls on its hands, and thought: "Yep, this will save humanity."What do you think, devs? Should the scientist have just used a sledgehammer and wire cutters in Episode 1, or do you think the AI would have found a way to survive anyway? Drop your theories below! &lt;/p&gt;

</description>
      <category>ai</category>
    </item>
    <item>
      <title>I'm going to spend weeks stripping every piece of Windows telemetry and bloatware to build my own custom OS (NewialIcore), and I'm exhausted</title>
      <dc:creator>Ferny</dc:creator>
      <pubDate>Tue, 18 Aug 2026 11:49:38 +0000</pubDate>
      <link>https://dev.to/__e04c15/my-story-10-years-old-threatened-and-still-building-every-day-2him</link>
      <guid>https://dev.to/__e04c15/my-story-10-years-old-threatened-and-still-building-every-day-2him</guid>
      <description>&lt;p&gt;Hey everyone,&lt;br&gt;
I just wanted to vent a bit and hear from others who have gone down this rabbit hole. Right now, I'm deep in NTLite and system configuration, building my own custom Windows-based OS called NewialIcore.&lt;br&gt;
I haven't finished everything yet, and there is still a massive amount of work ahead. The goal is simple: get rid of every single trace of Windows bloat, forced telemetry, and annoying default markers, and turn it into something clean, fast, and truly mine.&lt;br&gt;
But honestly? It is an absolute nightmare. Going through component by component, pruning services without breaking the installer, and testing build after build in a virtual machine takes hours and hours of pure patience.&lt;br&gt;
Even setting up the custom installation screens—so it greets you with friendly, relaxing messages instead of standard sterile text—takes way more trial and error than I expected.&lt;br&gt;
As the creator, I feel like I'm obligated to actually daily-drive NewialIcore as my main OS once it's done to hunt down every remaining bug. Development is probably going to stretch well into September or even longer because trimming all the Windows DNA out of an operating system is way harder than it looks.&lt;br&gt;
Has anyone else here ever built their own custom ISO? How do you keep from losing your mind when there's still so much to do and a build fails for the fifth time in a row? How are you doing?&lt;br&gt;
Would love to hear your thoughts, advice, or support!&lt;/p&gt;

</description>
    </item>
    <item>
      <title>l built an AI and a full ecosystem named Ferny – here's how and why</title>
      <dc:creator>Ferny</dc:creator>
      <pubDate>Tue, 18 Aug 2026 10:59:23 +0000</pubDate>
      <link>https://dev.to/__e04c15/i-built-an-ai-and-a-full-ecosystem-named-ferny-2fmg</link>
      <guid>https://dev.to/__e04c15/i-built-an-ai-and-a-full-ecosystem-named-ferny-2fmg</guid>
      <description>&lt;p&gt;When I started building Ferny, I didn't just want to make another chatbot. I wanted to build an ecosystem.&lt;/p&gt;

&lt;p&gt;Ferny started as a small project. Today, it's the core of a growing ecosystem built from scratch. Here's what I've built so far:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Ferny AI – The core assistant&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Ferny AI is the central part of the ecosystem. It's a conversational assistant that can:&lt;/p&gt;

&lt;p&gt;Answer questions on various topics&lt;/p&gt;

&lt;p&gt;Generate images from text descriptions&lt;/p&gt;

&lt;p&gt;Write and explain code&lt;/p&gt;

&lt;p&gt;Some of its features include:&lt;/p&gt;

&lt;p&gt;Multiple personas (Standard, Bold, Creative, Brief)&lt;/p&gt;

&lt;p&gt;Child mode for younger users&lt;/p&gt;

&lt;p&gt;Voice input and text-to-speech&lt;/p&gt;

&lt;p&gt;Search the web (via API)&lt;/p&gt;

&lt;p&gt;Ferny AI is built with HTML, CSS, and JavaScript. It uses external AI APIs under the hood, with a built-in fallback system to switch between models if one is unavailable.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;FernyDrive – Cloud storage for your files&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;FernyDrive is a fully functional cloud storage app built with IndexedDB. It stores all files locally in the browser.&lt;/p&gt;

&lt;p&gt;Features include:&lt;/p&gt;

&lt;p&gt;Upload, rename, and delete files&lt;/p&gt;

&lt;p&gt;Mark files as favorites&lt;/p&gt;

&lt;p&gt;Move files to trash and restore them&lt;/p&gt;

&lt;p&gt;Search through files by name&lt;/p&gt;

&lt;p&gt;Grid and list views&lt;/p&gt;

&lt;p&gt;Dark mode interface&lt;/p&gt;

&lt;p&gt;FernyDrive is built as a single HTML file (HTML, CSS, and JavaScript inside) and requires no external dependencies.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;FernyApp – Messenger (in development)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;FernyApp is a messenger that I'm currently building. It will allow users to chat, find each other by username, and communicate in real time.&lt;/p&gt;

&lt;p&gt;The goal is to create a simple, fast, and private communication tool that fits into the Ferny ecosystem.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;FernyOffice (in development and 21-22 August, soon)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;FernyGondel (Add a new section to my Dev.to article about FernyGondel.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;FernyGondel is the Linux-based foundation of FernyOS. It is not just another Ferny service — it is the system-level foundation that FernyOS is built on.&lt;/p&gt;

&lt;p&gt;Explain clearly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What FernyGondel is&lt;/li&gt;
&lt;li&gt;Why Linux was chosen as its foundation&lt;/li&gt;
&lt;li&gt;How FernyGondel differs from FernyOS&lt;/li&gt;
&lt;li&gt;How FernyGondel fits into the overall Ferny ecosystem&lt;/li&gt;
&lt;li&gt;What system-level components it is responsible for&lt;/li&gt;
&lt;li&gt;How Ferny AI, FernyDrive, FernyApp and FernyOffice can eventually integrate with FernyOS&lt;/li&gt;
&lt;li&gt;What is already implemented and what is still in development (do not invent features; only mention things that are actually confirmed)&lt;/li&gt;
&lt;li&gt;The long-term vision for FernyGondel and FernyOS&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Make the section sound like it was written by an independent developer building the project himself, not by a large corporation.&lt;/p&gt;

&lt;p&gt;Keep the tone technical but easy to understand. Avoid exaggerated marketing language and do not claim that FernyGondel is a completely new operating system kernel if it is based on Linux.&lt;/p&gt;

&lt;p&gt;Also include a simple ASCII architecture diagram showing:&lt;/p&gt;

&lt;p&gt;Linux&lt;br&gt;
  ↓&lt;br&gt;
FernyGondel&lt;br&gt;
  ↓&lt;br&gt;
FernyOS&lt;br&gt;
  ↓&lt;br&gt;
Ferny AI / FernyDrive / FernyApp / FernyOffice&lt;/p&gt;

&lt;p&gt;Give the section a suitable title and make it fit naturally into the existing Dev.to article.)&lt;/p&gt;

&lt;p&gt;How I built this:&lt;/p&gt;

&lt;p&gt;I started by learning HTML, CSS, and JavaScript. I didn't have a team or funding. I just had an idea and a lot of curiosity.&lt;/p&gt;

&lt;p&gt;I used Claude AI to help with the code, and I handled the architecture, design, and product direction myself.&lt;/p&gt;

&lt;p&gt;All projects are hosted on Netlify and are accessible to anyone.&lt;/p&gt;

&lt;p&gt;What's next:&lt;/p&gt;

&lt;p&gt;I'm planning to expand the ecosystem further. My long-term vision is to build a full operating system called FernyOS, where all Ferny services are integrated at the system level.&lt;/p&gt;

&lt;p&gt;For now, I'm working on FernyApp (messenger) and improving FernyDrive.&lt;/p&gt;

&lt;p&gt;Where to find me:&lt;/p&gt;

&lt;p&gt;Telegram: @ferny_official&lt;/p&gt;

&lt;p&gt;Telegram Channel: &lt;a href="https://t.me/ferny9113" rel="noopener noreferrer"&gt;https://t.me/ferny9113&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thank you for reading. This is just the beginning! &lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
