Site history
History of the original TNET Weather station website, including its operations, archived pages, privacy, credits, sitemaps and visitor tools.
- Entry URLs After a Weather Host Is RevivedA revived weather host still needs an entry URL: route old bookmarks to the Cumulus hub without a mass homepage 301 that erases path-specific citations.
- The Cumulus Default Template: Chrome Around Current ConditionsCumulus main was the default template: site chrome around a current-conditions slot bound to logger tags, not a parked-domain page or the subdomain root.
- History of the TNET Weather Station WebsiteHistory of the original Mesa TNET Weather station website, its observations and publishing tools, and the independent service using the domain today.
- Contacting a Personal Weather Station OperatorWhen to contact a personal weather station operator about readings, siting, timestamps and broken pages—and why this historical form is closed.
- What Archived Means on a Weather WebsiteArchived on a weather site means frozen pages and dated observations, labeled so they cannot be read as live. How to mark archived versus current.
- What a Weather Site Contact Page Should AcceptA dedicated weather contact page is for data errors and site issues, not emergencies. Direct hazards to the National Weather Service, not to a PWS form.
- When a Personal Weather Site Lapses, Historical URLs Still MatterWhen a personal weather site lapses, observation URLs and software citations break. Why those historical addresses still matter, and how TNET preserves the subject.
- Station-Site News as an Operations LogStation-site news is a dated operations log: sensor swaps, outages, siting moves. It is not a weather blog, and it is not the website-changelog page.
- Privacy on a Personal Weather Station WebsitePrivacy on a PWS is operational, not a shop policy: server IPs, webcam neighbors, and preference cookies. This is not legal advice and not a cookie-policy page.
- Mapping a Weather Site by Observations, Tools, and AboutA human sitemap is a scientific catalog of a weather site: observations, tools, and about pages. How to read that map without mixing evidence families.
- Auto-Published Station News from Weather DisplayWeather Display whatsnew auto-published station notices. Why that changelog is operations metadata, not an observation, and not the /news ops log.
- How Weather-Site Hit Counters Were Built and Why They LieHit counters used images and log files that leak visitor data and inflate counts. How they were implemented, why they lie, and why they are not science.
- Last Upload Time as Station Quality ControlStation status is last-upload time and logger health, used as stale-data quality control. This URL is not a live monitor or a fake dashboard.
- Crediting Software, Templates, and Data on a Personal Weather SiteA PWS credits page is citation practice for software, templates, and data sources. Distinct from About, and required for honest observation provenance.
- Template-Generated Sitemaps and Why a Station Had Two MapsTWS-prefixed HTML sitemaps were generated from station templates, not written by hand. Why a weather site kept both a curated map and a machine list.
- Wrapping Station Notices in a TWS Site-News TemplateTWS site-news was a PHP template that wrapped station notices from a text file. Distinct from the WD whatsnew page and from the editorial /news log.
- Visitor Counters Are Not a Scientific MetricHit counters and visitor maps on a PWS measure fetches, not climate quality. Use logs as access provenance; do not treat vanity totals as evidence.