What this is

Local-first home security & automation with attitude.
No subscriptions. No data siphons. Just a coyote that actually watches the yard.

I design and deploy a self-hosted security/automation stack built on Home Assistant + sane Linux glue, delivered with a bot support (short commands, readable alerts, optional sticker sass). It runs locally, survives shaky internet, and doesn’t hand your footage to a random cloud.

Who This Is For

Coyotes Vision isn’t just a smart-home setup — it’s a modular automation ecosystem designed for people who need more than plug-and-play tools. Straightforward, practical, and easy to evaluate.

• Smart home power users that need scalable, stable, modular automations without blowing up YAML spaghetti.
• IT professionals & automation engineers seeking real-world examples of orchestration across Telegram, cameras, email parsers, random-pool engines, and sensors.
• Developers looking at how to build a fully modular bot “brain” (CVBot Mind), text/media pools, fallback logic, and dynamic command routing.
• Home security users wanting practical monitoring via Telegram/Discord/Etc. (Agent DVR + CVBot alerts + manual video request/playback on TV).
• Tech recruiters needing a clear look at architecture mindset, reliability engineering discipline, and integration approach.

What you get

• Privacy by default. Video stays on your gear. Full auditability.
• Offline-tolerant. Internet dies, automations don’t.
• Human-friendly alerts. Snapshots, context, and zero logspam.
• No vendor lock-in. Standards, not walled gardens.
• Aesthetic & playful. Because security doesn’t have to feel like an airport checkpoint.

Coyote Behind the Console

CVBot is the conversational layer of Coyotes Vision: an always-awake automation companion that ties the entire ecosystem together with you and your devices.

It talks, reacts, routes commands, analyzes context, and bridges the gap between your smart home, your devices, and your daily workflow. It’s a lightweight orchestration engine with a personality. Its responses are randomized from curated text pools, giving every interaction a unique but consistent tone.

Real-time Communication

CVBot communicates through Telegram/Discord/Slack and more. Using a mix of text pools, coyote stickers, structured messages, and system alerts.
Depending on context, it can be:

• a friendly assistant
• a status reporter
• a camera operator
• a security monitor
• a dispatcher

Its responses are randomized from curated text pools, giving every interaction a unique but consistent tone.

Daily Utility

Security & Cameras
When something moves, CVBot knows before you do — and reports cleanly.

• manual recording
• event-based alerts
  (motion, alarm, system triggers)
• clip delivery with fresh MP4s
• selected video export on request

Presence Awareness
CVBot tracks phones, arrivals, departures, and alarm states. It reacts immediately and only when conditions are correct

This is part of the larger “home as a system” paradigm: smooth handoffs, zero noise.

Weather & Orders
Useful, compact, and readable — not a wall of numbers.

• formatted daily briefings
• precipitation warnings
• contextual messages depending on severity

Mail & Packages
Tracks marketplaces like Amazon, Ebay, Etsy shipping events, ETA changes, and delivery confirmations.

• Parses USPS Informed Delivery digests
• Sends updates summarizing what’s coming, what’s late, and what arrived

Personal Customization

Logic, content, and personality fully separated

Users can build their own “living” assistant from the ground up — custom voice, text libraries, stickers, behavioral patterns, visual identity, and even species. The character becomes modular, expressive, and truly theirs, without touching the underlying automation logic.

The assistant becomes part of the home, a digital roommate with a curated personality, tone, and emotional range. And because the system is modular, the character can evolve over time: new lines, new moods, new voices, new behaviors, all without rewriting the core engine.

Professional Scaling:

• Offices: announcements, room scheduling, staff alerts.
• Apartment complexes: package notifications, maintenance updates, visitor flow.
• Warehouses: event parsing, audio cues via VLC grids, workstation presence, shift briefings.
• Themed cafe spaces / escape rooms: audio triggers, lighting effects, story-driven messages.

Engagement model

1. Discovery (email) — goals, constraints, gears.
2. Design brief — topology, privacy settings, automation plan, hardware delta if needed.
3. Build & config — HA setup, cameras, notifications, tests.
4. Handoff — docs, one-page cheat sheet, quick training.
5. Support — pay-per-issue.

Pricing is project-based after the design brief. Time-based payment.

No subscriptions from me, ever.

Tiers

• Starter: 1–2 cams, Telegram/Discord/whatever alerts, local storage, basic scenes.
• Plus: multi-cam, weather logic, audio cues, friendly dashboards.
• Custom: weird layouts, privacy hardening, theming, custom mascot and his voice,
  whatever makes you happy.

FAQ (quick hits)

• Cloud required? No. Optional remote access if you want it.
• Apartment-friendly? Yep. Works fine with Wi-Fi cams and a small NUC/RPi.
• What gear? I’ll reuse what Ebay has or you where it makes sense and sometimes not. Or new.
• Is this open? Built on open platforms; your config is exportable and documented.

Call to action

If you want personalized, local, not-boring home security with a personality, I’ll spec it, build it, and hand it off clean.

Email: 10@r10.wtf
Subject: “Coyote me.” (Yes, really.)

Rio Fenris

