Lol still using her face as my PFP.I get off kiwifarms and the onions for months andis still kicking around spouting the same damn lines. very sad many such cases
All races, ethnicities, religions, gay/straight, CIS/trans, neurodiversity affirmative. If you can rock with us: You are one of us.
Tired of putting up with a Florida thin-skinned piss-ass? It's better with the burger boiler
Follow Onionfarms/Kenneth Erwin Engelhardt
Community Featured Submissions
June 24, 2025:
June 24, 2025:
June 24, 2025:
June 24, 2025:
June 24, 2025:
June 24, 2025:
Projects/Repair Work Needed
Onion Logo (Mobile Settings): Status: Mostly Resolved(June 14, 2025)
Onion Logo setting on same line as nav settings (like Kiwifarms)Status:(Not Yet Started)
Badges project: For starting threads that go viral: Status:(Not Yet Started) - June 14, 2025
Blocking Plugin: Status:(Almost Ready -Testing on local server) - June 14, 2025
Text Issue: No difference between bolded text and regular text: Status: Fixed -June 14, 2025
Kiwifarms Gossip & Slap Fights KF General 2.0
- Thread starter Crimson Fucker
- Start date
These threads cover general gossip and interacting with Kiwifarms (openly calling them out).
Dude its his life. I mean I hate modern Assassin Creed but hating someone because they enjoy the I.P is just tarded. Unless he goes the hypocrite route where he starts screaming "This shit is Woke/Sucks/Is unintelligent" then I'd understand. This post has such a snob mentality.
I just don't play them anymore and be done with it. I don't care if people want to waste their money on bad games.
Argonthomus
Registered Member
Update
The restore has been a nightmare, complicated by the fact I am mid-packing for my trip in December before I return to the US. The TL;DR is that the import is running and I think I've sorted out any issues preventing it from restoring this time.
The Kiwi Farms's raw backup file is over 60GiB of pure text. Trying to restore this under any conditions is a slow and painful process. Our situation is complicated manifold by having to run our own hardware which I am solely responsible for at approximately 6000 miles away.
At the beginning of the year, our original server died while being handled by remote hands. Somehow, the motherboard died. I've known people who've spent 20 years handling servers who have never seen a motherboard die. People refused to believe me when I said that was the actual problem.
We bought a new server off eBay and moved all the regular SATA SSDs over to it. These are very high capacity SSDs that are raided for extra redundancy, because if I need one video of Destiny gobbling cock, I need it four times. This highly resilient setup has a trade-off: much higher read speeds, much slower write speeds.
This server (which identifies its mainboard as the H12DSi-N6) came off eBay with two different sized M.2 SSDs (they are fast). We did not raid these because raiding NVMe actually slows it down. Instead, the smaller was made a boot drive, and the larger was made a MySQL drive. This worked great.
The MySQL drive melted within the first month, marking the latest victim of the Kiwi Farms hardware curse. There are years of history of drives failing spontaneously and I swear to fucking god it's not my fault.
In the emergency, I reimported the database then to the storage RAID. I made the decision that putting an intensive process on the boot drive was a bad idea. This worked OK for a while, but eventually I had to start putting in fixes to reduce I/O. Having a very read-optimized RAID sharing work with the write-heavy database caused problems. I also had to adjust the database to write less - the draw off being that if there's a crash, there's more data loss if you write less.
You can probably detect where this is going. Add in several thousand people trying to download a video of a goblin sucking dick along with a database already struggling to handle normal traffic, and you've got the potential energy for a disaster. A table locked up (the alerts table, which is millions of rows long) and in trying to get it to unlock the InnoDB structure completely collapsed.
After trying to fix it, I decided I would re-import it. This is not an easy decision to come to. The import is very, very slow because you're writing hundreds of millions of rows into a slow RAID. At a certain point, the import crashed. I became impatient and tried against to import, this time into the boot NVMe thinking it would be temporary until I can replace the NVMe I should have replaced months ago. Attempt #2 didn't work. The database is now so big it does not fit on that drive. Attempt #3 was attempting again to import on the slow raid. That didn't work. I fixed something and now we're on Attempt #4. Each of these attempts is at least two hours of time.
As it turns out, the motherboard has spaces for four M.2 slots, when I thought it had only two (one spare). I misremembered because it only came with two. I could have fixed this with zero downtime months ago but I never did, in part because I've never actually seen this server, and not knowing what I have is a huge detriment to being able to proactively solve problems.
I very much look forward to having a server in driving distance at some point in my near future, but even that has its own slew of problems because I have no idea how I'm going to move it to the east coast without 2 continuous days of downtime, and I really don't want to spend 4 to 5 figures on a new one just to avoid that.
Computers suck. Become an electrician or plumber. Do not become a computer person.
The restore has been a nightmare, complicated by the fact I am mid-packing for my trip in December before I return to the US. The TL;DR is that the import is running and I think I've sorted out any issues preventing it from restoring this time.
The Kiwi Farms's raw backup file is over 60GiB of pure text. Trying to restore this under any conditions is a slow and painful process. Our situation is complicated manifold by having to run our own hardware which I am solely responsible for at approximately 6000 miles away.
At the beginning of the year, our original server died while being handled by remote hands. Somehow, the motherboard died. I've known people who've spent 20 years handling servers who have never seen a motherboard die. People refused to believe me when I said that was the actual problem.
We bought a new server off eBay and moved all the regular SATA SSDs over to it. These are very high capacity SSDs that are raided for extra redundancy, because if I need one video of Destiny gobbling cock, I need it four times. This highly resilient setup has a trade-off: much higher read speeds, much slower write speeds.
This server (which identifies its mainboard as the H12DSi-N6) came off eBay with two different sized M.2 SSDs (they are fast). We did not raid these because raiding NVMe actually slows it down. Instead, the smaller was made a boot drive, and the larger was made a MySQL drive. This worked great.
The MySQL drive melted within the first month, marking the latest victim of the Kiwi Farms hardware curse. There are years of history of drives failing spontaneously and I swear to fucking god it's not my fault.
In the emergency, I reimported the database then to the storage RAID. I made the decision that putting an intensive process on the boot drive was a bad idea. This worked OK for a while, but eventually I had to start putting in fixes to reduce I/O. Having a very read-optimized RAID sharing work with the write-heavy database caused problems. I also had to adjust the database to write less - the draw off being that if there's a crash, there's more data loss if you write less.
You can probably detect where this is going. Add in several thousand people trying to download a video of a goblin sucking dick along with a database already struggling to handle normal traffic, and you've got the potential energy for a disaster. A table locked up (the alerts table, which is millions of rows long) and in trying to get it to unlock the InnoDB structure completely collapsed.
After trying to fix it, I decided I would re-import it. This is not an easy decision to come to. The import is very, very slow because you're writing hundreds of millions of rows into a slow RAID. At a certain point, the import crashed. I became impatient and tried against to import, this time into the boot NVMe thinking it would be temporary until I can replace the NVMe I should have replaced months ago. Attempt #2 didn't work. The database is now so big it does not fit on that drive. Attempt #3 was attempting again to import on the slow raid. That didn't work. I fixed something and now we're on Attempt #4. Each of these attempts is at least two hours of time.
As it turns out, the motherboard has spaces for four M.2 slots, when I thought it had only two (one spare). I misremembered because it only came with two. I could have fixed this with zero downtime months ago but I never did, in part because I've never actually seen this server, and not knowing what I have is a huge detriment to being able to proactively solve problems.
I very much look forward to having a server in driving distance at some point in my near future, but even that has its own slew of problems because I have no idea how I'm going to move it to the east coast without 2 continuous days of downtime, and I really don't want to spend 4 to 5 figures on a new one just to avoid that.
Computers suck. Become an electrician or plumber. Do not become a computer person.
Page 1 - May 2025 @kiwifarms Telegram message archive.
@kiwifarms - Telegram message archive.
tg.josh.rs
Archive: https://archive.is/GeqKl
ipreferpickles
An Onion Among Onions
I'd said it before, blue collar Joshua is in the works, we'll be eating crow when he's running his toilet cleaning company from his swamp fortress.
Nektar Geist
An Onion Among Onions
It's back up, for the time being, saw this...
And thought I'd post.
youthful_ shannel
An Onion Among Onions
Deleted User
An Onion Among Onions
i thought i was back on here with these numbers on display.
Shadfan666xxx000
Local Moderator
Josh tried to make fun of Destiny's dick, but his site ended up crashing from the sheer power of it.
Boobie Bomb
An Onion Among Onions
Broke dick mountain strikes againUpdate
The restore has been a nightmare, complicated by the fact I am mid-packing for my trip in December before I return to the US. The TL;DR is that the import is running and I think I've sorted out any issues preventing it from restoring this time.
The Kiwi Farms's raw backup file is over 60GiB of pure text. Trying to restore this under any conditions is a slow and painful process. Our situation is complicated manifold by having to run our own hardware which I am solely responsible for at approximately 6000 miles away.
At the beginning of the year, our original server died while being handled by remote hands. Somehow, the motherboard died. I've known people who've spent 20 years handling servers who have never seen a motherboard die. People refused to believe me when I said that was the actual problem.
We bought a new server off eBay and moved all the regular SATA SSDs over to it. These are very high capacity SSDs that are raided for extra redundancy, because if I need one video of Destiny gobbling cock, I need it four times. This highly resilient setup has a trade-off: much higher read speeds, much slower write speeds.
This server (which identifies its mainboard as the H12DSi-N6) came off eBay with two different sized M.2 SSDs (they are fast). We did not raid these because raiding NVMe actually slows it down. Instead, the smaller was made a boot drive, and the larger was made a MySQL drive. This worked great.
The MySQL drive melted within the first month, marking the latest victim of the Kiwi Farms hardware curse. There are years of history of drives failing spontaneously and I swear to fucking god it's not my fault.
In the emergency, I reimported the database then to the storage RAID. I made the decision that putting an intensive process on the boot drive was a bad idea. This worked OK for a while, but eventually I had to start putting in fixes to reduce I/O. Having a very read-optimized RAID sharing work with the write-heavy database caused problems. I also had to adjust the database to write less - the draw off being that if there's a crash, there's more data loss if you write less.
You can probably detect where this is going. Add in several thousand people trying to download a video of a goblin sucking dick along with a database already struggling to handle normal traffic, and you've got the potential energy for a disaster. A table locked up (the alerts table, which is millions of rows long) and in trying to get it to unlock the InnoDB structure completely collapsed.
After trying to fix it, I decided I would re-import it. This is not an easy decision to come to. The import is very, very slow because you're writing hundreds of millions of rows into a slow RAID. At a certain point, the import crashed. I became impatient and tried against to import, this time into the boot NVMe thinking it would be temporary until I can replace the NVMe I should have replaced months ago. Attempt #2 didn't work. The database is now so big it does not fit on that drive. Attempt #3 was attempting again to import on the slow raid. That didn't work. I fixed something and now we're on Attempt #4. Each of these attempts is at least two hours of time.
As it turns out, the motherboard has spaces for four M.2 slots, when I thought it had only two (one spare). I misremembered because it only came with two. I could have fixed this with zero downtime months ago but I never did, in part because I've never actually seen this server, and not knowing what I have is a huge detriment to being able to proactively solve problems.
I very much look forward to having a server in driving distance at some point in my near future, but even that has its own slew of problems because I have no idea how I'm going to move it to the east coast without 2 continuous days of downtime, and I really don't want to spend 4 to 5 figures on a new one just to avoid that.
Computers suck. Become an electrician or plumber. Do not become a computer person.
Page 1 - May 2025 @kiwifarms Telegram message archive.
@kiwifarms - Telegram message archive.
Archive: https://archive.is/GeqKl
K
kiwifails
The pink hedgehog wasn't enough of a clue?
Argonthomus
Registered Member
Now that the site is back up, here's screenshots of what I was talking about:
Attachments
Pretty obvious you came back as soon as a certain homelessman was ousted because you saw the chaotic way he was attacking people and you're too thin skinned and scared to deal with that.I get off kiwifarms and the onions for months and
To get you up to speed, a guy was caught red handed posting lewds from a site that advertised underage models. Ken responded to that by making the guy a moderator and justifying it by telling everyone it's fine since if they're not totally naked it's technically legal in the united states. Ken will also ban you if you bring it up. If that doesn't tell someone all they'd need to know about the fat schizo and his forum I don't know what else would.
In other words you're once again among your brethren and peers.
Nektar Geist
An Onion Among Onions
Oh, what a give away. You just can't resist the Jewess, can you? "You can check out any time you like, but you can never leave"
Similar threads
Kiwifarms Speculation
Why are Kiwis obsessed with porn and lolicon?
