SimpleRing
A dated 2003 capture documents webring administration, site-owner controls and automatic or manual acceptance. The historical copy itself is not reproduced.
- /main/scripts.html?script=SimpleRing
- /main/scripts.html?script=simplering
Section · historical reference
These entries record software formerly distributed by the original PerlCoders company. They exist because archived indexes and inbound links still point at the old catalogue URLs — not because there is anything to obtain.
Entries · 10
Five recovered entries now carry dated evidence. Older entries without documentation remain explicitly labelled as reconstructed rather than quietly upgraded into facts. Read the decision method.
A dated 2003 capture documents webring administration, site-owner controls and automatic or manual acceptance. The historical copy itself is not reproduced.
The former purpose is not documented. The name suggests an email autoresponder, but that remains a research lead rather than a product fact.
The former purpose is not documented. The name suggests an image rotator, but the page does not attribute generic image-script risks to this product.
The former purpose is not documented. The name suggests banner rotation and click counting; no implementation or product-specific risk is asserted.
We have a name and one legacy URL — which contains an encoded space — and nothing else. We would rather leave the purpose blank than guess at it.
HTML and plain-text newsletter management with headers, footers and multiple subscription categories, documented in a 2003 capture.
A daily gallery rotator that generated thumbnails and expected a cron job. The historical misspelling is preserved.
A MySQL-backed gift registry that prevented duplicate claims. No account, store, database or personal-data surface is restored.
A recursive crawler that followed page links and produced a URL list from a shell session.
A resumable checker that classified redirects, successes, forbidden responses and missing pages.
The old catalogue addressed everything through a query string. Each known
?script= value maps to exactly one Archive entry. An unrecognised value returns
404 — never the homepage, because a soft redirect to the front page tells a visitor their link
worked when it did not.
301 → the matching Archive entryscript= parameter301 → this page404 → with an Archive lookup on the error page410 Gone → permanently, with the reason stated
Reviewed decisions live in config/legacy-url-actions.json. Automated recovery QA
checks the matching API responses, built targets and the absence of a catch-all homepage redirect.
Documentation, a dated archive capture, or a screenshot with rights information would close any of them. Rights metadata is a hard requirement: without it we record the reference and do not display the image.