loypoll.com
Open in
urlscan Pro
2606:4700:3032::ac43:a48b
Public Scan
Submitted URL: http://loypoll.com/
Effective URL: https://loypoll.com/
Submission: On December 01 via api from US — Scanned from DE
Effective URL: https://loypoll.com/
Submission: On December 01 via api from US — Scanned from DE
Form analysis
0 forms found in the DOMText Content
UPDATE RESPONSE - 11/26/2023 Loypoll has made ANOTHER response. Link to it here (skip to 7:27). Now it's true, every online service collects your ip. HOWEVER not in the way Cheesed Up was doing it, especially while the mod was completely offline with no online added. Cheesed Up was taking your ip (in a list of victims), uploading it to a webhook and telling him exactly who you are. Google does not know who you are based off of ip. No one does. Hopefully this is enough to clarify what he was doing is seriously wrong. HERE'S EVEN AN ADMISSION OF GUILT FROM LOYPOLL. OF COURSE, THIS NEVER WAS ACTUALLY REMOVED Loypoll has made a response. It is basically downplaying what he did and full of lies. In fact, this whole website is true. Need proof? Zyle forked Cheesed Up when it was under loypolls account and public. You can view the source code AND commit history here this commit shows that when he got caught, he deleted it, as well as leaving a comment, "Plan A failed". We can expect more shit like this from him in the future. here is an invite to our discord server if you'd like to discuss loypoll. WELCOME TO THE LOYPOLL EXPOSÉ GIT HISTORY (OR WHAT'S RELEVANT) Loypoll has put an IP logger in Cheesed Up. it sends it to a discord webhook along with your computer's info. October 5th October 8th October 11th October 11th October 12th October 13th Now the numbers that you've seen through out the page are NOT the ips, these are discord ids that make it so if it detects your account, it makes the ip logger go off. Click here for the explanation. This is when Null made a truce with the CTCU server. He removed everyone (except juicyham44) from the list. October 18th Proof this is still here to this day, able to be uncommented out at any moments notice. LIES TOLD TO US As you'll soon see, what they are saying here is not only a lie, but covering up something potentially dangerous. Note: What RadixComet is saying here with "the only logging of your IP is when you join a server" is a straight up lie, the IP being logged is not even for the server, it is for sending to a discord webhook along with your computers name. CODE SHOWCASE CREATE CODE What the "Create" event here does is simply make sure the object is ready for use by initializing the variables needed and creating a function if desired. In this case, active is for if the RPC is working or not, character is the character you're playing as, userid is for your discordID, request is used for many things and subject is for identification. ALARM 0 CODE Now, what this alarm does in this case is it makes sure the build is either YYC or running from source, then it disables experimental mode and checks if the "request" variable is a string. If it isn't, creates a file named "dead" with the text seen inside. After this if your room location isn't any of the one refrenced it sends you to the "Realtitlescreen" room, then it check if the internet is connected. If it isn't, it closes the game. Now comes the harder pill to swallow, after this the game fetches your IP address from a site called "api.ipify.org" and stores it into the "request" variable, ready to be used. Now if the request check fails, it insteads sends a "global message" (basically the giant onscreen messages from ptt) with the contents of the "request" variable and your pc name. It then activates "Good Mode", making the game virtually unplayable. ASYNC - HTTP CODE What this code is simple enough, but i will explain it anyways. This first checks if the "id" thing is the same as the "request" variable and if the game is built in YYC or running from source. If this check passes, it stores a function into a variable named "q" and decodes a string that is a discord webhook. It then stores this into a variable named "web". After this, it creates a map for the body of the message, containing loy's discord id to be pinged, async_load[? "result"](your ip address), your PC name, the "Subject" number that you were assigned, and the version of the game that you're running. After this is done, it then pushes an https request to the webhook, sending the message to loypoll in a private server, where he stores it all. It then stores your IP into the "request" variable, ready to be used by the Alarm 0 event. ASYNC - SOCIAL CODE Now what this does is very simple, first it makes sure the discord rpc is working properly, and if it's all good to go, it sets the "a" variable with your discord id. It then sets the "userid" variable with the contents of the "a" variable, and creates a variable array named "lockout", containing the discord IDs of everyone he wants to hit. It then checks through every value in the array, and if one matches with the "a" variable, it sets the position of the array to the "subject" variable and runs the Alarm 0 event. The rest of what you see(the green stuff) is the older lockout system, and potentially more people he wants to hit. VIDEO DEMONSTRATION Screw the theoretical, this is how the code would behave in a real world situation (with the webhook changed to a different url of course) Pizza Tower Cheesed Up source code archive for evidence purposes. (mirror) A response to Loypoll's "Pizza Tower's community holds grudges" video. (Best experienced with the contents of this site) MUSIC CONTROL You can disable / change the music volume here. X THIS PAGE IS MADE TO INFORM PEOPLE ABOUT THE DANGER THAT LOYPOLL AND HIS PROJECT, "CHEESED UP!" CAN BRING. NOTHING FROM THIS IS "TAKEN OUT OF CONTEXT", "FRAMED WRONG" NOR "FAKED". Click anywhere to continue.