>>8781
4chanX, HPH, Oneechan, "4chan External Sound" or other sound scripts and there's more scripts you could get online.
Without going super deep into any one thing, if the script was made by someone who's adversarial to our moderation it's safer to run it in a completely separate environment from any janny shit (namely a separate browser, some schizos use virtual machines but that's a nuclear option to a problem that geriatrics easily solve on a daily basis by accidentally installing multiple browsers on their machines [and then asking you to remove them]). With that said it's entirely possible to neutralize MOST if not all attack vectors by editing the script's header or auditing the code for spooky shit, most importantly, doing all of that AND NOT POSTING will also go a long way in preventing ANY FORM of communication with the outside world if the script did manage to sniff you out as a concierge sans salaire. So keep in mind what it says it does, what it actually does and what you want it to do.
Too retarded to read code? No problem!
>Don't want scripts to run on janny stuff?
Remove/edit @match and @include or add @exclude for certain domains (actually check if the websites listed are the actual websites you think they are, don't fall for gmaiI.com tier shit [that was an uppercase i, not an l]).
>Don't want scripts to talk to spooky websites?
Remove @connect (definitely remove "@connect * " [which means "connect all " in plain English]), check what websites the script wants to access before clicking any pop-ups like an ADDfag or block those websites in the script's exceptions.
>Don't want your scripts doing spooky shit?
Remove @grant, namely unsafeWindow, look up what the others do if you're ever in doubt.
>Don't want to place your trust in some faggot that might maliciously edit the code down the line?
Remove @updateURL.
