Join our Folding@Home team:
Main F@H site
Our team page
Covers transactions:
2020-01-01 00:00:00 ..
2020-06-30 21:00:33 UTC
(SPIDs: [1207..1407])
Last Update:
2020-07-01 02:02:58 UTC
--martyb
Support us: Subscribe Here
and buy SoylentNews Swag
We always have a place for talented people, visit the Get Involved section on the wiki to see how you can make SoylentNews better.
Covers transactions:
2020-01-01 00:00:00 ..
2020-01-31 06:46:05 UTC
(SPIDs: [1207..1216])
Last Update:
2020-01-31 12:48:47 UTC
--martyb
It would be helpful for the user to have a label to explain what the seemingly barren "(1)" that appears in two places on a story actually means. Granted, on stories with enough comments, and that actually spills over onto additional pages, there is a bit more of an indication, but it could be made explicitly clear by adding just two lines to one template.
Extended copy has the updated version of the template. The two lines which contain only "Page:" are all it takes.
[% IF !((total < user.commentlimit) || (user.commentlimit < 1)) && (legacy == "yes") %]
[% pages = total / user.commentlimit %]
<div class="linkCommentPage">
Page:
[% FOREACH p = [1 .. pages] %]
[% start = user.commentlimit * p %]
[% IF p != 0 %] | [% END %]
[% IF start == form.startat || (!form.startat && p == 0) %]
<b>([% p %])</b>
[% ELSE %]
[% Slash.linkComment({
sid => sid,
pid => pid,
cid => cid,
threshold => threshold,
highlightthresh = highlightthresh,
subject => p,
subject_only => 1,
startat => (start ? start : 0),
}) %]
[% END %]
[% END %]
[% IF user.breaking %]
([% constants.sitename %] Overload: CommentLimit [% user.commentlimit %])
[% END %]
</div>
[% ELSIF (legacy == "no") %]
<div class="linkCommentPage">
Page:
[% form.page = (form.page || 1) %]
[% FOREACH p = [1 .. tpages] %]
[% IF p != form.page %]
[% Slash.linkComment({
sid => sid,
pid => pid,
cid => cid,
threshold => threshold,
highlightthresh = highlightthresh,
subject => (p),
subject_only => 1,
page => (p),
}) %]
[% ELSE %]
<b>([% p %])</b>
[% END %]
[% END %]
</div>
[% END %]
This story is for you. Feel free to play around with the new features, post comments, and moderate to your heart's content. If you find anything amiss or wish to discuss a feature or provide feedback, please comment here and/or leave a comment on the #dev channel on IRC.
20170215e - Test Story - Please DO NOT Moderate and DO NOT Post Comments - Comment Score Testing
The comment structure AND the comment scores have been carefully crafted - please do not touch. --martyb
There is one top-level comment (TLC); it has score: -1
That TLC has 4 children, respectively scored: -1, 0, 1, and 2.
EACH of those children has 4 children, respectively scored: -1, 0, 1, and 2.
-1 -1 -1
0
1
2
0 -1
0
1
2
1 -1
0
1
2
2 -1
0
1
2
Have a few issues with the new "[Continues...]" item which is automatically added to stories that have a non-empty "Extended Copy" section.
1) When editing a story, the "[Continues...]" text does not appear when I click on the "Preview" button.
2) Accidentally discovered it is implemented as a link, not just plain text, when I somehow clicked on it on the main page and saw the extended copy text suddenly appear... this is confusing. It looks exactly like the text we editors previously inserted into stories manually, but has a different effect -- need to visually distinguish it from the old-style, text-only version (e.g. one couldunderline the link but see next item).
3) Once I click on the "[Continues...]" link on the main page and see the expanded text, I see no way to re-collapse it. :(
4) May I suggest reusing the "Expand/Collapse comment" single-chevron that is employed in the new threaded comment code?
5) For completeness' sake, the prior 4 items were in the "Intro Copy" text box, and this item is at the top of the "Extended Copy" text box.
20170215d - clone of 20170215b - Please Moderate but post no comments
[cONTINUES...]
:: Specify cookie first, otherwise, the chain of invocations ends up defaulting to martyb:
CALL SN_API_cookies "cookies.martyb.txt"
:: This is the story we want to post comments to:
CALL SN_API_story_URL "https://dev.soylentnews.org/article.pl?sid=17/02/15/1622227"
:: Non-subscribers need to wait 10s after getting reskey before they can post a comment;
:: Subscribers do not need to wait:
CALL SN_API_comment_sleep 0s
SET sn
PAUSE
CALL comment 0000
SET sn
PAUSE
CALL comment 0001 --reply-to 0000
CALL comment 0002 --reply-to 0001
CALL comment 0003 --reply-to 0002
CALL comment 0004 --reply-to 0002
CALL comment 0005 --reply-to 0001
CALL comment 0006 --reply-to 0005
CALL comment 0007 --reply-to 0005
CALL comment 0008 --reply-to 0000
CALL comment 0009 --reply-to 0008
CALL comment 0010 --reply-to 0009
CALL comment 0011 --reply-to 0009
CALL comment 0012 --reply-to 0008
CALL comment 0013 --reply-to 0012
CALL comment 0014 --reply-to 0012
CALL comment 0015
CALL comment 0016 --reply-to 0015
CALL comment 0017 --reply-to 0016
CALL comment 0018 --reply-to 0017
CALL comment 0019 --reply-to 0017
CALL comment 0020 --reply-to 0016
CALL comment 0021 --reply-to 0020
CALL comment 0022 --reply-to 0020
CALL comment 0023 --reply-to 0015
CALL comment 0024 --reply-to 0023
CALL comment 0025 --reply-to 0024
CALL comment 0026 --reply-to 0024
CALL comment 0027 --reply-to 0023
CALL comment 0028 --reply-to 0027
CALL comment 0029 --reply-to 0027
20170215c - Test Story - Please Moderate but Post No Comments - Bifurcation Breadth-First
This story and its comments is intended to be a clone of 20170215a -- please post no comments, but DO feel free to moderate! --martyb
:: Specify cookie first, otherwise, the chain of invocations ends up defaulting to martyb:
CALL SN_API_cookies "cookies.martyb.txt"
:: This is the story we want to post comments to:
CALL SN_API_story_URL "https://dev.soylentnews.org/article.pl?sid=17/02/15/175202"
:: Non-subscribers need to wait 10s after getting reskey before they can post a comment;
:: Subscribers do not need to wait:
CALL SN_API_comment_sleep 0s
SET sn
PAUSE
:: Create 2 top-level comments
CALL comment 0000
SET sn
PAUSE
CALL comment 0001
:: Create replies (2nd-level comments) for each of those TLCs:
CALL comment 0002 --reply-to 0000
CALL comment 0003 --reply-to 0000
CALL comment 0004 --reply-to 0001
CALL comment 0005 --reply-to 0001
:: Create replies (3rd level comments) for each of the 2nd-level comments:
CALL comment 0006 --reply-to 0002
CALL comment 0007 --reply-to 0002
CALL comment 0008 --reply-to 0003
CALL comment 0009 --reply-to 0003
CALL comment 0010 --reply-to 0004
CALL comment 0011 --reply-to 0004
CALL comment 0012 --reply-to 0005
CALL comment 0013 --reply-to 0005
:: Create replies (4th level comments) for each of the 3rd-level comments:
CALL comment 0014 --reply-to 0006
CALL comment 0015 --reply-to 0006
CALL comment 0016 --reply-to 0007
CALL comment 0017 --reply-to 0007
CALL comment 0018 --reply-to 0008
CALL comment 0019 --reply-to 0008
CALL comment 0020 --reply-to 0009
CALL comment 0021 --reply-to 0009
CALL comment 0022 --reply-to 0010
CALL comment 0023 --reply-to 0010
CALL comment 0024 --reply-to 0011
CALL comment 0025 --reply-to 0011
CALL comment 0026 --reply-to 0012
CALL comment 0027 --reply-to 0012
CALL comment 0028 --reply-to 0013
CALL comment 0029 --reply-to 0013