Fueled by anxiety, isolation, and nightmares disguised as visions, this game was my way of coding through a personal exorcism. The core idea came from a dream I had back in 2016 — surreal, cold, distant. I started working on it alone in 2019. By the time I quit in 2021, I had stopped drinking and slowly climbed out of the pit I’d been in. No further development is planned. The game is abandoned, exactly how I needed it to be.

There’s no tutorial, no comfort, no friendliness. You learn through suffering. It doesn’t want you. It won’t even pretend. Every move feels like a mistake. Every mistake is punished — with death, and then, just for extra emphasis, a crash. You’re not a hero. You’re just a bug in the simulation.

At first, I thought about using royalty-free music. But people close to me started asking about the project, and I decided to write everything myself. It’s dark ambient stitched together with distortion, noise, detuned piano, and broken filters. Think haunted VHS run through a dying modem. You can stream the full soundtrack on YouTube or download it as a ZIP. It’s free. So is pain.

The Weapon: One and Done

a crossbow

It works like a rocket launcher, just faster and more chaotic. The arrows explode. And yes, they can hurt you. Add a warped FOV and some rough hitboxes, and congratulations: you’re now your own worst enemy.

Power-ups That Help (Sort of)

Acceleration.

Speeds you up. Often straight into your own death.

Chronoprochiberia.

Freezes time for 2 seconds. A gift you’ll misuse anyway.

Status Reset.

Full heal. Spoiler: doesn’t stop the crashing.

At the end of development, only one enemy had been made.

A turret

Only one enemy made it into the final build: a turret. It fires the same explosive bolts you do. Its behavior is governed by Doom’s cursed RNG. Sometimes it fires immediately. Sometimes it stares at you for a moment, just to build tension. Then it dumps four arrows in your general direction. Dodging is possible — assuming the level layout isn’t sabotaging you (it is).

There’s no health bar.

The more screen noise you see, the closer you are to dying. It’s like Doomguy’s classic face HUD — but instead of pixelated macho grunts, you get a glitchy mess reflecting your decay.

Just like Doomguy’s face!

Because his face sprites were replaced!

I was never great at level design. I barely scratched the surface of what GZDoom could do. Things like silent portals were goals I never reached. Still, the maps reflect the state I was in — raw, broken, and unwelcoming. There’s a kind of beauty in that.

I hate this project.

Not in the casual, “eh, I moved on” kind of way — I mean it viscerally. Finishing or releasing this game would’ve felt like sealing a coffin shut. Not the game’s — mine.

This wasn’t just a mod. It was me trying to simulate the feeling of being lost, numb, and functionally dead. I built it while drowning, and for some reason I thought turning that pain into gameplay was smart. In a way, it was — it kept me alive.

But releasing it? Would’ve been the end. A kind of grotesque celebration of everything I was trying to escape. Like turning trauma into a product.

I didn’t survive to make that kind of art.

So no, it won’t be uploaded to ModDB. No source code. No itch.io. No “v1.0”.

This thing stays buried — and that’s exactly where it belongs.

There was this. A cursed little mod I stitched together over a decade ago under the pseudonym Maxim Enotovski. It was never meant to be serious.

Back in 2012, in that glorious age when everything could be a Doom mod and everything shouldn’t be a terry wad, I took the infamous VID mask—that horrifying stone-faced logo from Russian TV—and shoved it straight into the Doom engine. First as a joke, a quick cacodemon sprite swap with creepy new sounds.

May 2015 I went off the rails.

For the uninitiated: VID (ВИD) was a Russian television company, and its intro was the stuff of childhood trauma. A slow pan on a bald stone face in pitch black, paired with cold ambient synths. That logo haunts generations. It’s been burned into the psyche of kids from the ‘90s and early 2000s not just in Russia, but across post-Soviet space—and somehow even beyond. This thing’s got international scare power. There’s something universally uncanny about a corporate stone idol staring into your soul.

The concept of the mod was simple: walk around a flickering TV maze and turn off evil floating VID heads before they scream your soul out. The sound design was criminally stupid in a good way—every head moved with that dreadful droning VID intro sound. If you screwed up and let one get too close, it would scream loud enough to blow out your speakers and take a quarter of your health. Game design? More like cultural PTSD therapy.

I’m not proud. But I’m not sorry either.

Huge shout-out to the Викискримия 2.0 fandom wiki who somehow immortalized this fever dream in a detailed article back when the internet still had pockets of weird. I forgot this existed and it felt like someone had dug up an embarrassing zine from my emo era—but for mods. Honestly, respect.

The project never got past version 1.4.1b and was mostly passed around in VK posts and nocens.ru forum no one remembers anymore. And yet—it lives. I still occasionally get comments on my ancient gameplay videos from people discovering this monstrosity for the first time. Somehow, the stone face continues to scream.

Doom of VID isn’t art. It’s not even a game in the traditional sense. It’s a perfectly Russian, extremely janky, deeply cursed relic of modding culture—and that’s exactly what makes it worth remembering.

Downloads!

doom_of_vid_1.2.4.exe
A completely random mid-dev build I found while digging through some old drives. No changelog, no context. Pure chaos.

dovinstall.exe
Final release: Version 1.4.1b with multiplayer support. Launch on modern systems at your own risk.
(No viruses included. Probably. I was broke, not evil.)