今后会继续为大家及时提供最新预览版信息。
网页原文：
Checking out
When I started up BuildFeed over five years ago, I never expected it to grow as large and as widely used as it has been. I've not been involved in the day to day running of BuildFeed for over two years now. I left that in the hands of a few trustworthy friends, and I and the users of the site owe a debt of gratitude to these men. Without them, this day would have arrived some time ago.
You've probably noticed some funky build strings pop up on BuildFeed lately. That's because a Microsoft employee posted them on BuildFeed. For those interested parties, don't bother coming to me. I have no IP logs, I have no "inside" insight as to what our mutual friend has been up to. Could you find out who it is? Sure, just look on Twitter and see who was posting build tags ahead of BuildFeed. He's not been remotely discreet and he handed out the strings to plenty of others before BuildFeed accepted them.
The long term future of BuildFeed has been in doubt for some time, but events over the past few days have resolved things in my mind. Given extensive internal pressures and external pressures (and yes, Microsoft is one of those relentless and ever-present external pressures), I have found myself unable to commit to running BuildFeed on the principles it was founded upon. In light of this, I have made the decision to terminate BuildFeed with immediate effect. The truth is that were it not for my failings, this day would not have come; and were it not for the persistent activities by third parties to force us offline, this day would not have come either.
The good-ish news for you is that what Tom giveth, Tom cannot always take away. You have the source code, safe on GitLab. Additionally, since many people have contributed to the database of build strings over the years, I'd feel a bit ashamed to take that away, so here's that database dumped into a JSON file. I would encourage anyone to take up the challenge and continue the desire I had those many years ago, to establish a truly authoritive build list.
- Thomas Hounsell
Addendum #1
Naturally, once the journalists have got ahold of the story, there's been some creative interpretations of my notice. Here's a few points I would wish to clarify...
Microsoft has not and has never issued a Cease & Desist to BuildFeed. They have never explicitly asked that the website has been taken down. They have never (directly) asked me to disclose the sources for the site. They have played their hand far too well to stoop to such messy and clumsy tactics.
The timing of this closure has everything to do with the internal pressures I mentioned and nothing to do with the external pressures such as Microsoft. Were Microsoft not placing any pressure on BuildFeed, I doubt there'd be an issue, but it's also true that had I not made some mistakes in the past, there would be little to no internal pressures and we wouldn't be looking to close either.
Indeed, ultimately, the internal pressures are ultimately the deciding factor. Those of you that know me, know that I am not one to merely accept someone elses' orders, even if they are from a large multinational corporation. However, it has for a while been a question of "When" rather than "If" for BuildFeed's closure, and I'll admit that this incident merely brought things to a head. In the end, I felt it better to jump rather than be pushed, and get ahead of things before external factors started making decisions for me.
翻译：（机翻）
退房
当我在五年前开始构建feed时，我从来没有想过它会像以前那样大，并且被广泛使用。我已经两年多没有参与BuildFeed的日常运行了。我把这件事交给了几个值得信赖的朋友，我和网站的用户欠这些人一笔人情债。没有他们，这一天早就到了。
您可能注意到最近在buildfeed上弹出了一些奇怪的构建字符串。这是因为一位微软员工在buildfeed上发布了它们。对于那些有兴趣的人，别费心来找我。我没有IP日志，我对我们共同的朋友的所作所为没有“内部”洞察力。你能知道是谁吗？当然，只要看看Twitter，看看谁在buildfeed之前发布了构建标签。他并不谨慎，在buildfeed接受之前，他把弦交给了很多其他人。
buildfeed的长期前景一直存在疑问，但过去几天发生的事件已经解决了我心中的问题。考虑到广泛的内部压力和外部压力（是的，微软是其中一个持续存在的外部压力），我发现自己无法承诺按照其建立的原则运行buildfeed。鉴于此，我决定立即终止BuildFeed。事实上，如果不是因为我的失败，这一天就不会到来；如果不是因为第三方的持续活动迫使我们离线，这一天也不会到来。
对你来说，好消息是汤姆所给予的，汤姆不能总是拿走。源代码在Gitlab上是安全的。此外，由于多年来许多人都为构建字符串的数据库做出了贡献，所以我觉得有点不好意思把它拿走，所以这里是转储到JSON文件中的数据库。我会鼓励任何人接受挑战，继续我多年前的愿望，建立一个真正具有权威性的构建列表。
-托马斯·豪塞尔
附录1
当然，一旦记者了解了这个故事，我的通知就会有一些创造性的解释。以下是我想澄清的几点…
微软没有也从来没有停止过构建feed。他们从未明确要求网站被关闭。他们从未（直接）要求我披露网站的来源。他们的手打得太好了，不能屈从于这种乱七八糟、笨拙的战术。
这个关闭的时机与我提到的内部压力有关，与微软等外部压力无关。如果微软没有对buildfeed施加任何压力，我怀疑会有一个问题，但如果我过去没有犯过一些错误，也不会有太多内部压力，我们也不会打算关闭它。
实际上，最终，内部压力是决定因素。你们中认识我的人都知道，我不是一个仅仅接受别人订单的人，即使他们来自一家大型跨国公司。然而，对于buildfeed的关闭来说，这已经是一个“何时”而不是“是否”的问题了，我承认这一事件只是把事情弄到了头上。最后，我觉得在外部因素开始为我做决定之前，最好跳起来而不是被推到前面去。
网页原文：
Checking out
When I started up BuildFeed over five years ago, I never expected it to grow as large and as widely used as it has been. I've not been involved in the day to day running of BuildFeed for over two years now. I left that in the hands of a few trustworthy friends, and I and the users of the site owe a debt of gratitude to these men. Without them, this day would have arrived some time ago.
You've probably noticed some funky build strings pop up on BuildFeed lately. That's because a Microsoft employee posted them on BuildFeed. For those interested parties, don't bother coming to me. I have no IP logs, I have no "inside" insight as to what our mutual friend has been up to. Could you find out who it is? Sure, just look on Twitter and see who was posting build tags ahead of BuildFeed. He's not been remotely discreet and he handed out the strings to plenty of others before BuildFeed accepted them.
The long term future of BuildFeed has been in doubt for some time, but events over the past few days have resolved things in my mind. Given extensive internal pressures and external pressures (and yes, Microsoft is one of those relentless and ever-present external pressures), I have found myself unable to commit to running BuildFeed on the principles it was founded upon. In light of this, I have made the decision to terminate BuildFeed with immediate effect. The truth is that were it not for my failings, this day would not have come; and were it not for the persistent activities by third parties to force us offline, this day would not have come either.
The good-ish news for you is that what Tom giveth, Tom cannot always take away. You have the source code, safe on GitLab. Additionally, since many people have contributed to the database of build strings over the years, I'd feel a bit ashamed to take that away, so here's that database dumped into a JSON file. I would encourage anyone to take up the challenge and continue the desire I had those many years ago, to establish a truly authoritive build list.
- Thomas Hounsell
Addendum #1
Naturally, once the journalists have got ahold of the story, there's been some creative interpretations of my notice. Here's a few points I would wish to clarify...
Microsoft has not and has never issued a Cease & Desist to BuildFeed. They have never explicitly asked that the website has been taken down. They have never (directly) asked me to disclose the sources for the site. They have played their hand far too well to stoop to such messy and clumsy tactics.
The timing of this closure has everything to do with the internal pressures I mentioned and nothing to do with the external pressures such as Microsoft. Were Microsoft not placing any pressure on BuildFeed, I doubt there'd be an issue, but it's also true that had I not made some mistakes in the past, there would be little to no internal pressures and we wouldn't be looking to close either.
Indeed, ultimately, the internal pressures are ultimately the deciding factor. Those of you that know me, know that I am not one to merely accept someone elses' orders, even if they are from a large multinational corporation. However, it has for a while been a question of "When" rather than "If" for BuildFeed's closure, and I'll admit that this incident merely brought things to a head. In the end, I felt it better to jump rather than be pushed, and get ahead of things before external factors started making decisions for me.
翻译：（机翻）
退房
当我在五年前开始构建feed时，我从来没有想过它会像以前那样大，并且被广泛使用。我已经两年多没有参与BuildFeed的日常运行了。我把这件事交给了几个值得信赖的朋友，我和网站的用户欠这些人一笔人情债。没有他们，这一天早就到了。
您可能注意到最近在buildfeed上弹出了一些奇怪的构建字符串。这是因为一位微软员工在buildfeed上发布了它们。对于那些有兴趣的人，别费心来找我。我没有IP日志，我对我们共同的朋友的所作所为没有“内部”洞察力。你能知道是谁吗？当然，只要看看Twitter，看看谁在buildfeed之前发布了构建标签。他并不谨慎，在buildfeed接受之前，他把弦交给了很多其他人。
buildfeed的长期前景一直存在疑问，但过去几天发生的事件已经解决了我心中的问题。考虑到广泛的内部压力和外部压力（是的，微软是其中一个持续存在的外部压力），我发现自己无法承诺按照其建立的原则运行buildfeed。鉴于此，我决定立即终止BuildFeed。事实上，如果不是因为我的失败，这一天就不会到来；如果不是因为第三方的持续活动迫使我们离线，这一天也不会到来。
对你来说，好消息是汤姆所给予的，汤姆不能总是拿走。源代码在Gitlab上是安全的。此外，由于多年来许多人都为构建字符串的数据库做出了贡献，所以我觉得有点不好意思把它拿走，所以这里是转储到JSON文件中的数据库。我会鼓励任何人接受挑战，继续我多年前的愿望，建立一个真正具有权威性的构建列表。
-托马斯·豪塞尔
附录1
当然，一旦记者了解了这个故事，我的通知就会有一些创造性的解释。以下是我想澄清的几点…
微软没有也从来没有停止过构建feed。他们从未明确要求网站被关闭。他们从未（直接）要求我披露网站的来源。他们的手打得太好了，不能屈从于这种乱七八糟、笨拙的战术。
这个关闭的时机与我提到的内部压力有关，与微软等外部压力无关。如果微软没有对buildfeed施加任何压力，我怀疑会有一个问题，但如果我过去没有犯过一些错误，也不会有太多内部压力，我们也不会打算关闭它。
实际上，最终，内部压力是决定因素。你们中认识我的人都知道，我不是一个仅仅接受别人订单的人，即使他们来自一家大型跨国公司。然而，对于buildfeed的关闭来说，这已经是一个“何时”而不是“是否”的问题了，我承认这一事件只是把事情弄到了头上。最后，我觉得在外部因素开始为我做决定之前，最好跳起来而不是被推到前面去。
