Soot

From soyjak wiki
Soot.

Soot (20 April 1889 – 30 April 1945) also known as nigger-admin, was a Dutch-born German alt-right chud incel politician who was the dictator of Soyjak.party from 1933 to 1945. He rose to power as the leader of the Soyjak.party, becoming Chancellor in 1933 and then assuming the title of Führer und Reichskanzler in 1934. During his dictatorship from 1933 to 1945, he initiated Soy War II in Soyurope by invading Poland on 1 September 1939. He was closely involved in military operations throughout the war and was central to the perpetration of the Holocaust, the genocide of about 6 million Jews and millions of other victims.

Timeline of Soot's involvement with the CIA[edit | edit source]

The Chuds on the website have kept a watchful eye on Soot's policies with regards to information security and datamining.

October 2020: Google AdSense[edit | edit source]

The earliest capture of soyjak.party's """privacy policy""" page, dated October 17, 2020 contained several questionable references to Google advertisement cookies, and explicitly stated that third-party services were able to track users.[1]

It contained some bone-chilling sentences, such as:

Google is one of a third-party vendor on our site. It also uses cookies, known as DART cookies, to serve ads to our site visitors based upon their visit to us and other sites on the internet.

and:

Third-party ad servers or ad networks uses technologies like cookies, JavaScript, or Web Beacons that are used in their respective advertisements and links that appear on soyjak.party, which are sent directly to users' browser. They automatically receive your IP address when this occurs. These technologies are used to measure the effectiveness of their advertising campaigns and/or to personalize the advertising content that you see on websites that you visit.

The last capture that features this wording was on November 29, 2020.[2] Sometime between then and December 7, 2020,[3] references to third parties were removed, and were replaced with the following notice:

soyjak.party no longer shares information with any third parties, including advertising agencies and any other groups. Google adsense was removed a long time ago.

Malicious ads[edit | edit source]

Soot once implemented ads with malware on the site. It was promptly removed, but begged the question of his retarded and sketchy behaviour as a web admin.

To do: is this referring to Google ads or another ad network?

March 2021: TrustAsia TLS[edit | edit source]

All of your shitpost have been siphoned to a Chinese datacenter, so that Based Lord Xi can read them at his leisure.
"What? Huawei has ties with the Chinese government, and has been accused of technology theft? What are you talking about? Take your meds, schizo!"[4]

TrustAsia is a Chinese provider of TLS certificates. I'm not even going to post a reference, look it up at your own risk.

Why would ((Soot)) not switch to Let's Encrypt?[5] He has no excuses:

  • He is no longer using shared hosting, but a VPS,[6] so he can install any software he wants.
  • Let's Encrypt does it for free (wholesome!).
  • It's dead-simple to set it up with nginx,[7] even someone who copy-pasted some shit code to create a random image array in JS[8] could do it.
  • The sunk-cost fallacy of having to use a (((botnet certificate))) he paid for until it expires is a meme, especially if he keeps reassuring us that this site is not a "datamining scheme".[9]

It really gets your noggin' joggin'.

April 2021: Matomo.js[edit | edit source]

What (((Soot))) could see while using Matomo.

Soot figured that maybe people would react less negatively to datamining software if it was open-source, instead of some proprietary tracking system by a giant corporation.

Soot thus included the open-source datamining software Matomo on his site. The schizos took notice, and started filling the boards with CIA soyjaks, exposing Soot's datamining scheme.

Soot, caught red-handed, was issued a standard apology by CIA's PR shills, which he published on April 19, 2021. It read:

apologies for any concern it may have caused, i was just trying to get some general time zone and user agent information, but i understand why everyone was concerned, since the software can collect way more. as i have said before, none of the information that i collected has ever been shared with a third party, and any data that i collected with matomo has already been deleted. hope this clears things up.[10]

However, in complete contradiction of his reassuring words, a file named analytics.js was present on the server as early as April 13, until May 16.[11] In fairness, it may have been accidentally left over after Soot removed the analytics.

May 2021: Removal of the Islamic Culture Thread[edit | edit source]

Soot declaring that a certain thread was unwelcome on his site.

On May 9, 2021, many people were shocked by the fact that the Islamic Culture thread on the /webm/ board had been removed. A Gigachad decided to recreate the thread, but Soot declared that such a thread was too problematic for his site. He defended his actions, claiming a zero-tolerance policy was necessary so that falseflaggers couldn't get the site B& and V&.

anyone can post this and then go to the hosting provider and submit an abuse report to try and have my shit taken down. it doesnt have to be the host itself monitoring.[12]

One schizo several defenders of the constitutional right to free speech insisted that the CIA and JIDF had taken over the site, and booted Soot from its admin position.[13]

Captchas[edit | edit source]

Less than a week later after the previous incident, datamining captchas were implemented on Soyjak.party, meaning that you won't be able to post without solving them.

To do: do we have any images/captures of one of the darkest hours in soyjak.party history?

Cloudflare[edit | edit source]

A MITM attack by any other name...

At some point, Soot activated Cloudflare because >muh DDoS protection or something along those lines.

