Six months ago I pulled a local language model onto my laptop. Took about 12 minutes with Ollama. No account, no API key, no data leaving the machine. It felt like a small act of sovereignty — exactly the kind of local-first approach I’d been arguing for.

Then I started using it. And I noticed something.

The model’s cultural centre of gravity was somewhere around San Francisco, circa 2022. Ask it about food systems and it defaulted to commodity agriculture and supermarket supply chains. Ask it about community governance and it reached for American municipal frameworks. Ask it about traditional land management and it gave me a careful, earnest summary that read like it had been assembled from university anthropology papers — not from anyone who had actually grown anything, or sat with the country long enough to know it.

Every few months, Australia’s business press discovers a new emergency. Right now it’s the capital gains tax. According to the usual commentators — founders, VCs, and their aligned media — Labor’s move to replace the 50% CGT discount with inflation-adjusted indexation is an act of vandalism against Australian ingenuity. Entrepreneurs will flee. Talent will dry up. The unicorns won’t come.

I’ve been working in and around Australian agtech and startups for the better part of two decades. I’ve watched the same arguments recycled through every policy debate: the R&D tax credit, the ESVCLP scheme, the startup visa. The answer is always the same — give us more upside, or we’ll take our toys elsewhere.

A few days ago I was listening to an episode of It Could Happen Here — Cooper Quintin and Colonel Panic from the EFF walking through the American surveillance state. Flock cameras on every corner. Cell site simulators at protests. Facial recognition with no accountability, built on databases scraped from your social media without asking. PenLink buying location data harvested from your phone’s apps and selling it to law enforcement — no warrant required, because it came from advertising networks instead of a phone carrier.

I’ve spent 30 years watching tech cycles come and go, from the first dial-up modems in rural Austria to the mesh networks I’m currently stringing across the Australian bush. Each time a “next big thing” arrives, we see the same pattern: a frantic rush to centralise, followed by a slow, painful enclosure of what should have been a common resource.

The current noise around AI in open source feels different. It feels heavier. There’s a justified fear that AI-generated code is hollowing out our commons. Maintainers are being buried under a drift of unvetted, mediocre pull requests, while a handful of platform monopolies strip-mine decades of community work to feed their proprietary black boxes.

After years of experimenting with various LPWAN mesh networking technologies, I’ve settled on Reticulum as my primary LoRa mesh platform. It emerged as the clear frontrunner not because it’s simpler than the rudimentary Meshtastic (it isn’t), nor because it’s overtly more feature-rich than the structured MeshCore, but because its design philosophy fundamentally aligns with what matters most: privacy, resilience, and true decentralisation. It supports multiple bearer protocols, making it a powerful tool for building a future decentralised network.

For many new to LPWAN mesh networking, MeshTastic often appears as a starting point due to its affordability and active community. It can get you from zero to sending a basic mesh message relatively quickly. For some, it may seem like a convenient entry into mesh networking.

In this post, I’ll dive into what makes MeshTastic tick, where it excels, and where it falls short based on my own experience using it across various scenarios.

In the last post, I explored the graveyard of ‘bricked’ devices—hardware rendered useless by corporate decisions. It’s a stark reminder that when you don’t control the software, you don’t truly own the hardware. The clear alternative is Open Source, but that path has its own critical vulnerability: sustainability.

But this is where the journey gets complicated. We flee to platforms like Home Assistant and embrace open-hardware projects, expecting a haven of stability and privacy. And while we find it, we often forget a crucial truth: “free and open source” does not mean free to create.

The promise of the “smart home” was a future of convenience, efficiency, and seamless automation. We bought into the vision of light bulbs that dim with a voice command, thermostats that learn our habits, and security systems we can monitor from halfway across the world. But for a growing number of consumers, that dream is turning into a nightmare of expensive, useless hardware. The culprit? A business model built on centralised control and proprietary systems.

As a new year begins, it’s a natural time for reflection. Looking back at the history of this blog, it started during my years working in online education. I was fortunate to be surrounded by inspiring colleagues who lived by the principles of “working out loud” and developing ideas “out in the open”. It was a vibrant, collaborative time.

A lot of water has flowed down the rivers Murray and Drau since then, and I’ll be the first to admit that my practice of sharing my work has become sporadic at best. I’m extremely keen to change that.

I’ve been living and working in Australia for a good while now, having moved from Europe with a healthy dose of open-source enthusiasm. Over the years, however, I can’t help but notice a stark difference between the two continents: the politically engaged, almost rebellious, hacker culture that is so vibrant in Europe seems to be missing its pulse here Down Under.

This has really hit home for me while watching the live streams from the 39th annual Chaos Computer Club Congress (39C3) in Hamburg. It’s one of Europe’s largest gatherings of hackers, activists, and creatives who don’t just write code, but actively question and shape the world it runs on. It’s a cultural phenomenon, not just a tech conference.

Having just wasted a few hours on getting this Java software running on Linux I am documenting this for future reference and hopefully saving other LoRa / TTN folks some time.

Prerequisites

Install a Java JDK + JavaFX. This should work with the default OpenJDK 8 or 9 which comes as part of the Ubuntu repositories. I ended up installing Oracle JDK 8 as well as I thought the error might be related to OpenJDK.

Unfortunately it is still much harder than necessary to find notebook hardware to use with Ubuntu (or other Linux variants). This blog is full of past experiences (some of them quite time-consuming) on finding notebook hardware that will work without too much fiddling. This short note is to document my recent research on that front to help others who want to do the same (as there doesn’t seem to be a lot of good current info around).