Oh buddy, let me tell you about amateur radio… If you’re having a good time on gmrs, consider exploring the ham hobby. So much fun. There’s a lot more landscape to explore than just gmrs gives you. And welcome to the world of RF!

Fair enough! I toyed with the idea of doing it that way because the systemd component would just reference a single yaml file for each service, which feels portable. That said though, my quadlets as they are are pretty portable too. Thanks for sharing!

Just curious why you chose a kube quadlet instead of the typical podman container quadlets?

Slime mold is so god damn cool man

That’s because they just terminate TLS at their end. Your DNS record is “poisoned” by the orange cloud and their infrastructure answers for you. They happen to have a trusted root CA so they just present one of their own certificates with a SAN that matches your domain and your browser trusts it. Bingo, TLS termination at CF servers. They have it in cleartext then and just re-encrypt it with your origin server if you enforce TLS, but at that point it’s meaningless.

Hey neat, I wrote this.

Happy to answer any questions. Feel free to also comment on the post itself if you see any issues or have strong opinions on the content.

Good callout! You’re absolutely right, and here I was primarily focused on publicly accessible services. Thanks for the addition.

That’s a super valid question, as it seems sometimes that some of these things are configured in a way that begs the question “why?” As far as contributing to documentation, that’s a moot point. This is already in the man pages, and that’s exactly what I referenced in writing this post, in addition to some empirical testing of course. As far as implementation goes, I think that probably lies at a per distribution level, where not one size fits all. Although I don’t know of it off the top of my head, I’m sure there’s a security centric distro out there that implements more of these sandboxing options by default.

Excellent! There’s certainly a lot to unpack, but being able to twist all these little knobs is part of the beauty of Linux.

Very glad to gear it! Learning new stuff with Linux is the fun part of the journey.

Hey, much appreciated!

What… This isn’t true at all.

The primary thing is rather than “dumb” flood routing, you can choose the path your message takes to its destination; as a repeater operator you can also choose the path it takes to repeat out. Its a slight compensation to people carelessly placing infrastructure nodes with poor configurations in poor places. Not perfect, but better. Adoption is much, much lower though, and the licensing is not copyleft.

My pleasure. It was a good question, I think I’ll even include a note on that in the post when I get home this evening and can edit.

Cheers!

That’s a great question!

No, blocking a node – router or other – will only block packets originating from that node. All traffic that is forwarded by that node, but originating from others will still be received.

Ultimately, the only place that blocking nodes strategically makes sense is on high utilization routers. If you’re just blocking nodes on a client, it’s not changing channel or airtime utilization for the rest of the mesh. That said though, if someone is harassing you then a block on a client is still fully worth it. 🙂

Meshcore does address some of the biggest shortfalls of Meshtastic, but I absolutely HATE that they’re positioned to either rugpull, or setup a perpetual “freemium” model. It’s also not interoperable, so if Meshcore is to work, it needs the numbers like Meshtastic has.

Yeah, so far the most prevalent thing around my area has been “it’s a hobby for the sake of being a hobby.” No one does anything terribly useful or important with it. I can tell you that I would certainly never rely on it as a form of emergency communication.

La Marzocco

It’s not about user-led synergy. The personal data market is slurped up by those that already have and are building correlations. Just because a user didn’t report anything to their insurer doesn’t mean an insurer sure as shit isn’t going to want the data if they can link it to the user whatsoever, so long as it will make them more money.

This is hypothetical, of course, but it’s the way the market of data brokers works.

You joke, but I guarantee there’s a market. Consider health insurance companies that see an opportunity to charge everyone more unless they can prove their good brushing habits via app data.