Feedback Technical Grievances

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
1703716854917.png

Wait, what?
 
🎉.st lives again!🎉

I'll stay on .hk for the time being, as it's still stable for me so far.
 
  • Winner
Reactions: skunt
Are you able to load https://89.221.224.80? It's one of the A records for kiwifarms.st and earlier on .hk. Tried posting earlier requesting it to be removed, but you-know-who didn't take it seriously. Another user verified it in the Cogent thread and I verified from a connection in Poland and a VPS in the US as well.
Code:
# curl --trace - --resolve "*:443:89.221.224.80" https://kiwifarms.st
== Info: Added *:443:89.221.224.80 to DNS cache
== Info: RESOLVE *:443 is wildcard, enabling wildcard checks
== Info: Hostname kiwifarms.st was found in DNS cache
== Info:   Trying 89.221.224.80:443...
== Info: Connected to kiwifarms.st (89.221.224.80) port 443 (#0)
== Info: ALPN: offers h2,http/1.1
=> Send SSL data, 5 bytes (0x5)
0000: 16 03 01 02 00                                  .....
== Info: TLSv1.3 (OUT), TLS handshake, Client hello (1):
=> Send SSL data, 512 bytes (0x200)
0000: 01 00 01 fc 03 03 ff a6 4c 98 79 78 cc bc 61 59 ........L.yx..aY
0010: 77 c5 b2 38 d4 3d 3b 2d ee 61 4d 5c 05 ca 56 a3 w..8.=;-.aM\..V.
0020: 64 7a db 03 df d0 20 05 1a 5f 9f ca 42 88 a3 41 dz.... .._..B..A
0030: 75 9f 36 55 bb 62 08 4b c3 e5 05 26 73 4a 77 54 u.6U.b.K...&sJwT
0040: 7e 26 83 ef 53 3b 28 00 3e 13 02 13 03 13 01 c0 ~&..S;(.>.......
0050: 2c c0 30 00 9f cc a9 cc a8 cc aa c0 2b c0 2f 00 ,.0.........+./.
0060: 9e c0 24 c0 28 00 6b c0 23 c0 27 00 67 c0 0a c0 ..$.(.k.#.'.g...
0070: 14 00 39 c0 09 c0 13 00 33 00 9d 00 9c 00 3d 00 ..9.....3.....=.
0080: 3c 00 35 00 2f 00 ff 01 00 01 75 00 00 00 11 00 <.5./.....u.....
0090: 0f 00 00 0c 6b 69 77 69 66 61 72 6d 73 2e 73 74 ....kiwifarms.st
00a0: 00 0b 00 04 03 00 01 02 00 0a 00 16 00 14 00 1d ................
00b0: 00 17 00 1e 00 19 00 18 01 00 01 01 01 02 01 03 ................
00c0: 01 04 00 10 00 0e 00 0c 02 68 32 08 68 74 74 70 .........h2.http
00d0: 2f 31 2e 31 00 16 00 00 00 17 00 00 00 31 00 00 /1.1.........1..
00e0: 00 0d 00 2a 00 28 04 03 05 03 06 03 08 07 08 08 ...*.(..........
00f0: 08 09 08 0a 08 0b 08 04 08 05 08 06 04 01 05 01 ................
0100: 06 01 03 03 03 01 03 02 04 02 05 02 06 02 00 2b ...............+
0110: 00 09 08 03 04 03 03 03 02 03 01 00 2d 00 02 01 ............-...
0120: 01 00 33 00 26 00 24 00 1d 00 20 9a 67 f9 94 b9 ..3.&.$... .g...
0130: 7d 9a 48 a4 ce 02 57 80 cd 25 a7 7a da 9f e7 7f }.H...W..%.z....
0140: 5c d4 ef 6e c7 eb be 06 ca 09 3e 00 15 00 b1 00 \..n......>.....
0150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
01f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
== Info:  CAfile: /etc/ssl/certs/ca-certificates.crt
== Info:  CApath: /etc/ssl/certs
== Info: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to kiwifarms.st:443
== Info: Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to kiwifarms.st:443
 
That's interesting that .st picked us up again, I thought they dropped us because of that huge ddos attack. Did they have a change of heart.
 
  • Like
Reactions: AgendaPoster
Not sure if this is the best place to ask, but what's the max attachment size for posts? Trying to attach a big file just gives a generic error message. It would be useful to know so I can come up with a target bitrate when I compress videos I want to eventually post/archive.
 
Desktop Firefox is still being a little bitch, refusing to load KF roughly 50% of the day. The problem I had with .hk before, I now have with .st.
Meanwhile Brave and even the shitty Android FF version work fine.

It's either:
ff2.png
Or sometimes when trying to get redirected over .net:
ff.png
I tried all the obvious stuff, such as reverting all settings to default, disabling all addons and clearing the cache.
Following the instructions from this thread gives me healthy ping results on all IP's.
Playing with DNS Server settings sometimes makes it work again for a while, but I can't properly reproduce or narrow it down. (Reverting the changes won't stop it from working again immediately and it doesn't always help.)
I did try flushing the DNS cache of Windows. I really don't know wtf is going on.
 
  • Thunk-Provoking
Reactions: Foreverial
Seeing .hk dead and .st suddenly working again had me worried that .st was compromised until I saw my account was still logged in.
 
I've been having real issues with getting onto the farms from my home PC. Is this my ISP fucking with the site?

Here's my junk:


C:\WINDOWS\system32>ping www.kiwifarms.st

Pinging kiwifarms.st [86.107.179.20] with 32 bytes of data:
Reply from 86.107.179.20: bytes=32 time=152ms TTL=48
Reply from 86.107.179.20: bytes=32 time=152ms TTL=48
Reply from 86.107.179.20: bytes=32 time=151ms TTL=48
Reply from 86.107.179.20: bytes=32 time=151ms TTL=48

Ping statistics for 86.107.179.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 152ms, Average = 151ms

C:\WINDOWS\system32>tracert www.kiwifarms.st

Tracing route to kiwifarms.st [212.23.222.112]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 36 ms 36 ms 36 ms 38.62.9.1
3 36 ms 37 ms 36 ms 10.50.0.6
4 50 ms * * 100ge0-78.core2.tor1.he.net [184.104.196.178]
5 * * * Request timed out.
6 * * 147 ms hurricane-ic-360371.ip.twelve99-cust.net [62.115.175.190]
7 * 146 ms 140 ms hurricane-ic-374288.ip.twelve99-cust.net [62.115.181.187]
8 139 ms 138 ms 138 ms meverywhere-sp-z-o-o.e0-2.switch1.waw1.he.net [216.66.93.6]
9 * * * Request timed out.
10 140 ms 140 ms 139 ms 212.23.222.112
 
This is probably just cogent being dicks, but .hk is like playing blackjack, very hit and miss. If it works, it's fast. If not, just generic "page cannot be loaded" browser error.

For some reason, once again, vpn'ing into fucking Norway of all places brings the errors down to null. Based oil Vikings ftw. (Having the same issues at present even in Holland, which before was up there with the Norsk.)
I've not been able to access clearnet at all for days and days. Last night I decided to give routing my vpn into Norway a go, and everything is working perfectly.

So yeah, if you're having trouble with clearnet, I suggest following @Dixieland Buckaroo and connecting via Norway.
 
I've not been able to access clearnet at all for days and days. Last night I decided to give routing my vpn into Norway a go, and everything is working perfectly.

So yeah, if you're having trouble with clearnet, I suggest following @Dixieland Buckaroo and connecting via Norway.
I've found Iran works quite well too.
 
The sneedchat failure to connect issue on .st has returned.

Despite the rest of the site performing better than it has in a long time, at times Sneedchat will become unavailable and fail to connect.

Refreshing will do nothing to fix the issue and sneedchat only becomes available again once KWFlare requests verification again.
 
theres a dns issue with Nordvpn and PIA's US servers. changing the in app dns settings to 8.8.8.8 allows their US servers to connect to .st and .hk. i dont know if that means less opsec protection or not bc im an idiot.

nordsvpn's Poland server connects to the farms with their default dns service without issue.
 
Back