TylerHobanDotCom

Keybase proof

I hereby claim:

• I am TylerHobanDotCom on github.
• I am tylerhoban (https://keybase.io/tylerhoban) on keybase.
• I have a public key whose fingerprint is 7A96 DAEE 0F8C AE26 B166 23FD 8480 4090 8FF1 A6FB

To claim this, I am signing this object:

TylerHobanDotCom

npm ERR! Error while executing:
npm ERR! C:\Users\namename\AppData\Roaming\npm\git.CMD ls-remote -h -t ssh://git@github.com/hydrabolt/discord.js.git
npm ERR!
npm ERR! C:\Users\namename\AppData\Roaming\npm\node_modules\bin-git\node_modules\bluebird\js\main\promise.js:680
npm ERR!             throw e;
npm ERR!             ^
npm ERR!
npm ERR! Error: could not find git
npm ERR!     at C:\Users\namename\AppData\Roaming\npm\node_modules\bin-git\index.js:25:20
npm ERR!     at tryCatcher (C:\Users\namename\AppData\Roaming\npm\node_modules\bin-git\node_modules\bluebird\js\main\util.js:26:23)

TylerHobanDotCom

//META{"name":"SendEmbeds"}*//

function SendEmbeds() {
	return;
}

SendEmbeds.prototype.load = function() {};

SendEmbeds.prototype.unload = function() {};

TylerHobanDotCom

*NOTE* This is a mirror of the properly formatted and commentable Google Doc. This may not be up to date and may have changed entirely.
But you know what is up to date, the actual Google Doc. The link is https://docs.google.com/document/d/1lonXMwgoFC2AYmqTO74AYphtwLe7TC4JdtqCq9xuFhc/edit?usp=sharing

Intro and FAQ:

Hello there,

In 2019 we face many Cybersecurity risks every day. From complex and large scale attacks like malware to simple but “tried and true” methods like phishing schemes. In this doc I will be going over my decision to roll out 2FA on all services that are capable, Why this action is being taken and projected timelines.

What is 2FA?

TylerHobanDotCom

To start, you're going to want to reset your chrome device to factory settings. If your chrome device is not managed or does not forbid this feature, use the Powerwash tool by signing out of your profile and then pressing Ctrl + Alt + Shift + r. 

If your chrome device has this feature forbidden, then enter the recovery boot by pressing esc + ↺+ ⏻ (refresh and power) and then pressing Ctrl + D to enter developer mode.  If Developer Mode is blocked, continue with clearing your data. If you are presented with a screen that says "OS Verification is OFF" press enter and then clear your data.

Once your data has been cleared, continue signing into your user profile. Fill out the Enterprise Enrollment screen if applicable. 

After logging into your profile, navigate to chrome://extensions and open the Task Manager. Wait for the enforcement extension to load in and then wait about 5 seconds. Press esc + ↺+ ⏻. If the recovery dialog shows, press ⏻ to turn off your chrome device and then press ⏻ again to turn it back