Galactic Vending Machine

WHAT THE LAST RELEASE GOT WRONG 1.0.27's notes said an empty ACTIVE NODES list was a fault on the server rather than on your device. That was wrong, and it was our bug. Your node was being published correctly the whole time — other people could see you. It was your own copy of the list that was broken, in two ways: it was only ever rebuilt when the network volunteered an update, so a device that missed one stayed empty forever; and when it did rebuild, it counted every stale copy of a node, so the same person could appear four or five times over. If you saw duplicates, that was the same fault from the other side. Both are fixed, and the list now repairs itself rather than waiting to be told. SAYING WHAT IS ON, AND WHAT IS MERELY OPEN The mesh and location channels rows said "activate" while the ⊞ chip in the header counted the same features as already on. Those rows only open a panel — they switch nothing on — so they now say open and close. The mesh also described itself as broadcasting your node before you had accepted the community guidelines. Nothing was ever published early; the label was simply wrong, and now it says nothing is published until you agree. HOW TO MESSAGE ONE PERSON You could always tap someone's name in the feed, or type /msg followed by their callsign. Neither was written down anywhere except inside /help, which you have to already know to type. It is on screen now. And when nobody is around, the panel says why a direct message needs someone to have appeared at least once — they are encrypted to that node's key, so there has to be a key. THE MESH AND YOUR SECTOR ARE NOT THE SAME PLACE Different channels, different people, nothing crosses between them. You also carry a different callsign in each sector, deliberately: it is what stops the places you visit being linked to each other, or to your mesh identity. Both panels now say so instead of leaving you to notice the name changed. SETTINGS THAT WERE STUCK OFF If you have had the app a while, features switched on by default in 1.0.27 may still have been off for you — a saved preference always won, even one you never chose. That is now corrected on first launch. If you deliberately turned something off after joining the mesh, it stays off. ——— 1.0.28 (79)