Community: Difference between revisions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
(Putting on a out of date and incomplete tag, this page hasn't seen any real updates since 2013 and is painfully lacking in info. Also axed the demographics section, with its information coming from a very outdated and dubious source, while such a section of questionable merit to begin with.)
mNo edit summary
Line 17: Line 17:
All three sites remained mostly unresponsive until August 28, when Smashboards briefly went back up before trying the CloudFlare anti-DDoS service. [[AlphaZealot]] reported that owners from each site were working together to find a solution. {{ref|DDoS3}} ''Project M'' webmaster [[Warchamp7]] later told video game blog site Kotaku that "the only viable solution to the problem at this moment is expensive and not something we can easily pursue," but added there were plans to mitigate the attacks if they continued{{ref|DDoS4}}.
All three sites remained mostly unresponsive until August 28, when Smashboards briefly went back up before trying the CloudFlare anti-DDoS service. [[AlphaZealot]] reported that owners from each site were working together to find a solution. {{ref|DDoS3}} ''Project M'' webmaster [[Warchamp7]] later told video game blog site Kotaku that "the only viable solution to the problem at this moment is expensive and not something we can easily pursue," but added there were plans to mitigate the attacks if they continued{{ref|DDoS4}}.


By September 2013, all three sites were functional again, though while Smashboards and the Project M website came out relatively unscathed, the DDoS attack dealt significant damage to AiB's aging website that was already in notoriously poor condition, playing a part in accelerating the site's ongoing decline and eventual shutdown. The perpetrator behind the DDoS attack remains unknown to this day, though it's believed to have been someone with a vendetta against the competitive Smash community, given their focus on the two primary competitive Smash hubs at the time and the website for the mod created with a heavily competitive-centric focus.
By September 2013, all three sites were functional again, though while Smashboards and the Project M website came out relatively unscathed, the DDoS attack dealt significant damage to AiB's aging website that was already in notoriously poor condition, playing a part in accelerating the site's ongoing decline and eventual shutdown. The perpetrator behind the DDoS attack remains unknown to this day, though it's believed to have been someone with a vendetta against the competitive Smash community, given the targeting of the two primary competitive Smash hubs at the time and the website for the mod created with a heavily competitive-centric focus.


==See also==
==See also==
Line 28: Line 28:
# {{note|Melee@MLG}} [http://www.nintendoworldreport.com/news/12909 Super Smash Bros. Melee at Evolution 2007]
# {{note|Melee@MLG}} [http://www.nintendoworldreport.com/news/12909 Super Smash Bros. Melee at Evolution 2007]
# {{note|EvoPetition}} [http://shoryuken.com/2013/07/09/changes-to-evo-2013-smash-schedule/ Update: Smash is Back!! Changes to the Evo 2013 Schedule]
# {{note|EvoPetition}} [http://shoryuken.com/2013/07/09/changes-to-evo-2013-smash-schedule/ Update: Smash is Back!! Changes to the Evo 2013 Schedule]
# {{note|Census1}} [http://smashboards.com/threads/behold-the-power-of-data-smash-census-results.340187/ BEHOLD THE POWER OF DATA - Smash Census Results!] (Direct link to census results [https://docs.google.com/forms/d/1xiSjLegEUUmesDx2YS6zFDWl2j6WwE30riYjLT5bIdY/viewanalytics here])
# {{note|vBExploit}} [http://smashboards.com/threads/smashboards-was-hacked.302874/ Smashboards was hacked]
# {{note|vBExploit}} [http://smashboards.com/threads/smashboards-was-hacked.302874/ Smashboards was hacked]
# {{note|DDoS1}} [https://www.facebook.com/smashboards/posts/568719856528722 Smashboards' Facebook announcement on server issues]
# {{note|DDoS1}} [https://www.facebook.com/smashboards/posts/568719856528722 Smashboards' Facebook announcement on server issues]