Difference between revisions of "User:Sitzkrieg/Sandbox/Source code"
(Created page with "'''This page will not discuss methods of acquiring or distributing the illegally leaked source code. It will only cover the impact of the leak(s) and major events.''' On Apr...") |
GrampaSwood (talk | contribs) |
||
Line 1: | Line 1: | ||
+ | {{Delete|See talk page discussion}} | ||
'''This page will not discuss methods of acquiring or distributing the illegally leaked source code. It will only cover the impact of the leak(s) and major events.''' | '''This page will not discuss methods of acquiring or distributing the illegally leaked source code. It will only cover the impact of the leak(s) and major events.''' | ||
Line 4: | Line 5: | ||
== RCE Scare == | == RCE Scare == | ||
− | |||
When news of the leak initially spread, fear, confusion, and worry was spread throughout the community from a speculated vulnerability discovered in TF2's source code that could potentially allow for RCE (Remote Code Execution). | When news of the leak initially spread, fear, confusion, and worry was spread throughout the community from a speculated vulnerability discovered in TF2's source code that could potentially allow for RCE (Remote Code Execution). | ||
This caused many players to not play during this time until it was deemed safe to play again. Some media figures within the community warned that only valve servers were effected, while other TF2 media sources claimed all servers were effected. | This caused many players to not play during this time until it was deemed safe to play again. Some media figures within the community warned that only valve servers were effected, while other TF2 media sources claimed all servers were effected. | ||
Line 12: | Line 12: | ||
Within weeks after the leak, media figures within the community began auditing the source code. During this time the "spaghetti code" rumors of TF2 were found to be verifiably true. | Within weeks after the leak, media figures within the community began auditing the source code. During this time the "spaghetti code" rumors of TF2 were found to be verifiably true. | ||
− | On social media websites, forums, and video sharing platforms, comments within the source code received the most media attention. This was due to the comical nature of emotions expressed by the developers. The developers expressed frustration, confusion, and anger throughout many of the comments | + | On social media websites, forums, and video sharing platforms, comments within the source code received the most media attention. This was due to the comical nature of emotions expressed by the developers. The developers expressed frustration, confusion, and anger throughout many of the comments. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 17:20, 31 August 2024
This user page has been marked for deletion. See discussion on the talk page. Reason given: See talk page discussion Staff: what links here – subpages – history (last) – logs – delete |
This page will not discuss methods of acquiring or distributing the illegally leaked source code. It will only cover the impact of the leak(s) and major events.
On April 21st 2020 the source code for many Source Engine games was leaked. Team Fortress 2 was no exception to the leak, as it contained a complete 2016 build of TF2.
RCE Scare
When news of the leak initially spread, fear, confusion, and worry was spread throughout the community from a speculated vulnerability discovered in TF2's source code that could potentially allow for RCE (Remote Code Execution). This caused many players to not play during this time until it was deemed safe to play again. Some media figures within the community warned that only valve servers were effected, while other TF2 media sources claimed all servers were effected.
Media Response
Within weeks after the leak, media figures within the community began auditing the source code. During this time the "spaghetti code" rumors of TF2 were found to be verifiably true.
On social media websites, forums, and video sharing platforms, comments within the source code received the most media attention. This was due to the comical nature of emotions expressed by the developers. The developers expressed frustration, confusion, and anger throughout many of the comments.