Contacting a Personal Weather Station Operator

When to contact a personal weather station operator about readings, siting, timestamps and broken pages—and why this historical form is closed.

Back to Site history

A contact form hanging off About is a mailbox with a station identity in front of it. At /aboutus/contactform on tnetweather.com, that mailbox belonged to the station website—the Mesa personal weather station host—not to the Cumulus software outpost. Visitors used it to reach whoever published the sensors and the public tools around them.

This article is about whom you would have been writing to, in each era, and why this URL is not a working form. There is no submit button here, no restored inbox, and no claim that mail to historical addresses still arrives. It is distinct from the dedicated contact page, which is about what a weather site should accept. It is also distinct from the same path on cumulus.tnetweather.com, which is about mailbox rot on a software host.

Historical context

Station sites needed a way for strangers to reach the publisher. The About section was the natural place: a reader who had just learned that the temperature came from a backyard in Mesa might want to ask about siting, a stuck timestamp, or a broken webcam. Putting the form next to identity said: this mail goes to the person named on the About page.

Recovered TNET Weather pages advertised a weather@ style address and, on other URLs, a mailing address for a historical Arizona firm. Those strings are historical clues. They are not current routing. Publishing them as live contact would send mail to a previous tenant, or to nobody.

The original interactive form is not rehosted. A restored submit control on a twenty-year-old path would collect messages under false pretenses. Preservation of the path is not restoration of the mailbox.

Modern TNET Weather restored this hostname so mapped backlinks remain useful. Restoration is not a claim that the current team is the historical operator, and it is not permission to harvest mail intended for someone else.

Same path, different host

The string /aboutus/contactform exists on two hostnames. They are not aliases.

| | This URL | Cumulus host | |---|---|---| | Host | tnetweather.com | cumulus.tnetweather.com | | Identity in front of the mailbox | Station website (Mesa PWS and tools) | Community software outpost | | Typical legitimate mail | Siting questions, stuck readings, webcam issues | Script credits, helper breakage, wiki citations | | This article’s job | Who the operator was, and that the form is dead | Why those endpoints rot and attract abuse |

If a wiki Toolbox note pointed at the Cumulus form, the writer was addressing a workshop. If a neighbor used this path, they were addressing a station publisher. Collapsing the two URLs would mix those audiences and those inboxes.

This page does not repeat the Cumulus article’s account of PHP mail() failure, SPF, copied skins posting to the wrong operator, or bot relays. That failure mode is real. It is documented on the other host. Here the thesis is identity: which operator, and which era.

Historical operator versus modern operator

Historical operator. The person or small firm that ran the Mesa logger and the public site. Recovered About copy described a private station and a development experiment in weather-related computing. That operator answered mail about sensors, outages, and the pages around them. When the domain lapsed, was sold, or was restored by someone else, that mailbox stopped being a valid scientific correspondence channel—even if the URL still resolved.

Modern operator. TNET Weather, an independent connection-intelligence and weather-research service. It is not SpaceX or Starlink. It is not the original station team. It holds the hostname so historical citations land on honest articles. Holding the hostname does not make TNET the addressee of 2008 siting questions, and it does not create a duty to answer mail sent to retired addresses.

If your question is “what is this site now?”, how the service works is the honest answer. If your question is “can I submit this form?”, the answer is no.

Do not write to this path expecting the person who logged Mesa observations, who wrote a 2009 template, or who once listed a Mesa street address. Do not write here expecting a live TNET support ticket either. Legacy contact URLs are documentation nodes. They are not a helpdesk.

What this URL will not do

  • It will not send mail.
  • It will not display a fake form “for historical accuracy.”
  • It will not harvest messages for a previous tenant.
  • It will not list a current personal inbox for the historical operator.
  • It will not replace weather.gov for warnings.
  • It will not be a login, a password recovery, or a membership gate.

A form that looks live after the mailbox is gone is worse than a 404. The visitor believes a message was sent. The publisher never sees it. Corrections stop. That is a quality-control failure dressed as a contact page.

About-form versus dedicated contact page

Hobby weather sites often grew two contact URLs by accident.

About-form. Nested under About because the CMS or the skin put “contact” next to “who we are.” The implied addressee is the identity on the About page. On this host, that identity was the station publisher. See the station-website About article.

Dedicated contact page. A top-level /contact.php that can state scope: what mail is for, what it is not for, and where emergencies go. That is a policy page. It is rewritten separately.

If you followed an old “contact us” link and landed here, you found the About-nested endpoint. Read it as “who,” then follow the dedicated page for “what.” Do not expect either URL to take a POST.

How to interpret an old contact bookmark

  1. Read the hostname first. tnetweather.com is the station site. cumulus.tnetweather.com is the software host. The path alone is not enough.
  2. Assume the mailbox is dead unless a current page, off this legacy URL, publishes a monitored channel.
  3. Do not send hazard reports here. Life-and-property weather goes to NWS and local emergency authorities.
  4. Do not send the historical operator’s mail to the current registrant and expect it to be forwarded. Domain restoration is not a mail-forwarding service.
  5. Treat unanswered historical questions as closed. A 2010 siting thread cannot be reopened through this path.

Operators who still run a living station should put a one-line retirement note on old contact URLs when they move: new channel, dated, and explicit that the old form does not post. Silence looks like a working form to a crawler.

Modern relevance

People still need to reach a data publisher. The mechanism that survives is a dated, monitored, clearly labeled channel on the current product—not an inherited About-form path. Research services and station operators who publish contact pages should treat them as part of the data path’s quality control, and should retire them in public when they stop being read.

TNET’s modern service is described on how the service works. That page is the primary next step if you arrived here hoping to reach the current operator about the research product. It states what TNET is and is not. It is not a mail form either, and that is the point: identity and method come before a mailbox.

TNET research bridge

Use how the service works as the entry to the current product. The site-history hub groups identity, contact, archive, and continuity pages on this host. The legacy hub maps the wider restored footprint. Provenance and source-quality language for public records are on data sources, quality controls, and methodology.

For frozen versus live pages after a site changes hands, see what “archived” means. For what a weather contact page should accept, see the dedicated contact article.

Sources