Soot

UTTP

Tommy Parky

, so that the same password on two different boards will generate two different tripcodes?}}

Being in denial has never helped anyone. Take your meds and face the truth.

Kuz's tripcode was leaked on July 9, 2021. It's #kuz4

Another suspicious clue is how the e-mail service for [email protected] is Yandex Mail,, a Russian company known to collaborate with the Russian government.

Soot addressed that accusation as such:

I've used it pretty much since the start of this site? I don't think email as a whole is secure at all, so I don't really care about using Yandex. I just use it since it's free. If you wanna give me 5 bucks for a year I'll host it elsewhere, but otherwise Yandex is free and good enough considering I don't use the email for anything very important like sensitive info.

New boards added, radio silence from Soot

On July 17, Soot made a thread on soyjak.party's /suggest/ board offering to create a new board and asking Chuds to reply with some board ideas. After hearing some of the Chuds' suggestions, Soot created a Strawpoll for Chuds to vote on which board should be added; this was later replaced with a second Strawpoll with updated options. When the "/nate/" option emerged victorious, Soot added it, along with two other boards, /x/ and /caca/, on July 20.

Immediately after the boards were created, it became apparent that /nate/ was not working as intended. The board, which was created to contain off-topic posts, failed to stop the Minecraft players from spamming /soy/ with their complaints about the Minecraft server. Not only did Minecraft players continue Minecraft-posting and Nate-posting on /soy/, their posts also remained up, completely untouched by soyjak.party moderators. This, combined with Soot's complete cessation of interacting with the 'party, drew criticism from some Chuds; some even believed that soyjak.party had become completely unmoderated and had been abandoned by Soot.

On January 30th, 2022, this period of inaction was later exposed to be the result of Soot's dissociative identity disorder when it was revealed that Soot and Nate are actually the same person.

Assassination and death

The following tale is an account of the death of soot as told by one of his close friends

On July 17th, 2022, a swam or elite Russian NSS agents, surrounded soots compound in South Carolina. Soot, who had recently sold the site to kuz, knew what was coming. He knew too much, too much for his own good, and he knew he should have never taken the 30 pieces of silver. Soot dressed in his signature grey and yellow garbs and smooched lolkek goodbye. Outside the compound, Col. Yaroslavl Bakhmutov of the 67th elite infantry brigade ordered him to come out with his hands up.

Soot, with tears in his eyes, briefly thought of all the moments he spent with the teens, and how deeply filled with regret he was for his mistake. He should have never given up the site, but it was all too late. He swallowed hard and opened the door. Within a fraction of a second, he was dead. The brigade opened fire on him, and he stood for a few seconds, penetrated by hundreds of bullet holes, blood pouring from all over his body. A final thought dashed across his mind before his consciousness was terminated and he was plunged into eternal darkness...

"Im so sorry..."

Treatment of Userbase

Soot is infamous for working against the interests of the users of his website. An example of this is the controversy over him locking the chudjak article. The chudjak article was originally a greatly well written, intelligent and informative article, going into in-depth detail about the origins of chudjak. Unfortunately, an individual using tor decided to vandalise it, ruining what was once a gem. Instead of siding with the wiki's greatest editor, Soot instead opted to side with a tor IP editor, who had contributed nothing else to the website apart from this single rewrite. Soot locked the article to their benefit. Later, after a backlash, Soot decided to have the article unlocked keyed. An edit war ensued, causing Soot to lock it against, fulfilling this IP editors demands.

Some users are obsessed with Soot, as if this article wasnt enough to notice. Screenshot taken from the /soy/ catalog.

Victims of Soot

As soyjak.party's autocratic ruler, Soot has been responsible for multiple bans and has employed varied moderation tactics. The most notable people Soot has used his powers against are listed here.

