There's also only 2 threads on the first page of /*/. It's all over, will another British imageboard arise from the ashes of .gs?

/*/ has gone a bit wonky for me, on the first page I see this thread, and /beat/11742, and then the page list. If I got to page 1, it works as normal.

BROKEN BRITFA.GS.

>>15086>>15087
How strange - all working fine for me here. What browsers are you using chaps?

Are you using a browser that has accidentally/something switched off Javascript, as those errors say? Script/ad blocker?

My apologies to whoever post it was in /beat/ - the videos weren't rendering so I deleted it. Star seems to be acting a little weird, will take a look.

>>15085
The date isn't the interesting thing, it's the post numbers. Those posts clearly aren't from the same thread.

>>15090
I'll be in IRC after work tomorrow if you've not fixed it by then.

>>15091
Yeah Star is mixing up a thread in /beat/ with a thread in /nom/ - interesting.

>>15092
Looks like you fairly recently killed the IRC? Don't blame you.

>>15095

So what's the info for IRC again?

Last attempts at jam.britfa.gs proved fruitless.

>>15266
>>/e/22563

>>15267
>>15266

You're being dragged kicking and screaming into the closed-garden third-party run internet. Pretty soon this place will close down and be replaced with r/britfa if I'm any judge.

http://www.britfa.gs/news/res/21041.html#i21731

Did a youtube video embed in this post, it worked fine at first but is now displaying a video posted much higher up in the thread. Weirdness.

>>15287

Correct link was http://www.britfa.gs/news/res/21041.html#21731

And now it's gone back to normal, anyway.

Sage.

>>15288
>>/news/21731.

>>15287>>15288
There is definitely a bug there, somewhere - I've seen it myself; appreciate the feedback chaps.

>>15290
I've said it before but I remain totally convinced that bug is YouTube's. That isn't to say we can't work around it, but you'll probably remember that we're not doing anything at all dynamic with the old players (the new one isn't affected but has other issues). It's just the same static and straightforward markup being served from the DB every single time. I can only speculate that our use case where we're loading dozens of full fat players at the exact same time isn't super well tested and we're probably using legacy embed code as well. I reckon they have a race condition somewhere in their stack. When it happens you can observe that we requested the right video, but received the wrong one.

FWIW on YouTube itself I frequently find it loads the wrong video until I refresh - it loads the previous one rather than the one requested. I'm not suggesting that's the same issue though.

>>15293
>we're loading dozens of full fat players at the exact same time isn't super well tested

Yeah that is exactly my guess too - very few sites would load a page with so many players showing, as some of our threads do, and my guess/hunch, like you, is that something around that is fucking up. The weird part on our side, perhaps we can fix/workaround, is that it seems to perhaps munch the HTML/DOM model in a weird way that cuts off the thread, but speculating a bit there.

>>15293
> When it happens you can observe that we requested the right video, but received the wrong one.

I'd love to see that happening in real time as it suggests some kind of serious sequencing bug in the back-end; potentially related to HTTP response splitting or potentially concurrent HTTP/2 streams going out of order somewhere in one of the components in their stack. Either way it's a pretty serious issue.

>>15293
>on YouTube itself I frequently find it loads the wrong video until I refresh
I've had this too. Quite weird.

Just caught this happening on the front page of /*/. I now think it might have something to do with browser cache.

>>15297
What browser are you using?

>>15298
Firefox, same as the otherlad in the other thread. I'm almost certain it's firefox fucking up caching that's an issue.

>>15299
I see it in Chrome, desktop and mobile.