Editing Project @tom Bomb (section)

=== General Overview: ===
The @tom Bomb itself is classified (I personally don't know what it was), but there is a certain amount that can still be learned about it.

The @tom bomb was a thread- a very- very- very- long thread- in fact a little too long (*cough*alottoolong*cough*). It is believed it was at least thirteen thousand messages, though it cannot be confirmed to be greater than that for a number of reasons, including, but not limited to, the fact that most peoples devices don't run well enough to load every single message in a thread that large (It was seen to be as big as 13 thousand though [citation/witness prolly needed]). While I am sure it was a strain on devices to respond to and load the thread as it grew up through the thousands, at some point it became too much. Eventually clicking on a notification from the thread would crash teams (possibly your device [verification necessary]), and the only "safe" way to continue the thread was by responding to it from the channel, without expanding the thread, reducing, though I am sure not canceling, the damage from the thread. While all of these things are bad enough, and I'm sure the lag when doing anything in the channel was terrible, this is still not the @tom bomb, though this the precursor and the largest thread NSA has had, or will ever have (NSA faculty will not allow it to happen again (see section above)).

As I previously stated, I don't know what the actual @tom Bomb is/was, but that does not mean I cannot describe it's effects. One or more students released the @tom Bomb on the thread, and that was it for Teams. ''ALL'' of teams crashed, chats, channels, buildings, everything crashed (should be verified), not just for the students in the thread, but for all of NSA. Gone.