Greasy Fork

Dam bro you really took shots at my script. Your really this salty about me taking top. You want to play, let's play.

Dam bro you really took shots at my script. Your really this salty about me taking top. You want to play, let's play.

Look at you trying to act tough. Sigh

I have no interest in being "on the top" since I don't try to profit off users like you. My goal was to create something that would inspire others to create chess bot userscripts, since there weren't any available, which seemed weird. Ironically, by trying to "beat me" you are actually helping me achieve my original goal by developing new userscripts. But the problem is that you're not even trying to make your userscript better or original.

What will you do when Chess.com updates their CORS policy so that the web worker doesn't load the engine anymore? Wait for me to come up with a solution? I've already done my job by stirring up the pot, now I just need to observe as new userscripts emerge. I believe in the userscripting community to come up with better userscripts that have no anti-features, and this has already happened, see C.A.S. If my userscript dies in the process, that's fine and expected, I have only played like 100 games of chess in my entire life, and don't really care for the game. There are clearly better people to continue this legacy than me.

If you genuinely want to succeed and stay on top, you need to develop your own methods and ideas instead of blatantly stealing them. Your lack of quality control has resulted in a buggy userscript that only makes you look incompetent. It's no wonder people think it's been patched when it's really just your garbage code at work.

As a sidenote, you might want to use the original source for the stockfish.js, since yours could be modified maliciously and minification/obfuscation is not allowed on GreasyFork. Though even doing this might not make the use allowed, so your userscript might be in danger of removal. Anyhow, I wish you happy growth with your userscript.

What will you do when Chess.com updates their CORS policy so that the web worker doesn't load the engine anymore?

Actually, more specifically, their CSP policy. You might want to start looking for an alternative way to load the engine already, since it's really easy for Chess.com to do this change and completely break your beloved and superior userscript.

1) Congrats to you on achieving your goal
2) The money I earn from ads is in cents.
3) Not too worried about CORS since there are a million solutions to this
4) Regarding the stockfish.js file, users are free to decide if they want to install the script and can look into my stockfish.js file
5) On CSP policy, there will always be a way around it, whether extensions or otherwise.
Honestly, just felt a little attacked by your updated homepage. Just want to apologize for the inconvenience.

The money I earn from ads is in cents.

Why do you even have ads, then?

On CSP policy, there will always be a way around it, whether extensions or otherwise.

You cannot disable the CSP policy with a userscript, and using extensions or other browser modifications to disable it is both risky and makes using the userscript more cumbersome.

There are a few options,

1. You could use an engine without a Web Worker, it'd have to be customized and optimized for that
2. Run the Web Worker on a different tab and communicate between tabs
3. Host a server which calculates the moves, your ads would be justified by doing this

users are free to decide if they want to install the script and can look into my stockfish.js file

Okay, so you understand what h+1|0;do if(o<<24>>24>-1)b[q>>1]=o&255;else{if((o&255)<194){e=2;break a}m=s-h|0;l=h+2|0;if((o&255)<224){if((m|0)<2){e=1;break a}e=d[e>>0]|0;if((e&192|0)!=128){e=2;break a} on the stockfish.js file does?

What about this function Yn(b,d,e,f,g,h){b=b|0;d=d|0;e=e|0;f=f|0;g=g|0;h=h|0;var i=0,j=0,k=0,m=0,n=0,o=0,p=0,q=0,r=0,s=0,t=0,u=0,v=0,w=0,x=0,y=0,z=0,A=0;z=l;l=l+240|0;w=z;u=z+204|0;x=z+192|0;y=z+180|0;v=z+176|0;r=z+16|0;s=z+8|0;t=z+4|0;c[x>>2]=0;c[x+4>>2]=0;c[x+8>>2]=0;b=0;while(1)?

In other words, no, they cannot look into your stockfish.js file's source code.

GreasyFork has rules for non obfuscation and minification for this purpose.

users are free to decide if they want to install the script and can look into my stockfish.js file

Okay, so you understand what h+1|0;do if(o<<24>>24>-1)b[q>>1]=o&255;else{if((o&255)<194){e=2;break a}m=s-h|0;l=h+2|0;if((o&255)<224){if((m|0)<2){e=1;break a}e=d[e>>0]|0;if((e&192|0)!=128){e=2;break a} on the stockfish.js file does?

What about this function Yn(b,d,e,f,g,h){b=b|0;d=d|0;e=e|0;f=f|0;g=g|0;h=h|0;var i=0,j=0,k=0,m=0,n=0,o=0,p=0,q=0,r=0,s=0,t=0,u=0,v=0,w=0,x=0,y=0,z=0,A=0;z=l;l=l+240|0;w=z;u=z+204|0;x=z+192|0;y=z+180|0;v=z+176|0;r=z+16|0;s=z+8|0;t=z+4|0;c[x>>2]=0;c[x+4>>2]=0;c[x+8>>2]=0;b=0;while(1)?

In other words, no, they cannot look into your stockfish.js file's source code.

GreasyFork has rules for non obfuscation and minification for this purpose.

People can build and compare stockfish.js files, I really don't care what they decide to do.

The money I earn from ads is in cents.

Why do you even have ads, then?

On CSP policy, there will always be a way around it, whether extensions or otherwise.

You cannot disable the CSP policy with a userscript, and using extensions or other browser modifications to disable it is both risky and makes using the userscript more cumbersome.

There are a few options,

1. You could use an engine without a Web Worker, it'd have to be customized and optimized for that
2. Run the Web Worker on a different tab and communicate between tabs
3. Host a server which calculates the moves, your ads would be justified by doing this

I use ads to hopefully earn something by posting these scripts.

Like you said yourself there are numerous ways to get around CSP

you sprayed my face with ads so this is better