Here is a summary of the problems that have been reported against SoylentNews and that have been addressed in the release labelled: "December 2017"
Issue: #279 "Add min karma for the journals slashbox"
Accounts signing up then posting commercial spam Journal entries in order to appear on most user's view of the main SN site, within the Most Recent Journal Entries box. Whilst offering zero other contribution to the community.
A. Most Recent Journal Entries only to be populated with Journal entries by accounts with a Karma > N. 5 to be the initial value for N (that would hide all currently seen Journal spam from view), but should be an easily tweaked parameter should we need to revisit this threshold).
B. Addition of a link to "Unfiltered Most Recent Journal Entries" to be added to the bottom of the Most Recent Journal Entries rehashbox so users can easily compare the filtered to unfiltered lists.
This change will need to be clearly announced and rationale explained. We will also need to monitor effectiveness in case spam accounts begin to farm Karma in order to route around this change.
Issue: #410: Spoiler tag doesn't work on Journal comments.pl
Issue: #281: Request: increase size of submission/story notes
It seems to be limited to 1024 characters. How about 8192 or 16384 characters?
Don't accidentally delete the notes!
Need to update stories and submissions tables to set the notes and comments columns to text (from varchar(1023). Then need to update all of the templates to change the maxsize attribute.
Issue: #309: Link to submission queue on side bar
Appears as a link to "https://dev.soylentnews.org/submit.pl?op=list" with link text "Subs Queue"
Issue: #413: Margins of lists are sometimes non-existent despite use of line breaks
The margin-top or especially margin-bottom of lists does not always work as expected. See the above comment. There should be a line break between "IV" and "I believe these moderations would be extremely popular."
The spacing (margins) does not match what is seen in the "Preview Comment".
Also <ol type="I"> is not implemented on dev.soylentnews.org
Issue: #402: Comments with no apparent subject using a unicode space
Chromas used a unicode space or zero-width space character to make a comment with no apparent subject. When you get a Message about receiving the comment, the CID is not clickable like it normally would be.
Test story created at 20170228_001952 UTC for paulej72 to have a place to play around with comments.
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
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.
Story posted to the meta section.
This is the second paragraph
This is the third, and last, paragraph.
Here's some text for the submission
some random text here. need to determine if getStoriesEssentials is behaving correctly.
SpallsHurgenson dropped a link in IRC.Apparently, an imgr user was uploaded 142 behind the sceenes photos of minitures frm blade runner. A massive gallery of behind-the-scenes Blade Runner slides has been uploaded to the internet, revealing a teeny, tiny world of space blimps and flying cars, all crafted with special care and beautiful attention to detail. Take a look at the dystopian miniatures, each tiny car hand painted with future dirt from riding clouds stuffed with future smug.
I have a theory that bug #85 https://github.com/SoylentNews/rehash/issues/85 might have something to do with a story which has a title which contains a character > U+007f
This story has the character ‘ before the word "prod" and the character ’ immediately after it. Those characters correspond to U+2018 and U+2019, respectively.
Will be interesting to see if this story gets e-mailed out okay.
NC: testing story edit. Test54