Editing Yuri Kuznetsov (kuz)
From Bibliotheca Anonoma
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
[[File:Kuz.png|270px|thumb|A picture of Kuz which used to be displayed on his personal website.]] | |||
[[File: | '''Yuri Mikhailovich Kuznetsov''', better known as '''kuz''' (pronounced "kooz") is a Russian internet businessman currently living in Memphis.<ref>[https://twitter.com/yurimkuznetsov Kuz's Twitter account.]</ref> He's mainly known for creating 9channel, owning and administrating several other imageboards, frequently posting on them and on websites he doesn't own as well as founding '''The Kolyma Network''', a "webhosting and internet services company", also known as '''KolymaNET'''.<ref>[https://www.kolyma.org/ KolymaNET's website.]</ref> Kuz is an infamous and controversial figure in the imageboard sphere, he's mostly popular and liked on websites he owns, but on other sites he's gotten involved with his reputation is much more negative, with the most common accusation thrown at him by critics being that he's an "imageboard monopolizer", which he and his supporters deny.<ref>[http://web.archive.org/web/20210831053830/https://kuz.lol/blog/harmful-rumors/ kuz's reposne to the claim that he's an imageboard monopolizer.]</ref>He also runs a personal blog.<ref>[https://kuz.lol/ Kuz's personal blog]</ref><ref>[http://kuz.fka.cx/ Another domain kuz formerly used for his personal blog.]</ref> | ||
'''Yuri Mikhailovich Kuznetsov''', better known as '''kuz''' (pronounced "kooz") is a Russian businessman currently living in Memphis | [[File:Kuzzy.jpg|230px|thumb|Another picture of kuz.]] | ||
[[File: | |||
<span style="color:red">'''Much of the following details surrounding his personal life and presence on the internet are in dispute, conflicting and come from many different sources. keep that in mind while reading. This page will provide several different perspectives and clashing information on him, followed by an analysis of that information.'''</span> | <span style="color:red">'''Much of the following details surrounding his personal life and presence on the internet are in dispute, conflicting and come from many different sources. keep that in mind while reading. This page will provide several different perspectives and clashing information on him, followed by an analysis of that information.'''</span> | ||
Line 98: | Line 97: | ||
There is still doubt to be had about the twitter page, however, since kuz by his own admission wiped out most of his presence on the internet prior to 9channel's collapse, which makes it strange that the account hasn't been deleted.<ref>[http://web.archive.org/web/20200705123359/http://kolyma.jp/ kuz claiming that he wiped his internet presence in 2017-2018.]</ref> | There is still doubt to be had about the twitter page, however, since kuz by his own admission wiped out most of his presence on the internet prior to 9channel's collapse, which makes it strange that the account hasn't been deleted.<ref>[http://web.archive.org/web/20200705123359/http://kolyma.jp/ kuz claiming that he wiped his internet presence in 2017-2018.]</ref> | ||
[[File:Possibly9channel.png|250px|thumb|A screencap of | [[File:Possibly9channel.png|250px|thumb|A screencap of Strawberryheaven's front page on May 28th, 2021.]] | ||
Similarly, however, the Github document can also be called into question. The page itself was written by an anonymous author and published in April 2021. It goes strangely in-depth into Kuz's life, leading one to ask how the writer could've gained any of this information without fabricating it or being kuz themselves. Furthermore, absolutely no proof or mention of the existence of Vass Boldizar or Zdavaprom (an advertisement agency kuz alledgedly owned prior to 9channel's collapse) could be found. One thing mentioned in the document that could be found mentioned *on Kuz's website and not by a user*, however, is '''Rychuvak'''. Archived snapshots could be found of | Similarly, however, the Github document can also be called into question. The page itself was written by an anonymous author and published in April 2021. It goes strangely in-depth into Kuz's life, leading one to ask how the writer could've gained any of this information without fabricating it or being kuz themselves. Furthermore, absolutely no proof or mention of the existence of Vass Boldizar or Zdavaprom (an advertisement agency kuz alledgedly owned prior to 9channel's collapse) could be found. One thing mentioned in the document that could be found mentioned *on Kuz's website and not by a user*, however, is '''Rychuvak'''. Archived snapshots could be found of Strawberryheaven (a kuz website we'll get to later) that show a list of dead boards, presumably original 9channel boards considering their date of closure is mentioned to be December 22nd 2017. The same list can be found on KolymaBBS. Among these boards are /ca/ - Crime Announcements, /rape/ - Porno/Rape and '''/ry/ - Rychuvak Criminial Syndicate'''.<ref>[https://archive.fo/EZ0cr The list of 9channel boards displayed on Strawberryheaven.]</ref><ref>[https://web.archive.org/web/20220219174325/https://bbs.kolyma.org/menu2.html The same list of boards as the above on KolymaBBS, under "9ch mira".]</ref> Considering that Kuz's main claim to fame is no longer a TOR website known for criminal activity but rather a legal business AND considering that he claimed to have actively wiped his presence on the internet, one has to wonder why on earth he would choose to make this information public, which gives more fuel to the theory that it and the Github document were fabricated by kuz for clout or other purposes. | ||
Line 111: | Line 110: | ||
As for the Cvnka incident, kuz entirely denies that any of it ever happened. He responded to the rumors in a blog post in December 2020 - | As for the Cvnka incident, kuz entirely denies that any of it ever happened. He responded to the rumors in a blog post in December 2020 - | ||
''"Wow, this is a whole lot of nonsense in just a couple sentences. I did go to a convention in saint petersburg, yes. I did not meet a polish girl halfway through, i never met any women there actually. This "cvnka" character was a mere 12 years old when this event took place (2009). If you are wondering, cvnka is the name of an american vtuber and online personality. I have no connections to her, but for some reason, there are very pertinent rumors that we know eachother—I assure you, we do not! Ask her yourself, or, better, stop harassing her with stupid and innapropriate questions about me. Thanks."''<ref>[https://archive.vn/EFHji#selection-277.0-281.359 Kuz's response to the Cvnka allegations.]</ref> | ''"Wow, this is a whole lot of nonsense in just a couple sentences. I did go to a convention in saint petersburg, yes. I did not meet a polish girl halfway through, i never met any women there actually. This "cvnka" character was a mere 12 years old when this event took place (2009). If you are wondering, cvnka is the name of an american vtuber and online personality. I have no connections to her, but for some reason, there are very pertinent rumors that we know eachother—I assure you, we do not! Ask her yourself, or, better, stop harassing her with stupid and innapropriate questions about me. Thanks."''<ref>[https://archive.vn/EFHji#selection-277.0-281.359 Kuz's response to the Cvnka allegations.]</ref> | ||
Do note that the Neocities page claims that Cvnka incident occurred in 2015 | Do note that the Neocities page claims that Cvnka incident occurred in 2015. | ||
Finally, kuz still claims to be working with DCP, despite the Github document claiming that he quit the internet following 9channel's collapse | Finally, kuz still claims to be working with DCP, despite the Github document claiming that he quit the internet following 9channel's collapse.<ref>[https://archive.fo/dke2X A blog post in which kuz mentions DCP helping him fix some bugs on Heyuri.]</ref> | ||
Line 168: | Line 166: | ||
<big>'''*ceje'''</big><ref>[https://web.archive.org/web/20210131221332if_/https://data.kolyma.jp/usr/profile_ceje.htm ceje's bio]</ref> | <big>'''*ceje'''</big><ref>[https://web.archive.org/web/20210131221332if_/https://data.kolyma.jp/usr/profile_ceje.htm ceje's bio]</ref> | ||
<big>'''*Kaguya'''</big><ref>[https://web.archive.org/web/20210131221347if_/https://data.kolyma.jp/usr/profile_kaguya.htm Kaguya's bio | <big>'''*Kaguya'''</big><ref>[https://web.archive.org/web/20210131221347if_/https://data.kolyma.jp/usr/profile_kaguya.htm Kaguya's bio.]</ref> | ||
<big>'''*Nakura/名無しあき'''</big><ref>[https://web.archive.org/web/20210131221336if_/https://data.kolyma.jp/usr/profile_nakura.htm Nakura's bio.]</ref> | <big>'''*Nakura/名無しあき'''</big><ref>[https://web.archive.org/web/20210131221336if_/https://data.kolyma.jp/usr/profile_nakura.htm Nakura's bio.]</ref> | ||
Line 177: | Line 175: | ||
<big>'''*Yemu/예무'''</big><ref>[https://web.archive.org/web/20210131221400if_/https://data.kolyma.jp/usr/profile_yemu.htm Yemu's bio.]</ref> | <big>'''*Yemu/예무'''</big><ref>[https://web.archive.org/web/20210131221400if_/https://data.kolyma.jp/usr/profile_yemu.htm Yemu's bio.]</ref> | ||
==Involvement With Various Websites/People== | ==Involvement With Various Websites/People== | ||
Line 190: | Line 182: | ||
'''Heyuri''' is an imageboard created by '''Riley James Bell''' (better known as '''lolico''') in 2018<ref>[https://www.heyuri.net/ heyuri.net.]</ref><ref>[http://www.heyuri.net/museum Heyrui Museum.]</ref><ref>[https://www.heyuri.net/index.php?p=rules Heyuri's rules.]</ref> It was originally hosted on the Heyuri.cf domain and meant to be a P2P filesharing website, but on November 24th 2019 it was relaunched in it's current form as an imageboard. On February 29th of 2020, the site switched to it's current domain, '''heyuri.net'''. It was incorporated into KolymaBBS prior to it's disslolution. kuz calls it his favorite website, which some consider strange since kuz is a fan of soyjak shitposting which is banned on Heyuri.<ref>[https://archive.is/miOP7 kuz calling himself a "soi duel veteran on /qa/" on his personal website.]</ref> Heyuri also hosts kuz's clone of ayashii world.<ref>[https://web.archive.org/web/20220207020008/https://ayashii.net/ kuz's ayashii clone.]</ref> | '''Heyuri''' is an imageboard created by '''Riley James Bell''' (better known as '''lolico''') in 2018<ref>[https://www.heyuri.net/ heyuri.net.]</ref><ref>[http://www.heyuri.net/museum Heyrui Museum.]</ref><ref>[https://www.heyuri.net/index.php?p=rules Heyuri's rules.]</ref> It was originally hosted on the Heyuri.cf domain and meant to be a P2P filesharing website, but on November 24th 2019 it was relaunched in it's current form as an imageboard. On February 29th of 2020, the site switched to it's current domain, '''heyuri.net'''. It was incorporated into KolymaBBS prior to it's disslolution. kuz calls it his favorite website, which some consider strange since kuz is a fan of soyjak shitposting which is banned on Heyuri.<ref>[https://archive.is/miOP7 kuz calling himself a "soi duel veteran on /qa/" on his personal website.]</ref> Heyuri also hosts kuz's clone of ayashii world.<ref>[https://web.archive.org/web/20220207020008/https://ayashii.net/ kuz's ayashii clone.]</ref> | ||
Kuz took interest in Heyuri in early 2020 and on the 26th of May, replaced '''Cavalier''' as the site's second administrator. In June, the site was transferred to KolymaNET's servers and a new developer was hired - '''akima'''. On July 9th, akima sabotaged Heyuri's main server, yukari, by running malicious commands until it fatally crashed, and the data lost was completely unrecoverable. akima claimed it was a hard drive failure. The site is down until lolico restores a backup and kuz makes a news post explaining the situation.<ref>[https://www.heyuri.net/#news19 The news post explaining Heyuri's server crash.]</ref> Spam and server issues continue into the following months, allegedly caused by further sabotage from akima. | |||
Lolico and kuz were prone to conflict and on the 29th of July, kuz gets demoted to a moderator and briefly fired before being rehired on August 23rd, but fighting between the two continues and heats up to the point where kuz threatens to reveal lolico's private information, though he quickly apologizes and asks to be demoted to a mod again, before completely resigning in August 27th.<ref>[http://web.archive.org/web/20200830060916/https://img.heyuri.net/q/imgboard.php?res=2398 kuz announcing his resignation on Heyuri's /q/ board.]</ref> His resignation isn't taken well by some users, and many turn on lolico. In September, kuz exposes akima for intentionally sabotaging the site. Lolico initially disbelieves him, and akima responds by spamming the site and using his ftp access to delete all files and replace the front page with guro and lolico's doxx.<ref>[http://web.archive.org/web/20200906210524/https://heyuri.net/ Heyuri's front page after akima vadalized it.]</ref> Lolico makes a post attacking kuz, exposing him for allegedly threatening him, spamming heyuri with soyjaks and secretly keeping his admin privileges when he demoted himself to a mod.<ref>[http://web.archive.org/web/20200903182956/http://heyuri.net/truth.html Lolico's post calling out kuz.]</ref> He also leaks private discord conversations with kuz.<ref>[http://web.archive.org/web/20200903183017/http://heyuri.net/temp/Direct%20Messages%20-%20Private%20-%20Kuznetsov%20%5B728440201499902022%5D.html The leaked chatlogs.]</ref> Following this, lolico kills Heyuri for several months. A thread about the drama is made on 3chan in which both kuz and lolico make an appearence.<ref>[http://web.archive.org/web/20200922163308/https://3chan.co/b/thread/11696 The 3chan thread about the Heyuri drama in September 2020.]</ref> In the meantime, kuz seizes the heyuri.cf domain and creates strawberryheaven.net to act as a successor to Heyuri, and many refugees settle there or on 3chan.<ref>[https://archive.fo/119D2 Strawberryheaven's front page.]</ref> | |||
[[File:Heyuriback.png|800px|thumb|center|A news post announcing Heyuri's return.<ref>[https://www.heyuri.net/#news24 The news post announcing Heyuri's return.]</ref>]] | [[File:Heyuriback.png|800px|thumb|center|A news post announcing Heyuri's return.<ref>[https://www.heyuri.net/#news24 The news post announcing Heyuri's return.]</ref>]] | ||
In late September, lolico announces that he's planning to bring Heyuri back sometime in the future, and on December 1st the relaunch is confirmed to be occuring under both kuz and lolico, who have supposedly made up their differences.<ref>[http://web.archive.org/web/20200929013712/https://www.heyuri.net/ "Long Live Heyuri!"]</ref> consequently, Straberryheaven is shut down, but in January 2021 it's reopened by kuz for "posterity" before being closed again later that year. Just a couple days after the relaunch, lolico retires, giving kuz ownership of the site. Kuz reveals this in a news post, in which he also says that DCP and the Strawberryheaven team would be stepping in to fulfill his role as developers, though lolico was later rehired by KolymaNET and as of February 2022 works as a developer for Heyuri which brings us to the current state of the site. As of February 2022, akima is listed by the NSS as a public enemy of The Kolyma Network, though he's marked as "handled".<ref>[https://nss.kolyma.org/public-enemies/akima/ akima's entry in the NSS list of public enemies.]</ref> | |||
consequently, | |||
Opinions on kuz are generally positive among those who still use the site, though among older users who left or unrelated onlookers it's more mixed. As for lolico, he also earned his fair share of infamy for the debacle, particularly amongst kuz loyalists who disliked lolico's handling of the situation as well as his management of the site in general compared to kuz. As one user wrote following the September 2020 incident- | Opinions on kuz are generally positive among those who still use the site, though among older users who left or unrelated onlookers it's more mixed. As for lolico, he also earned his fair share of infamy for the debacle, particularly amongst kuz loyalists who disliked lolico's handling of the situation as well as his management of the site in general compared to kuz. As one user wrote following the September 2020 incident- | ||
''"If you really want to know then I'll tell you, but it's nothing you haven't been told before, and most of it's water under the bridge at this point (and hopefully “lessons learned”): You waved off criticism by wrongly assuming that anyone who had developed a negative opinion of you or your actions must be a troll You believed that Heyuri was somehow going to surpass both 4chan and Reddit in size, and even saw that as a desirable outcome, despite proving to be unequipped to manage a site that's only a microscopic fraction of those Contrary to the above belief, you've expressed that Heyuri was better before the main userbase came along - a userbase which was more humorous, more lighthearted, more cancer-free, and more dense with amazing OC creators than any imageboard community I've ever seen. You couldn't have dreamt up a better userbase - rarely ever does any site get to experience such a golden age - and yet you were still unhappy with it, all because we didn't mongle your cock hard enough You got annoyed over people praising and making OC about kuz more often than they did you, even calling it “unfair”, and you threatened to fire everyone or give up Heyuri if it continued. This was despite you being the one who hired kuz to be co-admin and community liaison in your stead, and you rarely ever stepping foot outside of discord to make your presence known on Heyuri (at least beyond reporting that bugs had been fixed from time to time) You showed little to no respect to the people who volunteered their own time and effort to help Heyuri out behind the scenes, and you would frequently fire (or threaten to fire) them for the pettiest of reasons - usually for having the audacity to exercise privileges that you'd given them in the first place. When they would try to do some obvious good (like dealing with repeat rule breakers, running OC contests, creating a positions page to help get more volunteers onboard, or attempting to enable a captcha in the midst of a heavy spam attack), you would shut it down and/or fire them because you hadn't personally reviewed every aspect and given it the greenlight That part was so unbelievably dumb and arrogant that it's worth reiterating: you once fired Heyuri's co-admin/server host because they attempted to enable the captcha during a heavy spam attack without getting your express permission first. Anyone with their head outside their ass would have fired their co-admin for NOT enabling the captcha in that situation, but your head was wedged up there so firmly that I'm surprised you didn't consider selling molds of your head for use as a buttplug To add insult to injury, you'd been warned numerous times before and after that point that having no form of captcha or spam prevention in place on an imageboard in today's internet climate was a massive vunerability, but you chose to either ignore those warnings, or devalued their importance Ultimately, you didn't value the golden egg-laying goose that you'd happened upon, nor did you value much of the contributions made by others to help you rear it, and it ended up dying a violent and perfectly avoidable death Through sheer arrogance, you drove virtually everyone around you away; everyone that is except for notorious thorn in Heyuri's side “faganon”, and a double-agent skiddie who dox'd you and played you like a fool - and who pwned Heyuri beyond repair after you'd conveniently fired all the potential lines of defense for him. And then you had the gall to forgive the skiddie for his actions, while continuing to hold a grudge against your former staff and userbase! That's why I consider the lolico of 3-4 months ago to be an egotistical asshole, and why I hope for yours and everyone else's sake that you've changed since then If you have changed, and you do end up reviving Heyuri with kuz (or something to that effect), I will personally take pole position in the line to suck your cock, and I'll swallow your man juice with pride. Just saying… "'' | ''"If you really want to know then I'll tell you, but it's nothing you haven't been told before, and most of it's water under the bridge at this point (and hopefully “lessons learned”): You waved off criticism by wrongly assuming that anyone who had developed a negative opinion of you or your actions must be a troll You believed that Heyuri was somehow going to surpass both 4chan and Reddit in size, and even saw that as a desirable outcome, despite proving to be unequipped to manage a site that's only a microscopic fraction of those Contrary to the above belief, you've expressed that Heyuri was better before the main userbase came along - a userbase which was more humorous, more lighthearted, more cancer-free, and more dense with amazing OC creators than any imageboard community I've ever seen. You couldn't have dreamt up a better userbase - rarely ever does any site get to experience such a golden age - and yet you were still unhappy with it, all because we didn't mongle your cock hard enough You got annoyed over people praising and making OC about kuz more often than they did you, even calling it “unfair”, and you threatened to fire everyone or give up Heyuri if it continued. This was despite you being the one who hired kuz to be co-admin and community liaison in your stead, and you rarely ever stepping foot outside of discord to make your presence known on Heyuri (at least beyond reporting that bugs had been fixed from time to time) You showed little to no respect to the people who volunteered their own time and effort to help Heyuri out behind the scenes, and you would frequently fire (or threaten to fire) them for the pettiest of reasons - usually for having the audacity to exercise privileges that you'd given them in the first place. When they would try to do some obvious good (like dealing with repeat rule breakers, running OC contests, creating a positions page to help get more volunteers onboard, or attempting to enable a captcha in the midst of a heavy spam attack), you would shut it down and/or fire them because you hadn't personally reviewed every aspect and given it the greenlight That part was so unbelievably dumb and arrogant that it's worth reiterating: you once fired Heyuri's co-admin/server host because they attempted to enable the captcha during a heavy spam attack without getting your express permission first. Anyone with their head outside their ass would have fired their co-admin for NOT enabling the captcha in that situation, but your head was wedged up there so firmly that I'm surprised you didn't consider selling molds of your head for use as a buttplug To add insult to injury, you'd been warned numerous times before and after that point that having no form of captcha or spam prevention in place on an imageboard in today's internet climate was a massive vunerability, but you chose to either ignore those warnings, or devalued their importance Ultimately, you didn't value the golden egg-laying goose that you'd happened upon, nor did you value much of the contributions made by others to help you rear it, and it ended up dying a violent and perfectly avoidable death Through sheer arrogance, you drove virtually everyone around you away; everyone that is except for notorious thorn in Heyuri's side “faganon”, and a double-agent skiddie who dox'd you and played you like a fool - and who pwned Heyuri beyond repair after you'd conveniently fired all the potential lines of defense for him. And then you had the gall to forgive the skiddie for his actions, while continuing to hold a grudge against your former staff and userbase! That's why I consider the lolico of 3-4 months ago to be an egotistical asshole, and why I hope for yours and everyone else's sake that you've changed since then If you have changed, and you do end up reviving Heyuri with kuz (or something to that effect), I will personally take pole position in the line to suck your cock, and I'll swallow your man juice with pride. Just saying… "'' | ||
Kuz himself does not seem to share these negative views on | Kuz himself does not seem to share these negative views on lolico. | ||
===Gurochan/G3=== | ===Gurochan/G3=== | ||
Line 225: | Line 196: | ||
'''G3''' is a set of three sister sites with a focus on lolicon and gore/guro hentai hosted by The Kolyma Network.<ref>[https://web.archive.org/web/20220204211447/https://g3.kolyma.org/ KolymaNET's G3 subdomain.]</ref> It launched in March 14th, 2021. It's comprised of '''Loliboard/Loliach,''' a lolicon/shotacon imageboard, '''Gorechan,''' a gore imageboard and '''Gurochan''', a guro (real-life gore is not allowed) imageboard, which will be the main focus of this section. Loliboard and Gorechan were created by the Kolyma Network. | '''G3''' is a set of three sister sites with a focus on lolicon and gore/guro hentai hosted by The Kolyma Network.<ref>[https://web.archive.org/web/20220204211447/https://g3.kolyma.org/ KolymaNET's G3 subdomain.]</ref> It launched in March 14th, 2021. It's comprised of '''Loliboard/Loliach,''' a lolicon/shotacon imageboard, '''Gorechan,''' a gore imageboard and '''Gurochan''', a guro (real-life gore is not allowed) imageboard, which will be the main focus of this section. Loliboard and Gorechan were created by the Kolyma Network. | ||
Gurochan was founded in 2005, and has gone through many domain changes, reboots and ownership transfers in it's lifetime.<ref>[https://web.archive.org/web/20220221193536/https://guro.cx/faq/ Gurochan's FAQ. Strangely, the front page claims the site was created in 2004, but this FAQ as well as virtually every other source about the site says 2005.]</ref> After several months of being down, the site was brought back on January 29th 2021 by kuz under a new domain - gurochan.ga, after the staff found KolymaNET and agreed to use it's hosting services, and kuz is brought on as a co-admin. The site's structure is restored and on the 31st, a news post confirms that "Gurochan has been absorbed into the greater sphere of imageboards in the Kolyma Network".<ref>[https://web.archive.org/web/20220220183045/https://guro.cx/ The front page of Gurochan.]</ref> In February 6th, it's also decided to switch from TinyIB to kokonotsuba. Gurochan was also incorporated into KolymaBBS prior to it's dissolution. | Gurochan was founded in 2005, and has gone through many domain changes, reboots and ownership transfers in it's lifetime.<ref>[https://web.archive.org/web/20220221193536/https://guro.cx/faq/ Gurochan's FAQ. Strangely, the front page claims the site was created in 2004, but this FAQ as well as virtually every other source about the site says 2005.]</ref> After several months of being down, the site was brought back on January 29th 2021 by kuz under a new domain - gurochan.ga, after the staff found KolymaNET and agreed to use it's hosting services, and kuz is brought on as a co-admin. The site's structure is restored and on the 31st, a news post confirms that "Gurochan has been absorbed into the greater sphere of imageboards in the Kolyma Network".<ref>[https://web.archive.org/web/20220220183045/https://guro.cx/ The front page of Gurochan.]</ref> In February 6th, it's also decided to switch from TinyIB to KolymaNET's own imageboard software: kokonotsuba, which is also used on Heyuri. Gurochan was also incorporated into KolymaBBS prior to it's dissolution. | ||
[[File:Straitjakit.png|250px|thumb|Straitjakit's thread on r/guro.]] | [[File:Straitjakit.png|250px|thumb|Straitjakit's thread on r/guro.]] | ||
On February 13th, following an argument between kuz and the co-admin '''Straitjakit''' in which kuz proposed running ads on Gurochan to which Straitjakit refused, kuz seized ownership of the site, citing Straitjakit's mental instabillity. In his post announcing this on Gurochan's /dis/ board, he also states that the moderators have all been replaced with "Kolyma Network Operatives.<ref>[http://web.archive.org/web/20210226183741/https://img.gurochan.ga/dis/res/11127.html kuz announcing his seizure of Gurochan.]</ref> Straitjakit responds, claiming that kuz trademarked Gurochan's name behind the team's back and that he's planning to create a new website to replace it. He also makes a thread on the subreddit r/guro accusing kuz of going AWOL, datamining users and buying several domains to prevent a replacement site from being made.<ref>[http://web.archive.org/web/20210218084310/https://archive.vn/piVZG Straitjakit's r/guro thread.]</ref> kuz (u/kuzzykins) posts in the thread and the two argue, kuz denies that any user information other than IPs is being collected, explains that the ads he suggested would be guro-related and used to cover the cost of the servers and asserts that he owns "the domain, files and copyright." According to kuz, Straitjakit banned him from the staff channel following their argument about the ads, and Straitjakit's prospect of creating a new Gurochan violates his copyright. Straitjakit further accuses kuz of sending legal threats and threatening to doxx him and seize more of his property, kuz denies the latter two accusations and calls them "potential libel". Opinions in the thread are overwhelmingly pro-Straitjakit, with some users protesting the idea of kuz copyrighting Gurochan's name in the first place. Straitjakit later deleted his reddit and discord accounts. On the 24th, kuz publishes an explanation of the fiasco from his point of view on his personal blog.<ref>[https://web.archive.org/web/20210911043631/https://blog.kuz.lol/posts/022421.php The blogpost kuz made about the Gurochan drama.]</ref> | On February 13th, following an argument between kuz and the co-admin '''Straitjakit''' in which kuz proposed running ads on Gurochan to which Straitjakit refused, kuz seized ownership of the site, citing Straitjakit's mental instabillity. In his post announcing this on Gurochan's /dis/ board, he also states that the moderators have all been replaced with "Kolyma Network Operatives.<ref>[http://web.archive.org/web/20210226183741/https://img.gurochan.ga/dis/res/11127.html kuz announcing his seizure of Gurochan.]</ref> Straitjakit responds, claiming that kuz trademarked Gurochan's name behind the team's back and that he's planning to create a new website to replace it. He also makes a thread on the subreddit r/guro accusing kuz of going AWOL, datamining users and buying several domains to prevent a replacement site from being made.<ref>[http://web.archive.org/web/20210218084310/https://archive.vn/piVZG Straitjakit's r/guro thread.]</ref> kuz (u/kuzzykins) posts in the thread and the two argue, kuz denies that any user information other than IPs is being collected, explains that the ads he suggested would be guro-related and used to cover the cost of the servers and asserts that he owns "the domain, files and copyright." According to kuz, Straitjakit banned him from the staff channel following their argument about the ads, and Straitjakit's prospect of creating a new Gurochan violates his copyright. Straitjakit further accuses kuz of sending legal threats and threatening to doxx him and seize more of his property, kuz denies the latter two accusations and calls them "potential libel". Opinions in the thread are overwhelmingly pro-Straitjakit, with some users protesting the idea of kuz copyrighting Gurochan's name in the first place. Straitjakit later deleted his reddit and discord accounts. On the 24th, kuz publishes an explanation of the fiasco from his point of view on his personal blog.<ref>[https://web.archive.org/web/20210911043631/https://blog.kuz.lol/posts/022421.php The blogpost kuz made about the Gurochan drama.]</ref> | ||
[[File:Dramaticavandal.png|250px|thumb|Encyclopedia Dramatica's Gurochan page after it was vandalized.]] | [[File:Dramaticavandal.png|250px|thumb|Encyclopedia Dramatica's Gurochan page after it was vandalized.]] | ||
In June, kuz announced that he will be handing Gurochan over to another owner due to legal issues he's had with Gurochan's content, the new owner being Kaguya, who hosts a short Q&A on /dis/.<ref>[https://web.archive.org/web/20220222110948/https://dis.guro.cx/dis/koko.php?res=445 Kaguya's Q&A on /dis/.]</ref> | In June, kuz announced that he will be handing Gurochan over to another owner due to legal issues he's had with Gurochan's content, the new owner being '''"Kutay Demir"''', better known as '''Kaguya''', another KolymaNET official who also serves as a moderator on Heyuri.<ref>[http://web.archive.org/web/20220222111154/https://img.heyuri.net/q/koko.php?res=61064 An example of Kaguya posting with his mod capcode on Heyuri.]</ref> Kaguya hosts a short Q&A on /dis/.<ref>[https://web.archive.org/web/20220222110948/https://dis.guro.cx/dis/koko.php?res=445 Kaguya's Q&A on /dis/.]</ref> | ||
On July 7th, Encyclopedia Dramatica's page on Gurochan was vandalized with claims that the site is infected with malware. The vandalized page also called kuz a "Vodka-swilling Swindler" and a "notorious kike".<ref>[https://archive.is/UDmhj The vandalized version of the ED page on Gurochan.]</ref><ref>[http://web.archive.org/web/20220222112540/https://encyclopediadramatica.online/index.php?title=Gurochan The proper version of ED's page on Gurochan.]</ref> News of the vandalism is posted to KolymaNET's news aggregator.<ref>[https://web.archive.org/web/https://live.kolyma.org/news4vep/koko.php?res=64&q=65 The news post on KolymaNET's website about the ED vandalism.]</ref> Straitjakit (or someone pretending to be him), presumably the vandal, posts on /dis/,<ref>[http://web.archive.org/web/20211122173216/https://dis.guro.cx/dis/koko.php?res=635 "Straitjakit's" thread on /dis/.]</ref> mocking Kaguya and linking another /dis/ thread claiming that discord and reddit are where most of the guro community is.<ref>[http://web.archive.org/web/20211120190231/https://dis.guro.cx/dis/koko.php?res=632 The /dis/ thread "Straitjakit" linked.]</ref> The vandalism is brought up, and the OP recieves a ban message linking to Straitjakit's page on the Gurochan wiki.<ref>[http://web.archive.org/web/20211207103213/https://wiki.guro.cx/index.php/Straitjakit Straitjakit's page on the Gurochan wiki.]</ref> As of February 2022, Straitjakit has an entry on the NSS list of public enemies.<ref>[https://archive.ph/fE2WH Straitjakit's entry on the NSS list of public enemies.]</ref> | On July 7th, Encyclopedia Dramatica's page on Gurochan was vandalized with claims that the site is infected with malware. The vandalized page also called kuz a "Vodka-swilling Swindler" and a "notorious kike".<ref>[https://archive.is/UDmhj The vandalized version of the ED page on Gurochan.]</ref><ref>[http://web.archive.org/web/20220222112540/https://encyclopediadramatica.online/index.php?title=Gurochan The proper version of ED's page on Gurochan.]</ref> News of the vandalism is posted to KolymaNET's news aggregator.<ref>[https://web.archive.org/web/https://live.kolyma.org/news4vep/koko.php?res=64&q=65 The news post on KolymaNET's website about the ED vandalism.]</ref> Straitjakit (or someone pretending to be him), presumably the vandal, posts on /dis/,<ref>[http://web.archive.org/web/20211122173216/https://dis.guro.cx/dis/koko.php?res=635 "Straitjakit's" thread on /dis/.]</ref> mocking Kaguya and linking another /dis/ thread claiming that discord and reddit are where most of the guro community is.<ref>[http://web.archive.org/web/20211120190231/https://dis.guro.cx/dis/koko.php?res=632 The /dis/ thread "Straitjakit" linked.]</ref> The vandalism is brought up, and the OP recieves a ban message linking to Straitjakit's page on the Gurochan wiki.<ref>[http://web.archive.org/web/20211207103213/https://wiki.guro.cx/index.php/Straitjakit Straitjakit's page on the Gurochan wiki.]</ref> As of February 2022, Straitjakit has an entry on the NSS list of public enemies.<ref>[https://archive.ph/fE2WH Straitjakit's entry on the NSS list of public enemies.]</ref> | ||
In December, a news post by Kaguya announced that Gurochan would be migrated to another host due to downtime, but the decision was reversed, and the site continues to use KolymaNET's hosting. | In December, a news post by Kaguya announced that Gurochan would be migrated to another host due to downtime, but the decision was reversed, and the site continues to use KolymaNET's hosting. | ||
Line 240: | Line 211: | ||
*When Maki tried starting a webhosting service called "Makibox", kuz posted a warning on his personal blog telling people that the service is crap and that they shouldn't use it.<ref>[https://archive.vn/4n0YW The blogpost about Makibox.]</ref> | *When Maki tried starting a webhosting service called "Makibox", kuz posted a warning on his personal blog telling people that the service is crap and that they shouldn't use it.<ref>[https://archive.vn/4n0YW The blogpost about Makibox.]</ref> | ||
*Maki paid for a DDoS attack on KolymaNET's servers. | *Maki paid for a DDoS attack on KolymaNET's servers. | ||
*kuz placed a bounty on Maki, offering 1k USD for any information that can be used to get Maki arrested. This bounty has | *kuz placed a bounty on Maki, offering 1k USD for any information that can be used to get Maki arrested. This bounty has since been claimed.<ref>[https://web.archive.org/web/20210314040236/srv.kolyma.org/bnt/2021/3/9/bounty/computer-hacking-fraud/maki_lolifox_64chan.txt The bounty placed on Maki.]</ref> | ||
*Lolifox got spammed with CP and gore. | *Lolifox got spammed with CP and gore. | ||
*Months later, an official KolymaNET statement mentioned that the company used legal action against "a group that attempted to DDoS out network", possibly referring to Maki.<ref>[https://web.archive.org/web/20210703155525/www.kolyma.org/statements/Dismissing%20Rumors%20of%20Aggression The KolymaNET statement that mentions legal action against a DDoSer.]</ref> | *Months later, an official KolymaNET statement mentioned that the company used legal action against "a group that attempted to DDoS out network", possibly referring to Maki.<ref>[https://web.archive.org/web/20210703155525/www.kolyma.org/statements/Dismissing%20Rumors%20of%20Aggression The KolymaNET statement that mentions legal action against a DDoSer.]</ref> | ||
*In the blogpost in which kuz announced the dissolution of KolymaBBS, he also mentioned that several employees have been purged for "the | *In the blogpost in which kuz announced the dissolution of KolymaBBS, he also mentioned that several employees have been purged for "the lolifox attempted-seizure".<ref>[https://live.kolyma.org/news4vep/koko.php?res=74&q=74 A news post on KolymaNET's website about the event. See also - citation 40.]</ref> | ||
*Maki has an entry on the NSS list of public enemies, but it mentions that he's "deemed no longer a threat."<ref>[https://archive.ph/xEVdP Maki's entry on the NSS list of public enemies.]</ref> | *Maki has an entry on the NSS list of public enemies, but it mentions that he's "deemed no longer a threat."<ref>[https://archive.ph/xEVdP Maki's entry on the NSS list of public enemies.]</ref> | ||
Line 257: | Line 228: | ||
*Tokiko gets placed in the NSS list of public enemies.<ref>[https://archive.fo/3jruY Tokiko's NSS entry.]</ref> | *Tokiko gets placed in the NSS list of public enemies.<ref>[https://archive.fo/3jruY Tokiko's NSS entry.]</ref> | ||
*ripirc.org gets placed in the NSS dangerous websites list.<ref>[https://web.archive.org/web/20220216213533/https://nss.kolyma.org/dangerous-websites/ripirc/ ripirc's entry in the NSS dangerous websites list.]</ref> | *ripirc.org gets placed in the NSS dangerous websites list.<ref>[https://web.archive.org/web/20220216213533/https://nss.kolyma.org/dangerous-websites/ripirc/ ripirc's entry in the NSS dangerous websites list.]</ref> | ||
*A user on a KolymaNET imageboard puts up fliers in Tokiko's town calling him a pedophile.<ref>[https://web.archive.org/web/20210831055403/https://jun.kolyma.org/m/koko.php?res=177 A thread in which these fliers were posted.]</ref> | *A user on a KolymaNET imageboard puts up fliers in Tokiko's town calling him a pedophile.<ref>[https://web.archive.org/web/20210831055403/https://jun.kolyma.org/m/koko.php?res=177 A thread in which these fliers were posted.]</ref> | ||
*Multichan gets raided with pro kuz/anti Multichan threads.<ref>[https://archive.is/AHqry An archived view of the raid.]</ref> | *Multichan gets raided with pro kuz/anti Multichan threads.<ref>[https://archive.is/AHqry An archived view of the raid.]</ref> | ||
Line 267: | Line 237: | ||
===soyjak.party=== | ===soyjak.party=== | ||
[[File:Ty.png|250px|thumb|soyjak.party's front page.]] | [[File:Ty.png|250px|thumb|soyjak.party's front page.]] | ||
'''soyjak.party''', often shortened to "the party", is a soyjak themed imageboard spun off from 4chan's /qa/ board.<ref>[https://soyjak.party/ soyjak.party.]</ref> It was created in September 2020 by a guy called '''Soot''',<ref>[https://web.archive.org/web/20220219134710/https://wiki.soyjak.party/index.php?title=Soot The party's wiki page about Soot.]</ref> who advertised it in a thread on /qa/.<ref>[https://desuarchive.org/qa/thread/3484141 Soot's thread first shilling the party.]</ref> The vast majority of activity is concentrated on the /soy/ board. The site has it's own wiki and a booru for soyjaks. kuz posted on the party fairly often with his tripcode, sometimes just to shitpost.<ref>[http://web.archive.org/web/20220223144337/https://wiki.soyjak.party/index.php?title=Kuz kuz's page on the soyjak.party wiki.]</ref> The default name on the site is "Chud" instead of "Anonymous". | '''soyjak.party''', often shortened to "the party", is a soyjak themed imageboard spun off from 4chan's /qa/ board.<ref>[https://soyjak.party/ soyjak.party.]</ref> It was created in September 2020 by a guy called '''Soot''',<ref>[https://web.archive.org/web/20220219134710/https://wiki.soyjak.party/index.php?title=Soot The party's wiki page about Soot.]</ref> who advertised it in a thread on /qa/.<ref>[https://desuarchive.org/qa/thread/3484141 Soot's thread first shilling the party.]</ref> The vast majority of activity is concentrated on the /soy/ board. The site has it's own wiki and a booru for soyjaks. kuz posted on the party fairly often with his tripcode, sometimes just to shitpost.<ref>[http://web.archive.org/web/20220223144337/https://wiki.soyjak.party/index.php?title=Kuz kuz's page on the soyjak.party wiki.]</ref> The default name on the site is "Chud" instead of "Anonymous". | ||
Line 276: | Line 245: | ||
One user then pointed out something strange - The IP address that soyjak.party points to changed on June 22nd, the same day kuz posted his offer on /suggest/. Another user pointed out that the e-mail service used for [email protected] is Yandex, a Russian company. Soot claims he used Yandex since the site's creation and locks the thread. kuz posts in the thread before it gets locked, simply saying "yikes...". Another thread on the matter is made on /soy/ in which a user adds that two wiki mods were demoded shorty after kuz made his offer.<ref>[https://web.archive.org/web/20210710023759/https://soyjak.party/soy//res/128635.html The thread on /soy/ about the party potential having been sold.]</ref> Soot asserts that the IP change occurred because he changed hosts to improve performance, that the site is worthless and that he never talked to kuz at all. kuz posts in the thread, renewing his offer and asserting that he's being serious about buying the site. Despite this, Soot was added to the NSS list of public enemies and marked as "handled", though his entry specifies that he's not a "kolyma-specific enemy". The entry was later removed from the list entirely.<ref>[https://archive.fo/6OOya Soot's name on the NSS public enemies list.]</ref><ref>[https://archive.fo/2pvpR Soot's entry.]</ref> | One user then pointed out something strange - The IP address that soyjak.party points to changed on June 22nd, the same day kuz posted his offer on /suggest/. Another user pointed out that the e-mail service used for [email protected] is Yandex, a Russian company. Soot claims he used Yandex since the site's creation and locks the thread. kuz posts in the thread before it gets locked, simply saying "yikes...". Another thread on the matter is made on /soy/ in which a user adds that two wiki mods were demoded shorty after kuz made his offer.<ref>[https://web.archive.org/web/20210710023759/https://soyjak.party/soy//res/128635.html The thread on /soy/ about the party potential having been sold.]</ref> Soot asserts that the IP change occurred because he changed hosts to improve performance, that the site is worthless and that he never talked to kuz at all. kuz posts in the thread, renewing his offer and asserting that he's being serious about buying the site. Despite this, Soot was added to the NSS list of public enemies and marked as "handled", though his entry specifies that he's not a "kolyma-specific enemy". The entry was later removed from the list entirely.<ref>[https://archive.fo/6OOya Soot's name on the NSS public enemies list.]</ref><ref>[https://archive.fo/2pvpR Soot's entry.]</ref> | ||
On July 9th, kuz's tripcode, '''!WezrG/5mtU,''' was cracked and posted on /soy/ in a thread calling for a mass raid on KolymaNET imageboards while using kuz's trip - several sites were briefly taken down a result.<ref>[http://web.archive.org/web/20210711071346/https://soyjak.party/soy//res/131813.html The soyjak.party thread about the raid.]</ref><ref>[https://live.kolyma.org/news4vep/koko.php?res=63 A news post about the soyjak.party raid.]</ref> kuz later switched | On July 9th, kuz's tripcode, '''!WezrG/5mtU,''' was cracked and posted on /soy/ in a thread calling for a mass raid on KolymaNET imageboards while using kuz's trip - several sites were briefly taken down a result.<ref>[http://web.archive.org/web/20210711071346/https://soyjak.party/soy//res/131813.html The soyjak.party thread about the raid.]</ref><ref>[https://live.kolyma.org/news4vep/koko.php?res=63 A news post about the soyjak.party raid.]</ref> kuz later switched to his current tripcode - '''!netsovkMgo.''' | ||
A debate occurred in October when a user suggested adding a gemvote/coalvote system to the party (essentially likes and dislikes) which ended in many users ironically demanding the feature from soot, which kuz supported in an open letter to Soot where he also asks to be modded.<ref>[http://web.archive.org/web/20211022192644/https://kuz.lol/open-letter-to-soot.html kuz's open letter to Soot.]</ref> Eventually, a user comes in with their own soyjak imageboard, '''soyjaks.net''', to which he promised to add this feature.<ref>[http://web.archive.org/web/20211025190804/http://soyjaks.net/ soyjaks.net.]</ref> Eventually, he did.<ref>[http://web.archive.org/web/20211101104130/https://soyjaks.net/ soyjaks.net after the gemvote/coalvote system was added.]</ref> However, it didn't take long before users noticed that the site was hosted by KolymaNET, one clue to that being that the site used kokonotsuba, and kuz had to come out and admit he was the owner of the site. Drama ensued on the party and the site was taken down, it's front page being replaced with short text messages and eventually the "GO FUCK YOURSELF" Hatsune Miku gif.<ref>[http://web.archive.org/web/20211224050855/https://soyjaks.net/ GO FUCK YOURSELF 2]</ref> On December 29th, due to a large scale DDoS attack which kuz believes is coming from the party, he posts on his personal blog that he's willing to cease his involvement with the site if the attacks stop.<ref>[https://archive.is/m1ufi kuz's blogpost about the DDoS.]</ref> | A debate occurred in October when a user suggested adding a gemvote/coalvote system to the party (essentially likes and dislikes) which ended in many users ironically demanding the feature from soot, which kuz supported in an open letter to Soot where he also asks to be modded.<ref>[http://web.archive.org/web/20211022192644/https://kuz.lol/open-letter-to-soot.html kuz's open letter to Soot.]</ref> Eventually, a user comes in with their own soyjak imageboard, '''soyjaks.net''', to which he promised to add this feature.<ref>[http://web.archive.org/web/20211025190804/http://soyjaks.net/ soyjaks.net.]</ref> Eventually, he did.<ref>[http://web.archive.org/web/20211101104130/https://soyjaks.net/ soyjaks.net after the gemvote/coalvote system was added.]</ref> However, it didn't take long before users noticed that the site was hosted by KolymaNET, one clue to that being that the site used kokonotsuba, and kuz had to come out and admit he was the owner of the site. Drama ensued on the party and the site was taken down, it's front page being replaced with short text messages and eventually the "GO FUCK YOURSELF" Hatsune Miku gif.<ref>[http://web.archive.org/web/20211224050855/https://soyjaks.net/ GO FUCK YOURSELF 2]</ref> On December 29th, due to a large scale DDoS attack which kuz believes is coming from the party, he posts on his personal blog that he's willing to cease his involvement with the site if the attacks stop.<ref>[https://archive.is/m1ufi kuz's blogpost about the DDoS.]</ref> | ||
Line 282: | Line 251: | ||
CP spam on the party continued and intensified as the months went by and became a larger and larger topic of discussion due to it's frequency, and users grew upset by Soot's lack of communication and failure to handle the issue. Anons often requested Soot to ban TOR as a way of reducing the spam, but instead individual nodes were banned with no word from Soot on the possibility of banning TOR posting entirely. soyjak.party's rules state that part of the reason TOR and VPNs are allowed is various conspiracies about the site being a KolymaNET datamining honeypot, some users speculated that Soot's unwillingness to ban TOR stemmed from him not wanting to reignite those accusation even if they were mostly a joke.<ref>[https://web.archive.org/web/20211224072405/https://soyjak.party/rules.html soyjak.party's rules.]</ref><ref>[https://archive.ph/oDT5e A thread from December in which Soot implied his lack of interaction is a result of the KolmyaNET buyout conspiracy.]</ref> | CP spam on the party continued and intensified as the months went by and became a larger and larger topic of discussion due to it's frequency, and users grew upset by Soot's lack of communication and failure to handle the issue. Anons often requested Soot to ban TOR as a way of reducing the spam, but instead individual nodes were banned with no word from Soot on the possibility of banning TOR posting entirely. soyjak.party's rules state that part of the reason TOR and VPNs are allowed is various conspiracies about the site being a KolymaNET datamining honeypot, some users speculated that Soot's unwillingness to ban TOR stemmed from him not wanting to reignite those accusation even if they were mostly a joke.<ref>[https://web.archive.org/web/20211224072405/https://soyjak.party/rules.html soyjak.party's rules.]</ref><ref>[https://archive.ph/oDT5e A thread from December in which Soot implied his lack of interaction is a result of the KolmyaNET buyout conspiracy.]</ref> | ||
The CP issue reached it's (first) breaking point On January 8th 2022, when soyjak.party was taken down for over 20 hours. Many refugees flooded 4chan's /bant/ to wait it out, and speculated that the downtime is the result of a CP report. This theory was confirmed by Soot when the site came back up the next day.<ref>[http://web.archive.org/web/20220110021737/https://soyjak.party/soy//res/276233.html Soot confirming the downtime was due to CP.]</ref> Speculation that kuz is behind the spam, possibly to pressure Soot into using KolymaNET's services continue. The same thing happens again just a week later on January 14th, and this time refugees flee to a bunker on 9chan.tw, in which the admin of a soyjak.party Telegram channel claims data got wiped and Soot is restoring a 5 months old backup.<ref>[https://archive.fo/LkFRv The 9chan thread.]</ref> CP is posted on the bunker as well. While the site was down, one of soyjak.party's mods spammed the site's booru, Onionsbooru (which itself was replacement to the defunct Soybooru), with /pol/ memes before shutting it down permanently. It was later replaced by a third booru. The site was back up on the 15th, rebooted not from 5 months ago but from November, losing tens of thousands of posts as a result. Soot remained silent, and the mods restored the missing posts to the post counter over the next two weeks.<ref>[http://web.archive.org/web/20220123052100/https://soyjak.party/soy//res/249468.html A thread in which a mod clarifies why thousands of posts were suddenly added to the post counter.]</ref> | The CP issue reached it's (first) breaking point On January 8th 2022, when soyjak.party was taken down for over 20 hours. Many refugees flooded 4chan's /bant/ to wait it out, and speculated that the downtime is the result of a CP report. This theory was confirmed by Soot when the site came back up the next day.<ref>[http://web.archive.org/web/20220110021737/https://soyjak.party/soy//res/276233.html Soot confirming the downtime was due to CP.]</ref> Speculation that kuz is behind the spam, possibly to pressure Soot into using KolymaNET's services continue. The same thing happens again just a week later on January 14th, and this time refugees flee to a bunker on 9chan.tw, in which the admin of a soyjak.party Telegram channel claims data got wiped and Soot is restoring a 5 months old backup.<ref>[https://archive.fo/LkFRv The 9chan thread.]</ref> CP is posted on the bunker as well. While the site was down, one of soyjak.party's mods spammed the site's booru, Onionsbooru (which itself was replacement to the defunct Soybooru), with /pol/ memes before shutting it down permanently. It was later replaced by a third booru. The site was back up on the 15th, rebooted not from 5 months ago but from November, losing tens of thousands of posts as a result. Soot remained silent, and the mods restored the missing posts to the post counter over the next two weeks.<ref>[http://web.archive.org/web/20220123052100/https://soyjak.party/soy//res/249468.html A thread in which a mod clarifies why thousands of posts were suddenly added to the post counter.]</ref> | ||
[[File:Kuzp.png|250px|thumb|An exchange that | [[File:Kuzp.png|250px|thumb|An exchange that occured between kuz and a party user regarding CP.]] | ||
By this point many were sick of Soot and his management of the site, and some started to label themselves as kuz supporters. On January 25th, kuz leaked email exchanges between him and soot in which Soot actually considered selling the site for 600$ in bitcoin, but eventually changed his mind. kuz asks Soot to apologize for "betraying" him and to wordfilter his name. kuz also sent Soot an email requesting the IPs of several posters.<ref>[http://web.archive.org/web/20220126060507/http://soyjak.party/soy//res/295362.html The thread in which kuz leaked the emails regarding the sale.]</ref> The thread blew up and similarly did the catalog, it wasn't long before the board was hit by one of the hardest ever waves of CP due to the recaptcha having been recently removed, and than reenabled as a result. Users point out the correlation between kuz's appearances and CP being spammed, which kuz claimed is deliberately done by the CP spammer(s) in an attempt to frame him. kuz makes additional offers to help Soot deal with the problem. The party remains in disarray for many hours. In the following few days, CP begins being disguised in regular soyjak gifs/videos, causing more chaos. After a particular mp4 that starts with a dancing swedejak and than switches to a baby rape video is posted several times, users grow even more unsatisfied with Soot's handling of the site. | By this point many were sick of Soot and his management of the site, and some started to label themselves as kuz supporters. On January 25th, kuz leaked email exchanges between him and soot in which Soot actually considered selling the site for 600$ in bitcoin, but eventually changed his mind. kuz asks Soot to apologize for "betraying" him and to wordfilter his name. kuz also sent Soot an email requesting the IPs of several posters.<ref>[http://web.archive.org/web/20220126060507/http://soyjak.party/soy//res/295362.html The thread in which kuz leaked the emails regarding the sale.]</ref> The thread blew up and similarly did the catalog, it wasn't long before the board was hit by one of the hardest ever waves of CP due to the recaptcha having been recently removed, and than reenabled as a result. Users point out the correlation between kuz's appearances and CP being spammed, which kuz claimed is deliberately done by the CP spammer(s) in an attempt to frame him. kuz makes additional offers to help Soot deal with the problem. The party remains in disarray for many hours. In the following few days, CP begins being disguised in regular soyjak gifs/videos, causing more chaos. After a particular mp4 that starts with a dancing swedejak and than switches to a baby rape video is posted several times, users grow even more unsatisfied with Soot's handling of the site. | ||
Line 311: | Line 279: | ||
On March 23rd, /soy/'s 400000 GET is taken by a kuz thread which gets deleted shortly after, either by a janitor/mod or by the poster.<ref>[http://web.archive.org/web/20220323041702/https://soyjak.party/soy//res/400000.html The 400000 GET on /soy/, the full thread wasn't archived in time.]</ref> kuz posts in the thread, denying accusations that he DDoSed the site to steal the GET. He also responds to another thread about the GET and makes a couple threads of his own, causing a new flood of drama threads and CP for the next few hours.<ref>[http://web.archive.org/web/20220323103646/https://soyjak.party/soy//res/400178.html A thread about the GET getting deleted.]</ref><ref>[http://web.archive.org/web/20220323104156/https://soyjak.party/soy//res/399732.html A thread kuz made right before the GET.]</ref><ref>[http://web.archive.org/web/20220323104410/https://soyjak.party/soy//res/400314.html Another thread kuz made after the GET.]</ref><ref>[http://web.archive.org/web/20220323104621/https://soyjak.party/soy//res/400407.html kuz's last thread following the GET.]</ref> | On March 23rd, /soy/'s 400000 GET is taken by a kuz thread which gets deleted shortly after, either by a janitor/mod or by the poster.<ref>[http://web.archive.org/web/20220323041702/https://soyjak.party/soy//res/400000.html The 400000 GET on /soy/, the full thread wasn't archived in time.]</ref> kuz posts in the thread, denying accusations that he DDoSed the site to steal the GET. He also responds to another thread about the GET and makes a couple threads of his own, causing a new flood of drama threads and CP for the next few hours.<ref>[http://web.archive.org/web/20220323103646/https://soyjak.party/soy//res/400178.html A thread about the GET getting deleted.]</ref><ref>[http://web.archive.org/web/20220323104156/https://soyjak.party/soy//res/399732.html A thread kuz made right before the GET.]</ref><ref>[http://web.archive.org/web/20220323104410/https://soyjak.party/soy//res/400314.html Another thread kuz made after the GET.]</ref><ref>[http://web.archive.org/web/20220323104621/https://soyjak.party/soy//res/400407.html kuz's last thread following the GET.]</ref> | ||
===Vidlii=== | ===Vidlii=== | ||
Line 318: | Line 284: | ||
'''Vidlii''' is a video sharing website launched in 2015 by '''Jan'''.<ref>[http://web.archive.org/web/20220223180616/https://altipedia.fandom.com/wiki/Jan Jan's page on the altipedia.]</ref> It's design invokes youtube in the 2000's.<ref>[https://web.archive.org/web/20220223075215/https://www.vidlii.com/ Vidlii.com.]</ref> | '''Vidlii''' is a video sharing website launched in 2015 by '''Jan'''.<ref>[http://web.archive.org/web/20220223180616/https://altipedia.fandom.com/wiki/Jan Jan's page on the altipedia.]</ref> It's design invokes youtube in the 2000's.<ref>[https://web.archive.org/web/20220223075215/https://www.vidlii.com/ Vidlii.com.]</ref> | ||
The site was struggling in the 2020's and in January 2022, it's announced that the site will become a read-only archive, to many people's dismay.<ref>[http://web.archive.org/web/20220131134817/https://www.vidlii.com/vidlii_future The announcement that Vidlii will become read-only.]</ref> On February 4th, kuz makes a thread on soyjak.party claiming he bought "a video sharing site, a big one" for "10k in bitcoin". Shortly after that day, the news is made official on KNN,<ref>[https://web.archive.org/web/20220223181541/https://live.kolyma.org/newsplus/koko.php?res=172 The news post about kuz buying Vidlii.]</ref> accompanied by an announcement on Vidlii about the change in ownership.<ref>[https://web.archive.org/web/20220223180825/https://www.vidlii.com/vidlii_future The announcement on Vidlii about the new owner.]</ref> The announcement says that Vidlii will NOT become read-only, and will be hosted by KolymaNET in the future. The new owner is not kuz but a guy called "lolwut".<ref>[http://web.archive.org/web/20220223182513/https://www.vidlii.com/user/lolwut lolwut's Vidlii profile.]</ref> Later that month, the channel "CL21" uploads an interview with both kuz and lolwut, conducted in discord.<ref>[http://web.archive.org/web/20220223182736/https://www.vidlii.com/watch?v=gKRB3I5rBLG&pl=i62xwEhZWKs The interview with kuz and lolwut.]</ref> | The site was struggling in the 2020's and in January 2022, it's announced that the site will become a read-only archive, to many people's dismay.<ref>[http://web.archive.org/web/20220131134817/https://www.vidlii.com/vidlii_future The announcement that Vidlii will become read-only.]</ref> On February 4th, kuz makes a thread on soyjak.party claiming he bought "a video sharing site, a big one" for "10k in bitcoin". Shortly after that day, the news is made official on KNN,<ref>[https://web.archive.org/web/20220223181541/https://live.kolyma.org/newsplus/koko.php?res=172 The news post about kuz buying Vidlii.]</ref> accompanied by an announcement on Vidlii about the change in ownership.<ref>[https://web.archive.org/web/20220223180825/https://www.vidlii.com/vidlii_future The announcement on Vidlii about the new owner.]</ref> The announcement says that Vidlii will NOT become read-only, and will be hosted by KolymaNET in the future. The new owner is not kuz but a guy called "lolwut".<ref>[http://web.archive.org/web/20220223182513/https://www.vidlii.com/user/lolwut lolwut's Vidlii profile.]</ref> Later that month, the channel "CL21" uploads an interview with both kuz and lolwut, conducted in discord.<ref>[http://web.archive.org/web/20220223182736/https://www.vidlii.com/watch?v=gKRB3I5rBLG&pl=i62xwEhZWKs The interview with kuz and lolwut.]</ref> | ||
===Additional websites=== | ===Additional websites=== | ||
Line 326: | Line 290: | ||
*'''kissu.moe''' is an anime/moe themed imageboard spun off from 4chan's /qa/ board in 2018, created by '''"Kai Nicoll-Griffith",''' better known as '''"Verniy"'''. After getting sick of kuz drama discussed on the site, the owner wordfiltered "kuz" to "that guy". Kissu has an entry on the NSS dangerous websites list.<ref>[https://archive.fo/rUExt kissu's entry on the NSS dangerous websites list.]</ref> | *'''kissu.moe''' is an anime/moe themed imageboard spun off from 4chan's /qa/ board in 2018, created by '''"Kai Nicoll-Griffith",''' better known as '''"Verniy"'''. After getting sick of kuz drama discussed on the site, the owner wordfiltered "kuz" to "that guy". Kissu has an entry on the NSS dangerous websites list.<ref>[https://archive.fo/rUExt kissu's entry on the NSS dangerous websites list.]</ref> | ||
*'''Lainchan''' is a technology themed imageboard created on April 20th of 2014 by '''"Kalyx"''', though he's no longer the owner. kuz posted on Lainchan several times, offering his services. | *'''Lainchan''' is a technology themed imageboard created on April 20th of 2014 by '''"Kalyx"''', though he's no longer the owner. kuz posted on Lainchan several times, offering his services. | ||
==Citations== | ==Citations== |