Sigh. Standard disclaimer: nothing I write here has got anything to do with my job, I'm not representing my employer in any way. I cannot talk about anything I know personally. I've also never worked on any of these projects. However, I can read, describe, and link to public material on the internet like anybody else.
In all honesty, I have no interest in the news archive projects; I read an HN link, followed some of the links in it, and said "this isn't what I was promised on the previous page". It sounds like you just made a second attempt at writing the article. I suggest you take the original one down and put this one up instead; it stands up to at least the completely superficial fact-checking of reading the links in it, which makes it a significant improvement - although it now appears to be a list of fairly straightforward bug reports. (I like bug reports. Bug reports are actionable.)
Engaging with the subject would require substantially more effort on my part to research and investigate what's going on here, because I don't know anything about it beyond what I read in links here. I'm not going to do that. However, I would encourage anybody with an interest in this subject to do the research and write up their findings.
Saying that these problems look like bug reports is dismissive of the depth of the problems. Stopping development of products and removing access to features isn't unintentional, and a lot of people have already complained about each of these problems over the years. Andy's article is making a larger point that what has happened to these products is part of a pattern, that Google is not being as responsible in stewarding its information as its mission statement said it would try to be.
> Saying that these problems look like bug reports is dismissive of the depth of the problems.
Personally I completely disagree with your priorities. I think a bug report is far more valuable, since people can act on bug reports and make things better, while I would not anticipate any meaningful action as a result of speculation about mission statements.
That makes me wonder why the Chromium bugtracker appears to effectively be a black hole, if the bug reports are so "valuable". I don't think I've ever gotten a single response to my CSS calculation bug report.
In all honesty, I have no interest in the news archive projects; I read an HN link, followed some of the links in it, and said "this isn't what I was promised on the previous page". It sounds like you just made a second attempt at writing the article. I suggest you take the original one down and put this one up instead; it stands up to at least the completely superficial fact-checking of reading the links in it, which makes it a significant improvement - although it now appears to be a list of fairly straightforward bug reports. (I like bug reports. Bug reports are actionable.)
Engaging with the subject would require substantially more effort on my part to research and investigate what's going on here, because I don't know anything about it beyond what I read in links here. I'm not going to do that. However, I would encourage anybody with an interest in this subject to do the research and write up their findings.