ChaosMeeting 2026/05

• Meshnet
  • Website
  • Logo
  • Branding - how to frame Meshnet
  • Handheld nodes - did they arrive?
  • Node config: regio Settings

xbr got a skeleton website based on Hugo and the "Blowfish" theme, it's up on projects.c3l.lu (Kallithea) under freifunk/meshnet/www.

The README.md has documentation regarding how things work, how you can add new pages, … . The website does not have a lot of text/content yet.

Ideally, we should focus on 1 language to write things in, and then have translation done somehow (manual machine translation?), and the translations must also never be out of date.

Feel free to start adding content/text to it. There are some skeleton pages for Meshtastic and Meshcore, but we need a common page for Meshnet that explains what the project is about, and most importantly, what differentiates the subprojects, and how they belong to Meshnet, which brings us to the following topic.

orimpe made an initial draft logo, we discussed it in a previous ChaosMeeting (2026/03), and xbr reworked it into a vector logo.

During this ChaosMeeting we discussed the current logo, and tinkered with multiple variations (e.g. vertical text as an example Sticker)

They are available on projects.c3l.lu (Kallithea) under freifunk/meshnet/artwork.

Meshnet was a great branding idea to regroup all of our mesh network efforts.

While it may make sense to us, it needs to make sense to people we talk to about this: people that have never heard of Meshnet, Meshcore, Meshtastic, Freifunk. Imagine how confused they may be:

"What's what? How do they relate to one another, and why should I care? Is Meshtastic like Meshnet, they both start with Mesh, unlike Freifunk?"

We did some brainstorming on "Why did we make Meshnet? / Why are we interested in (projects)?": what came out of it was that our main interest comes from a resiliency perspective.

We do trust and use networks every day, be it cellular, coax, fiber, the PSTN, the Internet, but we also know how co-dependent they have become on one another, and how one unrelated software failure can cascade into a whole ISP / Telco being down.

It's worth noting that outside, there are other perspectives on this, f.i. preppers find interest in it for their purposes, many radio amateurs like the far-reaching network aspect of it, as it uses the same technology, but develops a solution differently, and some critical infrastructure providers may want to still be able to communicate and organize responses, even when other networks are down.

This solves "how to brand Meshnet" but not "how to introduce the subprojects and their differences".

Yes they did, orimpe and virii are working on it.

We're tending more towards Meshcore nowadays, so some questions have been asked upstream regarding that.

We probably should approach this like we used to with Freifunk: have a bunch of (models of) nodes in-stock, and we can thus do workshops and sell them.