Nah, he didn't. Not yet. I couldn't find a thread for general complaints, so I made one. The forum appears to be tracking unread posts only about a month into the past. After that, everything is marked as read. The cutoff date keeps moving forward with time. All those unread posts I was going to get around to eventually are now lost in time, like tears in rain. I'm pretty sure it used to track all the way back to the board's creation, or at least further than a month. Was this a deliberate change, Lum?
I clicked this thread and the black background came up but no posts. It took a few seconds to load, but in those few seconds I thought, "DAAAMN! Lum did break everything."
There is some sort of expiration date on the cookie that tracks when you last checked a thread. I agree that it would be pretty awesome to just remove that expiration entirely. When I click a thread title, I love that it takes me to the last read post. That's a killer feature.
It's handled server-side. I imagine the expiry is there so that users who go away forever or never check a particular thread again don't clog up the system.
Yeah, I used cookie but I knew it was server side since it persists across multiple computers. Still, maybe not indefinitely, but could doubling it or tripling it really hurt much?
I agree with the killer functionality that RyanMM is saying, but you can also just as easily click "Go to first unread post" if it happens that you haven't checked that thread in a while, and it'll still take you to the first post you haven't seen yet.
Here's the thing - it never stops tracking which was the last read post. It's just that after a certain period of time, it stops taking you to that post. I don't see how upping that time limit would cause a resource issue, because it's still tracking the last read.
It never does for me. On posts where I click the thread title, and it takes me to the first post, there's still a flag for "Go to first unread." Even months later.
That's how it works for me--after some point, clicking the thread doesn't take me to the first unread post, but clicking "go to first unread" does.
That is a separate recurring issue. I can infiltrate the LP forum and click on a thread I have most certainly never read and the oldest unread post will be January 11th.
Oh shit, I just verified this. A thread I never read and it takes me to the post most recent after a 30 day cutoff. That's...weird. I can't say that this is a new behavior or not because I never paid close enough attention.
Well, I didn't change anything and honestly this is not something I am going to muck about (possibly breaking other things) trying to "fix". If you can't read a thread in a month, well, maybe it wasn't FOR YOU.
Where it gets to be annoying is when a thread lies dormant for a few months and then someone decides "HEY I NEED TO POST ABOUT <subject>" and digs up the ancient thread for that purpose and I have to find the break point between "four months ago" and "now." But that's pretty rare.
People earnestly replying to posts from months ago (or longer) is an amusing feature, not a bug. If the forum software contributes to this sort of thing happening:
It doesn't seem that rare. I've been noticing this forum behavior a lot lately. Particularly when there's news about a game that hasn't been released yet. Maybe once or twice a day?
Has anybody seen that Penny Arcade where they're all like "IT'S NOT FOR YOU"? Because that reminds me of this.
It's probably because every time an old thread gets bumped, I think Ooh, I remember that thread. I wonder why it got bumped. And then I click on it.
Paging Lum! Pages with embedded tweets on them display this error at the top of the page, one for each embedded tweet. Code (text): file_get_contents(https://api.twitter.com/1/statuses/oembed.json?id=317275985772957696&omit_script=true&align=left&maxwidth=400): failed to open stream: HTTP request failed! HTTP/1.0 400 Bad Request in /var/www/brokenforum.com/html/library/MediaSites/Twitter.php, line 7: 6: 7: '; 8: $__extraData['title'] = '';
I clicked to like a post and got taken to a page that said 'Are you sure you want to like this post?' Is this a new gate meant to slow down Elyscape? Edit: I swear, this isn't a honeypot meant to garner likes! But by all means, keep liking, you fools! It does appear to not be happening anymore. I THOUGHT IT WAS WEIRD!
Actually I just read the post and now I will respond. I've gotten this a lot when using my phone web browser, before I switched to Tapatalk. Not all the time though... maybe only a third or so of the time, and I never was able to figure out what was triggering it. It's not new, though.
I couldn't resist. It's just as well he didn't also ask me to help deposit $40,000,000 in Nigerian oil money.
I see the .. are you sure you want to like this post , everytime I like a post. I think it is because I haven't allowed BF past my no script so it is forced to script it in a secondary page. I don't mind.
This happens when Javascript isn't supported, I believe. Make sure the site is whitelisted if you're using Noscript.
This happens to me occasionally, and it always makes me panic slightly. I DON'T KNOW! I'M NOT SURE OF ANYTHING ANYMORE
Well if this was there for everyone the server would crash from the Elyscape load factor with all the extra prompts.