Sign inRegisterCheck connection

The Cumulus Host as a Community Software Outpost

The historical Cumulus host was a community software outpost: credits, independence, and why it was not the Mesa homepage or original-team continuity.

Back to Cumulus weather software guides

An About page on a personal weather site is an identity document. It answers who the host claimed to be, whom it served, and which names it refused to wear. At /aboutus on cumulus.tnetweather.com, that identity was a community software outpost: a public place for Cumulus helpers, file contracts, and credits. It was not the Mesa observation homepage on tnetweather.com, and it is not a claim that modern TNET Weather is the original station team.

This article is that identity note. The subdomain homepage explains the hostname as a citation host for software objects. This page explains the outpost: independence, credits, and the difference between a community workshop and a climate station.

Historical context

Steve Loft’s Cumulus, distributed through Sandaysoft as donationware, and the later Cumulus MX line, both sit in the same slot as Weather Display: read a logger, keep local files, optionally publish a website. Operators still needed PHP, graphs, banners, and parsers that the vendor did not ship. Community sites filled that gap. The Cumulus Wiki catalog of TNET Cumulus Scripts records that this hostname was cited as one such workshop (last checked 13 August 2026).

A workshop is not a weather station. The main TNET property mixed Mesa-area observations, Weather Display tooling, notebooks, and a cross-stack project index. Putting “about us” on the Cumulus hostname let an operator, a wiki editor, or a forum thread name the software outpost without landing on a temperature table. The original interactive credits screen is not rehosted. The URL still means identity, not a live dashboard.

Modern TNET Weather acquired the hostname as part of restoring a historical weather-site footprint. Restoration of the address is not resurrection of the original legal identity, not authorship of recovered PHP, and not a statement that the current research service logged the old Mesa observations.

What “community software outpost” meant

Three claims belong on an About page of this type. Mixing them is how hobby weather sites become unreadable.

It served operators, not a general public looking for a forecast office. Visitors came because they ran Cumulus, needed a helper that understood realtime.txt or web tags, or needed a URL that a wiki Toolbox entry could cite. The product was documentation and named tools. It was not a National Weather Service briefing. For warnings, use the National Weather Service or the national service with authority at the site.

It was first-party to this hostname and third-party to Cumulus. Sandaysoft and the MX maintainers define the station program. This outpost did not become Cumulus by hosting helpers. The Cumulus Wiki Software page and Cumulus MX on GitHub are the live software references (last checked 13 August 2026). TNET is not affiliated with Sandaysoft or with the MX maintainers.

It was a credit surface. An About page on a community PHP host is where template authors named Cumulus, JPGraph, GD, hosting, and other operators’ scripts. Credits are provenance. They are not a transfer of copyright to whoever later holds the domain.

Those three claims are why a software outpost needs its own About URL. A station About page would instead describe siting, elevation, and the logger. That is a different scientific object.

Credits without appropriation

A useful credit list on a Cumulus community site named the stack in the order a later reader needs it:

  1. The station program — Cumulus or Cumulus MX, with a version if the footer knew it.
  2. The template or skin — the HTML/PHP family that wrapped the tags.
  3. Named helpers — graphs, banners, parsers, notices, each with a project path.
  4. Libraries — GD, JpGraph, and any other third-party code the pages called.
  5. Upstream documentation — the Wiki, vendor notes, and other operators’ write-ups.

What a credit list must not do is collapse those lines into “TNET Weather made Cumulus” or “this domain owns the scripts.” Acquisition of a hostname does not transfer copyright in third-party libraries, in Cumulus itself, or in community packages whose licenses were never verified here. Where a living archive still offers a named script under its own notice, that archive is the place to look. This About page records the outpost role, not a download cabinet.

Independence runs the other way as well. The historical site was not an official Sandaysoft property, not an NWS page, and not a university department. Community weather PHP was volunteer engineering. Calling it a lab does not make the observations official.

Independence from the observation homepage

The Mesa-facing site and this Cumulus host shared a brand string and split the work. That split is identity, not trivia.

| Question | Observation homepage | Software outpost | |---|---|---| | What was measured? | A place, a siting, a logger | Not applicable | | What was published? | Readings, climate tables, webcams | Helpers, file contracts, credits | | Who is the audience? | People who want that station | Operators and citers of Cumulus files | | What does “about us” mean? | Who ran the sensors | Who maintained the workshop |

If you arrived here expecting current Mesa weather, you are on the wrong identity document. If you arrived here because a wiki or a forum named TNET Cumulus scripts, you are in the right building. The Cumulus-side projects map is the engineering index of what the workshop built. The About-section project narrative is why it built them. Neither page is a station climate record.

Modern TNET Weather is an independent connection-intelligence and weather-research service. It is not SpaceX or Starlink. It is not a continuation of the original operator’s legal person. The honest About sentence is: this URL keeps the outpost’s name in the citation graph and replaces a missing body with an original identity article.

What this About page is not

It is not a membership roster. Contributor identity as scientific provenance belongs on the memberships About pages, not here.

It is not a cookie policy, a contact form, or a login. Those paths keep their own jobs. This page does not simulate an account system.

It is not a software-version dump. Generator, template name, and last-updated as metadata belong on the website-info About page.

It is not a claim that every historical asset on the hostname was authored by one person, or that the current writers wrote the recovered PHP.

How to read an old “About us” link that lands here

  1. Treat the URL as an identity citation, not as a live staff directory.
  2. Separate the outpost from the station. Software credits are not siting metadata.
  3. Do not infer official status from a weather hostname. Hobby publishing is not a forecast office.
  4. Follow current upstream docs for software you still run (Wiki and MX GitHub; last checked 13 August 2026).
  5. Keep the path. Changing /aboutus into an unrelated product landing page would erase the identity the backlink expected.

Modern relevance

Operators still need a public sentence that says: this host is a workshop, these names are credits, this team is not the vendor, and these observations (if any) belong to a different URL. Raspberry Pi stations, MX JSON endpoints, and custom templates fail in new ways, but the identity problem is unchanged. A GitHub README that forgets to distinguish the logger from the dashboard helper repeats the same error this About page exists to prevent.

TNET does not operate this hostname as a Cumulus support desk and does not claim the original workshop’s authorship.

TNET research bridge

Identity is provenance: a later reader must know which host, which role, and which team boundary produced a page. TNET’s public account of how the modern service is framed—independent, evidence-aware, not a substitute for official warnings—is how the service works. That page is about the current research service. This page is about the historical outpost.

The Cumulus legacy hub collects related historical pages across both hosts.

Sources