thank you nostr:nprofile1qy2hwumn8ghj76rfwd6zumn0wd68ytnvv9hxgqgewaehxw309ahx7um5wf3ksetrdvhx6ef0wfjkccteqqsrkl7gyds37xh2af37uwlknvjm32ska3hgr5d0cwgzdqy0ux2r2ncqcsc2a

really appreciate what you’re building here, this kind of work is crucial for real digital sovereignty and self‑hosting.

I’m still too much of a beginner with networking and security to run a setup like this safely, and for people without the right skills there’s a real risk of doing the opposite of privacy and exposing a critical vulnerability. So for now I’ll keep learning and experimenting on a smaller scale.

Your work is essential for people who want to self‑host their own infrastructure. Huge respect.

Reply to this note

Please Login to reply.

Discussion

Maybe read it over first before jumping to conclusions. WireGuard is battle tested and trustworthy. Running your own resolver is pretty straightforward and I include instructions on how to setup spill over in case it doesn’t work. The canary is oh shit backup to let you know something is not working right.

Response not intended to be as harsh as it sounds upon second reading. 🙏Mia copa

You’re absolutely right, I will definitely read it. You probably already understand that my criticism was more of a self-critique rather than about your work, which I actually consider extremely valuable.

After all, nothing stops us from starting to experiment with networks and secondary devices until we gain enough confidence.

Another key aspect, in my opinion, is being able to count on developer and advocate “proxies” who can self-host, even just for a small circle of close friends, in a federated, value-for-value mindset, which I believe is one of the hallmarks of open source technologies.

🙏