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
Created at 20170228_014015 UTC to provide a place for NCommander to play around with the new commenting code.
CALL comment 0000
CALL comment 0001 --reply-to 0000
CALL comment 0002 --reply-to 0001
CALL comment 0003
CALL comment 0004 --reply-to 0003
CALL comment 0005 --reply-to 0004
CALL comment 0006
CALL comment 0007 --reply-to 0006
CALL comment 0008 --reply-to 0007
CALL comment 0009 --reply-to 0008
CALL comment 0010
CALL comment 0011 --reply-to 0010
CALL comment 0012 --reply-to 0011
CALL comment 0013
CALL comment 0014 --reply-to 0013
CALL comment 0015 --reply-to 0014
CALL comment 0016
CALL comment 0017 --reply-to 0016
CALL comment 0018 --reply-to 0017
CALL comment 0019 --reply-to 0018
CALL comment 0020
CALL comment 0021 --reply-to 0020
CALL comment 0022 --reply-to 0021
CALL comment 0023
CALL comment 0024 --reply-to 0023
CALL comment 0025 --reply-to 0024
CALL comment 0026
CALL comment 0027 --reply-to 0026
CALL comment 0028 --reply-to 0027
CALL comment 0029 --reply-to 0028
CALL comment 0030
CALL comment 0031 --reply-to 0030
CALL comment 0032 --reply-to 0031
CALL comment 0033
CALL comment 0034 --reply-to 0033
CALL comment 0035 --reply-to 0034
CALL comment 0036
CALL comment 0037 --reply-to 0036
CALL comment 0038 --reply-to 0037
CALL comment 0039 --reply-to 0038
CALL comment 0040
CALL comment 0041 --reply-to 0040
CALL comment 0042 --reply-to 0041
CALL comment 0043
CALL comment 0044 --reply-to 0043
CALL comment 0045 --reply-to 0044
CALL comment 0046
CALL comment 0047 --reply-to 0046
CALL comment 0048 --reply-to 0047
CALL comment 0049 --reply-to 0048
CALL comment 0050
CALL comment 0051 --reply-to 0050
CALL comment 0052 --reply-to 0051
CALL comment 0053
CALL comment 0054 --reply-to 0053
CALL comment 0055 --reply-to 0054
CALL comment 0056
CALL comment 0057 --reply-to 0056
CALL comment 0058 --reply-to 0057
CALL comment 0059 --reply-to 0058
Created 20170228_005306 UTC for TheMightyBuzzard to have some comment he can moderate and/or add to as he sees fit.
CALL comment 0000
SET sn
PAUSE
CALL comment 0001 --reply-to 0000
CALL comment 0002 --reply-to 0001
CALL comment 0003
CALL comment 0004 --reply-to 0003
CALL comment 0005 --reply-to 0004
CALL comment 0006
CALL comment 0007 --reply-to 0006
CALL comment 0008 --reply-to 0007
CALL comment 0009 --reply-to 0008
CALL comment 0010
CALL comment 0011 --reply-to 0010
CALL comment 0012 --reply-to 0011
CALL comment 0013
CALL comment 0014 --reply-to 0013
CALL comment 0015 --reply-to 0014
CALL comment 0016
CALL comment 0017 --reply-to 0016
CALL comment 0018 --reply-to 0017
CALL comment 0019 --reply-to 0018
CALL comment 0020
CALL comment 0021 --reply-to 0020
CALL comment 0022 --reply-to 0021
CALL comment 0023
CALL comment 0024 --reply-to 0023
CALL comment 0025 --reply-to 0024
CALL comment 0026
CALL comment 0027 --reply-to 0026
CALL comment 0028 --reply-to 0027
CALL comment 0029 --reply-to 0028
CALL comment 0030
CALL comment 0031 --reply-to 0030
CALL comment 0032 --reply-to 0031
CALL comment 0033
CALL comment 0034 --reply-to 0033
CALL comment 0035 --reply-to 0034
CALL comment 0036
CALL comment 0037 --reply-to 0036
CALL comment 0038 --reply-to 0037
CALL comment 0039 --reply-to 0038
CALL comment 0040
CALL comment 0041 --reply-to 0040
CALL comment 0042 --reply-to 0041
CALL comment 0043
CALL comment 0044 --reply-to 0043
CALL comment 0045 --reply-to 0044
CALL comment 0046
CALL comment 0047 --reply-to 0046
CALL comment 0048 --reply-to 0047
CALL comment 0049 --reply-to 0048
CALL comment 0050
CALL comment 0051 --reply-to 0050
CALL comment 0052 --reply-to 0051
CALL comment 0053
CALL comment 0054 --reply-to 0053
CALL comment 0055 --reply-to 0054
CALL comment 0056
CALL comment 0057 --reply-to 0056
CALL comment 0058 --reply-to 0057
CALL comment 0059 --reply-to 0058
Bytram's Bored Room -- 20170320_143211 UTC
:: This is the story we want to post comments to:
CALL SN_API_story_URL "%~1"
:: 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
CALL comment 0004 --reply-to 0003
CALL comment 0005 --reply-to 0004
CALL comment 0006
CALL comment 0007 --reply-to 0006
CALL comment 0008 --reply-to 0007
CALL comment 0009 --reply-to 0008
CALL comment 0010
CALL comment 0011 --reply-to 0010
CALL comment 0012 --reply-to 0011
CALL comment 0013
CALL comment 0014 --reply-to 0013
CALL comment 0015 --reply-to 0014
CALL comment 0016
CALL comment 0017 --reply-to 0016
CALL comment 0018 --reply-to 0017
CALL comment 0019 --reply-to 0018
CALL comment 0020
CALL comment 0021 --reply-to 0020
CALL comment 0022 --reply-to 0021
CALL comment 0023
CALL comment 0024 --reply-to 0023
CALL comment 0025 --reply-to 0024
CALL comment 0026
CALL comment 0027 --reply-to 0026
CALL comment 0028 --reply-to 0027
CALL comment 0029 --reply-to 0028
CALL comment 0030
CALL comment 0031 --reply-to 0030
CALL comment 0032 --reply-to 0031
CALL comment 0033
CALL comment 0034 --reply-to 0033
CALL comment 0035 --reply-to 0034
CALL comment 0036
CALL comment 0037 --reply-to 0036
CALL comment 0038 --reply-to 0037
CALL comment 0039 --reply-to 0038
CALL comment 0040
CALL comment 0041 --reply-to 0040
CALL comment 0042 --reply-to 0041
CALL comment 0043
CALL comment 0044 --reply-to 0043
CALL comment 0045 --reply-to 0044
CALL comment 0046
CALL comment 0047 --reply-to 0046
CALL comment 0048 --reply-to 0047
CALL comment 0049 --reply-to 0048
CALL comment 0050
CALL comment 0051 --reply-to 0050
CALL comment 0052 --reply-to 0051
CALL comment 0053
CALL comment 0054 --reply-to 0053
CALL comment 0055 --reply-to 0054
CALL comment 0056
CALL comment 0057 --reply-to 0056
CALL comment 0058 --reply-to 0057
CALL comment 0059 --reply-to 0058
CALL comment 0100
CALL comment 0101 --mod Interesting
CALL comment 0102 --mod fun touch under
CALL comment 0103 --reply-to 0102 --mod insight interest
In Chile a woody vine, Boquila trifoliolata, has been discovered to change the shape of its leaves depending on what tree is is climbing.
Further, the same single vine can drape from one tree to different species of tree, and it will match the shape and size of its leaves to those of each host only along that portion of its length.
Other vines are known to mimic one species of host, as a defense against herbivores, but this vine can mimic many, along its length.
Biologists say "It is unclear how B. trifoliolata vines discern the identity of individual trees and shape-shift accordingly." Speculation is that chemicals or microbes might trigger gene-activating signals that trigger leaf differentiation.
But left unsaid is how would the vine "learn" match the shape of its new host's leaf, how it would know it had succeeded, where it would acquire the genes to do so, and how many different trees it can mimic.
Don't you need eyes to copy someone else's look?
Research has shown that smartphone sensors leave trackable fingerprints. Due to imperfections in the hardware manufacturing process, it is possible to distinguish different devices just from sensor data.
The researchers tested more than 100 devices over the course of nine months: 80 standalone accelerometer chips used in popular smartphones, 25 Android phones and two tablets.
The accelerometers in all permutations were selected from different manufacturers, to ensure that the fingerprints weren't simply defects resulting from a particular production line.
With 96-percent accuracy, the researchers could discriminate one sensor from another.
"We do not need to know any other information about the phone—no phone number or SIM card number," Dey said. "Just by looking at the data, we can tell you which device it's coming from. It's almost like another identifier."
Maybe this explains why Facebook would be interested in a fitness app.
So the Dev Team has been hard at work fixing up issues with with the 17_02 release. We compiled all of your comments from the 17_02 Meta stories into a large bug and feature request list. We have been working on getting these issues fixed as soon as we can.
You may have noticed some changes over the last week that went out to fix some issues, and we just released some more fixes today.
Here is a list of the major fixes since the last story:
Continuation of:
Site Update 17_2
Comments Redux
Site Update: The Next Episode
Site Update - Taking a Breather
Outstanding Issues
So if you see any new bugs that you think are related to these changes, or just want to let us know about an ongoing issue, please feel free to comment below.
Here are the currently known bugs that we are working on:
And here are the feature requests:
At the moment, no matter what Breakthrough/Threshold setting I choose, every Top Level Comment (TLC) is displayed fully expanded.
Consider what the "Deuteronomy child bride", "Penis Bird", and "Cheap Canadian V14gra" users would make of knowing that they can make sure that their TLC will always appear in full.
For the following "T:" denotes setting for Threshold and "B:" denotes a setting for Breakthrough.
Am I missing something or shouldn't: (T:-1, B:5) produce the same result as: (T:5, B:-1)
Under Threaded-TOS, I'm seeing different results on: https://dev.soylentnews.org/article.pl?sid=17/02/16/0222248 where the highest score for a comment is: 2.
T:-1, B:5 -- https://dev.soylentnews.org/article.pl?sid=17/02/16/0222248&threshold=-1&highlightthresh=5&commentsort=0&mode=threadtos&page=1&noupdate=1#commentwrap
T:5, B:-1 -- https://dev.soylentnews.org/article.pl?sid=17/02/16/0222248&threshold=5&highlightthresh=-1&commentsort=0&mode=threadtos&page=1&noupdate=1#commentwrap
Based on what I understand, T:-1, B:5 Says show me everything (scoring -1 or better) in full (oh, and boost visibility of those scoring 5 or better) -- but we are already selecting to show everything anyway
OTOH, T:5, B:-1 Says show me only those scoring 5 or better (there are none for that story), but boost all those scoring -1 or better, which is ALL of the comments, so it again selects to display everything.
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 %]