Stories
Slash Boxes
Comments

Dev.SN ♥ developers

Dev.SN is powered by your submissions, so send in your scoop. Only 13 submissions in the queue.
Meta
posted by Bytram on Thursday December 14, @02:40PM   Printer-friendly
from the early-Christmas-gift dept.

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:

Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(1)
  • (Score: 1) by mrpg on Friday December 15, @07:30PM

    by mrpg (4057) <{mrpg} {at} {soylentnews.org}> on Friday December 15, @07:30PM (#31473)

    Congratulations for your success. #MSGA

  • (Score: 2) by Bytram on Thursday December 21, @06:56PM (2 children)

    by Bytram (4031) Subscriber Badge on Thursday December 21, @06:56PM (#31475) Journal
    Verifying max length of Subject of a top-level comment on dev is now 46 chars instead of 50. after updating: edit_comment;comments;default as follows:

    Changed:
      <input type="text" name="postersubj" value="[% form.postersubj | strip_subject %]" size="50" maxlength="50">
    to be:
      <input type="text" name="postersubj" value="[% form.postersubj | strip_subject %]" size="46" maxlength="46">

    --
    A sig for when you want to see one
    • (Score: 2) by Bytram on Thursday December 21, @06:59PM (1 child)

      by Bytram (4031) Subscriber Badge on Thursday December 21, @06:59PM (#31476) Journal

      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, @07:04PM

        by Bytram (4031) Subscriber Badge on Thursday December 21, @07:04PM (#31477) Journal

        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, @07:09PM

    by Bytram (4031) Subscriber Badge on Thursday December 21, @07:09PM (#31478) Journal

    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, @09:35AM

    by Bytram (4031) Subscriber Badge on Friday December 22, @09:35AM (#31483) Journal

    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.

      This element includes the global attributes.

    compact
        This Boolean attribute hints that the list should be rendered in a compact style. The interpretation of this attribute depends on the user agent and it doesn't work in all browsers.
        Note: Do not use this attribute, as it has been deprecated: the <ol> element should be styled using CSS. To give an effect similar to the compact attribute, the CSS property line-height can be used with a value of 80%.

    reversed [HTML5]
        This Boolean attribute specifies that the items of the list are specified in reversed order.

    start [HTML5]
        This integer attribute specifies the start value for numbering the individual list items. Although the ordering type of list elements might be Roman numerals, such as XXXI, or letters, the value of start is always represented as a number. To start numbering elements from the letter "C", use <ol start="3">.

        Note: This attribute was deprecated in HTML4, but reintroduced in HTML5.

    type
        Indicates the numbering type:

            'a' indicates lowercase letters,
            'A' indicates uppercase letters,
            'i' indicates lowercase Roman numerals,
            'I' indicates uppercase Roman numerals,
            and '1' indicates numbers (default).

        The type set is used for the entire list unless a different type attribute is used within an enclosed <li> element.
        Note: This attribute was deprecated in HTML4, but reintroduced in HTML5. Unless the value of the list number matters (e.g. in legal or technical documents where items are to be referenced by their number/letter), the CSS list-style-type property should be used instead.

    Test using a variety of sequential and nested ordered lists (OLs):

      <p>Defaults with one LI:</p>
      <ol>
        <li>one</li>
      </ol>

      <p>Defaults with two LI:</p>
      <ol>
        <li>one</li>
        <li>two</li>
      </ol>

      <p>Defaults with three LI:</p>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Sequence of OL with defaults:</p>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Trying different values of TYPE: 'a', 'A', 'i', 'I', '1'</p>

      <p>Single list with type='a'
      <ol type='a'>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Single list with type='A'
      <ol type='A'>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Single list with type='i'
      <ol type='i'>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Single list with type='I'
      <ol type='I'>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Single list with type='1'
      <ol type='1'>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Nested OL using defaults:</p>

      <ol>
        <ol>
          <li>one</li>
        </ol>
      </ol>

      <p>Nested list BEFORE first item:</p>

      <ol>
        <ol>
          <li>one</li>
          <li>two</li>
          <li>three</li>
        </ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Nested list AFTER first item:</p>

      <ol>
        <li>one</li>
        <ol>
          <li>one</li>
          <li>two</li>
          <li>three</li>
        </ol>
        <li>two</li>
        <li>three</li>
      </ol>

      <p>Nested list AFTER second item:</p>

      <ol>
        <li>one</li>
        <li>two</li>
        <ol>
          <li>one</li>
          <li>two</li>
          <li>three</li>
        </ol>
        <li>three</li>
      </ol>

      <p>Nested list AFTER third (last) item:</p>
      <ol>
        <li>one</li>
        <li>two</li>
        <li>three</li>
        <ol>
          <li>one</li>
          <li>two</li>
          <li>three</li>
        </ol>
      </ol>

    Test using a variety of sequential and nested ordered lists (OLs):

    Defaults with one LI:

    1. one

    Defaults with two LI:

    1. one
    2. two

    Defaults with three LI:

    1. one
    2. two
    3. three

    Sequence of OL with defaults:

    1. one
    2. two
    3. three
    1. one
    2. two
    3. three

    Trying different values of TYPE: 'a', 'A', 'i', 'I', '1'

    Single list with type='a'

    1. one
    2. two
    3. three

    Single list with type='A'

    1. one
    2. two
    3. three

    Single list with type='i'

    1. one
    2. two
    3. three

    Single list with type='I'

    1. one
    2. two
    3. three

    Single list with type='1'

    1. one
    2. two
    3. three

    Nested OL using defaults:

      1. one

    Nested list BEFORE first item:

      1. one
      2. two
      3. three
    1. one
    2. two
    3. three

    Nested list AFTER first item:

    1. one
      1. one
      2. two
      3. three
    2. two
    3. three

    Nested list AFTER second item:

    1. one
    2. two
      1. one
      2. two
      3. three
    3. three

    Nested list AFTER third (last) item:

    1. one
    2. two
    3. three
      1. one
      2. two
      3. three
    --
    A sig for when you want to see one
  • (Score: 2) by Bytram on Monday January 01, @08:27AM

    by Bytram (4031) Subscriber Badge on Monday January 01, @08:27AM (#31485) Journal

    Here's the perfect way to implement this:

    +1 Cynical
    +1 Optimistic

    -1 Gloomy
    -1 Naïve

    1. Cynical and Gloomy are synonyms, as well as Optimistic and Naïve. But the moderator chooses whether to assign the positive or negative version.
    2. Gloomy allows you to describe someone as if they are a bog monster.
    3. Naïve gives us an excuse to use another moderation with a special character in it.
    4. If you wanted another ±0 moderation, it should be ±0 Agree, as a counterpart to Disagree.

    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, @09:34AM

    by Bytram (4031) Subscriber Badge on Tuesday January 02, @09:34AM (#31486) Journal

    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 "&ensp;&ensp;". Hit lameness filter: "Your comment violated the "postersubj" compression filter. Try less whitespace and/or less repetition in the subject line."

    Tried: Subject with "&ensp;&ensp;&ensp;&ensp;&ensp;&ensp;&ensp;" (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, @12:18PM

    by Anonymous Coward on Saturday January 13, @12:18PM (#31487)

    Niggers Niggers Everywhere
    And Not A Cock To Suck

    Ebony Hos

(1)