// DFAULT.IT // Copy + Paste until broken

D-FAULT originally started as a manifesto by Kenny Wang on how to make movies, fabricate films, vaulting videos, and it still is, at its core.

Online, D-FAULT was supposed to become something else entirely: a TV platform, an organizational workflow tool, and most of all, a philosophy of “dfaulting” any process or system down to its simplest, most recognizable and repeatable patterns.

I’m still light years away from recapturing the essence and building what D-FAULT could, or should, have been. For now, dfault.it is a home for some web tools I actually use, and a house for my domain and website projects.

While each new website project will be a test of some sort, trying a new feature, an idea, or just figuring out how something works so I can go back and find it if I ever need it. Dfault.it is where the tools beyond displaying a website will live. Where I can meddle with Bootstrap when creativity needs to fiddle.

Back in the hayday I made a Pop-up Generator, mostly by copy+pasting from wherever I could find code. Monitors were like literally way smaller back then, if you go back 10-12 years, 1920×1080 was considered big. I still even had a trusty 1280×1024. And when you’re poor, when you can’t afford a third monitor, and when Google had the fucking audacity to believe people wanted to stare into bright light all motherfucking day, you had to make your own solutions.

Dark Mode Before Google Gave a Shit – Google Keep Edition

For example I could style Google Keep into a soothingly pleasant dark theme, which I did, heck it even had like 3.2k installs on Userstyles.org before being archived. Keeping up with the constant class changes was a hassle, eventually Google stopped cosplaying Mark Strong in Sunshine and put some shades on their apps.

Even with a dark Google Keep, monitor size was still an issue. This is where the Pop-up Generator became useful. You see, a pop-up didn’t have any of that browser bullshit stealing valuable screen area. Didn’t even show the URL back in the day. Making a pop-up of a website made it feel like a proper program. An app if you’d so kindly not call it that. I could work on my main monitor, and have Google Keep lined up on monitor two, next to WhatsApp and Telegram, all of them with custom dark CSS using the Chrome extension Stylus, all three as pop-ups, none of the blinding lights.

Actually, why the fucking fuck did every single website and app that was released 10 to 15 years ago, all have it in for Gizmo the Mogwai? I rooted my first smartphone so that I could install custom APKs where smarter people had blacked out all the white in apps such as Gmail, Keep, Facebook, etc and so on. It took Google almost 10 years to realize that white light consumed more energy and battery… really?! Were Google developers some sort of super fans of the Gorillaz song White Light? I would have assumed they were psychos, but then they would’ve exploded by their own design…

Anywho!

Copy + Paste until broken!

DFAULT.IT

// KillingHeat.com // The 3000 Photos No One Ever Saw

Killing Heat is a low budget amateur movie I auteured when living in Thailand. While I actually never got around to editing the film, Kenny Wang did that, the domain always lingered as an unfinished project. Also during the shooting we took roughly 3000 photos which I never got around to using for anything. Not even sure it got shared with anyone who were part of the production. Now that I’ve lost my Facebook account with accompanying friend list, I don’t know how I can ever reach out to any of them. Heck, at least two of the actors in Killing Heat have since died (both young and gone too early), and all of the financial backers have passed on due to old-age-related issues. That hit harder than I expected. So I finally decided it was time to do something with all those lost photos before they disappeared forever.

What became my main goal for killingheat.com was a gallery for those lost behind the scenes photos that no-one ever got to see. Unredacted, unedited and raw. But also mostly trash photos that should’ve been deleted…

Click here to see the Killing Heat BTS Gallery!

Without a doubt, I’m pretty much a fanboy when it comes to choosing products, platforms and programs. I was, and still kinda am, a Google Henchman. Gmail, Google Drive, Maps, Keep, Chrome, Pixel, list prolly goes on. I make hard changes to things I like, abandoning other ships, along with all reason. When I was introduced to Telegram in 2014 by KiAnDe I was amazed at this futuristic cloud saving feature. I could receive a file in a chat and have it available on both my mobile and desktop. Simultaneously. At the time I was using Messenger, Skype and WhatsApp. If I was to receive a file on either of those apps, I had to be there to accept it, and if I was on Skype on my phone when someone sent me a file, that file ended up on my phone. Never where I needed it, so I had to manually send it to my PC. That marked the beginning of a new fanboying change. A hard change. I left all other chat apps and embraced Telegram. Has it reduced my social circle? Probably. Anywho!

I started killingheat.com with the “help” of Grok. Because I like Grok. I like Elon Musk. I am a fanboy. And I really tried. Really really tried. Grok would dump new code, even though I asked it to only mention changes I had to make, while making ridiculous claims such as “Fixed — PhotoSwipe is back, fully working”. Didn’t work. Again and again. Maybe this would have been better for my learning curve, to have to figure it out myself, but I noticed that Grok kept rewriting all the code, making changes to parts we were not changing. While not crucial, it annoyed me.

