Well it's not something setup to just "go away". It's simply a place to archive and showcase.
Yes, that's exactly it, the Internet, like radio itself, evolves...the old gets pushed aside, the new, more functional comes on the scene, finds favor for a bit, then too takes it's own place at be back of the bus. Nothing wrong with that, it's just the natural order of things.
Some time ago, the AM Window was the focus, then came AM Fone, just wait, the next incarnation will be up around the corner. It's really not so important exactly what that new form is, but I rather think the key thing is to not just read and then discard information, but rather as John puts it, to "archive and showcase", allowing it to serve as a reference to those looking back. That is one thing I greatly appreciate about the AM Window, that Steve kept it up so we could all look back...
As one deeply interested in radio history, websites like the AM Window, AM Fone, and yes even the humble AM Buffalo have become the Radio News, Short Wave Craft and QST of our day. Like its paper counterparts, this electronic media is volatile, not so much by dust or damp, but rather by neglect. While our own individual archives may be far too disparate to effectively search 25, 30 or 50 years in the future, a mirror of the AM Window and AM Fone sites will not.
In due time AM Fone will too be eclipsed by the next greatest thing, it may be Facebook, or something we haven't even heard of yet...the only constant is change. The key thing, in this ham's view, is to archive the material, so even when the "next great thing" comes along, we can all look back on where we've been. That is going to be the great challenge for the current group entrusted with this page, they too will be replaced or move aside in due time, again the only constant - change, the prime challenge is to keep the fundamental knowledgebase we've created intact. I see AM Fone as a tremendous reference, a Encyclopedia of sorts, a brain trust for a specific slice of the amateur radio community, and each and every one of us is a stakeholder in that knowledgebase.
