I'll finish the UI and roll it out when I wake up sometime.

Change of plans - I ate a bad hamburger patty at a superbowl party last night and I've been suffering all day. I'll resume working on it this weekend. @Captain Jordan: Good ideas. I'll think about them this weekend. @BBeast: Good call, that's one of the reasons I split up the topic & convo systems for the rewrite. Easier to lock down all convos with one line of code (you must be a participant to read/post in a convo) rather than have this overloaded topics-for-convos system. @LegendBegins: Yeah, I'd like to push updates to the browser. Maybe I can keep it simple. @Kirra: Aw. Poor [@Mr_pink] :( - Thanks, I'll fix.

We know the number might be depressing, but we found ourselves wondering how many users there are that haven't logged in since the relaunch... Its listed on individual user pages, but as userlist hasn't been implemented yet, it can't be checked easily.

We know the number might be depressing, but we found ourselves wondering how many users there are that haven't logged in since the relaunch... Its listed on individual user pages, but as userlist hasn't been implemented yet, it can't be checked easily.

A newsletter like Email that is sent out in bulk to all the members on the site could help bring back some of those members that forgot about the site for a bit. It'd be a reminder to say, "Hey, we still exist and we wanna see you again. :)"

We know the number might be depressing, but we found ourselves wondering how many users there are that haven't logged in since the relaunch... Its listed on individual user pages, but as userlist hasn't been implemented yet, it can't be checked easily.

We know the number might be depressing, but we found ourselves wondering how many users there are that haven't logged in since the relaunch... Its listed on individual user pages, but as userlist hasn't been implemented yet, it can't be checked easily.

I made a user search page for the next update, but it currently has no filter options. Now that you mentioned it, I'll amend that whenever I have time, hopefully before it is launched on the guild. Sort by newest or oldest are obvious, and based on who has an old guild name. Are there any other filter options people would like?

No fun at all @Mahz. Hopefully it passes quickly! I was wondering if you could implement two things in the PM list. I've noticed there is a page forward button and one that takes you back to the first page. Do you think you could add another button so that we can go to the previous page (Now I think about it, it also applies to the recent posts on the userpage). Also, do you think you can bring back the PM count for each convo on the PM list? It was a helpful way for me to distinguish between convos with similar names and people involved.

No fun at all @Mahz. Hopefully it passes quickly! I was wondering if you could implement two things in the PM list. I've noticed there is a page forward button and one that takes you back to the first page. Do you think you could add another button so that we can go to the previous page (Now I think about it, it also applies to the recent posts on the userpage). Also, do you think you can bring back the PM count for each convo on the PM list? It was a helpful way for me to distinguish between convos with similar names and people involved.

1. I'll see about adding a "Previous" button for recent-posts and convos. That there's only a "Next" button is a bit of a performance hack since it's easy for the server to calculate. I didn't try to add a "Previous" button yet since I figured it wasn't so common for people to be iterating through history. But yeah, bit of a usability annoyance. 2. Haha, I didn't realize the convo message count wasn't displaying. Must've typo'd something. I will fix.

No fun at all @Mahz. Hopefully it passes quickly! I was wondering if you could implement two things in the PM list. I've noticed there is a page forward button and one that takes you back to the first page. Do you think you could add another button so that we can go to the previous page (Now I think about it, it also applies to the recent posts on the userpage). Also, do you think you can bring back the PM count for each convo on the PM list? It was a helpful way for me to distinguish between convos with similar names and people involved.

1. I'll see about adding a "Previous" button for recent-posts and convos. That there's only a "Next" button is a bit of a performance hack since it's easy for the server to calculate. I didn't try to add a "Previous" button yet since I figured it wasn't so common for people to be iterating through history. But yeah, bit of a usability annoyance. 2. Haha, I didn't realize the convo message count wasn't displaying. Must've typo'd something. I will fix.

Would a back button be more difficult than telling the server to go to page - 1?

Would a back button be more difficult than telling the server to go to page - 1?

Indeed, a simple javascript back would be an easy hack for the meantime.

Would a back button be more difficult than telling the server to go to page - 1?

The hack is that, unlike for posts and PMs, there are no pages for recent-posts and convos. I go through great length to get fast pagination for posts and PMs by monotonically increasing a number that starts at 0 for each post/PM in that topic/convo (I call it the post.idx and pm.idx). That way it's easy to calculate which range of idx to query from the database given a page number and the amount of posts/PMs to display per page. The database is fast at "WHERE idx > X AND idx < Y" queries. That system doesn't work as well for things with high churn like convos, so I'll see if I can get a previous-button working with the current hack.

Indeed, a simple javascript back would be an easy hack for the meantime.

Oh man. Didn't think of that nasty hack which actually isn't that bad since a user is never deep-linking to a page of recent-posts or convos. It'll be my quick plan B if plan A sucks.

Would a back button be more difficult than telling the server to go to page - 1?

The hack is that, unlike for posts and PMs, there are no pages for recent-posts and convos. I go through great length to get fast pagination for posts and PMs by monotonically increasing a number that starts at 0 for each post/PM in that topic/convo (I call it the post.idx and pm.idx). That way it's easy to calculate which range of idx to query from the database given a page number and the amount of posts/PMs to display per page. The database is fast at "WHERE idx > X AND idx < Y" queries. That system doesn't work as well for things with high churn like convos, so I'll see if I can get a previous-button working with the current hack.

Indeed, a simple javascript back would be an easy hack for the meantime.

Oh man. Didn't think of that nasty hack which actually isn't that bad since a user is never deep-linking to a page of recent-posts or convos. It'll be my quick plan B if plan A sucks.

I really hope that's not going to bite you in the ass once the database has accumulated a high amount of posts/convos. Deletes are going to be a bitch if that happens.

So it essentially generates "pages" based on the number of posts to display, while no true pages are being generated, but simply a number of posts to display before breaking forward, which is why you can't go back? Because there's theoretically no place to go back to?

I really hope that's not going to bite you in the ass once the database has accumulated a high amount of posts/convos. Deletes are going to be a bitch if that happens.

It scales because it's incremental at the same cost whether there are 2 posts or 1,000,000 posts in the topic.

So it essentially generates "pages" based on the number of posts to display, while no true pages are being generated, but simply a number of posts to display before breaking forward, which is why you can't go back? Because there's theoretically no place to go back to?

Yeah, pretty much. If you hover over your "Next" button on recent-posts, you can see that it's passing in the ID of the last post on the current page. I could probably implement the "Previous" button as the inverse. Probably in the time I've been talking about it here.