Sign inRegisterCheck connection

Entry URLs After a Weather Host Is Revived

A 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.

Back to Site history

When a personal-weather hostname comes back online, the first human problem is not DNS. It is the bookmark. Someone typed cumulus.tnetweather.com/lander years ago, or followed a forum credit that used that path, and they now arrive at a living site that is no longer the page they remembered. A lander is the honest answer to that arrival: a short orientation that says which host this is, where the organized archive lives, and why this particular URL was not silently folded into the homepage.

This article is about routing people after revival. It is not about a domain that lapsed and served a registrar warning. That failure mode, and why observation URLs still matter after it, belongs on the main-host preservation essay. Here the hostname is already restored. The question is how to greet an old inbound click without destroying the citation graph that made revival worthwhile.

Historical context

Hobby weather sites accumulated extra entry paths because the public web of the 2000s treated “home” as several objects at once. Shared-host control panels offered a default index. Station software uploaded a template named main or index.htm. PHP content managers added a lander, a splash, or a “you are here” script for visitors who arrived from a banner, a mesomap, or a WAP bookmark. Search engines and other operators copied whichever URL first returned 200.

The historical TNET Cumulus host was a software citation hostname: project pages, helpers, and realtime artifacts, distinct from the station site on tnetweather.com. That split is explained on the subdomain homepage. /lander sat beside that root as an arrival path, not as a second software catalog. The original splash, redirect script, or greeting page is not rehosted. What remains useful is the job the path still has: tell a human who followed an old bookmark how to read this host now.

Revival without a lander produces two equally bad defaults. The root becomes a catch-all and every old path is 301’d onto it. Or every old path is left as a stub that says nothing except “this URL existed.” The first destroys meaning. The second wastes the click.

Why a mass homepage 301 is the wrong revival

HTTP 301 Moved Permanently tells crawlers and browsers that the old identifier is gone and that the new identifier is the successor. That is correct for a renamed file, a trailing-slash alias, or an asset that truly moved. It is incorrect as a bulk policy for a restored weather host.

Paths were the citations. A wiki Toolbox note that pointed at a graph-pack URL, a forum post that cited /projects/..., and a mobile bookmark for /m were not three ways of saying “the homepage.” They named different objects: a helper, a file contract, a small-screen observation. Collapsing them onto / teaches search engines that those objects were always the same page. Later readers lose the ability to tell a software artifact from a station root.

A lander is not a successor of those objects. /lander can introduce the host and point at the Cumulus legacy hub without claiming to be the graph pack, the webcam pipeline, or the mobile deck. A homepage 301 claims succession. An entry article claims orientation.

Soft 404 disguised as home is also a failure. Serving the full root template at /lander with a 200 looks convenient and pollutes analytics, search snippets, and anyone who quoted the lander URL as a distinct resource. If the path is kept, it needs its own thesis. That is this page.

Temporary redirects are not a preservation strategy. A 302 from every unknown path to / hides breakage during a migration and then becomes permanent by neglect. Mapped content URLs on this restoration stay 200 with original articles. Unmapped junk stays unmapped. The lander is for humans who still have the lander bookmark, not a dumpster for every 404.

The Internet Archive stores snapshots of what a URL used to return. TNET is not the Internet Archive. Revival here means the identifier still resolves, and the body still matches the kind of thing the identifier was. /lander was an entry. It stays an entry.

What an entry URL should say after revival

A useful lander is short on nostalgia and specific about coordinates.

Which host you reached. cumulus.tnetweather.com is the historical Cumulus software host. It is not the main TNET weather-station site, and it is not a live logger dashboard. One sentence is enough. Repeat it whenever a visitor might have typed the other hostname by habit.

What this path was for. An arrival page, splash, or bookmark target—not a data file, not a project ZIP, not a forecast. If the recovered bytes were a thin stub or a copied chrome page, say that. Do not invent a vanished interactive tool.

Where the map is. The organized entry to Cumulus-side historical pages is the Cumulus hub. Site-history pages that explain preservation, credits, and continuity live under site history. Those hubs are the correct next click for a human who wanted “the TNET Cumulus site” and landed on a leftover path.

What not to expect. No live webcam. No working member login. No rehosted PHP packages with unclear rights. No claim that the modern team wrote the old templates. Modern TNET Weather is an independent connection-intelligence and weather-research service that restored identified URLs so backlinks lead somewhere honest.

How to read neighboring URLs. / on this host is the citation-host essay. /main on this host is the default Cumulus template (chrome plus a current-conditions slot). The main-host /main is the lapse-and-URL-preservation article. Three paths, three jobs. The lander’s job is to keep a visitor from flattening them.

Practical routing without lying

Operators who revive a hostname, and editors who restore a backlink footprint, can use the same rules.

  1. Keep path-specific URLs as path-specific articles when the path was a public content object. Do not 301 the catalog into the lander, and do not 301 the lander into the catalog.
  2. Use the lander for humans, the sitemap for machines. A person needs a paragraph and two hub links. A crawler needs stable 200 documents with distinct titles. Do not make the lander a doorway that noindexs itself while still serving as the only public explanation.
  3. Prefer one hop to a hub, not a chain of splash pages. /lander → Cumulus hub is a complete orientation. /lander → /main → / → a project index is a maze that looks like the old CMS.
  4. Label evidence types if the lander mentions weather at all. A lander that reprints “72°F” without time, units, and “historical or live” is doing station work it is not qualified for. Leave current conditions to the template page that owns that slot.
  5. Do not put a fake search box or a fake login on the lander. Those controls imply a live account system. Historical member and gallery logins become articles about access, not forms.
  6. Record the revival as metadata, not as a banner claim of ownership. “This hostname was restored so mapped backlinks resolve” is accurate. “We have always been this station” is not.

These rules are editorial, not a claim about the original operator’s intent. The original splash art, if any, is not reproduced here.

What changed, and what did not

What changed is the body. A 2000s lander might have been a graphic, a frameset, or a one-line PHP redirect. Those artifacts copy badly and teach nothing. Replacing them with an orientation article is the point of this rewrite.

What did not change is the inbound graph. Other sites and bookmarks still hold /lander as a string. Search engines treat a 301 to / as “this was always the homepage.” Keeping the path and writing a distinct arrival thesis respects those strings without pretending the old bytes were literature.

TNET research bridge

If you arrived here from an old Cumulus bookmark, start at the Cumulus legacy hub. That hub is the primary map for software, templates, and project pages on this host. Preservation and continuity pages sit in site history.

Modern TNET work is connection outlooks and public methodology, not a recreation of a 2000s splash screen. How the service works states how observed, modelled, and derived information are distinguished in that research. This lander does not estimate a Starlink interval. It only returns you to a catalog that still means Cumulus.

Sources