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 282: Line 282:
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>


[[File:kuz_w_cunny.jpg|250px|thumb|Kuz with a little girl - suspicious...]]
[[File:kuz_w_cunny.jpg|270px|thumb|Kuz with a little girl - suspicious...]]
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 occurred between kuz and a party user regarding CP.]]
[[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.


Please note that all contributions to Bibliotheca Anonoma are considered to be released under the Creative Commons Attribution-ShareAlike (see Bibliotheca Anonoma:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!
Cancel Editing help (opens in new window)

Templates used on this page: