>>
|
No. 155845
ID: af273c
File
139798116763.jpg
- (1.07MB
, 2560x1600
, 543802__safe_solo_spitfire_cloud_artist-colon-mysticalpha.jpg
)
>>155721 >>155803 >>155810 >>155723 Ah, and here it comes. You guys deserve an explanation for this change, and there's no way to do this without being blunt, so this is it.
So in pX2 I introduced a feature that is very, very common on imageboards that gets a lot of use known as ajax fetching, where basically, when you hover over a link to a post that isn't found on the page you're on, the browser behind the scenes calls up the html document of the appropriate thread, then searches its contents and pairs it with the link you hovered over, and after it's done with that, it pairs any other links that need paired with a post that are found in the same fetched thread. That's how it was implemented here, that's how it was implemented on Efchan, that's how it was implemented on MLPchan, hell even 4chan has it the same way. Generally, both this feature and the thread updater are the most server strenuous features found on a browser end script that you can find on an imageboard, yet also amongst the most useful.
I guess what it all blows down to is the fact that all these new features have been introduced on an imageboard that has never had them before, and now we have to acknowledge the fact that server cpu usage and bandwidth are never unlimited. You can't get the best of both worlds; you can only make compromises. Though kusaba X's inefficiency may be partly responsible for the current issues, this isn't a concern that's exclusive to Ponychan. On 4chan, they have an inline extension now with most of those features inspired by third party extensions, but in order to autoupdate, you still have to check the box at the bottom of the page. On efchan, they have a native ajax fetcher and an autoupdater, but the updater has a fixed timer. On MLPchan, they have all of the above without overloading their server, but in return, the browsers do the dirty work of generating image thumbnails, which don't always come out so perfect. It's not really a matter of throwing hardware at the solution so much as it is to find the best solution to get the most out of what you already got. And frankly, I really don't want to be held accountable (or at least feel like I am) for slowing down Ponychan's servers and ruining the fun for everyone else, just because people expect an immediate response out of a thread that has gone without a single post for over 2 minutes and 35 seconds (because to hit 90, you idle for 5 + 10 + 20 + 40 + 80 seconds) because that really doesn't seem fair.
However, what I can do, now that I see complaints saying that the cooldown is running a little too fast, and noticing that the cooldown approaches that 90 second ceiling at a degree quicker than the one on 4chan X where I got the idea, is that I can extend the duration of the cooldown period with a shallower algorithm. Maybe a pattern like, 5, 10, 20, 30, 45, 60, 90? I think that seems reasonable.
>>155807 Yeah, my bad, I fixed the settings box for you quickly, and I found out that some browsers aren't playing the notification sound because some of them are looking for mp3 files and others are looking for ogg's, which I'll take care of tomorrow.
|