Codefag
Codefag | |
---|---|
Nationality | Unknown, Assumed to be Indian |
Occupation | Developer at soyjak.party |
Tripcode | Chud ## Developer |
IAS? | Unknown |
Codefag, also known as Chud ## Developer, is currently the parties' Developer. He was confirmed to be the 'parties developer on the 23rd of March 2024. Not much is known about him.
History
Soygem.party
He wasn't too notable while He was actually working on the site, in which he worked from January to Feburary.
Things he added:
- Failed archive
- Rainbow text, which was quickly copied by Leno
- Various funny pages
- /Caca/ and /SSS
- Various other text themes.
- Soyquote button (Leno also added it to sharty right after)
- Otherwise, not much.
What was interesting about him was the Codefag Incident, which in short: Codefag hires a new developer to replace him, who he didn't know was from Discord. Then, 'Corder spergs out and destroys the log and plugs his 'cord. Codefag, trying to save face, posted something from xis mod account, and leaked everyone's IPs. In embarrassment, he leaves the site and totally blow it up for a few hours.[it just is, ok?]
On Soyjak.party
After Root became admin, he hired a new Developer and Manager. There was much speculation on who the new developer was, and to the surprise of soyteens, Mud revealed that the developer is Codefag, with it now being 100% confirmed on 3/22/24, in the Q&A.[1]
Controversies
On April 4th, 2024, he thought it would be a great idea to force everybody to solve a hCaptcha to even look at the website. This broke marge.moe and archiving entirely. Both archive sites can't solve a captcha so you VILL not archive the sharty. The developer's excuse was to "prevent bots raping the site".
-
Forced hCaptcha screen
-
Developer's excuse "I'm sorry for not letting bots rape the site."
Devbaiting
Chud ## Developer is rather easy to bait. Calling out the Apple Pay datamining or making up false claims about the site will cause him to drop in to an autistic fit of rage, write a seething paragraph to debunk your posts, and eventually lock the thread. He has done that at least 5 times so far.