安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题



The reason all of the archives in the big table source Wayback Machine is that, as far as I know, unprivileged users can only request for their servers to save a copy, which in a way ensures that the data hasn't been tampered with.
It is the reason I don't feel very comfortable sharing personal archives, since anyone who cannot manually verify them shouldn't even try using them for sake of security, and those who can would have a lot of work to do.
Thank you for sharing, however this can provide limited utility at best as it is more than likely that the older versions are half-functional, if at all.
As of now there isn't a convenient way of verifying legitimacy of packages, but if I had a lot of free time, I would source SteamDB's SteamTracker commits and compare file hashes for packages. This does not cover most of your archives though, which consisted of compressing the entire Steam installation into an archive, which would be impossible to verify without sourcing someone else's package archives.
Because of all these reasons, I am highly sceptical of adding more user-submitted archives to the mix. The one I did add is much more straightforward to verify, so it made the cut, although even that was merely an exception.
https://github.com/SteamDatabase/SteamTracking/commits/master/ClientManifest/steam_client_win32