Feedback Technical Grievances

@Null Sneed chat is down and I cannot express how annoyed I am. I wrote a small report on what you can do to improve it:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque a sagittis nibh. Nam tellus mi, malesuada consectetur eros vel, aliquet iaculis urna. Aliquam faucibus porta massa. Duis et nulla in risus congue semper eget sit amet eros. Phasellus viverra quis ligula eget mollis. Morbi posuere, lacus gravida faucibus pellentesque, velit odio accumsan nisl, vitae condimentum elit justo eget nulla. Vestibulum et tortor nec dui porta placerat eu ac leo. Quisque luctus felis non luctus congue. Duis blandit mauris ipsum, eu rutrum nunc convallis quis. Ut sit amet nisi ipsum. Aenean eget elit orci. Praesent id augue vel nulla aliquet pretium et at purus. Nullam cursus lorem sed lobortis condimentum. Duis vel metus id ipsum semper lobortis eu vitae est.

Vivamus porta nulla quis accumsan iaculis. Pellentesque vehicula dui leo, condimentum accumsan lectus varius sed. Vivamus porta enim at viverra imperdiet. Vivamus sem erat, pretium sit amet lorem id, fermentum iaculis metus. Proin et feugiat mi. Nulla lobortis molestie orci quis congue. Sed varius metus at lorem venenatis aliquam. Nullam scelerisque pellentesque lacus finibus tristique. Etiam sagittis dictum pulvinar. Maecenas egestas mi at posuere volutpat. Proin tincidunt, ligula a posuere hendrerit, risus eros tincidunt metus, in aliquam risus elit quis lorem. Pellentesque augue leo, iaculis at ornare quis, sagittis nec est.

Sed ornare efficitur nisl ut gravida. Donec tincidunt diam sed elit commodo pellentesque. Sed molestie ipsum consectetur euismod tincidunt. Vivamus pellentesque lorem eget risus dapibus condimentum. Praesent rhoncus nulla libero, eget ornare enim venenatis in. Aenean ut ex eget orci molestie blandit sed sed velit. Donec iaculis purus sit amet lorem malesuada, a pharetra justo placerat. Donec sagittis iaculis elit, ac eleifend risus. Vivamus vel tempus justo, eget placerat libero. Duis lacinia ante sed ipsum congue laoreet. Ut sit amet mauris vitae ante fringilla lacinia ac at odio. Duis feugiat nulla ut nisi dapibus, at vulputate magna iaculis. Suspendisse quis risus quis augue convallis bibendum. Phasellus dui mi, luctus nec velit id, placerat hendrerit ante. Etiam vitae lacus a dolor lacinia dictum. Sed maximus augue accumsan vestibulum posuere.

Suspendisse at congue ligula, id sagittis lectus. Donec id fringilla ante. Aliquam molestie malesuada justo sed faucibus. Maecenas fringilla lacus at blandit sodales. Vivamus pulvinar venenatis massa imperdiet pulvinar. Aenean condimentum ipsum in ligula ullamcorper, a faucibus nibh convallis. Donec eu semper justo. Vestibulum aliquet nibh et velit accumsan, ac auctor nunc malesuada.

Nullam eleifend dapibus nulla. Nulla sit amet est rhoncus, condimentum enim et, interdum justo. Pellentesque in blandit dui. Mauris felis turpis, pharetra in turpis sed, efficitur mollis lacus. Nulla tempus urna id justo auctor, et fermentum turpis semper. Donec iaculis lobortis lorem, sit amet suscipit nunc bibendum eget. Sed bibendum dolor eu iaculis placerat. Nullam dignissim sodales tortor, consectetur maximus mauris tempus id. Etiam feugiat diam augue, eget aliquet odio consequat ut. Phasellus congue viverra dui a blandit. Nulla a magna elit. Maecenas ornare, tortor quis bibendum mattis, nisi sem sollicitudin quam, eu pharetra libero est ultricies tellus.

Hope it helps.
 
What's on Telegram? You can't read the channel without an account. There should be somewhere where we could see the status without logging into anything when the site is down.
The telegram is mostly just for delivering the site status when it's offline. During the great tranny reeing it was public but I think they got it to require an account to view. I concur on an alternative being a good idea.

On my own technical error note, I'm having increasing issues with getting hyperlinks to properly work. I posted about this a bit ago but It's continuing. I've gotten this infrequently over time but it's getting worse and it's selective. It seems like it really doesn't like archive links. Weird. Any solutions if they exist would be good.
 
