Issue 47 just dropped: eight new dispatches from the Harbor District. Build your reading queue before the next power cut.

WIRE::LIVE  ·   ·  REPORTING FROM THE ROOFTOPS  ·  9 RESPONSES LOGGED

Inside the Mesh Networks Keeping the Harbor District Online

RHEA OKONKWO 4 MIN READ 623 WORDS 9 REPLIES 108 VIEWS HOT
Photo accompanying the story "Inside the Mesh Networks Keeping the Harbor District Online"

Two winters ago the last commercial carrier in the Harbor District stopped answering repair calls. What happened next is the most interesting network story in the city.

Where It Started

Nobody planned the rooftop network. It grew the way ivy grows, one bracket and one borrowed extension cord at a time, until a map of the district looked less like a street grid and more like a nervous system. The early nodes were salvaged routers flashed with community firmware, zip-tied to water tanks and pointed at whichever neighbour had line of sight. Today the mesh carries school homework, pharmacy orders and late-night gossip, and it does so without a single invoice. The people who maintain it rarely call themselves engineers. They call themselves neighbours who got tired of waiting for someone else to fix things.

Community radio stations were among the first to embrace the rooftop mesh. Their studios are small, their budgets smaller, and their audiences live within a few kilometres of the transmitter anyway. Streaming over the local network lets them reach listeners without paying for bandwidth, and the shows have adapted accordingly. There are call-in programmes about fixing routers, late-night synth sets recorded live in a stairwell, and a weekly bulletin of power cut schedules read out in four languages. Local media, it turns out, thrives when the infrastructure is local too.

Power is the quiet dependency underneath every other story we cover. The grid in this city was designed for a cooler climate and a smaller population, and every summer it reminds us of that fact. Transformers cook, substations trip, and entire blocks go dark just as air conditioners are needed most. The utility publishes cheerful statements about resilience, but the maintenance backlog tells a different story. Engineers we spoke to described replacing equipment older than they are, rationing spare parts between districts, and watching demand charts climb toward numbers the network was simply never built to carry.

  • Over 400 homes connected, by the collective’s own count
  • Nodes built mostly from salvaged routers
  • Monthly repair nights at the laundromat
  • No subscription fees, ever

Volunteers now count more than four hundred connected homes.1 The number doubles every winter, when the carrier’s outages get worse.2

How It Actually Works

Every city has a layer of infrastructure that nobody notices until it breaks. Here it is the tangle of copper and fibre running beneath the old telephone exchange, a building that officially closed years ago but still carries a surprising share of the district’s traffic. Contractors refer to it as the graveyard because so much abandoned cable remains in the ducts. Removing it would cost more than leaving it, so the dead lines stay, wrapped around the live ones like roots. Mapping what is still connected has become a hobby for a small group of retired technicians.

Corrections are part of the job, not an embarrassment to hide. When we get something wrong, we change the article, note what changed and explain why. Readers are remarkably forgiving of honest mistakes and remarkably unforgiving of silent edits. We also keep a public log of significant updates, because trust is built on the record rather than on promises. If you spot an error, tell us. Include a link, a quote or a document if you have one, and we will look at it within a day and let you know what we decided and why.

We are not waiting for permission anymore. We are waiting for parts.

Ada Brennan, mesh volunteer

INTEL
Node maps are refreshed every Sunday night. If your block is missing, send us the street corner of your nearest rooftop relay.

FOOTNOTES

  1. Figure from the collective’s own node census; we could not verify it independently. ↩
  2. Outage data comes from residents’ logs shared with Chromewire. ↩
OPERATIVE_PROFILE
RHEA OKONKWO

RHEA OKONKWO

@rhea // NETWORK DESK

Rhea covers community networks, power and the physical internet. She has climbed more rooftops for this job than she will admit to her landlord.

9 TRANSMISSIONS RECEIVED
  1. Emeka Lindqvist

    How long did the whole build take you?

  2. Aiko Brandt

    Any chance you could publish the raw data behind this?

  3. Emeka Lindqvist

    Our lab has a spare centrifuge if anyone needs one.

    1. Hana Ivers

      Happy to share notes. Drop by the Thursday meetup.

  4. Ivo Petrov

    I was at that council hearing. The room was packed.

    1. Emeka Lindqvist

      Good point, thanks for flagging it.

  5. Jonah Reyes

    Bookmarked. Sending this to my cousin who works in transit.

  6. Ravi Castellano

    Finally someone explains this without the hype.

  7. Hana Ivers

    The part about the maintenance backlog is the scariest thing I have read all week.

TRANSMIT_RESPONSE

Your email address will not be published. Required fields are marked *