Keeping dead beta sites as "archive sites"

Question

This is not a duplicate of Keeping closed sites in suspended animation: a modest proposal because the main point of that is to allow for a process in Area 51 to "reopen" a closed site, while this one merely asks for closed sites to remain alive and read-only, without a special procedure for "reopening".

When a beta site is closed, the questions that can be migrated are given to other sites. But what about the questions that aren't relevant on other sites?

Let's say you have a question, that was fairly high voted, and has an accepted answer. That question may be useful to someone else in the future, even if it will not be useful to as many people as a StackExchange site requires. If that question is deleted, than in the future, people who are searching for answers on a question that happened to be covered by a closed beta, will not be able to get it.

What I propose, is that when a beta site dies, instead of deleting it, it should be turned into an "archive site".

The archive site would basically be the same as the regular site, except there would be a big "Archive" at the top of the site (it would look just like the meta site, except with "archive" instead of "meta", and it would be colored even more gray), and it would be read-only. People would be able to view the questions and answers, but no one would be able add anything, or vote.

Also, I would suggest that Stack Exchange keep track of the traffic that comes into that site. If, for some reason, the topic of that dead beta become of interest to enough people, the site could be recreated.

Any questions, comments, suggestions?

Answer 1

I have to respectfully disagree with the arguments here.

The whole point of Google algorithm is to rank active and useful content higher than useless and low quality. So it is impossible that the site remains both dead and high in Google ranking at the same time. Either the site remains dead and people hardly find it on Google, or it remains useful and thus does make internet better.

I also cannot support the concern about "Sorry, that information can no longer be updated.":

• 99% of internet cannot be updated by users, yet they have no problem with that.

• It can be clearly and honestly stated that, in order to make the site live, people can go to Area 51 and push for it.

If the SE is really concerned about its brand "getting hurt", it can easily make the site look completely different. Even redirect to another domain, change colours, style, if that matters.

What makes internet really worse place is creating 404 dead pages. People who link to this site work hard on providing quality content to their readers and breaking their links is simply unfair to them and breaks their faith.

At least, it would be fair to state clearly and prominently on every page that the content can disappear any time, if that is the case.

In contrast, keeping links intact will give people faith in site's stability and support of their work, motivating them to work on site's revival, which is precisely what is needed for making internet better place, in my opinion.

On other hand, making the content hard to access will only turn people off. If fact, the more generous and active they were, the harder they worked for the site, the more turned off, disappointed, feeling betrayed they become. They will look for other forums and find them. So who remains then? Less active people who don't care and the majority who aren't even aware the site ever existed. I am sad to say it, but I just don't see how this can make internet better.

---

EDIT. Upon request by Dan Dascalescu adding his comment:

Another aspect is that users are now well-used to archived content. Reddit archives threads older than 6 months, and the vast majority of content on Reddit is exactly like that; archived, impossible to modify, but not deleted - because it's very useful, and the downside of being unable to upvote that Reddit comment, it far smaller than the upside of being able to read it in the first place.

Answer 2

There are some substantial unintended side-effects that would make this somewhat undesirable.

It doesn't make the Internet better

We have a very ambitious company goal: "Make the Internet a better place to get expert answers to your questions." Even the content worth saving has pretty much peaked at the time the site was closed. It will never be updated or improved, ever. Users trying to correct the information will be met with "Sorry, that information can no longer be updated." Users seeking help will be met with "Sorry, this site is closed." A wasteland ghost town does not make for a pleasant end-user experience.

It hurts the network

Long after the site has been closed, remember, Google search will continue drawing people into this outdated legacy content… and those potential users aren't going to understand the history and nuance of an "archived" site. Their first experience will be a sad little place where content hasn't been added or updated in recent memory. The apparently neglect will detract irreparably from the sites that work hard to keep their content of high quality and up to date. A bad first impression is really hard to recover from.

The Poison Pill

Once you lock in a failed site, that's a pretty big head-on-a-stick gesture for future audiences. Let's say someone wants to start an AI site again — it will happen; our network is only getting bigger — that's a pretty dire legacy to overcome. "That didn't work and we could never do that again." Don't lock in failure.

Answer 3

This would be excellent. While closed off betas already have a data dump, it would be much easier if we could still use the SE engine for accessing it. Specifically, searching and navigating through the data would be much easier through the SE engine rather than XML files from the data dump.

Answer 4

If you are not after the official, reference-quality resource, you can do this yourself. I wrote a tiny Lua/shell script to regenerate the meta for the failed Freelancers site:

https://github.com/chalst/sxdatadump2lua

giving the output seen at

http://www.textproof.com/ar/freelancers-meta/

I like the approach in my code, but since other hackers probably will not, I note that it's pretty easy to put together your own code. Remember the data dumps have a licensing requirement to link back to the site.