Msg#: 3602975 posted 3:15 pm on Mar 17, 2008 (gmt 0)
I find the fact that thread notifications point to the start of the thread rather than the most recent post irritating. Wouldn't it be possible to point them to the last page with most recent entry?
This would make accessing the thread a bit quicker and more intuitive. I mean if you are subscribed to a thread and you get a notification that someone has added something what's the point of linking back to the start?
Msg#: 3602975 posted 3:18 pm on Mar 17, 2008 (gmt 0)
because everyone has different settings for "posts per thread" therefore making it ridiculously intensive to get everyone's settings to send the email, which would then be a unique email per user that has notification for any given thread, and fix a link
Msg#: 3602975 posted 3:48 pm on Mar 17, 2008 (gmt 0)
Because everyone has different settings for "posts per thread" therefore making it ridiculously intensive to get everyone's settings to send the email.
I'll second the motion! I'm not sure I understand the challenge. Each reply has a unique number associated with it, why can't there be a "fragement identifier" attached that takes you to that post? Just like when you are returned to your reply?
Msg#: 3602975 posted 4:17 pm on Mar 17, 2008 (gmt 0)
I will admit that I have no idea of the technicalities involved.
Me too. I still don't understand how the multi thread affects the fragment identifier. Its a client side function and no matter where that post is, the user should end up there. I'm sure Adam has been mulling this one over as it has been this way as long as I can remember. I do believe there was a time where it was implemented but only briefly, yes?
Msg#: 3602975 posted 4:25 pm on Mar 17, 2008 (gmt 0)
A lot of BBS software allows a link to a post, as well as to a thread (the post is an extra variable in the URL).
The problem with the fragment identifier on this site is that it must point to an anchor on the page you're viewing. So 3602975.htm#msg3603003 might work, but 3602975-2-30.htm#msg3603003 may well not. At a minimum it would need the post ID to passed to the server.
[edited by: Receptional_Andy at 4:26 pm (utc) on Mar. 17, 2008]