ArchiveSCVAll collections
SCV Talk · Archive

About this archive

Where this archive has been wrong, it says so on the Corrections page.

What this is, and why

SCV Talk was Santa Clarita’s pioneering community blog. From 2006 to 2015 it ran daily briefs, covered the development fights and the council meetings, and hosted an argument that 1,555 display names take part in across the recovered threads. It was written by a small group and read by a valley.

Then it went. Two database compromises destroyed material at the source, a hosting shutdown ended one platform, and the last one simply stopped. By the time anyone thought to look for it, most of SCV Talk existed only as irregular snapshots in the Internet Archive.

This is the surviving publication reassembled into a reading edition: recovered from Wayback Machine and Common Crawl captures, extracted from five platform eras, and presented in chronological order. The goal is findability of what remains. Researchers of the valley’s politics and development history can search the recovered posts and the surviving comment threads; they must also consult the documented gaps on the What is missing page, because absence here records capture failure, not original silence.

The five eras

The version numbers are the site’s own. A 2012 comment gives the dating first-hand: “SCVTalk.com/oldsite was version 1 from March 2006 to about mid 2007. SCVTalk.com/v2a was version 2 was from 2007 to September 2009, when the site was hacked.”

The fourth era needs its own sentence. When the 2012 hack and the hosting shutdown ended the WordPress years, the site moved to Blogger and, for a while, changed its name: it ran first at www.scvtalk.com and then at notesfromnewhall.com as Notes from Newhall. The banner never let go of the lineage though — it read “aka SCVTalk.com v 4.0”. Same publication, same writer, a different masthead while the ground was unsteady.

Two hacks, in the site’s own words

September 2009 — Jeff, under the headline “Whoa! This isn’t the SCVTalk I know and love (hate)”: “it looks like the hack actually penetrated the database of the old SCVTalk, meaning all 799 posts, 10,000+ comments were affected.”

August 2012 — Rider, “And we’re back”: “SCVTalk and the WordPress blog engine it ran on, has been hacked twice in the last four years. In 2009, the hack was so complete that it forced me to rebuild the site completely. Earlier this year it appears the site was hacked again, despite my best efforts.”

The 2009 compromise, not the Internet Archive’s coverage, is the likeliest reason the 2006–2007 record is thin: much of it was destroyed at the source before any later crawl could reach it.

The arc

When Jeff started in 2006, he wrote that he was thrilled when a post drew twenty readers and a comment. Signing off in 2011 he put numbers to the rest of it: “And that’s a wrap!” — from “those lonely days in 2006 when I only had 2 or 3 hits a week” to peaks of “nearly 1,000 daily visitors”, and 781,000 unique visitors across five and a half years. With the audience came pressure. Some of it was technical: running a community site in the era when you had to guess which platform would survive, staying ahead of hackers when WordPress was still young. Some of it was personal: as the site’s reporting cut closer, the pushback found its way past the comment box. That the site kept publishing through all of it — two hacks, five platform eras, nine years — is part of the record this archive preserves. Most blogs of its generation didn’t survive one of those hurdles. SCV Talk cleared them for a decade.

The last words

The site’s last sustained voice was Josh Premako’s, whose 29 May 2015 sign-off closed the santaclarita.com era:

I regret to inform you that today marks the end of the Daily Brief. It has been a good run, and I’m sure we’ll see each other on the social medias. Or perhaps even in real life. Josh Premako, 29 May 2015

Jeff hinted more than once afterward that SCV Talk might return; it never quite did. There was one last flicker: in September 2015, a post appeared — “You say river, I say wash” — and a few longtime commenters turned up in the thread within hours, as if they’d never left.

Whoa! Look who’s back! Yippyiyay! Yeah, its a river! Just wait until El Nino hits and see what they call it! Spineflower, 11 September 2015

It was a false alarm. Five days later a reader named Mike worked out what had happened — “This was a never-published post from May 2013” — and Spineflower had the last word in the archive, one syllable long: “Damn”. A decade of the valley talking to itself, ending on a draft that escaped by accident and a reader’s disappointment. Which is how town squares end, when they end.

Sources and method

Pages were recovered from Internet Archive Wayback Machine captures, supplemented by Common Crawl where Wayback had gaps, and by the Blogger Atom feeds for the 4.0 era. Nothing was taken from the live web.

Every post was extracted from its capture into a single reading template: site furniture, navigation and advertising removed, images localised, dead embeds turned back into links. Each post links the underlying capture, so any page here can be checked against the original.

The metadata is downloadable. A data directory publishes one manifest per year, as JSON and CSV: title, date, author as published, platform era, the page’s URL here, its original URL, and the capture it was recovered from. A companion manifest lists the articles the record proves existed and the archive does not hold. The field list carries a schema version, so work that cites these files can say which shape it read.

The manifests are post-level only. The archive publishes no comment-level or per-commenter export: a downloadable compilation of one person’s complete speech is a different object from a page they can be found on, and the archive does not make it.

Every published file is checksummed. Each build writes a fixity manifest — a SHA-256 digest, byte count and path for every post, author page, chrome page and recovered image — alongside a plain SHA256SUMS file that sha256sum -c reads directly. It is there so that any copy of this archive, made by anyone, can be checked against what we published: if the digests match, the bytes are the bytes. The build refuses to publish a manifest that does not describe the files it shipped.

Editorial policy

Presentation is standardised; content is unaltered. Spelling, grammar, formatting quirks and factual errors are left exactly as published. Where a title was too generic to identify — a bare “Daily Brief” — the post’s own date is appended; the published title is kept in the metadata.

Bylines appear as published. Where a writer used several handles and was publicly known here by their own name, the name is shown with the handle: “By admin — Jeff Wilson”.

Authorship the archive supplies is marked as such. Some posts ran with no byline at all. Where the archive attributes one anyway it says so, in italic, and only on evidence: posts published before the first guest writer joined in March 2007, and PHP-Nuke daily briefs in a format the record shows was Jeff’s. Everything else stays unattributed, because the archive does not know.

Pseudonymous writers stay pseudonymous. Several contributors wrote under pen names, and some of those are the only name this archive holds. It records no identity its author did not publish, at the cost of findability. Where a writer authorised the connection between their names, it is shown.

Comments are readable but not searchable, and carry display names only — no addresses, no URLs, no IP data, even where the captures hold them.

Timestamps are shown as the source recorded them. Where only a date survives, only a date is shown; nothing is inferred to fill a gap.

A small number of link-farm spam comments — currently 90 — are withheld from display; the records are retained. Every withheld username was read and confirmed by the editor; no comment is withheld by automated detection alone. Where one comment was captured twice, the archive shows it once. Where somebody posted the same thing twice minutes apart, both stay, because that is what happened.

How to read absence

Absence from this archive is evidence of capture gaps, not absence from the site. This is a record of what survived, not a record of what was published.

The practical consequence matters most for any view of a single person. If a writer or commenter appears in some years and not others, that pattern reflects which pages were captured — not when they were active. No list here should be read as a complete account of anyone’s participation.

A full accounting of what did not survive, including hundreds of articles we can name but cannot show, is on the What is missing page — along with how to help fill the gaps.

Custodianship and contact

A note on the domain: SCVTalk.com itself later came up for sale, and the archive’s editor bought it — not to revive the site, but to keep its name from passing to someone with no stake in its history. It now points here.

The archive is maintained by SCV Talk. Contact addresses from the original site are long defunct and have been removed; correspondence should go to the archive’s own address.

Generated August 17, 2026, 10:03 PM PT. Counts, coverage and dating change with each rebuild as recovery continues.

This archive is maintained by SCV Talk · Support this work

Support