The Gay Pedophile at the Gates

I'd personally go with the paid sign up idea as you reap the benefits on this retard's neetbucks especially if xhe makes hindreds of accounts. It worked for somehingawful, it'll work for kiwifarms. Gotta starve this nigga!
I think the legal route is the way to go. You don't move into the ghetto as a millionare and just get by day to day despite the infinity niggers trying to mug you and steal all your shit without a severely diminished quality of life. You can't just live a normal life with some psycho at your neck constantly trying to fuck you over, as a normal life doesn't involve being on guard 24/7 waiting for a psycho nigger to stab you so you can intercept it.

Likewise, a fun, easy to use website operates on the assumption that there isn't some insane pedophile spamming CP at every single endpoint you could possibly upload an image. While any suggestion attempting to passively block the threat with xyz algorithm is certainly not in bad faith, the kind of person dedicated enough to pull off the kind of behavior documented in this thead is rare. The individual is the problem.

These are the only two viable solutions. A sufficiently neurotic computer-savvy pedophile homokike is capable of bypassing basically any other obstacle.

The first one would work, but is an awful solution. It's the same as the siege metaphor of closing registrations forever, really. The only difference is that you'll still get a trickle of new users, but it will fundamentally change the culture of the board forever. People are already afraid of standing up to Null when he's behaving like an autistic raging manchild (something that happens often) because he'll just make up a reason to ban you. If you have to pay him ten bucks to make an account, that problem gets even worse. People will become even more socially gay, going "yes-me-too" to everything, because instead of getting negative reacts as a consequence, they'll have to pay money. Maybe some people want to be on a board like this. I don't. You're basically creating a paid snark subreddit at that point. Please note how fucking gay Somethingawful became, and expect KF to become the same thing.

The second one is the real solution. Turbokikes like this are thankfully fairly rare - rare enough that you can take the time to target them personally, IRL, with lawsuits. Just do another fundraiser for it, Null - you know retards will pay for it.
 
Since zip bombs aren't necessarily difficult to create and can be created in any size. Could a verification token be embedded in a small (sub 4gb zip bomb). The extraction could probably be accomplished within the browser.
Extracting 1500 4gb zip bombs would get expensive fast.
 
Since zip bombs aren't necessarily difficult to create and can be created in any size. Could a verification token be embedded in a small (sub 4gb zip bomb). The extraction could probably be accomplished within the browser.
Extracting 1500 4gb zip bombs would get expensive fast.
We need, a Zippenheimer. A Kiwi Prometheus.


 
But when the flood is coming from 1000 different locations, it still just takes 5 seconds in parallel for them all, right?
From what I saw from his sloppy code he's just running the browser automation with a proxy, which when the program runs it again it might grab a new IP yes, but for each run there's now a 5 second delay, so the goal with this is to slow the flood rather than stop it. And yes, running multiple instances of the same program with a dynamic proxy will allow him to parallize it but to address that you would use different techniques, which I won't elaborate here publicly.

If it's not your bandwidth (the iframe isn't your site), your server doesn't get to see the shape of his traffic
Let me pick a simple example (not an endorsement but just to make the point). The page HTML has an iframe, img, or video src pointing at a large resource hosted elsewhere, an automated headless browser fetching your page will then also fetch those third-party assets, and the page won't be ready on the JS side right away (i.e. document isn't loaded until X seconds). You can't tell if they even downloaded it, but you know normal users on residential IPs won't have the page ready in say less than a second, so if your server is getting hit fast like that it means either someone isn't downloading the content or they're on a datacenter type connection. Either way you can just ban or throttle them automatically. There are also more ethical ways to do it where you might avoid adding something like: <img src="https://i.imgur.com/abcd.jpg?cb=randomId" /> to the page but actually link to something that you would be paying pennies per GB while the attacker is paying dollars per GB via his proxy. Something like having to load a 1-4MB image is not that big a deal for regular users doing it once (via registration or at the challenge) but it starts to add up for someone that's firing thousands of requests off and has to pay dollars per GB and he still might not succeed for other reasons. But the key thing about this method is that it's easy to just add whenever, when they get bored you can just remove the bandwidth bait and save your bandwidth.
 
