I remember when they would call you a lunatic for saying this kind of tracking was possible.

Now it’s in commercial products as a feature.

I've vibe coded almost a dozen weekend projects this year and with every single one, I've done something I've never tried before. Whether it's developing for a wholly new platform, using a completely new JavaScript framework, or accessing hardware APIs I have zero experience with.

It's incredible how much you can learn by fully submitting to the vibe. Instead of spending days researching the tools I'd like to use, I'm just using them. In the process, I'm learning new things every single day. The learning experience is much more intense than it has ever been in my rather long coding career.

I've never learned as much about programming as I did in the last year. Insane. If this isn't the singularity, I don't know what is.

In a wallet focused on tracking financial activity to add on that

our biggest risk as bitcoiners is complacency

push forward

never stop 🫡

Being Off-the-Grid Isn’t the Goal. Being Intentional Is.

There’s a certain romantic appeal to disappearing. No phone. No social media. Cash only. A cabin in the woods with a shortwave radio and a garden full of root vegetables.

But going off-grid isn’t a realistic or even necessary goal for most people. It’s not about disappearing completely. It’s about being deliberate with what you allow in, and what you give away.

---

You Don’t Need to Nuke Your Digital Life

You still need to communicate. Pay bills. Use maps. Work. Not everything digital is the enemy. The real problem is blind trust.

Most people walk around with surveillance machines in their pockets and call it convenience. They click “Accept All” because it’s faster. They post without thinking. And then they wonder why ads seem psychic or why a random account knows what city they slept in.

Intentional privacy means you use tools on your terms. It’s not all or nothing.

---

Minimal Exposure, Maximum Control

Being intentional means asking simple questions:

* Do I *need* this account?

* What am I sharing, and with who?

* Can I do this with less data involved?

You might still carry a phone but maybe it’s running a hardened OS. You still of course use the internet but behind a VPN and a hardened browser. You keep accounts but they’re segmented, minimal, and rarely tied to your real name.

You don’t stop living. You just stop leaking.

---

Off-Grid Fantasies Miss the Point

Sure, living entirely offline avoids a lot of problems. But unless you're a monk or a fugitive, it’s not practical. You’ll just end up isolated, frustrated, and eventually crawling back to the very systems you were trying to escape without having learned how to use them properly.

Instead of cutting cords, learn to route the cables through filters you control.

---

Build with Purpose

Privacy isn’t about rejecting tech. It’s about reclaiming control. Use alias emails. Harden your OS. Avoid convenience traps like autofill and social logins. Compartmentalize accounts. Use encrypted communication. Disable junk you don’t use.

This doesn’t make you a hermit. It makes you a functional digital citizen with a spine.

---

Final Thought

Off grid fantasies are a distraction, not a destination. The goal isn’t to vanish. The goal is to be harder to track, influence, or exploit.

You don’t have to disappear. You just have to stop being easy to find.

#UNTRACEABLE #privacy

Don't let the bad actors trick you into thinking Bitcoin Core 30 allows you to re-enable the datacarrier limit:

1) Along with unlimiting the default, they also broke it further. datacarriersize=83 now (as of Core 30) allows for 83 outputs totalling 830 bytes of spam, instead of just 92 bytes of spam (9 bytes of which couldn't be arbitrary) as in Core 29 and earlier.

2) datacarriersize is marked as deprecated, and explicitly planned to be removed in a future release (likely silently, since "it's already deprecated").

3) Core never fixed the Inscription exploits (CVE-2023-50428 and CVE-2024-34149) which allow spammers to bypass the datacarriersize limit.

The only way forward now is a mass migration to Knots. Not the way I wanted things to go, but Core has given us no other choice. Once this is resolved, we should avoid putting all our eggs in one basket, and encourage the creation and use of multiple clients.

Seems like that's a question to Lumi... are they using NWC?