A Blog That Lasts, a Space That Is Beloved
by
gg582 · 2026-11-05 13:01:49 · 25 views · 4 min read
Also in: 한국어
Table of contents
What It Means to Build a Sustainable Blog
Many people consider using WordPress or Velog as a sustainable way to maintain a blog.
And surprisingly, a critical security vulnerability surfaced in PHP recently. While this may not compromise every single WordPress installation, a vulnerability within the language itself has likely loosened the front doors of far more blogs than most realize.
Here is another point: if WordPress were to cease maintenance tomorrow, we would be forced to trace someone else's architecture backward just to maintain a fork.
In contrast, "Oborona's House" remained completely unaffected throughout these recent security incidents. It runs on roughly 40,000 lines of blog logic alongside approximately 50,000 lines of a C-based web framework. The core runtime itself is merely in the 20,000-line range.
If I ever need to address security concerns, it usually amounts to pulling the latest commit of BoringSSL, an internal dependency of CWIST.
And even if BoringSSL were to be abandoned, switching to a different implementation is always an option.
At the end of the day, it is just about 50,000 lines of bare-bones C code. Incrementally swapping out a few modular components is hardly a daunting task.
And Backups Are Always Essential, Right?
A common blind spot when running a personal blog is treating a VPS as if it were a physical server.
The primary node of this blog is indeed a VPS located in Finland. However, without a physical backup node, all data would be irretrievably lost if the hosting provider were to shut down for any reason.
That is why I maintain a physical server in South Korea myself-- a compact machine powered by an N150 CPU.
The shutdown of publishing platforms, the sudden public archiving of open-source projects... losing one's writing space due to decisions made by third parties has always been a familiar story.
If you are Korean, do you remember the shutdowns of Paran Blog or Daum Blog? I remember them distinctly.
Those platforms did provide "data backups" to their users. But could anyone actually restore and run those backups, littered with severed connections to defunct external services? Anyone who received them would likely say no.
Through that process, we lost countless memories those are far more valuable than tens of thousands of lines of C code. Regardless of our intentions, we powerlessly crammed data into external hard drives, only to forget about them entirely.
The AI Era Is a Truly Fortunate Time
While legitimate issues like copyright disputes and the dilution of minority identities exist, the AI era makes mastering codebases of tens of thousands of lines surprisingly straightforward. Compared to the intrinsic value of preserving memories, maintaining a blog engine of this scale and patching vulnerabilities in a custom framework requires negligible effort today.
The volatile nature of the web environment? Backups and service recovery are painless in this era.
Provided that the system is truly your own.
In practice, adding a new feature to this blog only requires feeding the framework's context, generating the code, reviewing it, and integrating it. Even when there is little bandwidth to obsess over code quality, rolling out an extension remains manageable.
Just today, I added video subtitle support to this blog-- a straightforward extension for digital accessibility.
Therefore, This Blog Holds No Regrets
This site serves as a space for sharing technical posts, yet it leans a bit too casual to be considered a strict portfolio.
Compared to Github.io, which was designed as a proper portfolio, the arguments here are firmer, and the writing is not bound strictly to neutrality or detached objectivity.
Because the portfolio links back here, I still refrain from overly personal subjects. Nonetheless, genuine memories continue to accumulate on this blog, including insightful remarks left on posts like the one on Heron's formula that broadened my perspective. (That comment was in Korean. A commenter was noticing me that my formula is prone to value loss when calculating extremely small triangle.)
How should I put it? Sharing these small moments of daily life, alongside the recorded traces of my past self... it feels far too wasteful to let them freeze over under an external maintainer's "public archive." Furthermore, today's standard practices will inevitably reach an end someday.
Yet, as long as it remains under personal ownership, it can outlast the shift of those conventions.
In the United States, there are still enthusiasts keeping Diversi Dial chat rooms alive from the Apple II era. Landlines and TELNET are no longer the standard internet, yet users still connect and converse actively.
In contrast, services like Hitel BBS and Chollian BBS, which were used by the affluent of my parents' generation, have vanished completely. The writings once hosted there have left no trace behind.
Much like Diversi Dial, I hope this blog remains a living, breathing space well into the 2050s, even as virtual reality and advanced AI-driven webs become ubiquitous. And I hope that does not remain an empty wish.
People still read printed newspapers in the AI era. And I was reading a physical book just a few days ago.
Ultimately, I want this blog to remain a quiet, warm, and personal space. Much like the red accents that define its interface.
Comments
No comments yet.