jase
 admin, 3798 posts
 Cogito, ergo procuro.
 Carpe stultus!
Sun 17 Jan 2021
at 06:03
Re: RPoL Design Update
Haven't fallen into the trap of being logged into rpol.net at the same time, have you?

r.rpol.net sets cookies for the domain r.rpol.net while rpol.net (and the www variant) sets cookies for plain rpol.net.

Unfortunately when browsers retrieve settings for subdomains they'll also grab any cookies for the parent domain.  So when a webpage at r.rpol.net requests a list of the cookies it'll return a combination of r.rpol.net and rpol.net cookies.  As far as I can tell in a random order, and the order also seems to differ between PHP and Perl (though haven't done any testing on that).

So when the page asks for a list of the threads that have been read it can either use the cookie set for r.rpol.net (which is correct) or the cookie from rpol.net.

Furthermore we rationalise cookies as we go, but that uses the information we've grabbed from the browser to collate the relevant information and then trim the list.  So we can ask for the read indicator cookie, get the list from rpol.net (the wrong cookie), rationalise it and then set it for r.rpol.net.  Then we've got cookies set for r.rpol.net poisoned with what was retrieved from the rpol.net version of the cookie.

I've done a work-around for the beta site to avoid the cookie conflict but I can't do the same on the responsive site.  I suppose I could just use and set the cookies for rpol.net... will have to contemplate whether that'll cause any issues.  Can't actually think of any issue at the moment.
Skald
 moderator, 924 posts
 Whatever it is,
 I'm against it
Sun 17 Jan 2021
at 08:10
Re: RPoL Design Update
I did have both sites open the first time I noticed it, but subsequently closed the old site and retried a couple of times and couldn't get the flag to close ... but it might have been too late by then if the cookie had already been broken ?

Edit: just had a new forum thread pop up and have been able to open and view and clear flag on responsive ... so yup, jase is right yet again, it's the old/new/simultaneous trap.  Something to ignore.  ;>

This message was last edited by the user at 14:12, Sun 17 Jan.

SunRuanEr
 subscriber, 357 posts
Sun 17 Jan 2021
at 17:00
Re: RPoL Design Update
In reply to jase (msg # 464):

Thanks for all the updates, jase, especially the new red rMail notification.

I do feel that the player-view cast list is a step backwards, since it returns Last Login to being automatically viewable (when it previously required a mouseover on responsive), but I appreciate the removal of the groups from the automatic list so I suppose it's a wash in the end. I'll just have to accept that I'm in the minority about wanting stuff less obvious to players, and deal, I guess. =)

(Any kind of rough ETA on having PMs trip Last Logins for GM-controlled characters?)

As a complete aside, just noticed an interesting glitch with the Last Post for characters that have never posted publicly...

quote:
Wed, 31 Dec '69

This message was last edited by the user at 17:06, Sun 17 Jan.

Locke1221
 subscriber, 53 posts
Sun 17 Jan 2021
at 17:19
Re: RPoL Design Update
Thanks for the updates Jase, I imagine it's been busy and I appreciate the effort.

Acknowledging that I'm in the minority in regards to last login as well, I do have to say that the current bareness of the Cast List, showing -only- last login and last post is jarring and not terribly attractive.

I also have to put a request forward for Tag to return to being automatically displayed. In my current military games, I use those for player rank, and find that being obvious rather than the players having to mouse over for the dropdown to be far advantageous. I feel like I'm probably not the only one who uses it in some way that feels like it's more integral to the game than either login or last post.

Is there any possibility of GMs getting to select what is visible for their games? Not knowing what sort of coding that would require, I can understand it not being so, but it sounds like a great compromise if it is.
jase
 admin, 3799 posts
 Cogito, ergo procuro.
 Carpe stultus!
Mon 18 Jan 2021
at 04:37
Re: RPoL Design Update
Forgot to put in my last change notes, posting a private message now updates your "last post" (which will also affect last logon).  A post is a post, just because everyone doesn't have access to it doesn't negate that's the date of your last post.

As for the cast list, I don't disagree that's it's pretty bare now.  That's the problem when we enlarge the font and also start to care about not having some crazy squished view on narrower views.  The only thing I could possibly squeeze in is post count.  Tags can be long and I'm pretty sure it will cause issue if the tag is near maximum length (though I'll double-check).
jase
 admin, 3800 posts
 Cogito, ergo procuro.
 Carpe stultus!
Mon 18 Jan 2021
at 15:13
Re: RPoL Design Update
Try the cast page now.
  • Changed the way each cell/block is rendered, which will make text wrap rather than potentially overlap other text.  On really narrow screens (or a very long name with no spaces) it'll force the screen to scroll left/right.
  • To give us more room I removed the weekday from the date of last post/logon.
  • Added both post count and character tag columns.  Groups are still hidden (until mouse over/tap).
  • The post count column will automatically hide on small screens (695 pixel with and lower) and instead appear under the mouse/tap section.

Also fixed the 1969/1970 post date (depending on your time zone).  (c;

This message was last edited by the user at 15:19, Mon 18 Jan.

SunRuanEr
 subscriber, 358 posts
Mon 18 Jan 2021
at 15:23
Re: RPoL Design Update
Thanks for putting the tags back, jase! \ o /

In regards to PMs tripping last logins...that's not currently working. =( Just tested, using a GM-controlled character and a regular character, and the PM didn't trip Last Post for either, or Last Login for the GM-controlled character. (Obviously, the regular character tripped login like normally).
jase
 admin, 3801 posts
 Cogito, ergo procuro.
 Carpe stultus!
Tue 19 Jan 2021
at 05:51
Re: RPoL Design Update
Whoops, I was updating the user last logon.  Have now done what I said, posting a private message will update the last post for that character (regardless of who posted it).

So hawk eyed cast-list-watchers beware, GMs posting for a character played by someone else can make the last post be newer than the last logon.  That'll add some more confusion to those trying to figure out who plays what.  (c;

I'm also thinking about making the last logon field be "this week", "this fortnight", "this month", "this quarter", "this year" and "ages ago".  Or something like that.  Apparently we need to go to great length to hide GM controlled PCs.

Was a fair bit of work and pretty pleased with the new cast layout so would appreciate any other feedback.  (c;
nauthiz
 subscriber, 698 posts
Tue 19 Jan 2021
at 06:12
Re: RPoL Design Update
Works good.

The only issue I can forsee is that the date can already cause word wrap making the visible line entry two lines high on narrow screen devices

While I'm thankful that everything is at least top aligned now (vs one of the mockups previously presented where it was the opposite) anything more verbose might make it visually worse unless you force it to stick to one line and horizontally scroll or something.
SunRuanEr
 subscriber, 359 posts
Tue 19 Jan 2021
at 14:49
Re: RPoL Design Update
Sweet, thanks jase! Works just like it's supposed to, now. \ o /

Aesthetically, I'm down with the new layout. The four columns give it a balance that it didn't have when there were just two, while providing the information that the majority of people need & obscuring what most people didn't - so it's win-win.

I wouldn't argue with the last login field being something like 'Today', 'This week', 'This month', 'Months ago' for players if you really wanted to go there, but it's probably not necessary now that PMs trip logins. (I'll admit that I *do* wish that PMs could trip logins without tripping last post so that it could be done more surreptitiously - so that GMs could just have all their characters in a PM with each other without it looking like they were all in a PM with each other - but I feel those two things are clearly just inextricably linked with regards to GM-controlled characters, so I'll take what I can get! An obvious PM post that trips login is waaaaay better than a hidden PM post that doesn't.) I do think that keeping the 'Today' is going to be important for people who want to know if someone else has seen a recent post, if you do decide to obfuscate last login dates more.

quote:
Apparently we need to go to great length to hide GM controlled PCs.

Ironically, what necessitated the need for being able to trip last login for GM-controlled PCs with posts of any kind is the first layer of hiding them! =)

Years ago, GM-controlled PCs logged in whenever the GM logged in, then the code started making that last login appear random from the player side, while the GM still saw their characters all log in at the same time*. Which meant that it was necessary to force-update the last login to 'Today' if those characters made a post, because otherwise it looks like a bizarro glitch from the player side and the GM wouldn't have had any idea.

Truthfully, you could do away with that original obfuscation entirely, and it would solve the issue just as much because then GM-controlled characters would just look like active players, instead of needing a way to trip logins for characters that look (to other players) like they've taken a weeks'/months' long powder. =)

* - this is still weird, and for GMs that don't have a friend/spouse/etc that play in their games with them that know their characters, they tend to have no idea that their characters have wonky login times that probably should be tripped so that they don't look inactive.
Low Key
 subscriber, 251 posts
Tue 19 Jan 2021
at 15:23
Re: RPoL Design Update
Thanks for your work on this Jase, and for not taking 'last logon' away from us players who make use of it.

jase:
I'm also thinking about making the last logon field be "this week", "this fortnight", "this month", "this quarter", "this year" and "ages ago".  Or something like that.  Apparently we need to go to great length to hide GM controlled PCs.


I'd second the idea to add "today" to the options.
Otherwise a lot of functionality to me (as a player) would be lost. (I made a post a while back explaining how/why I use last login as a player. I can repeat the relevant points if that'd be helpful, but I don't want to wall o' text the thread with things I've already said if it isn't helpful to anyone).

This message was last edited by the user at 15:23, Tue 19 Jan.

jase
 admin, 3804 posts
 Cogito, ergo procuro.
 Carpe stultus!
Thu 21 Jan 2021
at 09:35
Re: RPoL Design Update
After letting it stew in the back of my mind for a few days I've now set the responsive and traditional site to share cookies.  This means you should see the exact same message read/unread over both sites.

Please relog one more time to make sure all the old cookies from the responsive site are cleared.  As always if you're switching browsers/machines it's recommend that you relog to sync up the cookies.
evileeyore
 member, 442 posts
 GURPS GM and Player
 Joined August 2015
Thu 21 Jan 2021
at 20:49
Re: RPoL Design Update
Low Key:
I'd second the idea to add "today" to the options.

I'm in this camp.  I use Player login dates to determine if we're waiting on someone to login to post so I don't spotlight hog or step on people's toes by post more prolifically than they are able.

If I see they've been in repeatedly and said nothing, I'll happily steal all their spotlights and step on all the toes.


Side note, what does Last Login measure?  Last time logged into RPoL?  Last time they opened threads to that game?  Last time they posted?
bigbadron
 moderator, 15992 posts
 He's big, he's bad,
 but mostly he's Ron.
Thu 21 Jan 2021
at 21:02
Re: RPoL Design Update
In reply to evileeyore (msg # 478):

It reports the last time they opened that particular game.
evileeyore
 member, 443 posts
 GURPS GM and Player
 Joined August 2015
Thu 21 Jan 2021
at 22:09
Re: RPoL Design Update
bigbadron:
It reports the last time they opened that particular game.

Thanks!  That's what I hoped.
jase
 admin, 3811 posts
 Cogito, ergo procuro.
 Carpe stultus!
Sun 24 Jan 2021
at 05:04
Re: RPoL Design Update
Small update popped on.

  • Removed javascript requirement for the "wanted" forums search box.  Now just uses HTML, a checkbox and the CSS general sibling selector.  Same as what the menus use on small/mobile screens.
  • Removed most usages of "document.write".
  • Added SLA Industries to the dice roller (as per that thread, Cyberpunk RED coming as soon as I can figure it).
  • Fixed (presumably) some small stuff as I encountered/spotted it.

jase
 admin, 3815 posts
 Cogito, ergo procuro.
 Carpe stultus!
Mon 25 Jan 2021
at 09:50
Re: RPoL Design Update
Popped on another update.  Small tweak to the CSS colours so update your themes when you can.  You'll have some minor overzealous border colouring for the below until you do.
  • Improved(?) the mutli-private window.  Also removed table usage.
  • Also tweaked the selection toggles for the portrait searching.
  • Changed the user preferences on/off selections to toggles while I was at it.

SunRuanEr
 subscriber, 362 posts
Mon 25 Jan 2021
at 13:43
Re: RPoL Design Update
Awesome.

Do we need to relog again? I'm seeing instances of unread threads not keeping the unread message flag, now that I wasn't seeing before this morning. Like when I open a forum, read one thread with new messages but not another that also has new messages, but then go back to the main menu - the forum is no longer popping red even though there are still unread messages in it.

That's not an entirely new thing I don't think, but I'm pretty sure that for a while here recently (at least after the recent cookie synch) that wasn't happening... (Or I could be losing my mind, always a possibility!)
jase
 admin, 3816 posts
 Cogito, ergo procuro.
 Carpe stultus!
Mon 25 Jan 2021
at 15:27
Re: RPoL Design Update
Shouldn't be a need to relog.  I had odd message indicators today when I switched between devices, which should generally be expected, but I'm still keeping an eye on it.

I have an idea floating around in my head to detect when you switch devices and update the read cookies like you've done a relog.  Pondering it for a bit longer before I pull the trigger on that.

Also just updated the main menu a tad, the "main menu" menu links should now jump to the various spots on the screen (if you've got enough listed to cause a scroll) plus it'll hide the menu items you don't have any of (i.e. won't display a discussion forum link if you don't have any discussion forums stickied).
nauthiz
 subscriber, 702 posts
Mon 25 Jan 2021
at 23:53
Re: RPoL Design Update
A fix for the cookie issue would certainly solve what seems to be the most frequently brought up issue.
jase
 admin, 3821 posts
 Cogito, ergo procuro.
 Carpe stultus!
Sat 30 Jan 2021
at 06:06
Re: RPoL Design Update
Ok I think I've got the view impersonation and private lines (which includes private groups and language lines) sorted.  About the most complicated thing I've done here.

When viewing a thread with private groups it will only reveal the lines to players who have a character in that group.  Basically if a character would qualify as a recipient in a private line but they're not a participant in thread to then it'll skip them as a valid recipient.  This includes "not".  So if you say "not woof" but woof isn't a party to the thread then it'll skip excluding them, so the owner of woof will still see the line.

This flows to view impersonating as well.  Even further, if you view as woof and woof isn't part of the thread then you're going to see absolutely no private lines and all languages will be scrambled.  There is a minor exception to this when you're a GM and using "not" but you'll see that.

The preview notice will let you know if you've opted to view as a character who can't see the thread.

I also fixed private lines and previewing for private messages, same rules apply as above.

As mentioned it's very complicated so let me know if anything awry happens.

Also removed some more tables before I tackled the above.  Little bit in rMail and info screens, you shouldn't notice much change there as the visual output should be the same.
Starchaser
 member, 848 posts
 Shoda mo tsumoreba taibok
Sat 30 Jan 2021
at 06:19
Re: RPoL Design Update
In reply to jase (msg # 486):

Thats much better for the preview as but I think the languages preview might still be broken. If I preview as the poster with a language group tag then his speech is legible. If I preview as another character of the same language group then the speech is gobbledygook to her.
jase
 admin, 3822 posts
 Cogito, ergo procuro.
 Carpe stultus!
Sat 30 Jan 2021
at 07:48
Re: RPoL Design Update
That's by design, check the note at the top.

If it wasn't that way then you'd know who was in the private group, which has its members hidden.
JohnB
 supporter, 2114 posts
 Demigod of the Stunties
Sat 30 Jan 2021
at 08:20
Re: RPoL Design Update
jase:
Ok I think I've got the view impersonation and private lines (which includes private groups and language lines) sorted.  About the most complicated thing I've done here.


Thank you  :)  I might not be as active as I was, but I appreciate the work you do to keep the site developing and growing.  All power to your elbow :)
jase
 admin, 3823 posts
 Cogito, ergo procuro.
 Carpe stultus!
Sat 30 Jan 2021
at 08:54
Re: RPoL Design Update
To further clarify "preview as", unless you're a GM it's severely limited when using private groups (and languages, which are just a special way of addressing groups).

In a nutshell to avoid revealing members of a private group it'll assume the "worst".

That is if you say "private to group xxx" it'll assume the player is not a member.  If you say "private to not group xxx" it'll assume they are a member.

So, if you preview as "Bob" who is or isn't a member of the private group "Whatever" (the result is the same regardless whether he's a member of the private group):

Private lineVisibility
Private to BobShown
Private to group WhateverHidden
Private to not group WhateverHidden
Private to Bob; group WhateverShown
Private to Bob; not group WhateverHidden
Language WhateverScrambled

Also, if you preview as Bob and he doesn't have access to the thread then everything will be hidden/scrambled anyway.  Kind of a moot point as they can't even open the thread, but the permission check figures the character has no access to the thread so hides everything.  Behaviour of this could be changed and instead provide a theoretical view if they did have access, might be slightly helpful of a GM plans on moving the thread group after (or giving the character access to that group).