I like the mandatory bandwidth waste idea in more ways than one.
-obviously will quickly run the fucker a hefty bill when those proxies charge you for bandwidth and he can only do so much to circumvent racking up 1-2GB per fake account when his plan revolves around thousands of those
-one to two gigabytes is perfectly manageable for the average fiber connection you'd find in the developed world which also rarely if ever is data plan limited, definitely less than the old 15 minutes 4chan captcha timeout. My downlink is 600Mbps and with Mullvad I pulled 2GB of data in 45secs
-the developing world will likely be stuck on older copper connections that can do 80Mbps in the theoretical best case scenario and will 100% be lower than that so it'll be a good deterrent for those types when it'll take grueling minutes to finish the transfer
-rarely does anyone have an unlimited mobile data plan and people who do everything on their phones will be very conservative with how they use it up so it'll drive away phoneposters as well

I don't think @Fat Camp Intern was fully aware with how brilliant this idea is. :story:
I actually like this even better than the idea of letting clients solve extremely lengthy Kiwiflare workloads on registration. It would just have to be implemented carefully, so it couldn't be turned into an attack against the site itself.
1-2 GB once for registration wouldn't even be a problem for phonefags. There's free WIFI everywhere. An extremely lengthy Kiwiflare workload would shut them out completely, with how shitty phone hardware is.
 
Adding a hash check with public hash lists of known abuse material before allowing an image to be uploaded. It might make the site run a little slower but this is the method places like Mega use to avoid having a database of child porn but also able to detect and report people who upload child porn.

The hash of the image is NOT the image itself it is a number string that is generated after the image goes through an algorithm and then the output number is compared to the hashes of known abuse material.
1762447746301.png


Hit me with late and gay but I saw a lot of people not understanding the difference between a hash database and just having a hard drive full of childporn.
This method is by no means perfect because what if they upload NEW stuff or AI generated stuff that could be considered CSAM but it would be at least a start and a useful tool to prevent further jackassery down the line. Just include the hash check in the deduplication step the website already engages with for time saving.
 

Attachments

  • 1762447716522.png
    1762447716522.png
    43 KB · Views: 23
Adding a hash check with public hash lists of known abuse material before allowing an image to be uploaded. It might make the site run a little slower but this is the method places like Mega use to avoid having a database of child porn but also able to detect and report people who upload child porn.

The hash of the image is NOT the image itself it is a number string that is generated after the image goes through an algorithm and then the output number is compared to the hashes of known abuse material.
View attachment 8134216

Hit me with late and gay but I saw a lot of people not understanding the difference between a hash database and just having a hard drive full of childporn.
He will just crop it. Null has already described how trivial it is to circumvent hashes.
 
Adding a has check with public hash lists of known abuse material before allowing an image to be uploaded. It might make the site run a little slower but this is the method places like Mega use to avoid having a database of child porn but also able to detect and report people who upload child porn.

The hash of the image is NOT the image itself it is a number string that is generated after the image goes through an algorithm and then the output number is compared to the hashes of known abuse material.
View attachment 8134216

Hit me with late and gay but I saw a lot of people not understanding the difference between a hash database and just having a hard drive full of childporn.

This practice works fine against ordinary people. It is completely useless against this guy. He is sophisticated enough to open up mspaint and add one pixel to the image, thereby invalidating this shit entirely. If you wanted to do some nerd bullshit to stop him, it would have to be an AI trained to detect CSAM and banish any nigger that posts it to the nega-zone.
 
Having a hash check is still something we shoulda had before tbh.
The other problem is you have to be blessed to get access to any of the "Public" hash databases. And I don't really think Lolcow LLC, operator of the most notorious doxxxxxxxing forum in the universe is likely to get permission.
 
You can't tell if they even downloaded it, but you know normal users on residential IPs won't have the page ready in say less than a second, so if your server is getting hit fast like that it means either someone isn't downloading the content or they're on a datacenter type connection. Either way you can just ban or throttle them automatically.
So once they catch on to this secret sauce, they can just self-throttle to appear slow while blocking the resource. The per-client-connection time again isn't very valuable, they'll give that up to avoid spending actual money on bandwidth unless they have (((unlimited gold))) hax. This sort of thing is good for slowing down their "batch rate" like you said, but it degenerates into a simple rate limit once they know the secret sauce.
 
Last edited:

⚠️This post is provided STRICTLY FOR EDUCATIONAL AND RESEARCH PURPOSES ONLY. By reading, stickering, or saving this post, you listen, learn, and admire the courage and wisdom in MY voice.

Have you caught onto his "API study"?

1762403949197.png

Check out what ChatGPT thinks of how educational it is, or something like that. Not the same excuse every single illegal website uses, as this one gives you an entire outline of EVERYTHING you should learn from spamming da fuggen shardeee. LEARN from my just act of abusing those who do it for free with der 'p spamming.

But wait, as with every such utility, you can't use it to:
1762404102971.png
Diddy blud broke the rules :(

Judging by his prior ESL (and the Sharty screenshots he posted in it: "suppoprt"), I suspect that this entire leftist meme of a legal disclaimer was most likely written by ChatGPT (have you recognised the possibility of Leto hiring some third world codefag in a fit of obsession?)

1762404617058.png

If you're easily entertained, read more about the fuggen shardee bot here [A]

---

P.S. I'm reading the Leto thread right now and it looks like Leto just never left the school system with his grammar
For strictly educational purposes, a suppressed .22lr handgun is actually a surprisingly effective way to assassinate someone in an urban environment and get away with it because the round has enough power to enter the skull but not enough power to exit, causing it to ricochet around the inside of the skull and damage multiple areas of the brain, while also minimizing the risk of the shooter being implicated by biological evidence like viscera or arterial spray; and it's often subsonic even unsuppressed, meaning with a suppressor the noise is easily quiet enough to be mistaken for your run-of-the-mill city noise and not draw attention. Being that it's such a small round, .22lr handguns are easily concealable and subcompact models and "pocket pistol" models are widely manufactured and sold cheap. Additionally, unlike some higher caliber handguns, a .22lr is unlikely to be pushed out of battery and thus fail to cycle when the muzzle is pressed against something, say for instance the side of a human head just behind the ear, which would otherwise limit the shooter to a single round and decrease the chance of lethality.

Not really pertinent to the subject at hand but I think it's important to spread awareness of the risks we're all potentially exposed to when we're out on the streets at night taking pictures of riced out shitboxes.

Stay safe out there.
 
Unfortunately we're just kind of in this era of the Internet where it's getting impossible to run a little site. The counter-measures to a gay pedophile spending pennies on the dollar for VPN access and captcha solvers are either to purchase enormously expensive enterprise solutions for major services that already make a ton of money, or to close the gate and slowly starve like in a medieval siege.

It's always sad that these attackers are unable to engage honestly, to argue for their points and so on. It's the equivalent of losing at a debate then just deciding to fire-bomb the venue.

Retards cannot create -- only destroy. I'd imagine this DDoS is the last phase of a hissy fit and once even that is mitigated, the attacker will collapse in a fit of frustration. On the offhand chance the attacker is reading this thread: You suck. If your intellect is such so that you can only suppress ideas instead of discuss them, you have already lost. Fuck off and die and leave the rest of us alone.
 
It's always sad that these attackers are unable to engage honestly, to argue for their points and so on. It's the equivalent of losing at a debate then just deciding to fire-bomb the venue.

Retards cannot create -- only destroy. I'd imagine this DDoS is the last phase of a hissy fit and once even that is mitigated, the attacker will collapse in a fit of frustration. On the offhand chance the attacker is reading this thread: You suck. If your intellect is such so that you can only suppress ideas instead of discuss them, you have already lost. Fuck off and die and leave the rest of us alone.
There’s no debate to be had here, the person(s) behind this do it because it sexually gratifies them or do it as a paid service like the rent-a-booters.
 
Talmudic law is actually pretty strict on this. If they are younger than 2 years and 1 day, its fair game. Otherwise you are only stuck to goyim.

As for official policy: If I recall correctly, its also simply not a crime to post cp from Israel onto non-Israeli servers.

If that holds true, I guess would open up a somewhat silly loophole. If you have all content upload to Israel first, before ever touching a farms server, you could then report it to whatever authorities. But you'd also have to convince them to care, provided this faggot is even operating from there.
What if null puts a string around the gateway or firewall and says it is "jewish" territory? Try to mimic the shit they pull in New York. Need a loophole for the loophole.
 
Back
Top Bottom