Reporting in.

>>123 Welcome!

Onion check.

>>125 Received. Over!

If you see this, I advise NOT to use catchan to post anything. There are many people there who troll relentlessly and harass people and sites. Posting anything there from L's socials puts her at risk. Please don't do it. If you still want to share your presents (I hope!), use an upload site and paste link. We will find somewhere better, or at least make a generic thread on /m/ to share only candids.

>>127 this is a bunch of FUD bullshit

>>128 Crawl back to your pit, mutt.

I'm here, so this place is better? wtf is going on

>>130 No, this place is only for regrouping. Catchan isn't the place. I think you can post links here ok though. I wish you would join us on the onion.

I don't use onion its too slow I'm ok here

>>132 We can probably get away with only recent candids here. No CD stuff at all - but that is fine, for now.

I'm thinking this is too much and I just got back from work my tacos are getting cold haha

>>134 No one is posting anything like that. Go to catturd if you want that.

Why is my flag always wrong?

>>135 Have a think. I only have Lera's well-being in mind. I think you do too.

I have an Idea, on December 24th we can make a thread on /m/ and I will share my work there, and look for unhoard news. I think the thread can survive at least one day. After that we can wait for things to settle down on KC and if not then we find a new place to stay like here. What do you think

>>141 Very reasonable. Thanks. Enjoy your tacos, lol

I don't know if what you say is true about catchan but it doesn't matter because I can clearly see KC users there and whatever was posted on our /m/ thread they have it too

>>143 You had the benefit of the KC audience, then the migrants showed up that fill catchan now. But they weren't always regulars on KC, like us. Now you're in their domain, with a few stragglers from KC. You don't know who you're posting with.

I will not post anything here or the other place, only news or new finds but save it for the 24th, I will still come here for anything new ok, see you then

only written messages I mean

>>145 Thanks. You know, I believe this is all temporary. KC had to clear out the shit. It will get better again. See you on the 24th.

>>145 Just keep in mind that this site will share your IP address with anyone, including the open public and police. Something to consider.

>>148 Yes. That's why this board is used solely for posting news updates.

The owner of the /kc/ board is maisiecuck - - the same one that spammed maisie and black cock edits in the threads - - he even did some of LB, the worthless nigger.

A simple screenshot was enough to warrant an entire post deletion. lmao @ this place.

It seems kohl is actually under attack. Ernst must be destroyed for this.

>>148 >2023 >no vpn wtf

Onion is now dead. I fear onion/proxy posting will be next on the chopping board. It's quite amusing, but annoying, that they even turned up Cloudflare security level to max when the problem is internal.

>>204 Someone mentioned the exploit is multilevel, on top of the trouble the malicious files cause to the engine itself, Bernds inadvertently engage in the DDOS on kohl through JS (after loading a page with such a file?). In such a case I would block onion too at least temporarily, since you can't block ip addresses via v3 onion services.

>>205 >Bernds inadvertently engage in the DDOS on kohl through JS Yes, it does appear this is the case. I wonder why moths haven't purged the thread with the malicious files yet. They must be aware.

>>206 I would believe they do indeed delete the files. But they could be reuploaded anytime. And the files may look different each time, since such exploits could easily change some unimportant extra bytes to avoid auto detection by simple measure like hashsum. Detecting them automatically would then be a little more involved. I also doubt it is dependent on a specific file type (extension). I could come as any file. This will all depend on Stephen doing some core fixing of the lynxchan code. Until then there is no protecting kohlchan. ;__; I hope I am wrong though, but I have a feeling that someone put considerable effort into this attack.

Onion kohl seems to werk against right now. :3

>>207 >But they could be reuploaded anytime True :/ >Until then there is no protecting kohlchan I believe this too. It will require a patch once the exploit is known and then for the servers to be upgraded. This could take a while. >>209 >How to disable the snow here? It causes considerable CPU load I looked and couldn't find any setting either. I just run without JS now and manually refresh the page. Also, Bernd... you may want to remove the photo of dear Lauri... it may get your post deleted.

>>211 Thanks. So I will keep JS off too. Deleted the post.

Helmut has shutted down the onions against. ;___;

>>215 I can't keep up with all these onion genocidings! I wonder if garlic is also down..?

>>211 >>213 You can use uBlock to block the snow. Just add https://8chan.moe/.static/js/snowfall.js (replace 8chan.moe with the domain you're using) to the filters.

KC's onion has been up and down more times than a whore's panties

>>220 Yes, let's hope this normalizes during the next days.

My Brother in Christ, we are back.

Onion is crap this night