Here is a summary of the problems that have been reported against SoylentNews and that have been addressed in the release labelled: "December 2017"
- Pull Request: #414 addresses:
-
Issue: #279 "Add min karma for the journals slashbox"
PROBLEM:
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.SOLUTION:
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.
ADDENDUM:
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.
-
- Pull Request: #420 addresses:
-
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
https://soylentnews.org/comments.pl?noupdate=1&sid=22853&page=1&cid=604019#commentwrap
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".
https://dev.soylentnews.org/comments.pl?sid=1401
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.
https://soylentnews.org/comments.pl?noupdate=1&sid=21276&page=1&cid=559159#commentwrap
-
(Score: 1) by mrpg on Friday December 15 2017, @07:30PM
Congratulations for your success. #MSGA
(Score: 2) by Bytram on Thursday December 21 2017, @06:56PM (2 children)
A sig for when you want to see one
(Score: 2) by Bytram on Thursday December 21 2017, @06:59PM (1 child)
Now, when "Re: " is prepended to the parent comment's subject for a reply comment, it should fit without truncation.
A sig for when you want to see one
(Score: 2) by Bytram on Thursday December 21 2017, @07:04PM
Making sure a grandchild comment's Subject is not adversely affected, as well.
A sig for when you want to see one
(Score: 2) by Bytram on Thursday December 21 2017, @07:09PM
Note to self: May need to address additional template(s) for Top-Level Comments (TLCs) to a Journal 'story' and to a Poll... Anything else?
A sig for when you want to see one
(Score: 2) by Bytram on Friday December 22 2017, @09:35AM
Tests of ordered lists to address issue #413 [github.com].
Mozilla's specs for ol [mozilla.org]:
Note: This is a quick stab to get a feel at what works and how -- really should be broken up into sub-tests, but I knew that already... have to get ready to go to work but did not want to lose these, and wanted to make the results more generally available.
Test using a variety of sequential and nested ordered lists (OLs):
Test using a variety of sequential and nested ordered lists (OLs):
Defaults with one LI:
Defaults with two LI:
Defaults with three LI:
Sequence of OL with defaults:
Trying different values of TYPE: 'a', 'A', 'i', 'I', '1'
Single list with type='a'
Single list with type='A'
Single list with type='i'
Single list with type='I'
Single list with type='1'
Nested OL using defaults:
Nested list BEFORE first item:
Nested list AFTER first item:
Nested list AFTER second item:
Nested list AFTER third (last) item:
A sig for when you want to see one
(Score: 2) by Bytram on Monday January 01 2018, @08:27AM
Here's the perfect way to implement this:
+1 Cynical
+1 Optimistic
-1 Gloomy
-1 Naïve
I believe these moderations would be extremely popular.
A sig for when you want to see one
(Score: 2) by Bytram on Tuesday January 02 2018, @09:34AM
Issue #402 - Test 001
In the following, where the word "tried" appears, means I entered the stated text in the subject field, and clicked on the "Preview" button, while leaving the 'format' selection at "Plain Old Text".
Tried: Subject with 7 (0x20) followed by a period character. Hit lameness filter: "Lots of space in the subject ... lots of space in the head." (Form: "comments", Regex: "^(?:\s+)", Modifier: "gi", Field: "postersubj", Minimum match: "7", Minimum length: "0")
Tried: Subject with "  ". Hit lameness filter: "Your comment violated the "postersubj" compression filter. Try less whitespace and/or less repetition in the subject line."
Tried: Subject with "       " (Max number that would fit) got same lameness filter message: "Your comment violated the "postersubj" compression filter. Try less whitespace and/or less repetition in the subject line."
Tried: Subject with: " " (NARROW NO-BREAK SPACE) and got same lameness filter message.
More to come, but have to leave for work so saving now for posterity.
A sig for when you want to see one
(Score: 0) by Anonymous Coward on Saturday January 13 2018, @12:18PM
Niggers Niggers Everywhere
And Not A Cock To Suck
Ebony Hos