My rusty old friend Lemon kept pushing me to use Claude Code. I took the code Grok gave me, fed it into Claude, explained the problem, and Claude just fucking fixed it. Like a glove! Easily impressed I got Claude Code for VSCode and let Claude read and edit files directly in my project… and good lord this is a mindblowing gamechanger. Claude improved on everything. My code. Groks code. My commenting. Sorting, organizing and cleaning. I felt like a Warlock shouting the forbidden words to create magic. Could this be the vibe they speak of?

The project has grown beyond what I intend to paste into this database, I will update this post once I got git and can link to or fetch from GitHub. Going forward, I assume all projects will way too many files to list here, so I’ll stick to posting individual code snippets I wanna save for posterity. Look, here’s one we did earlier: Arguing with Grok until PHP does what I want!

However, I’ll mention the other elements of this project that isn’t entirely code. I loved PhotoSwipe.js back in 2015, and it’s still a reactive and fluid experience, like how I want it to feel when I swipe through a gallery. Allegedly CSS can now solve what Masonry.js did for me, and while that may be… it while have to be for another project. We had organized the 3000 photos by day of shooting, and each day into three folders: Promo, BTS, and Off. To make the filenames readable without folders, I used PowerRename from PowerToys to name the files in this fashion: killing-heat_day-4_2008-07-02_dsc_9573. To make the gallery load fast, photos were converted to webp in thumbnails and full sized using XnConvert. Original files were 8gb, thumb and full only 3gb. Image degradation not that visible when viewing by phone. It’s not like anyone is using those images (other than to feed into an LLM), so original quality was not needed… but I did include them with a download button. Fancy feature, 90% for myself.

Killing Heat is an ever ongoing project, so I might add new functionality, photos, videos, links and etc to the site. Check the news modal on the site, or simply look to see if the version number has changed (located in footer).

KillingHeat.com

// Meloslave.com // The First Real Project of 2026

Out of all the domains at my fingertips, Meloslave.com was the most straightforward project to approach. I needed a quick fix, a site that could go live fast without too many distractions or variable factors to contemplate. Glenn Thomas Andersen being an artist, musician and a DJ, my first thought was that Meloslave.com needed a linktree (link in bio). His main activity is on Spotify, where people stream his  music (he has 3.8K monthly listeners), so you don’t really need an elaborate website with pages, posts or galleries. You can find all of that on Meloslave’s social media accounts, hence the linktree.

Click here to view Meloslave.com 

The main goal was to figure out video playback as a background, together with social media sharing details, which I must say is rather easy with Grok and Claude at my disposal. Grok may not be perfect, but he does all the heavy lifting, all the noise and chatter, then I ask Claude to refine. Actually, I did ask Chad too… and while he does have good input, my attitude towards The Woke Chad is mostly fuck off. Come to think of it, are alle the LLMs male?

Doing a new thing here where I just link directly to the files on Meloslave.com. Should that work? Weird that it worked… I might have to learn GitHub, eventually.

Did you know? The video used in background was shot on location in Thailand. Click here to see the music video!


Update 17-03-26:
Added code reviewed by Claude into post, rather than fetching from file.

The Landing of Parked Domains

Tackling a sudden comeback to web development hasn’t been easy on my mind. Figuring out where to begin, what to start with, how to approach a long forgotten and perhaps even dead hobby within me… did take a couple rounds. Staring down the barrel of a forced retirement from being a layger gnome, I had to consider the future. My the future.

While I still constantly discuss with the endless voices of myself, the year of the future offered something I didn’t have last time I was active with webdev…

We marveled at our own magnificence as we gave birth to AI.

— Morpheus, The Matrix (1999)

Perhaps not quite the Skynet we were promised, so I will refrain from misusing the term. Glorified Google. Spell Checker on Steroids. Large Language Models… Chad? Grok? Claude? Any of the stupid terms we give each night? Anywho, this technology made it easier for me to discuss with a different entity other than myselves, one that could do the Google for me, collect information at light speed, and help me reach a starting point.

So we landed on making a template for my parked domains. Me, Myself and Grok. We have spun the tiny totem that will eventually weave itself into existence, as my brain reconnects to the web of dev. Or so to speak.

So here we are… screenshots of the parked-domain landings I’ve built so far, plus the code to view them. In time, each parking spot will become a real site, and this post will be the archive of those forgotten placeholders. Also I needed to kickstart writing about whatever the fuck it is that I’m doing…

I won’t go too much into details, I wanted a simple parked setup that would display something slightly different for each domain, with a countdown that is random (giving myself endless time to actually make a real website).

Built with the help of Grok, based on Bootstrap, using Grok Imagine to generate background images. Also I might’ve written a line or two…


Update 17-03-26:
Added refactored code into post, rather than fetching from file. Remember to add “learning GitHub” to ToDo-list.