February 16 nuke - Revision history

Saucy: Text replacement - "Category:Events" to "Category:Irony Hub events"

2022-07-13T05:46:28Z

Text replacement - "Category:Events" to "Category:Irony Hub events"

← Older revision		Revision as of 05:46, 13 July 2022
Line 25:		Line 25:
	Luq now gets PTSD when he sees an @everyone or when the command is used.		Luq now gets PTSD when he sees an @everyone or when the command is used.

	[[Category:~~Events~~]]		[[Category:Irony Hub events]]

Saucy: Reverted edits by An anonymous user from whenthe (talk) to last revision by The o

2021-08-24T18:25:20Z

Reverted edits by An anonymous user from whenthe (talk) to last revision by The o

← Older revision		Revision as of 18:25, 24 August 2021
Line 1:		Line 1:
			The '''February 16 nuke''' (or '''February 17 nuke''' depending on where you live, also '''2/16''' and '''2/17''') was a mini-nuke that started on February 16, 2021 at 4:13 PM PST (7:13 PM EST, 00:13 UTC). An exploit with Dyno was discovered that resulted in 40 @everyone pings, until the server was locked down 8 minutes later.

			== Cause ==
			[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]

			The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


			While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.

			[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]

			== The Nuke ==
			[[File:Banning everyone.png\|thumb\|This was the first message to do this ([https://discord.com/channels/710551456091996260/746219559307968583/811389950393974795 view in Discord])]]

			The exploit was first used at 4:13 PM PST (7:13 PM EST, 00:13 UTC) in the #casual channel. It quickly spread to all other channels. This resulted in alive chat dx

			Only admins had the power to truly fix the issue. Mods tried their best to help, but the only thing they could really do was lock the channels this was happening in. But once one channel got locked, people just moved to another. There were 40 @everyone ping exploits in total, plus 1 more by Soapkiller in #announcements {{troll}}

			[[Weezor]] and [[Luq]] were both offline at the time. That left [[Soapkiller]] as the only admin that could step in, but even he was on Do Not Disturb. His first message was sent at 4:19, but with Soap being the laziest admin, he didn't do anything at first. Dyno got kicked at 4:21, which prevented any further exploits from happening, but also left the mods unable to unlock any channels. With every channel being unusable, VCs got very crowded very fast. Soap re-added Dyno at 4:27. #general was finally unlocked at 4:32, and other channels followed later.

			== Aftermath ==
			Like 200 people left as a result of the incident.

			Luq now gets PTSD when he sees an @everyone or when the command is used.

	[[Category:Events]]		[[Category:Events]]

An anonymous user from whenthe: Replaced content with " Category:Events"

2021-08-24T17:57:27Z

Replaced content with " Category:Events"

← Older revision		Revision as of 17:57, 24 August 2021
Line 1:		Line 1:
	The '''February 16 nuke''' (or '''February 17 nuke''' depending on where you live, also '''2/16''' and '''2/17''') was a mini-nuke that started on February 16, 2021 at 4:13 PM PST (7:13 PM EST, 00:13 UTC). An exploit with Dyno was discovered that resulted in 40 @everyone pings, until the server was locked down 8 minutes later.

	~~== Cause ==~~
	~~[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]~~

	The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


	~~While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.~~

	~~[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]~~

	~~== The Nuke ==~~
	~~[[File:Banning everyone.png\|thumb\|This was the first message to do this ([https://discord.com/channels/710551456091996260/746219559307968583/811389950393974795 view in Discord])]]~~

	~~The exploit was first used at 4:13 PM PST (7:13 PM EST, 00:13 UTC) in the #casual channel. It quickly spread to all other channels. This resulted in alive chat dx~~

	Only admins had the power to truly fix the issue. Mods tried their best to help, but the only thing they could really do was lock the channels this was happening in. But once one channel got locked, people just moved to another. There were 40 @everyone ping exploits in total, plus 1 more by Soapkiller in #announcements {{troll}}

	[[Weezor]] and [[Luq]] were both offline at the time. That left [[Soapkiller]] as the only admin that could step in, but even he was on Do Not Disturb. His first message was sent at 4:19, but with Soap being the laziest admin, he didn't do anything at first. Dyno got kicked at 4:21, which prevented any further exploits from happening, but also left the mods unable to unlock any channels. With every channel being unusable, VCs got very crowded very fast. Soap re-added Dyno at 4:27. #general was finally unlocked at 4:32, and other channels followed later.

	~~== Aftermath ==~~
	~~Like 200 people left as a result of the incident.~~

	~~Luq now gets PTSD when he sees an @everyone or when the command is used.~~

	[[Category:Events]]		[[Category:Events]]

The o: Reverted edits by A very evil person (talk) to last revision by Saucy

2021-08-24T02:18:45Z

Reverted edits by A very evil person (talk) to last revision by Saucy

← Older revision		Revision as of 02:18, 24 August 2021
Line 1:		Line 1:
	lol		The '''February 16 nuke''' (or '''February 17 nuke''' depending on where you live, also '''2/16''' and '''2/17''') was a mini-nuke that started on February 16, 2021 at 4:13 PM PST (7:13 PM EST, 00:13 UTC). An exploit with Dyno was discovered that resulted in 40 @everyone pings, until the server was locked down 8 minutes later.

			== Cause ==
			[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]

			The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


			While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.

			[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]

			== The Nuke ==
			[[File:Banning everyone.png\|thumb\|This was the first message to do this ([https://discord.com/channels/710551456091996260/746219559307968583/811389950393974795 view in Discord])]]

			The exploit was first used at 4:13 PM PST (7:13 PM EST, 00:13 UTC) in the #casual channel. It quickly spread to all other channels. This resulted in alive chat dx

			Only admins had the power to truly fix the issue. Mods tried their best to help, but the only thing they could really do was lock the channels this was happening in. But once one channel got locked, people just moved to another. There were 40 @everyone ping exploits in total, plus 1 more by Soapkiller in #announcements {{troll}}

			[[Weezor]] and [[Luq]] were both offline at the time. That left [[Soapkiller]] as the only admin that could step in, but even he was on Do Not Disturb. His first message was sent at 4:19, but with Soap being the laziest admin, he didn't do anything at first. Dyno got kicked at 4:21, which prevented any further exploits from happening, but also left the mods unable to unlock any channels. With every channel being unusable, VCs got very crowded very fast. Soap re-added Dyno at 4:27. #general was finally unlocked at 4:32, and other channels followed later.

			== Aftermath ==
			Like 200 people left as a result of the incident.

			Luq now gets PTSD when he sees an @everyone or when the command is used.

	[[Category:Events]]		[[Category:Events]]

A very evil person: Replaced content with "lol Category:Events"

2021-08-23T22:52:40Z

Replaced content with "lol Category:Events"

← Older revision		Revision as of 22:52, 23 August 2021
Line 1:		Line 1:
	The '''February 16 nuke''' (or '''February 17 nuke''' depending on where you live, also '''2/16''' and '''2/17''') was a mini-nuke that started on February 16, 2021 at 4:13 PM PST (7:13 PM EST, 00:13 UTC). An exploit with Dyno was discovered that resulted in 40 @everyone pings, until the server was locked down 8 minutes later.		lol

	~~== Cause ==~~
	~~[[File:Disable everyone.png\|thumb\|Luq forgot to click this~~ lol ~~(EPIC FAIL)]]~~

	The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


	~~While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.~~

	~~[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]~~

	~~== The Nuke ==~~
	~~[[File:Banning everyone.png\|thumb\|This was the first message to do this ([https://discord.com/channels/710551456091996260/746219559307968583/811389950393974795 view in Discord])]]~~

	~~The exploit was first used at 4:13 PM PST (7:13 PM EST, 00:13 UTC) in the #casual channel. It quickly spread to all other channels. This resulted in alive chat dx~~

	Only admins had the power to truly fix the issue. Mods tried their best to help, but the only thing they could really do was lock the channels this was happening in. But once one channel got locked, people just moved to another. There were 40 @everyone ping exploits in total, plus 1 more by Soapkiller in #announcements {{troll}}

	[[Weezor]] and [[Luq]] were both offline at the time. That left [[Soapkiller]] as the only admin that could step in, but even he was on Do Not Disturb. His first message was sent at 4:19, but with Soap being the laziest admin, he didn't do anything at first. Dyno got kicked at 4:21, which prevented any further exploits from happening, but also left the mods unable to unlock any channels. With every channel being unusable, VCs got very crowded very fast. Soap re-added Dyno at 4:27. #general was finally unlocked at 4:32, and other channels followed later.

	~~== Aftermath ==~~
	~~Like 200 people left as a result of the incident.~~

	~~Luq now gets PTSD when he sees an @everyone or when the command is used.~~

	[[Category:Events]]		[[Category:Events]]

Saucy: Reverted edits by 104.223.98.157 (talk) to last revision by Saucy

2021-06-08T20:07:40Z

Reverted edits by 104.223.98.157 (talk) to last revision by Saucy

← Older revision		Revision as of 20:07, 8 June 2021
Line 1:		Line 1:
			The '''February 16 nuke''' (or '''February 17 nuke''' depending on where you live, also '''2/16''' and '''2/17''') was a mini-nuke that started on February 16, 2021 at 4:13 PM PST (7:13 PM EST, 00:13 UTC). An exploit with Dyno was discovered that resulted in 40 @everyone pings, until the server was locked down 8 minutes later.

			== Cause ==
			[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]

			The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


			While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.

			[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]

			== The Nuke ==
			[[File:Banning everyone.png\|thumb\|This was the first message to do this ([https://discord.com/channels/710551456091996260/746219559307968583/811389950393974795 view in Discord])]]

			The exploit was first used at 4:13 PM PST (7:13 PM EST, 00:13 UTC) in the #casual channel. It quickly spread to all other channels. This resulted in alive chat dx

			Only admins had the power to truly fix the issue. Mods tried their best to help, but the only thing they could really do was lock the channels this was happening in. But once one channel got locked, people just moved to another. There were 40 @everyone ping exploits in total, plus 1 more by Soapkiller in #announcements {{troll}}

			[[Weezor]] and [[Luq]] were both offline at the time. That left [[Soapkiller]] as the only admin that could step in, but even he was on Do Not Disturb. His first message was sent at 4:19, but with Soap being the laziest admin, he didn't do anything at first. Dyno got kicked at 4:21, which prevented any further exploits from happening, but also left the mods unable to unlock any channels. With every channel being unusable, VCs got very crowded very fast. Soap re-added Dyno at 4:27. #general was finally unlocked at 4:32, and other channels followed later.

			== Aftermath ==
			Like 200 people left as a result of the incident.

			Luq now gets PTSD when he sees an @everyone or when the command is used.

	[[Category:Events]]		[[Category:Events]]

104.223.98.157: Replaced content with " Category:Events"

2021-06-08T16:37:55Z

Replaced content with " Category:Events"

← Older revision		Revision as of 16:37, 8 June 2021
Line 1:		Line 1:
	The '''February 16 nuke''' (or '''February 17 nuke''' depending on where you live, also '''2/16''' and '''2/17''') was a mini-nuke that started on February 16, 2021 at 4:13 PM PST (7:13 PM EST, 00:13 UTC). An exploit with Dyno was discovered that resulted in 40 @everyone pings, until the server was locked down 8 minutes later.

	~~== Cause ==~~
	~~[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]~~

	The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


	~~While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.~~

	~~[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]~~

	~~== The Nuke ==~~
	~~[[File:Banning everyone.png\|thumb\|This was the first message to do this ([https://discord.com/channels/710551456091996260/746219559307968583/811389950393974795 view in Discord])]]~~

	~~The exploit was first used at 4:13 PM PST (7:13 PM EST, 00:13 UTC) in the #casual channel. It quickly spread to all other channels. This resulted in alive chat dx~~

	Only admins had the power to truly fix the issue. Mods tried their best to help, but the only thing they could really do was lock the channels this was happening in. But once one channel got locked, people just moved to another. There were 40 @everyone ping exploits in total, plus 1 more by Soapkiller in #announcements {{troll}}

	[[Weezor]] and [[Luq]] were both offline at the time. That left [[Soapkiller]] as the only admin that could step in, but even he was on Do Not Disturb. His first message was sent at 4:19, but with Soap being the laziest admin, he didn't do anything at first. Dyno got kicked at 4:21, which prevented any further exploits from happening, but also left the mods unable to unlock any channels. With every channel being unusable, VCs got very crowded very fast. Soap re-added Dyno at 4:27. #general was finally unlocked at 4:32, and other channels followed later.

	~~== Aftermath ==~~
	~~Like 200 people left as a result of the incident.~~

	~~Luq now gets PTSD when he sees an @everyone or when the command is used.~~

	[[Category:Events]]		[[Category:Events]]

Saucy at 10:05, 18 February 2021

2021-02-18T10:05:55Z

← Older revision		Revision as of 10:05, 18 February 2021
Line 22:		Line 22:
	== Aftermath ==		== Aftermath ==
	Like 200 people left as a result of the incident.		Like 200 people left as a result of the incident.

			Luq now gets PTSD when he sees an @everyone or when the command is used.

	[[Category:Events]]		[[Category:Events]]

GuyGuy: /* Aftermath */ changed 100 to 200

2021-02-18T08:18:13Z

Aftermath: changed 100 to 200

← Older revision		Revision as of 08:18, 18 February 2021
Line 21:		Line 21:

	== Aftermath ==		== Aftermath ==
	Like ~~100~~ people left as a result of the incident.		Like 200 people left as a result of the incident.

	[[Category:Events]]		[[Category:Events]]

Cas: chungu

2021-02-17T09:55:07Z

chungu

← Older revision		Revision as of 09:55, 17 February 2021
Line 4:		Line 4:
	[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]		[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]

	The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". ~~But~~ when [[Luq]] was ~~creating~~ the ~~command~~, he ~~failed to disable @everyone for~~ the command. ~~When someone figured this out..~~. ~~chaos ensued lol~~		The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


			While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.

	[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]		[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]

← Older revision		Revision as of 09:55, 17 February 2021
Line 4:		Line 4:
	[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]		[[File:Disable everyone.png\|thumb\|Luq forgot to click this lol (EPIC FAIL)]]

	The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". ~~But~~ when [[Luq]] was ~~creating~~ the ~~command~~, he ~~failed to disable @everyone for~~ the command. ~~When someone figured this out..~~. ~~chaos ensued lol~~		The ?nuke command (ironic right) had just recently been created. The command output "{{twemoji\|✅}} Banning users... {user parameter}/6700". However, when the command was being created by [[Luq]], the syntax {noeveryone} was not added and the disable everyone box was not ticked, meaning that, if the user paramater was an everyone ping, it would ping everyone.


			While Caskain was browsing through changelog, he noticed the command was active. He did "?nuke @everyone," not expecting it to work, however it did :badluck:.

	[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]		[[File:NUKE FORESHADOWING.png\|thumb\|Foreshadowing???????]]