All is in the title!
#Reticulum Meetup #Berlin
Thursday, July 16, 2026
18:00 – 21:00
Reticulum is post-internet, unstoppable mesh networking for all. Whether you are curious or already running your own nodes, join an informal meetup to discuss all things Reticulum!
xHain hack+makespace
Grünberger Str. 16 (<this one of their 3 addresses)
10243 Berlin
https://x-hain.de/en/calendar/events/2026-07-16-reticulum-meetup/
@tobeku well the idea is just to publish this consensus and also to open it for comments.
There are probably people in Berlin interested by Reticulum who are not aware of this forum (i met 4 last week), and they need to know somehow how to tune their parameters?
Or said differently: now that this is public, shall we make it more public (forget about the Fediverse, it's just one way of speaking to wider circles...)
@l5y @tobeku @scotty (sorry for replying in English!)
I am fascinated by this process, and grateful to everyone here who knows much more than I do about radio for it!
I understand that local/regional consensus on settings, to match with local parameters, density, regulations, etc.. will be critical for a diverse deployment of reticulum networks!
Do you think it's a good idea to (test and) spread this consensus further than this channel? Like announce it over the Fediverse to whomever it may concern?
It may be good sometimes to be keeping notes of those, place by place...
So the way I understand it, there was what looked like a ragequit last December:
https://github.com/markqvist/Reticulum/blob/master/MIRROR.md
(sorry for the github.com link!)
... but after a few weeks of a break code began being pushed again to github.com but solely as a mirror.
More explanation was published a few weeks ago here:
https://github.com/markqvist/Reticulum/blob/master/This Is Not a Teahouse.md
(again as mirror)
The way I see it: Mark Qvist stepped back from github and through this gesture formulated quite an acid criticism of what free/libre software became as commodified by microsoft/github: standardisation of the roles (multiple!) of maintainer revolving around the following: expectation to be publishing code AND to be a public front for the software / obligation to do tech support and answer any request even the most stupid ones / judgement on how well you will manage everyon's sensibility and ego in the process / etc.
It's well explained in the seminal "this is not a tea house" text. Mark Q. likes to produces code and that what he is apparently good at. He will now focus on doing this and just this, and others can decide what to do with it (and it seems to be working well to be fair).
To put his code where his mind is, he also transition the main source for the reticulum code to rngit as of one of the latest releases (1.3.4).
I am personally impressed and confident that his criticism of the "auto-entrepreneur/tech-supporter/influencer maintainer" (my words) will ripple and inspire others to realize the toxic influence and monoculture github culture has instilled in free/libre software.
A lesson of (software) freedom overall!
Go, Mark go! and go Reticulum! 