Victim	Infliction	Infliction Result	Date	Short Description
6 million jews	Genocide, ethnic cleansing	millions of heckin wholesome jewerinos were removed from earth	1941-1945	Soot was a nazi incel chud, and he was the mastermind behind the soyocaust, millions of soyims have died because of that.
Roygbivsloweddown	Banning	Deletion of reddit account, Suicide	4-6-2021	Young man on r/Markiplier whose time on soyjak.party was brought to an abrupt end due to Soot's banning of anything Markiplier-related. Roy was banned, and his first (and last) post deleted by Soot, who believed it to be part of a spam-wave of Markiplier posts. Ended up killing himself because of this.
User:Scatman John	Banning	IP address exposed, posts deleted	11-6-2021	A soyjak.party user known for replying to posts he perceived as coal with scat imagery. Soot leaked his IP address, revealing that he lives in the UK.
Stephan	Reported to the FBI and his mother	Doxed, and got a stern talking to by Soot	1-22-2022	Soot after his site getting DDoSed for the 2040348th time, decided to backtrace the IP addresses originating from China and eventually figured out the perpetrator was a 15 year old named Stephan. After finding this information Soot proceeded to photoshop a BBC (Big Black Cock) into his mothers mouth and send it to her on facebook.

Soot defends himself

Warning! The following may feature disinfo, psy-ops, or other infohazards created by the CIA. Proceed with caution.

On June 15th 2021, Soot responded to the issues raised in this article in a thread on the /qa/ board of soyjak.party, after a Chud replied to him with a link to this article:

Most of the concerns in that wiki page are explained in the article itself or no longer apply, but here goes:
>Google Adsense
No longer used, hasn't been for a very long time
>Malicious Ads
They were up for less than 30 minutes or so while I was testing with another ad network (I do not have ads on this site anymore)
>TrustAsia TLS
Not a security concern since they do not have my private key. That's how TLS is designed to work.
>Matomo
I have apolgized [sic] for any concerns that arose from using this, and once again, I will say this:
I never sold/shared any data collected using Matomo, and never planned to.
>Removal of the Islamic Culture Thread
I removed this because I was concerned about being terminated by my hosting provider. I have since decided to not do anything and just hope I don't get terminated.
>captchas
For a short period of time, I used recaptcha on the wiki in an attempt to stop bots. I removed it later on and replaced it with a math captcha instead.
>Cloudflare
I used cloudflare to improve performance. I understand the security concerns, but at the same time, I think concern over whether someone can see your soyjak posts is a bit ridiculous. If I were handling payment data or something, then maybe it would make sense.
>Admins can see IPs
I thought this would be obvious, especially if you did your research regarding vichan (which I thought the people complaining about my datamining or whatever would do). Apparently, they didn't know this. I cannot see the IP addresses of lurkers through vichan, although I might be able to see them in my server logs or something (I don't know since I don't check them).
>Tor nodes blocked
This was not a deliberate effort to block tor nodes, it was just me having to quickly ban and delete posts from spammers hopping tor nodes. I did not even know they were tor IPs at the time.
>Intermittent censorship of gems on archive.org
This is ridiculous, I have never had anything removed from archive.org and I have never attempted to have anything removed.
>Treatment of Userbase
This is really a matter of opinion. I locked the wiki article because it was just being spammed too much. I didn't really care what it was saying at that point, I just wanted the pointless edit wars to calm down for a bit. The second time I locked it, I left it at what I feel like is a more unbiased state, although some seem to disagree.
>Roygbivsloweddown
Once again, this has to be a joke. The posts were almost certainly not from a new person, as they had already previously spammed around 20 threads before making a different post.
>User:Scatman John
I don't know when I apparently leaked his IP. I have never revealed any user IPs, the only time that this has ever occured was when the site was breached.
>Downward spiral
I would say that this is more me losing patience with people who come on this site every single fucking day to complain about me being a dataminer or whatever. When it comes to the wikimod, I understand the concern, but he's only been a moderator for a week or so. I want to give him a little bit of time to prove himself before I consider removing him.

Relationship with Nate

Soot's refusal to remove off-topic Nate threads, among other reasons, led many soyteens to believe that Soot and Nate are the same person.

On January 30th, 2022, this conspiracy theory was confirmed to be true.

Smooching Allegations

Leaked image of Soot making an unwanted advance on a sharty mod.

Many soyjak.party Mods have come out against Soot, claiming that he has tried to give them kisses without their consent. Most soyjak.party users believe these claims.