Offline Anchors: Why I Built a Life System Resistant to Algorithms

For a while, my first instinct when unlocking my phone wasn’t to look for information—it was to get swept away by it.

I’d wake up in the morning, intending only to check the weather, but I’d end up tapping into messages, scrolling through two short videos, and skimming a few financial headlines. Ten minutes later, I hadn’t even seen the forecast, yet my mind was cluttered with judgments unrelated to my day: who blew up, which model just launched, which stock is being discussed, or which route got turned into another “Guizhou secret.”

None of this content is necessarily trash. The problem is that it arrives too fast, too densely, and too aggressively fights for attention.

I eventually realized that someone is truly influenced by algorithms not because they consume certain content, but because their order of judgment gets rewritten. Before, I would ask myself what I needed to do today. Now, it’s easier for the information feed to ask me: Do you want to see this? Do you want to jump on this trend? Do you want to feel anxious about this?

This is what I call my “offline perceptual coordinate.” It’s not some mystical concept; it’s a system of boundaries I’ve built for my life and work.

Why I Need an Offline Coordinate

Programmers easily underestimate how invasive recommendation algorithms can be.

We tend to think we understand technology well enough—knowing how these systems operate—so we assume we won’t be affected. But the reality is exactly the opposite. The more you know about algorithms, growth, and content distribution, the more reasons you find to justify consuming the feed: I need to keep an eye on this, I have to research that, I can’t fall behind on this trend, I must try out that new tool.

At the end of the day, your computer is open, your browser has a dozen tabs, and your phone keeps pushing notifications. You feel like you’ve absorbed a lot of information, but very little actual judgment has settled.

Running XBSTACK, I’ve become increasingly clear on one thing: a personal system isn’t built by taking in more input, but by establishing a more stable filtering sequence.

I need a coordinate system that tells me what deserves to come in, what stays outside for now, what’s worth writing an article about, and what’s just today’s noise.

My Personal Website Is the First Layer of Filter

I used to treat my website as a publishing tool. Write an article, publish it, wait for search indexing, wait for traffic changes.

Later, I realized the more important function of a personal website isn’t publishing—it’s filtering.

If an idea can’t be written into a post on the site, it might just be an emotion. If a judgment can’t be supported by a title, summary, body text, internal links, and follow-up reviews, it probably isn’t mature enough to go public. If a project can’t settle into a long-term page on the site, it’s likely just a temporary distraction.

This filtering process is clunky, but effective.

For example, AI tech articles eventually need to settle into /ai/. Tools need to connect to /tools/. Investment reviews need to return to /investing/. Outdoor routes need to return to /life/hiking/. If a piece of content doesn’t have a place on the site, I ask myself: Is this really a long-term asset of mine, or just a reaction triggered by the information feed today?

This is also why I’m reluctant to write everything as “hot-take commentary.” Trends move fast, but they rarely accumulate value.

NAS, Reading, and the Outdoors Aren’t Three Separate Things

On the surface, NAS, reading, and the outdoors don’t seem related.

NAS is about storage and self-hosting. Reading is about input and thinking. The outdoors is about stepping away from screens and walking in the mountains. But in my system, they all solve the same problem: taking back control of my own judgment.

NAS teaches me that important data doesn’t have to live on someone else’s cloud. Reading teaches me that viewpoints don’t have to be picked up off the information feed. The outdoors teaches me that physical feedback is more reliable than emotions displayed on a screen.

Some judgments only become clear when you step away from the desk.

When I night-hike Qianlingshan in Guiyang, I usually carry nothing but a bottle of water and a flashlight, too lazy to even change my shoes. As I climb the slopes, my phone signal is still there, but my focus naturally narrows. I stop thinking about ten different trends at once; I only think about where to place my next step, whether my breathing is steady, and if rain is coming.

That state is precious.

It reminds me that humans aren’t meant for high-speed input all the time. A system without cooling periods will treat every signal as a task and every piece of information as a command.

Rules I’ve Set for Myself Now

First, I don’t check the information feed in the morning.

Not because I’m particularly disciplined, but because I know I’m not strong enough. If the first thing I consume in the morning is platform-fed content, my entire thought process for the day gets disrupted. So I check the weather, my schedule, server status, and the tasks I absolutely must complete today.

Second, I write down important judgments.

Writing them down isn’t to look serious; it’s to expose those judgments to structure. Can the title hold up? Is the evidence sufficient? Can the links be filled in? Can it be reviewed later? These questions force me to compress vague ideas into solid thoughts.

Third, I schedule offline time every week.

It can be a night hike, a route nearby, or simply sitting for a while without opening social apps. The point isn’t the posture; it’s pulling your brain out of the recommendation engine for a bit.

Fourth, tool-service systems should serve you, not your anxiety.

I use AI, automation, NAS, website backends, Search Console, and GA4, but I don’t want to become a slave to these tools. Tools should help me reduce chaos, not create more dashboards, more metrics, and more meaningless to-dos.

Why this belongs in XBSTACK

In the past, I wouldn’t have included an article like this in my sitemap. I’d have felt it wasn’t a technical tutorial, nor a tool page, lacking clear search keywords.

I don’t see it that way anymore.

XBSTACK isn’t just about AI Agents, MCP, n8n, and tool pages. It’s also the manual for my long-term personal asset system. If readers only see tutorials, they’ll struggle to understand why AI, investing, reading, outdoors, and NAS all coexist here. That’s the value of Thinking articles: they explain the underlying connections.

This isn’t fragmented diary entries; it’s what links the different sections of the site together.

The personal website is the sedimentation layer, NAS is the physical foundation, reading is input for judgment, the outdoors are for bodily calibration, and tool pages are the next steps. Together, they make up the XBSTACK I actually want to build.

Final thoughts

I’m not against algorithms, nor against AI.

I use AI every day myself, relying on it to boost efficiency in development, writing, and operations. But the more I use these tools, the more I need a space they don’t default to taking over.

For me, that space is my personal website, offline time, real-world routes, long-term reviews, and those slow-written essays on core principles.

If a person lacks their own coordinates, they’ll think they’re making choices when they’re really just being pushed along.

The meaning of XBSTACK is to nail down those coordinates, one by one.