Nice! (Score: 3, Informative) by computermachine@pipedot.org on 2014-05-13 10:54 (#1J0) This is a very useful feature. Re: Nice! (Score: 1) by zafiro17@pipedot.org on 2014-05-13 16:34 (#1JD) Agreed - this is very useful and is a huge improvement in useability. Im not aware of any other site on earth that does this. Does anyone know of another site offering this functionality? Has it ever been seen in the wild? Re: Nice! (Score: 3, Insightful) by fatphil@pipedot.org on 2014-05-13 17:33 (#1JH) It's totally freaking awesome!Of course, it's been seen before in the environment called "Usenet" (and also "email"), but on something that's a web-forum, it indeed does seem to be new.Which reminds me - I look forward to the NNTP interface ;-) Re: Nice! (Score: 2, Interesting) by fatphil@pipedot.org on 2014-05-13 17:38 (#1JJ) However, there's a bug :-(If you reply to a post at the top of the thread, before reading the whole thread, then when you return to the thread after clicking "post", all those things you've not read are greyed out.I presume this is just timestamp-based? If so, perhaps don't commit the "thread last rendered" timestamp until some affirmative thread-leaving action is performed. Posting a reply would not be classified as a thread-leaving action. This might require some significantly trickier smarts to implement than just the naive situation we have at the moment.Simpler Workaround: middle-click the "reply" link to get it in a new tab, and then just close after posting. Re: Nice! (Score: 2, Informative) by bryan@pipedot.org on 2014-05-18 03:12 (#1PS) Posting a reply would not be classified as a thread-leaving action.Implemented. Posting a reply will now prevent the colors from changing on the rest of the comments. Re: Nice! (Score: 1) by fatphil@pipedot.org on 2014-05-18 18:28 (#1Q6) There seems to be a bug which appears related to such a change:Notice: Undefined index: last_time in /var/pipedot/lib/tools/tools.php on line 768 error: sql [insert into story_history (sid, zid, time, last_time) values (?, ?, ?, ?)] arg [183, fatphil@pipedot.org, 1400437667, ] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'last_time' cannot be null]
Re: Nice! (Score: 1) by zafiro17@pipedot.org on 2014-05-13 16:34 (#1JD) Agreed - this is very useful and is a huge improvement in useability. Im not aware of any other site on earth that does this. Does anyone know of another site offering this functionality? Has it ever been seen in the wild? Re: Nice! (Score: 3, Insightful) by fatphil@pipedot.org on 2014-05-13 17:33 (#1JH) It's totally freaking awesome!Of course, it's been seen before in the environment called "Usenet" (and also "email"), but on something that's a web-forum, it indeed does seem to be new.Which reminds me - I look forward to the NNTP interface ;-) Re: Nice! (Score: 2, Interesting) by fatphil@pipedot.org on 2014-05-13 17:38 (#1JJ) However, there's a bug :-(If you reply to a post at the top of the thread, before reading the whole thread, then when you return to the thread after clicking "post", all those things you've not read are greyed out.I presume this is just timestamp-based? If so, perhaps don't commit the "thread last rendered" timestamp until some affirmative thread-leaving action is performed. Posting a reply would not be classified as a thread-leaving action. This might require some significantly trickier smarts to implement than just the naive situation we have at the moment.Simpler Workaround: middle-click the "reply" link to get it in a new tab, and then just close after posting. Re: Nice! (Score: 2, Informative) by bryan@pipedot.org on 2014-05-18 03:12 (#1PS) Posting a reply would not be classified as a thread-leaving action.Implemented. Posting a reply will now prevent the colors from changing on the rest of the comments. Re: Nice! (Score: 1) by fatphil@pipedot.org on 2014-05-18 18:28 (#1Q6) There seems to be a bug which appears related to such a change:Notice: Undefined index: last_time in /var/pipedot/lib/tools/tools.php on line 768 error: sql [insert into story_history (sid, zid, time, last_time) values (?, ?, ?, ?)] arg [183, fatphil@pipedot.org, 1400437667, ] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'last_time' cannot be null]
Re: Nice! (Score: 3, Insightful) by fatphil@pipedot.org on 2014-05-13 17:33 (#1JH) It's totally freaking awesome!Of course, it's been seen before in the environment called "Usenet" (and also "email"), but on something that's a web-forum, it indeed does seem to be new.Which reminds me - I look forward to the NNTP interface ;-) Re: Nice! (Score: 2, Interesting) by fatphil@pipedot.org on 2014-05-13 17:38 (#1JJ) However, there's a bug :-(If you reply to a post at the top of the thread, before reading the whole thread, then when you return to the thread after clicking "post", all those things you've not read are greyed out.I presume this is just timestamp-based? If so, perhaps don't commit the "thread last rendered" timestamp until some affirmative thread-leaving action is performed. Posting a reply would not be classified as a thread-leaving action. This might require some significantly trickier smarts to implement than just the naive situation we have at the moment.Simpler Workaround: middle-click the "reply" link to get it in a new tab, and then just close after posting. Re: Nice! (Score: 2, Informative) by bryan@pipedot.org on 2014-05-18 03:12 (#1PS) Posting a reply would not be classified as a thread-leaving action.Implemented. Posting a reply will now prevent the colors from changing on the rest of the comments. Re: Nice! (Score: 1) by fatphil@pipedot.org on 2014-05-18 18:28 (#1Q6) There seems to be a bug which appears related to such a change:Notice: Undefined index: last_time in /var/pipedot/lib/tools/tools.php on line 768 error: sql [insert into story_history (sid, zid, time, last_time) values (?, ?, ?, ?)] arg [183, fatphil@pipedot.org, 1400437667, ] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'last_time' cannot be null]
Re: Nice! (Score: 2, Interesting) by fatphil@pipedot.org on 2014-05-13 17:38 (#1JJ) However, there's a bug :-(If you reply to a post at the top of the thread, before reading the whole thread, then when you return to the thread after clicking "post", all those things you've not read are greyed out.I presume this is just timestamp-based? If so, perhaps don't commit the "thread last rendered" timestamp until some affirmative thread-leaving action is performed. Posting a reply would not be classified as a thread-leaving action. This might require some significantly trickier smarts to implement than just the naive situation we have at the moment.Simpler Workaround: middle-click the "reply" link to get it in a new tab, and then just close after posting. Re: Nice! (Score: 2, Informative) by bryan@pipedot.org on 2014-05-18 03:12 (#1PS) Posting a reply would not be classified as a thread-leaving action.Implemented. Posting a reply will now prevent the colors from changing on the rest of the comments. Re: Nice! (Score: 1) by fatphil@pipedot.org on 2014-05-18 18:28 (#1Q6) There seems to be a bug which appears related to such a change:Notice: Undefined index: last_time in /var/pipedot/lib/tools/tools.php on line 768 error: sql [insert into story_history (sid, zid, time, last_time) values (?, ?, ?, ?)] arg [183, fatphil@pipedot.org, 1400437667, ] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'last_time' cannot be null]
Re: Nice! (Score: 2, Informative) by bryan@pipedot.org on 2014-05-18 03:12 (#1PS) Posting a reply would not be classified as a thread-leaving action.Implemented. Posting a reply will now prevent the colors from changing on the rest of the comments. Re: Nice! (Score: 1) by fatphil@pipedot.org on 2014-05-18 18:28 (#1Q6) There seems to be a bug which appears related to such a change:Notice: Undefined index: last_time in /var/pipedot/lib/tools/tools.php on line 768 error: sql [insert into story_history (sid, zid, time, last_time) values (?, ?, ?, ?)] arg [183, fatphil@pipedot.org, 1400437667, ] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'last_time' cannot be null]
Re: Nice! (Score: 1) by fatphil@pipedot.org on 2014-05-18 18:28 (#1Q6) There seems to be a bug which appears related to such a change:Notice: Undefined index: last_time in /var/pipedot/lib/tools/tools.php on line 768 error: sql [insert into story_history (sid, zid, time, last_time) values (?, ?, ?, ?)] arg [183, fatphil@pipedot.org, 1400437667, ] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'last_time' cannot be null]