>I would like to believe it is an issue on anon.cafe's end somehow obviously, but I am doubtful.
Given what you've posted, we agree with you.
>I've determined that I can only download at 20kbps while on /k/. On /comfy/ and /meta/ I do not have this issue.
That's definitely abnormal. The slowest we've ever seen it over a congested VPN link is 200kB/s (around 204800kb/s). Testing from here shows no difference in speed between downloading files from /k/ and downloading files from any other board.
>I have latencies of about 25 seconds yes, seconds, not milliseconds on other anon.cafe boards, while I have latencies as high as 70-80 seconds while browsing or posting on /k/ specifically.
That's even more abnormal. For comparison, we get about 300ms ping latency over a congested VPN link. When you say "latencies", what exactly do you mean? Ping? Time from HTTP request to first response packet? Time from HTTP request to last response packet? For comparison, we see HTTP waiting times (request to first response packet) on the base board document request of about 600ms over VPN, with no difference between boards. (We consider this slow and are going to be changing some things behind the scenes to try and speed things up.) We get about 1000ms when doing the same over Tor (with Tor running through VPN connection).
>it's at the point now where files over 500kb won't even upload to /k/ any more for me.
We're seeing files coming through from others without issue, many of sizes much greater than that.
>So I suppose if it's not an issue on anon.cafe's end, that would implicitly mean I'm either being monitored by the feds while visiting anon.cafe/k, not that I really give a shit, or my ISP is specifically throttling anon.cafe/k specifically (which seems unlikely since they'd just throttle the whole website if they were going to throttle it).
Monitoring an individual's traffic in a way that creates delays of that magnitude would be quite incompetent. This is not to say your traffic isn't
being inspected, just that if it is it's being done by the signals desk of the Keystone Cops. I assume you've tested this repeatedly to be sure that the differences in timing between boards are not coincidence.
HTTPS requests conceal the requested path, so unless your HTTPS stream is being decrypted then there should be no way for a listener to know which board you are requesting. You might consider thoroughly comparing the HTTPS certificate fingerprint you get when accessing the https://anon.cafe
address via Tor and via the link you suspect is being monitored. (We see SHA-256 17 D0 A7 9D 74 E8 F6 E5 F1 69 0F 89 84 BE 16 5E 66 3E 05 64 43 86 FF 2F 37 9C D0 55 53 2B 6D 72; future readers note that this changes with each Let's Encrypt renewal so don't freak out if it's different for you after some time.) If the fingerprint you get when hitting the HTTPS endpoint (not onion endpoint) via Tor is different from that you see with the normal method, then your HTTPS traffic is being MITM'd. If it's the same then you might still be getting MITM'd, but not using spoofed certificates, or you might be getting MITM'd so hard that onion routing itself has been compromised and turned against you.
It's also possible that one of the networks between you and Anon.cafe is throttling traffic to our IP, our subnet, our ASN, or something else.