I'm surprised my post went through here. If I try to post on /kind/, I get the error mentioned above.

Okay, I figured it out. The problematic post was >>>/kind/4645, it had two links to huge files, and for some reason /kind/ was trying to download those files using curl:
https://github.com/vichan-devel/vichan/blob/master/inc/functions.php#L2868

You should set CURLOPT_NOBODY to true so that it sends a HEAD request which means that the actual page won't be downloaded, only the response headers will be sent:
https://www.php.net/manual/en/curl.constants.php#constant.curlopt-nobody

But maybe it would be better to just disable this feature? Does this mean that the server is visiting those shady sites that are sometimes spammed on imageboards?

>>3099
>can't post
>posts

ok

>>3101
This feature exists since the vast majority of spam sites use some sort of link shortener to try and hide their domains. Didn't know it had an issue with large files though, so I added that option

>>3105
Thanks!

I did not know that this actually caught spam. Interesting.

I tried to post something the other day here with links innit and for some reason it wouldnt allow it, didnt know this was a thing now it makes sense why it wouldnt.

>>3107
Very heavy (maetel) thoughts