A weather site that titles a page “News” is making a choice. It can become a blog of storm color and weekend photos, or it can become a dated operations log: the sensor was swapped, the logger was down, the rain gauge was moved off the roof. At /news the historical TNET Weather station site kept that slot. This article takes the second job. Commentary about the sky belongs on observation pages. Chrome and template changes belong on site news. This URL is the station as an instrument over time.
The original interactive feed is not rehosted. There is no live ticker here, and there is no claim that modern TNET logged the historical Mesa hardware.
Historical context
Personal weather websites mixed three clocks and then labeled all of them news.
The atmosphere’s clock. A thunderstorm, a heat wave, a frost. That is weather. It should be labeled as observation or as a dated case study, with units and provenance.
The instrument’s clock. A Davis fan failed. The software was upgraded. FTP stopped for three days. That is operations. It explains gaps and spikes in the record.
The website’s clock. A new skin, a new menu, a counter script. That is publication. It explains why a screenshot from 2009 does not match a screenshot from 2011 even when the thermometer did not move.
Hobby operators often wrote all three into one blog because the template had one “News” include. Readers then could not tell whether “we were down Tuesday” meant the valley had no rain or the logger had no power. The scientific cost shows up years later, when someone treats a flatline as a drought.
Recovered TNET Weather pages used /news as a site-level slot next to privacy and sitemaps. The stub that later occupied this URL was not an operations log. Replacing it with a blog of monsoon color would steal the observation category’s job. Replacing it with a changelog of PHP files would steal /sitenews.php. The honest remainder is the instrument diary.
What an operations log is for
An operations log is metadata for the time series. It answers questions a later reader cannot get from the temperature column.
- When was the thermometer replaced, and did the new unit run beside the old one?
- When did the station move, even ten metres, and did the series keep the same ID?
- When was the site offline, so a gap is missingness rather than calm weather?
- When did units or software versions change?
- When was a known bias introduced (new pavement, a dryer vent, a shade tree removed)?
WMO observing practice treats station history as part of the measurement. Hobby networks implement a thinner version: a CWOP or Weather Underground metadata form, plus whatever the operator bothered to write on the website. The website note is often the only public sentence that a logger was in the garage for a week.
A useful entry is short and dated:
12 June 2009. Rain gauge relocated from roof to a 1 m mast, 4 m north of the previous mount. No overlap period. Expect a step change in catch.
That is not journalism. It is a flag on the series. Without the date, it is a rumor. Without the “no overlap” clause, a later analyst will invent a calibration they cannot see.
What station news is not
It is not a weather blog. “Beautiful sunset after the dust storm” is not operations. If the dust storm is the subject, it needs time, place, instruments, and a label as observation or as a historical case. Mixing lyric weather with a sensor swap trains readers to skip the only line that matters.
It is not a forecast. “Looks like a wet week” on a news page becomes a competing product. Forecasts belong on labeled forecast URLs, with the producer named (NWS, WXSIM, or another model). TNET Connection Outlook is a different, derived product on the modern site. It does not belong in a station operations log.
It is not /sitenews.php. That sibling URL is the place for website and software-chrome changes: a new template, a counter, a menu rename. A reader who wants to know why a screenshot’s header changed should not have to dig through anemometer notes. This page will not clone that changelog.
It is not a press room. Domain restoration, product launches, and independent-research framing belong on identity and method pages—the About article and how the service works. Putting “we are under new management” into a fake 2008 news list would be a false historical observation.
It is not current Mesa weather. Undated “station news” that still reads as a live bulletin is a trap. If an old item is quoted, it needs its original date and the word historical.
How to keep the log honest
- One date per entry, in the operator’s local civil date, plus time zone if the outage is short. “Tuesday” is not a date.
- Name the instrument, not the brand mood. “Anemometer bearings replaced” beats “upgraded our wind suite.”
- State missingness. “No rain data 03–05 August 2011 (logger power).” A gap without a reason will be filled by someone else’s imagination.
- Separate overlap from replacement. If two sensors ran together, say for how long. If they did not, say that the series has a break.
- Do not delete old entries. Strike or annotate. A vanished outage note is how a quality flag disappears.
- Do not use the log as a visitor-counter brag. Hit counts are not operations. See visitor counters.
If the station is dead, freeze the log and label it archived. The archived article is about that label. A news URL that still looks live after the logger is gone is a different kind of lie from a clearly frozen diary.
Reading an old /news link
Assume you have landed on a subject page, not on a feed. There is no restored item list from the Mesa station. Do not infer a sensor history that is not written here.
If you are reconstructing a historical series from files that once lived on this hostname:
- Prefer the observation files and their timestamps over any narrative.
- Treat a news note as a flag, not as a substitute for the file.
- Prefer official networks (NWS, NCEI, MADIS/CWOP) when the claim is climatological.
- Record that this URL is now an explanation of operations logs, not a diary of TNET’s current hardware.
Modern TNET Weather does not claim the original team’s maintenance record. Continuity is the subject—how a station should document itself—not the wrench that turned in 2009.
Modern relevance
Cloud dashboards still hide operations in “status” blogs and Twitter. The scientific need is unchanged: a later user of the series must know when the instrument was not the same instrument. A Starlink dish, a rooftop logger, and a research ingest all fail in ways that look like weather if nobody wrote the outage down.
TNET’s public research pages distinguish observed, modelled, and derived information. An operations log is how an operator helps the next person make that distinction for a station series. It does not disclose how any proprietary forecast is assembled. It does not turn a hobby diary into NCEI.
TNET research bridge
Gaps, sensor changes, and missingness are source-quality problems. TNET’s public statement of how records are treated as evidence is data sources, quality controls, and methodology. That page is the primary next step if you came here to understand why a dated outage note belongs next to a time series.
The legacy hub and site-history hub map identity, archive labels, and continuity pages. How the service works describes the modern research product, which is not this operations log and not a weather blog.
For website-chrome news rather than hardware, use site news. For identity of the station website, use About.