- Joined
- Nov 14, 2012
As discussed earlier this month in The Gay Pedophile at the Gates, a persistent threat which has been targeting Soyjak Party and 4chan for years has started attacking the Kiwi Farms. His stated purpose is to kill these websites by forcing them to implement anti-bot mechanisms which are so invasive it reduces how willing a user is to post. That's it. He is posting child porn on websites to reduce their PPH. All attempts to get police to do something about him have been unsuccessful. I have contacted journalists, I have contacted local and federal law enforcement, I have supplied enormously detailed dossiers to them and I have not heard back from anyone.
The Kiwi Farms has a way to deal with this problem that other sites don't have: I can close registration. Soyjak and 4chan don't have the luxury of this, they just have to learn to live with child pornography. 4chan takes extraordinary measures in reducing spam by blocking all VPNs. Even that doesn't help because, as stated in the previous thread, the pedophile has access to Residential VPNs ('free' VPNs that are free because they sell your home IP to botnets, allowing them to masquerade as domestic broadband traffic).
So the law's the law but I'm one guy. How can I possibly be expected to report thousands of posts by thousands of accounts by hand manually? Surely I can't just build my own enterprise level reporting tool for compliance with the world's most obscure law, right...?
BROUGHT TO YOU BY KIWI GOLD™ MEMBERS (LEARN MORE)
I have built my own enterprise level reporting tool for compliance with the world's more obscure law. Paid for by the brave users who have bothered to set up billpay. Now that I have steady income I can sit down and actually dedicate myself to 8 hours of programming a day, every day, for a month straight, to get things done.
It will probably be deployed tomorrow. I am doing very extensive bugtesting before rolling it out. It's the largest mod I've ever made for XF, probably the most complicated project I've done in years.
Features of this new mod include...
1. A report button in the top-right. This allows you to report posts without scrolling past them.
2. A 4chan-style emergency report feature. Do not abuse this. It will be limited to more senior users.
3. Emergency reports immediately hide posts from public.
And that's it. I can now deal with thousands of accounts spamming thousands of images faster than they can be made. I can shut off registration at a button click.
Data soyentists have submitted to me a concept for a novel captcha being tested already by big companies which will assist in defeating automated captcha solvers and force the attacker to pay for indian manual solves.
After this I will be confident enough to open registrations again.
I have an idea for assisting in auto-moderation. It's a really clever idea and I do not want to share details. However, it does require more computer.
The word of God is going around the world and your help is so greatly appreciated. What we need now is an enterprise grade surplus supercomputer able to process six hundred billion points of data so we can stomp on chomos. For Jesus. Send money now
If you have access to an NVIDIA SXM board with V100s and you want to donate it to USIPS, read here. If you want to help, set up billpay or donate by crypto. $20/mo from about 35 more people would allow me to finance a big purchase over a year.
I know it's the Christmas season and shit so if you want to hold off that's no worries, this will be an early 2026 thing. I can develop the project on my computer GPU in the mean time.
My project with the NCMEC report for XF2 is already public as part of USIPS. If I have the resources, I can deploy the captcha and AI as a service via USIPS to other at-risk sites such as the Soyjak Party or even 4chan. I'm in contact with the 4chan guys and they're pretty limited on resources but I am insane and can do anything I want so I want to build a nice big tent. That's what USIPS is for, basically.
Yeah that's basically it. Happy Thanksgiving.
Big ups to the gold boys and their support.
The Kiwi Farms has a way to deal with this problem that other sites don't have: I can close registration. Soyjak and 4chan don't have the luxury of this, they just have to learn to live with child pornography. 4chan takes extraordinary measures in reducing spam by blocking all VPNs. Even that doesn't help because, as stated in the previous thread, the pedophile has access to Residential VPNs ('free' VPNs that are free because they sell your home IP to botnets, allowing them to masquerade as domestic broadband traffic).
Step 1. Reduce Legal Liabilities
There's a little-known law called 18 U.S. Code § 2258A. It states that if CSAM is posted to your website, you (as an ESP) must report it to the 501(C)(3), the National Center For Missing and Exploited Children (NCMEC). This might surprise you because guess what? I've never heard of it either! No major software suite seems to do it, and quite frankly the number of ESPs in their annual reports that actually bother is shockingly small.So the law's the law but I'm one guy. How can I possibly be expected to report thousands of posts by thousands of accounts by hand manually? Surely I can't just build my own enterprise level reporting tool for compliance with the world's most obscure law, right...?
BROUGHT TO YOU BY KIWI GOLD™ MEMBERS (LEARN MORE)
I have built my own enterprise level reporting tool for compliance with the world's more obscure law. Paid for by the brave users who have bothered to set up billpay. Now that I have steady income I can sit down and actually dedicate myself to 8 hours of programming a day, every day, for a month straight, to get things done.
It will probably be deployed tomorrow. I am doing very extensive bugtesting before rolling it out. It's the largest mod I've ever made for XF, probably the most complicated project I've done in years.
Features of this new mod include...
1. A report button in the top-right. This allows you to report posts without scrolling past them.
2. A 4chan-style emergency report feature. Do not abuse this. It will be limited to more senior users.
3. Emergency reports immediately hide posts from public.
4. Two ways for responsible mods to flag as CSAM, either in the mod queue or the report queue.
5. Reports handled in this way instantly clean up the account, put it into a frozen state, and create an incident in the admin backend.
6. The backend is where most of the effort went and contains panic buttons.
7. The backend has ways of dealing with users in bulk as well so reports are not needed.
8. Attachments can be browsed directly. The spammer has previously uploaded CSAM directly to drafts of posts which resulted in them not being detected until he reported them because they could not be seen. I can now view attachments, including those attached as drafts, to occasionally check for this behavior.
9. If attachments are reported I have a way of just posting the links in and getting a report going based off those.
10. Incidents can also be created directly from the attachments uploads.
11. And creating incidents this way lets me review all attachments by these users.
12. Incidents are created per-mod, so if several mods and admins are generating incidents, I can merge them together to form a case.
13. The case management and incident management screens are pretty informative.
14. The finalization screen lets me set up information for the case per the NCMEC ESP report standards.
15. You might notice the Reporter and Reported Person fields. I have a way of storing information about people which is required both for the reporter of the incident, but also allows me to specify information about who's doing it. Meaning I can slam the full dox of these people into their fucking faces over, and over, and over again automatically until it fucking stops.
16. Submission is automatic and I have it set up to give me a preview of the XML so I can manually review it. The submission process deletes everything attached.
17. And then I get legally compliant XML receipts of everything.
5. Reports handled in this way instantly clean up the account, put it into a frozen state, and create an incident in the admin backend.
6. The backend is where most of the effort went and contains panic buttons.
7. The backend has ways of dealing with users in bulk as well so reports are not needed.
8. Attachments can be browsed directly. The spammer has previously uploaded CSAM directly to drafts of posts which resulted in them not being detected until he reported them because they could not be seen. I can now view attachments, including those attached as drafts, to occasionally check for this behavior.
9. If attachments are reported I have a way of just posting the links in and getting a report going based off those.
10. Incidents can also be created directly from the attachments uploads.
11. And creating incidents this way lets me review all attachments by these users.
12. Incidents are created per-mod, so if several mods and admins are generating incidents, I can merge them together to form a case.
13. The case management and incident management screens are pretty informative.
14. The finalization screen lets me set up information for the case per the NCMEC ESP report standards.
15. You might notice the Reporter and Reported Person fields. I have a way of storing information about people which is required both for the reporter of the incident, but also allows me to specify information about who's doing it. Meaning I can slam the full dox of these people into their fucking faces over, and over, and over again automatically until it fucking stops.
16. Submission is automatic and I have it set up to give me a preview of the XML so I can manually review it. The submission process deletes everything attached.
17. And then I get legally compliant XML receipts of everything.
And that's it. I can now deal with thousands of accounts spamming thousands of images faster than they can be made. I can shut off registration at a button click.
In case you're wondering, my avatar on the test site is Prigozhin. No, there's no reason for it.
STEP 2. IMPLEMENT A BETTER CAPTCHA
Data soyentists have submitted to me a concept for a novel captcha being tested already by big companies which will assist in defeating automated captcha solvers and force the attacker to pay for indian manual solves.
After this I will be confident enough to open registrations again.
STEP 3. USE AI
I have an idea for assisting in auto-moderation. It's a really clever idea and I do not want to share details. However, it does require more computer.
The word of God is going around the world and your help is so greatly appreciated. What we need now is an enterprise grade surplus supercomputer able to process six hundred billion points of data so we can stomp on chomos. For Jesus. Send money now
If you have access to an NVIDIA SXM board with V100s and you want to donate it to USIPS, read here. If you want to help, set up billpay or donate by crypto. $20/mo from about 35 more people would allow me to finance a big purchase over a year.
I know it's the Christmas season and shit so if you want to hold off that's no worries, this will be an early 2026 thing. I can develop the project on my computer GPU in the mean time.
STEP 4. PROTECT THE LESSER INTERNET
My project with the NCMEC report for XF2 is already public as part of USIPS. If I have the resources, I can deploy the captcha and AI as a service via USIPS to other at-risk sites such as the Soyjak Party or even 4chan. I'm in contact with the 4chan guys and they're pretty limited on resources but I am insane and can do anything I want so I want to build a nice big tent. That's what USIPS is for, basically.
Yeah that's basically it. Happy Thanksgiving.
Big ups to the gold boys and their support.
Last edited:
