"I'd say that there is evidence that the victim has been killed by a human, has not committed suicide, that only one other person is alive in the house, and that no human has entered or left the house during the entire process. Oh, and the knife in the victim's back also has the alive man's fingerprints on it. And he's stabbing the corpse every time you blink while refreshing the page." -- Étienne Pérot; WindPowa
Ha, I'll say I lost the one about it being a glitch. I didn't really think about it, but yeah. That's something that would have to be manually coded in there.
As for the symlinks, it's basically just talking about how we think it would be done. Neither one of us have enough information to say definitively how it's done, so I guess it was a pointless argument.
Well as you can see here, the page parameter used to work, but now will redirect to the first page. The parameter for the post is unknown to us mere mortals, but since the current structure is topicid_post, we can be fairly certain they no longer make use of the page parameter. I'd assume they replaced it with a post parameter, but that could be a number of things. p, post, postid, etc. I'm not really in the mood to go around trying to find it. Either way, it's not like the symlinks mean they changed files. That doesn't make sense, to me. I assume they modified their viewtopic.php file, and added symlinks that basically change the way the url looks. With a followsymlinks setting, the old links will change to the new ones, but you're still getting the content of the old one. It's how wordpress has pretty urls now, even though really it's a page like post.php?postid=1. It's essentially used for search engine prettiness.
Wow, good job. you proved it wasn't a glitch. But, in the process, you argued a few incorrect things.
Your argument about symlinks kinda disproves your argument about _recent not being a parameter.
If /forum/t.topicid gets changed into /forum/viewtopic.php?t=topic_id, whose to say _recent doesn't get converted into &post=_recent?
FollowSymLinks is obviously redirecting the old links to new ones, so there's no way for us to tell.
_recent is pretty obviously a parameter that they use. And like I said, I've seen it on completed pages. Doesn't matter if it's page 1, page 30, or page 750,000, it happens when there is a multiple of 15 (as the post count). At least, used to happen. Maybe they changed how it works. But I never knew it was _recent that caused it. I think the upside down page issue occurred before _recent was used
A lot of the security concerns have been worked out, and there are ways to implements HTML5 in a safe and secure way, and RuneScape is a pretty good example of that. I'm not saying it's possible, since I'm not sure what goes on behind closed doors; I'm just saying the reply codemonkey gave was pretty broad, and he should have gone more in-depth with why HTML5 is not suitable. It would allow people to play from mobile devices, and remove the entire Flash Player dependency all together. I'm not expecting Gaia to make a change that large, but it would be a nice addition to access games from my phone.