litphoria

Like in suggestion - in certain situations you have to read post at the very bottom of page then scroll all the way up (through quite a bit of text) to get to click next page and read what is there. I would like for the bar that links to pages and allow for IC&OOC/IC filter to appear not only at the top but also at the bottom. Would be quite helpful.

So, whenever anyone talks about adding stuff to the bottom, I have to remind that there used to be a lot more at the bottom and it made people very upset because it put distance between their post preview and their entry box and any new messages coming in.

But there is space below that too. That kind of stuff can go there, can't it? That would both add more thing, and not distance the input box from the messages. It's slightly unintuitive, but it would still be there.

WA, I don't know how many people were upset. I do recall that it was a desire of yours to minimize that distance. But currently, there is a lot of void space that page links would fit very nicely into, or they could be right-justified on the same line as the typing notifications. That works for desktops generally, but might create two lines on a phone, of course.

It wasn't actually a desire of mine. My original designs had the "users participating" right above the entry box. Typing notifications were done with 'x is typing' underneath each of the icons. This was almost universally hated because it put too much distance between where people focused on (the input box) and new messages, even though the entire box is maybe 100 or so pixels high? So I'm just careful about any more additions down there.

Well, that is a lot of stuff, especially when an RP has more than a few users. I can see people pushing back on that.

But still, the current design has enough dead space to hold filters and page links with room left over for something else.

This is an earlier, related suggestion about adding page number links at the bottom.

If Kain's suggestion above is what I think it is, I've commented that I would like that as well. I'm thinking of where the text entry is fixed at the bottom, and the previous posts are freely scrollable. This allows you to place the post you need to reply to directly above your reply-in-progress. This means certain elements that sit at the very bottom of the post stream would be scrolled down as well: Just the proposed filters and page links are what I'm thinking of, atm.

Ahh! Thanks, Anne, I was trying to find that one.

No, Anne, Kain's suggestion means a way where site is not breaking RP into pages but instead loads part (presumably last page) and when you scroll up to the point where pre-loaded page ends - it automatically loads you previous one, without making a separate page, but just bigger list.
It usually is employed with scrolling down, of course, for Tumblr blogs and such - just the whole idea is to scroll "infinitely" without clicking any buttons to switch pages.

Yeah, infinite scrolling is... something else, and would need its own discussion outside of this. It has its own troubles that we shouldn't care for when talking about adding links to the bottom of the page.

Oh, I might want infinite scrolling. I'm thinking that it's often not done because of keeping load times of a page below a reasonable limit. Some sites seem to have infinite scrolling, but it's really similar to 'infinite' scrolling of levels or worlds in games. So, invisibly or sort-of-invisibly, dynamic loading and unloading of 'pages' is occurring. But again, with that kind of feature, the scrolling posts have to be a separate scroll from the page as a whole, and the input/preview area has to ideally be kept stationary relative to the post-scroll.

I'm just saying that infinite scroll deserves its own conversation outside of this one.

There is also this feedback: Add page number links to bottom of RP page, which is marked as the 'master' of this page.

There is also this feedback related part of the above discussion: Let me see the most recent posts while im roleplaying not just the last page

I see this may have reached implementation stage?

Oh, it has. I'm not sure how this didn't get moved along.