Anonymous ID: 70e128 Nov. 11, 2019, 7:09 p.m. No.7353154   🗄️.is 🔗kun

You faggots need to assign the board to one time zone if you’re using tor for the back end otherwise it bounces around between front and back end and fucks everything up. God fucking damnit will this shit every be back an operational? I’m so fucking tired of watching land of the lost reruns I need some Q

Test ID: 70e128 Nov. 11, 2019, 7:36 p.m. No.7353192   🗄️.is 🔗kun

Happy happy joy joy still an apple up your ass. What’s habbenin with the comms? Seems thing be twerkin a lil better no?

Anonymous ID: 70e128 Nov. 11, 2019, 7:45 p.m. No.7353203   🗄️.is 🔗kun

Ya something tells me that between the tor nodes the server is over cached from NTP. Definitely cache issue cause when y’all’s switched time to consolidated it likely flushed cached entry’s but then a few minutes later it slowed again. Are teh comms guud what’s habbenin?

Anonymous ID: 70e128 Nov. 11, 2019, 7:49 p.m. No.7353209   🗄️.is 🔗kun

Ermagerd clear the ntp cache the tor node hops are fagging things up. Got to keep that shit clean or it’s like pullin teh plug out on that ass gravy know what I memes? R teh comms guud now?

Anonymous ID: 70e128 Nov. 11, 2019, 7:56 p.m. No.7353215   🗄️.is 🔗kun

Okay lucky guess. Still in school not a wizard yet. Best luck frens an hope it’s up soon. R teh comms guud

Anonymous ID: 70e128 Nov. 11, 2019, 8:23 p.m. No.7353243   🗄️.is 🔗kun

Aside from the NTP thing something else I pondered. I briefly read a post that mentioned tor so I assumed that this site was running through it which makes me wonder how certain elements on the site load. Each time the server handles a request does it switch servers? Ddos mitigation is tricky but I think you need some consolidation within each board and that should halp speed things along. It’s smart to switch nodes but be consistent per board.

 

R teh comms guud what’s habbenin?

Anonymous ID: 70e128 Nov. 11, 2019, 8:34 p.m. No.7353257   🗄️.is 🔗kun

Err what I meant was split the database up. Concatenize that shyat. Each board to refresh individually via individual requests. Too much habbenins on one tor node at a time. Board refresh to central database / central database refresh / then refresh board to user etc

 

R teh comms guud

Anonymous ID: 70e128 Nov. 11, 2019, 9:02 p.m. No.7353286   🗄️.is 🔗kun

Images aren’t coming through. Example: So it’s probably because request to view /board-catalog then has to pull a request to the /images then send back to /board-catalog which won’t populate because page already loaded and the request for /images timed out. All this done over tor too? Id find a way to do snapshots and save bandwidth and make it function better and faster.

Anonymous ID: 70e128 Nov. 11, 2019, 9:04 p.m. No.7353289   🗄️.is 🔗kun   >>3292 >>3293

Images aren’t coming through. Example: So it’s probably because request to view /board-catalog then has to pull a request to the /images then send back to /board-catalog which won’t populate because page already loaded and the request for /images timed out. All this done over tor too? Id find a way to do snapshots (for /board-catologs etc) and save bandwidth to make it function better and faster.

 

R teh comms guud wats habbenin??

Anonymous ID: 70e128 Nov. 11, 2019, 9:21 p.m. No.7353307   🗄️.is 🔗kun

Oh geez take current snapshot not revert.

Exclude from snapshot the posts element otherwise it may revert (just show the titles and images and post counts). Then refresh snapshots every so often. I think this all needs an overhaul sweet jeebus

Anonymous ID: 70e128 Nov. 11, 2019, 9:24 p.m. No.7353309   🗄️.is 🔗kun   >>3320 >>3394

I’m on iPhone so this is how I can post:

 

Use safari

Disable JavaScript

Post reply to thread

If black screen or says server error then hit back button and refresh page.

 

To be sure it posted I also hit reply again then it says the error message already posted. And I can only read my post in the index.