What is Cloudflare? It's a literal MITM attack, the "hackers that will steal your passwords" that all VPN advertisements talk about. (Not that you should trust a VPN either, see below why).

Note for a site to use cloudflare, the owner has to point their DNS records to cloudflare's servers, at which point they effectively handed cloudflare full control of their website (as long as the DNS records point to cloudflare's servers). They can prove control of a domain to certificate authorities who will issue certificates for your domain to cloudflare.

Now cloudflare has control to eavesdrop and log any user interactions with your website or silently tamper content if they please.

However, this is not a Man-in-the-Middle attack, because the website owner gave cloudflare permission to do all of this. So it's not an attack, it's a secure connection to cloudflare (who the website owner gave permission to serve content at their domain name).

[...]

In the end, that's all you have. You have to trust that the organization running the website at the other end is trustworthy with whatever data you give them by browsing there. When visiting websites on the cloudflare CDN part of the trust is in cloudflare.

(This is in contrast to real MitM attacks, where some attacking middleman who does not have authorized access eavesdrops and/or tampers with the network traffic).[14]

To do: has anyone archived any thread about this, and the sticky note thing?; Talk about 100 MB upload limit disrupting the wholesome Tom and Jerry poster on /webm/: https://soyjak.party/webm//res/425.html

June 2021: Soot is a boomer, admins can see IPs[edit | edit source]

The Captain Coal fiasco of June 2021 taught us two things:

  • The "hack" happened because Soot had forgotten to disable the default admin account. Soot needs to learn the basics of OPSEC, NOW.
  • Soot confirmed that Vichan admins can see the IP of both posters and lurkers, which means you should be using TOR.

Don't fall for the (((VPN))) meme, they're only good for bypassing geographical restrictions or hiding your IP address, but they DO NOT give you anonymity: the VPN provider can datamine the shit out of you, knows everything you're looking at, and on top of that, has your credit card details.

TOR nodes being blocked[edit | edit source]

Anyone using TOR will have experienced that many nodes are permabanned. This is because a lot of people coalposters proxyhop with TOR, and Soot found that the easiest way to deal with this is to just permaban TOR exit nodes one by one. He said that he will unban them if you ask in the appeal box.

Treatment of Userbase[edit | edit source]

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.

Victims of Soot[edit | edit source]

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
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.

June 2021: Downward spiral[edit | edit source]

At some point, Soot's mental state began to deteriorate. He began to act in a similar fashion to Lee Goldson, becoming quick to enrage and insult soyjak.party's userbase. Soot increasingly became agitated and lost his composure when confronted with conflicting opinions. [15][16] Soot bombarded his own userbase with homophobic slurs, and frequently put himself on a pedestal saying he "didn't have time" to moderate his own website because he had "better" things to do.

During a wiki edit war on the Colorfuljaks article, Soot appointed a wiki moderator called called Syjck, creator of the SoyBooru. Soot has ignored all criticism of this moderator; he has not responded to any of the multiple threads requesting that he investigate the moderator's conduct, and in a thread in which he was highly active, he chose instead to have a long-winded, repetitive, and unproductive argument with a few schizos. [17]

Soot defends himself[edit | edit source]

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.

-Soot, 2021 [18]

Citations[edit | edit source]

  1. (((Soot))). Privacy Policy for soyjak.party. October 17, 2020. https://web.archive.org/web/20201017212456/https://soyjak.party/privacy.html
  2. https://web.archive.org/web/20201129105214/https://soyjak.party/privacy.html
  3. https://web.archive.org/web/20201207005644/https://soyjak.party/privacy.html
  4. https://www.npr.org/2019/06/08/730898429/huawei-accused-of-technology-theft?t=1623276723388
  5. https://letsencrypt.org/
  6. Soot. Recent Downtime. November 28, 2020. https://web.archive.org/web/20210408185627/https://blog.soyjak.party/?p=57
  7. https://certbot.eff.org/
  8. I'm not joking: https://web.archive.org/web/20210609224016/https://soyjak.party/suggest//res/408.html#2275
  9. Soot. Financials April 29, 2021. https://web.archive.org/web/20210609223259/https://blog.soyjak.party/?p=84
  10. https://web.archive.org/web/20210514210357/https://soyjak.party/#12
  11. https://web.archive.org/web/*/https://soyjak.party/js/analytics.js
  12. /webm/, post no. 604. https://web.archive.org/web/20210509184020/https://soyjak.party/webm//res/586.html
  13. /webm/, thread no. 586. https://web.archive.org/web/20210509184020/https://soyjak.party/webm//res/586.html
  14. https://security.stackexchange.com/a/177301
  15. "You're saying that as if the scat posters were somehow any better than the spammers. I was just checking the recent posts for a bit on my phone, so forgive me if I can't sit here all day and patrol the catalog for you."https://soyjak.party/soy//res/105899.html#105919
  16. https://soyjak.party/soy//res/105899.html#105927
  17. https://web.archive.org/web/https://soyjak.party/suggest//res/4803.html#4952
  18. https://web.archive.org/web/https://soyjak.party/qa//res/6141.html#6148