On a personal weather network, a “member” is someone who ran a sensor, a logger, or a publishing stack—not someone who joined a social club. The word looks like a forum rank. Scientifically it is a contributor role: who produced the observation, under what siting, with what software. At /aboutus.memberships the historical Cumulus host kept that About-section idea next to credits and projects.
This article is the network-role essay. It is distinct from the membership-list article, which treats published name lists as citation instruments for template credits. This page does not invent a member count, does not restore logins, and does not claim that modern TNET Weather is a continuation of any historical roster.
Historical context
Hobby weather sites of that period often showed a Members, Neighbors, or Network page: other stations the operator traded links with, people who used the same PHP skin, or contributors to a regional mesonet-style map. Cumulus operators also appeared as names on the Cumulus Wiki and in forum threads about files and helpers (last checked 13 August 2026). The social texture was real. The scientific content was who is responsible for which instrument.
Official observing networks already treat observer identity as metadata. NOAA’s Cooperative Observer Program exists because volunteer stations are usable only when the observer, the siting, and the record can be named (last checked 13 August 2026). WMO guidance on instruments and methods likewise treats station metadata—location, exposure, instrumentation—as part of the observation, not as optional biography. A PWS “memberships” page is a rough, unofficial cousin of that habit. It is not a WMO station catalogue and it is not an NWS product.
The original roster, if one existed at this URL, is not rehosted. Republishing a recovered list of personal names and emails without a clear right to do so would be a privacy error as well as a copyright error. What can be taught is the role.
What “member” meant on a PWS network
Strip the word down to contributions that later users of the data still need.
Sensor operator. A person (or household) who sited a thermometer, a rain gauge, a vane, or a logger and kept it running. The observation belongs to that siting. “Member since 2009” is not a climate statistic; “this Davis/Fine Offset/other logger at this exposure” is.
Publishing operator. Someone who kept Cumulus (or Weather Display) writing files and a web host serving them. A silent FTP failure makes a live page look like still air. The publisher is part of the data path even when they did not install the mast.
Software contributor. Someone who wrote or adapted a helper that other stations used: a graph pack, a banner, a parser. Their membership in the community is real, but it is not membership in the atmosphere. Crediting them as authors of a tool is correct. Listing them as if they measured your backyard is not.
Linker or neighbor. Reciprocal links among PWS sites were common. A neighbor list is a graph of websites. It becomes scientific only when each node still carries siting and software metadata. A dead link with a first name is not a station.
These roles can coincide in one person. They must still be labeled separately when a later reader reuses a number. A temperature copied from a neighbor’s realtime.txt is observed at the neighbor’s site, not at yours. A graph drawn by a shared PHP pack is derived visualization of whatever series it was fed.
Provenance: who ran the sensors
Provenance is the chain from air to published number. A memberships page is useful only if it strengthens that chain.
Minimum identity for a contributing station:
- a stable station name or identifier;
- location at a precision the operator was willing to publish (often town and elevation, not a street address);
- logger or sensor family, if known;
- station software and a version when the footer provided one;
- native units;
- a time zone or a statement that stamps are local or UTC;
- a contact or credit line that is not a live password form.
Without those fields, “member” is a caption. With them, a later notebook can say: this series came from that operator’s siting, through that program, in those units. That is the same discipline official networks encode in station metadata, at hobby resolution.
What a memberships essay must not do:
- invent how many people “joined”;
- treat a forum handle as a calibrated instrument;
- imply that networked PWS sites were quality-controlled as a single mesonet unless a documented program said so;
- turn neighbor temperature into your station’s observation.
Exposure errors do not become smaller because a site had a Members menu. A thermometer over asphalt is still a biased thermometer. Membership is identity, not a correction factor.
Not a social club
Club language—join, friends, profile, login—was often just CMS chrome. Saratoga-style and other PHP weather templates reused membership vocabulary for pages that were really credits, neighbor maps, or optional mail forms. Reading that chrome as a living social network in 2026 would be a category error.
This URL is not a sign-up. There is no restored member area. Modern TNET Weather accounts, where they exist for forecasts and speed tests, are a different system on a different product. Do not treat a historical About-section memberships path as a password recovery page.
The outpost identity article states the host’s independence from the original team and from official services. Contributor roles sit under that independence: naming who ran a sensor is not a claim that TNET employed them or that the current service inherits their observations.
How to use an old memberships link
- Ask which role the page meant. Sensor, publisher, software author, or linker.
- Look for siting and software, not for a headcount.
- Keep personal data off the new page unless you have a lawful, necessary reason to republish a name. A role essay does not need a scraped roster.
- Cite the station files (
realtime.txt,dayfile.txt, logs) as the observation objects. Cite people as operators of those objects. - For warnings and official climate, use NWS and NCEI, not a hobby neighbor list.
If you still run a network of stations, publish a machine-readable station table with the fields above. A pretty Members grid without metadata is a club page pretending to be a network.
Modern relevance
Distributed sensors are more common now, not less: school yards, farms, Raspberry Pi loggers, MX instances pushing JSON. The memberships problem is unchanged. A map pin without an operator, a siting note, and a software name is decoration. Connection-intelligence research that consumes weather fields has the same need: know the source, not just the value.
TNET does not claim the historical roster and does not operate this URL as a community directory.
TNET research bridge
Who produced a record, in which units, with what freshness, is source identity. TNET’s public statement of that discipline for research records is data sources, quality controls, and methodology. It does not list historical PWS members. The Cumulus legacy hub collects related pages on this host.
Sources
- NOAA NWS: Cooperative Observer Program (last checked 13 August 2026)
- NOAA National Centers for Environmental Information
- Cumulus Wiki: Software (last checked 13 August 2026)
- National Weather Service