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 [github.com] "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: [github.com] Spoiler tag doesn't work on Journal comments.pl
It seems to work fine for articles:
Issue: #281: [github.com] 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: [github.com] 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: [github.com] 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
See, also: https://soylentnews.org/comments.pl?noupdate=1&sid=22853&page=1&cid=604070#commentwrap [soylentnews.org]:
> Are you talking about seeing "Score: +1 Funny, +2 Informative, +1 Insightful, -1 Overrated, -1 Flamebait" instead of "Score 4, Informative"?
> So a comment modded (in chronological order): +1 Insightful, +1 Underrated, +1 Underrated, -1 Flamebait, -1 Flamebait, +1 Underrated, +1 Insightful, ±0 Disagree, ±0 Disagree
That would be "Score 5: +3 Insightful +3 Underrated -2 Flamebait , 2 Disagree", which tells you more about the readers' feedback than 5 Insightful. (it might require a smaller font)
I have heard rumors that this society could use more nuances in discourse than Black or White and Us vs Them.
Issue: #405: [github.com] 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.