Experiencing those blank white 500 gateway errors. Using Ukraine vpn completely breaks site structure and still experiencing 500. Using USA vpn I can navigate fine for one or two pages before it stops loading anything. I am constantly changing vpn servers to use this site at all. Using Firefox.

What's on Telegram? You can't read the channel without an account. There should be somewhere where we could see the status without logging into anything when the site is down.
Ok seriously this has been bothering me for a while now. What is wrong with posting information on a Fediverse Poast or Chudbud user account? Why force people to sign up for Telegram? The second the Telegram became account-only due to trannies, an alternate method of relaying site information to users should have been adopted immediately. It's fucking bullshit people need to spend money to get a burner phone number, or use a real personal telephone number, just to view updates on the Telegram.
 
Last edited:
Saw a return of random 429 errors this evening. Hadn't been moving around rapidly or opening many threads at once. Not sure if because of your tinkering or what but I hadn't seen a single 429 error since KiwiFlare went up
 
Mullvad VPN giging 502 and 503s
Switched to Proton VPN and its fine
I'm having the opposite now that I'm on mobile again. Proton is triggering 502s whenever I open a thread, nada on main pages though they do sometimes load incompletely.
 
I can confirm PIA Denver cannot reach the Farms. Traceroute:
Code:
 1  _gateway ([redacted])  35.547 ms  35.494 ms  35.458 ms
 2  38.32.95.33 (38.32.95.33)  36.642 ms  36.630 ms  36.593 ms
 3  be2530.ccr21.den01.atlas.cogentco.com (154.54.88.29)  35.936 ms  35.945 ms be2762.ccr22.den01.atlas.cogentco.com (154.54.88.81)  35.926 ms
 4  be2402.rcr21.b006467-6.den01.atlas.cogentco.com (154.54.88.46)  36.407 ms be2401.rcr21.b006467-6.den01.atlas.cogentco.com (154.54.88.42)  36.328 ms  36.321 ms
 5  gtt.den01.atlas.cogentco.com (154.54.10.122)  97.396 ms  97.372 ms  97.342 ms
 6  ae12.cr7-dal3.ip4.gtt.net (213.200.120.106)  54.900 ms  56.287 ms  56.332 ms
 7  * * *
[etc.]
Hey WhiteNight, just wanted to hop in here and say that I ran my own tracert that showed the same thing, which was then looked at by Null who said that PIA US Denver's upstream is Cogent which is getting KF blackholed by GTT. If you care, open a support ticket with PIA and do as Null said which is to send them your traceroute and tell them to tell Cogent to tell GTT to stop, or knock it off, or however you want to say it. Here is the link to my post.
 
  • Informative
Reactions: WhiteNight
I haven't seen it for a couple of days now, behind a Amsterdam VPN connection.
 
  • Agree
Reactions: Cloacan
Don't think I've had any whitepage issues the last couple days. Did you figure out what it was?
 
I haven't gotten any whitepage issues over the weekend, on both Brave and Firefox. I'm mobilefagging on Firefox right now, and no whitepage so far here either.
 
I haven't had any whitepage issues either (Firefox) for at least a couple of days maybe a week now. I did have a brief odd issue where all the text in sneedchat (only sneedchat) was popping up as ⍰, but I cleared the cache and restarted the browser and that fixed it.
Emphasis on restarting the browser afterward, in case anyone is as dumb as me lol.
 
429 Too Many Requests- Emote use and search from submission form.
URL/Hyperlinking not working Working now!
Win10/Firefox/PIA VPN (ATL, DC, FL, TX)/Normal Comment Submission Box
Not huge/site breaking and I have clear steps to reliably avoid/work around, providing info here for reference.
Details:
1676292003820.png
I noticed last night when opening the emote thing in the submission tool it starts throwing an error like this if you search. After this error happens, attempting to do anything else will get you a 429 response. Refreshing alone does not work, refresh+cleared cache works sometimes, and changing VPN location+clear cache+refresh resolves the 429 error every time.

Also using the hyperlinking tool in the submission box appears to have stopped working. Added like normal to submit a reply, the reply posted without it, and I could not edit it in. I just plugged it in as plain text for readers so no huge issue.

Okay weird, it did let me edit in a hyperlink to the post where I previously couldn't.
 
Back