History of the TNET Weather Station Website

History of the original Mesa TNET Weather station website, its observations and publishing tools, and the independent service using the domain today.

Back to Site history

An About page on a weather hostname is supposed to say what the site is. At /aboutus.php the historical TNET Weather property was a station website: a Mesa, Arizona personal weather station (PWS) with public tools around it—live pages, lightning and webcam slots, maps, alerts, and climate tables. It was not a National Weather Service office, and it was not the Cumulus software outpost on cumulus.tnetweather.com.

This article is that identity note for the main host. Continuity here is continuity of subject: observations, station publishing, and weather software. It is not continuity of company, staff, or legal person. Modern TNET Weather is an independent connection-intelligence and weather-research service that restored this hostname. It is not the original station team.

Historical context

Hobby weather sites in the 2000s were often one backyard logger plus a domain. The operator ran Weather Display or similar software, uploaded HTML and data files, and treated the website as the public instrument. Neighbors used it for a local temperature. Other operators used it for scripts, parsers, and examples. Search engines treated /aboutus.php as the identity document.

Recovered material for this URL described a private Mesa station, on the western side of the city near the Tempe border, offered as a public-facing experiment in weather-related computing. Those details identify the historical subject. They are not a live siting sheet for anything TNET operates today, and they are not reprinted here as current coordinates, mail, or staff.

The original About body is not rehosted. Domain acquisition does not transfer copyright in old prose, images, or PHP. It also does not transfer the original operator’s identity. The useful replacement is an original article that still answers the question an inbound About link expected: what kind of site was this?

What a station website is

A station website is a publication of a place.

It has a location. Latitude, longitude, elevation, and a plain-language neighborhood are metadata for the thermometer, not decoration. Without them, a temperature is an unattached number.

It has instruments. Temperature, humidity, pressure, rain, wind, and optional extras (lightning, webcam, soil) are the payload. The About page should name the role of those instruments without pretending the backyard is a Weather Forecast Office.

It has software. Weather Display, later Cumulus, FTP or HTTP upload, and PHP templates were how the logger became a URL. The tools were part of the site’s identity because other people cited them.

It has a clock. “Last updated” is part of the observation. An About page that never mentions freshness invites readers to treat a stale dashboard as now.

It is not official. NWS Phoenix (Weather Forecast Office PSR) issues forecasts and warnings for the county warning area that includes Mesa. A PWS can link those products. It does not become them by being local. For current warnings, use weather.gov or the Phoenix office (last checked 13 August 2026).

Those five claims belong on a station About page. Mixing them with “we sell hosting,” “we are Cumulus,” or “we are the same people who logged 2005” is how identity documents become false.

Station host versus software outpost

The main hostname and the Cumulus hostname shared a brand string and split the work.

| Question | Station website (tnetweather.com) | Software outpost (cumulus.tnetweather.com) | |---|---|---| | What was measured? | A Mesa-area siting and logger | Not the job of that host | | What was published? | Readings, climate tables, webcams, station tools | Helpers, file contracts, credits | | Who is the audience? | People who wanted that station, plus operators borrowing tools | Operators and citers of Cumulus files | | What does “about us” mean? | Who published the sensors and the station site | Who maintained the workshop |

If you arrived here expecting a Cumulus credit list, you are on the wrong identity document. If you arrived here because a forum, a template comment, or a search result named TNET Weather as a Mesa station site, you are in the right building.

The Cumulus-side About page is a different URL on a different host. This page does not clone it. The software outpost explained independence from the vendor and listed credits. This page explains the station website: a place, a logger, and the public tools that sat around that logger.

Revival is not resurrection of a team

TNET Weather acquired tnetweather.com as part of restoring a historical weather-site footprint so mapped backlinks lead somewhere honest. Restoration of the address is not:

  • resurrection of the original legal identity;
  • a claim that the current writers authored recovered PHP, templates, or images;
  • a claim that the current service logged the historical Mesa observations;
  • a live recreation of the old dashboard.

What is continuous is the subject matter. Both eras concern weather data, observation quality, software tooling, and practical interpretation. That is a legitimate bridge. “We have always been this station” is not.

The modern property is an active TNET Weather site. It is independent of SpaceX and Starlink. It is not an NWS product. Identity on an About page has to say those sentences in that order: historical station site, restored hostname, independent research service, no original-team claim.

A later reader who finds “TNET Weather” in a 2008 template comment and “TNET Weather” on this domain in 2026 is looking at a brand string that survived a change of operator. Brand strings are not provenance. Observer identity, station ID, and file date are provenance. The About page’s job is to keep those layers from collapsing.

What this About page is not

It is not a working staff directory. Names and mailboxes from recovered pages are historical clues, not current inboxes.

It is not a contact form. The About-section contact URL and the dedicated contact page have their own jobs. This page does not simulate a mailbox.

It is not a live siting or equipment advertisement. Hardware changes. An undated “we run X in Mesa” sentence would be a false observation.

It is not a cookie policy, a visitor counter, or a news blog. Those paths stay distinct.

It is not a claim of official status. A weather hostname is not a forecast office.

It is not an archive index. Frozen pages and dated observations are explained on the archived article. This page is identity, not a freezer label.

How to read an old About link that lands here

  1. Treat the URL as a station-site identity citation, not as a live personnel roster.
  2. Separate the station from the software outpost. Mesa observations and Cumulus helpers were related subjects on related hosts, not the same page.
  3. Do not infer that modern TNET logged the old series. Hostname continuity is not observer continuity.
  4. Do not treat recovered temperatures or coordinates as current. Historical siting is context for the old site, not today’s weather.
  5. Keep the path. Changing /aboutus.php into an unrelated product landing page would erase the identity the backlink expected.

If you still run a station website, the same checklist applies in reverse. Publish a short identity paragraph that names the place, the software family, and the fact that you are not the national meteorological service. When the domain changes hands, that paragraph has to be rewritten, not inherited.

Modern relevance

Operators still need a public sentence that says: this is a station website or it is not; these observations have a place and a clock; this host is not the warning service; this revival is not the original staff. Raspberry Pi loggers and cloud dashboards fail in new ways, but the identity problem is unchanged. A GitHub README that forgets to distinguish the backyard from the vendor repeats the same error.

Readers who followed an old TNET Weather link are often looking for one of three things: a Mesa observation, a weather-software artifact, or whatever now lives at the domain. This page answers the third without lying about the first two. Observations belong on labeled observation pages. Software belongs on software pages. Identity belongs here. Hardware and outage notes belong in an operations log, not in About.

TNET research bridge

The organized map of preservation, credits, and continuity pages is the site-history hub. That hub is the primary next step if you arrived via an old About link and need the rest of the station-site story rather than a product pitch.

The legacy hub is the entry to the wider restored footprint. How the service works states what modern TNET Weather actually is—an independent research service, not a WFO and not the original team. Public notes on source identity sit in data sources, quality controls, and methodology.

Sources