Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by martyb on Tuesday February 28 2017, @05:53PM   Printer-friendly
from the reset-button dept.

Hi there. Martyb again with an update of our progress on issues arising from the site update. (The new comment grouping and display code was necessitated by huge server loads as well as long delays on constructing and returning highly-commented articles.)

First off, please accept my sincere thanks to all of you who made the time to comment in the prior stories and/or engaged us on the #dev channel on IRC. Really! Thank you for your passion and willingness to provide steps to reproduce and ideas for overcoming the issues that have been found.

ACs: If you access the site as an Anonymous Coward, be aware that we have NOT forgotten you. We are still trying to ascertain what features work best for the most people and are holding off changing (and rechanging and...) settings until we have a better idea of what to change those settings to be. So, please speak up on anything that you continue to find problematic and help guide us to making a choice that works the best for the most.

Scrolling Within a Comment: From what I saw in the reports from Monday, one of the key issues had to do with the scrolling within comments. We heard you. Oh, did we ever! Scrolling within comments was quickly removed and replaced by setting a limit on how long a comment could be submitted. This was especially problematic on mobiles and tablets.

Display Modes: Another of the often discussed issues had to do with "Display Mode." This can be set in your preferences (for logged-in users) and ad hoc when you load a story.

Display Mode - Defaults: If, prior to the release you had chosen "Flat", then you were transitioned to "Flat" (Doh!) If you had anything else as your selection for "Display Mode", you were transitioned to "Threaded-TOS". That mode was intended, as best as we were able to do using only CSS, to replicate the behavior previously supported by the old "Threaded" mode. You CAN change this. Many have reported that changing "Threaded-TOS" to "Threaded-TNG" and setting a lower value for "Breakthrough" (in this mode, "Threshold" is ignored) seemed to do the trick.

Display Mode - ad hoc setting: For the ad hoc case, just load the story as you normally would. Below the actual story text and before the comments is a set of controls. If you are having issues with the current default of "Threaded-TOS" click on that text and change it to "Threaded-TNG". if you find you have way too many icons to click in order to read comments, choose a smaller value for Breakthrough (-1 displays all; in this mode Threshold value is ignored).

Spoiler: Another popular topic of discussion was the way the new <spoiler> tag was implemented. We've heard you, but have not as yet decided on a course of action on how to update its functionality... Stay tuned!

*NEW* and/or Dimming: A surprising (to me at least) number of folks had issues with how we flagged old/new comments. For logged-in users, again go to the "Comments" tab of your "preferences" page, scroll down a little, and there are checkboxes that you can toggle:

Highlight New Comments [ ] Highlight new comments with *NEW* tag
Dim Read Comments [ ] Dim already read comments

Please give those a try and see if that works for you. Our first implementation of "Dimming" was a bit too strong for most folk's liking - this has been reduced so as to be less jarring. As for the "*NEW*" text, there were several positive comments that on mobile devices especially, one could quickly search for the text and rapidly navigate comments to find out what was new. There was a suggestion that uppercase-only looks like YELLING. Yes, it does. On the other hand, whatever text is selected for display has to be a reasonably unlikely string to appear in the normal course of reading comments. (False positives, anyone?)

There were some suggestions on changing the color of the comment title to flag it as new. This sounds pretty simple, but the devil is in the details. We have some in our community who are color-blind and others who have very limited vision, if any at all. For them, any color changes could be well nigh invisible. But it gets worse. On the "Homepage" tab of the "Preferences" page, there are currently 11 different themes that one can choose as your default. Setting a new comment to have a lighter (or darker) title bar would not work across all of those disparate themes.

Chevrons: And as for those chevrons that control the display of a single comment and of a comment tree, yes we heard you. Work is underway to see if we can replace those images with single/double plus/minus characters.

Penultimately, I would like to add a call-out to Paulej72 who took point yesterday (giving TheMightyBuzzard a well-deserved respite) and worked tirelessly into the night to address the issues that were raised.

Lastly, again many thanks to you, our community, who have guided us through this transition. Your feedback matters. We listen and for those who have been following along, I hope you can see the changes and the progress. We continue to strive to earn your trust and support. Thank you!

Dev Note: Currently there is an issue with Flat mode and viewing single comments such as https://soylentnews.org/comments.pl?sid=18223&cid=472653. It just came to our attention and we will be working on it to fix it. This issue will cause you to get a server error. Workarounds are to either switch modes to anything other than Flat or avoid going to single comment views.

Continuation of:
Site Update 17_2
Comments Redux

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/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.
  • (Score: 2) by NCommander on Tuesday February 28 2017, @06:17PM (6 children)

    by NCommander (2) Subscriber Badge <michael@casadevall.pro> on Tuesday February 28 2017, @06:17PM (#472934) Homepage Journal

    Can you try Threaded-TNG, and then manipulate the score, or be more specific on how things need to change.

    On the whole, none of us really spotted much difference between Nested and Threaded overall, but the original code implementation was incredibly convoluted and scary so I'm not exactly surprised we missed something subtle. Last I checked, almost all the editors used Improved Threaded last time we checked the database.

    --
    Still always moving
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @06:27PM (5 children)

    by Anonymous Coward on Tuesday February 28 2017, @06:27PM (#472941)

    Before -1 nested would show all comments, nested. Thread-TNG seems to do the trick, but changing to it also changes score threshold to 2 (default?), so needs another step to change it back to -1.

    • (Score: 2) by frojack on Tuesday February 28 2017, @06:36PM (2 children)

      by frojack (1554) on Tuesday February 28 2017, @06:36PM (#472949) Journal

      Thread-TNG seems to do the trick, but changing to it also changes score threshold to 2 (default?),

      I'm not seeing that. I switched to TNG, and my threshold remained the same.
      Maybe that one extra step is your AC penance?

      --
      No, you are mistaken. I've always had this sig.
      • (Score: -1, Offtopic) by Anonymous Coward on Tuesday February 28 2017, @07:03PM (1 child)

        by Anonymous Coward on Tuesday February 28 2017, @07:03PM (#472966)

        > Maybe that one extra step is your AC penance?

        Screw you.
        Seriously.
        Your dislike of ACs is not a justification for giving them a deliberately poor user experience.
        Especially when all it would take is a change in the default behavior.
        The previous version of the site defaulted to the most functional settings, there is no reason the newest version of the site can't either.

        • (Score: 1, Insightful) by Anonymous Coward on Tuesday February 28 2017, @07:10PM

          by Anonymous Coward on Tuesday February 28 2017, @07:10PM (#472969)

          OP AC here. Maybe frojack is suggesting that the behavior may be specific to AC mode (i.e., not logged in)?

    • (Score: 2) by paulej72 on Tuesday February 28 2017, @06:45PM (1 child)

      by paulej72 (58) on Tuesday February 28 2017, @06:45PM (#472957) Journal

      For AC, we may need to change the default Breakthrough to a lower number.

      Also we may have a bug in the breakthrough setting code that I need to check on tonight.

      --
      Team Leader for SN Development
      • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @09:48PM

        by Anonymous Coward on Tuesday February 28 2017, @09:48PM (#473060)

        I don't tend to -click- links.
        I drag and drop them into a blanked Address Bar and modify them there.
        I make sure that I add &threshold=-1&highlightthresh=-1 to those, so I don't tend to see what GP does.
        Your lower-default-breakthrough notion would seem to be the trick for him.

        WRT nested, after I (finally) embraced improvedthreaded (the default before the recent update), I found that the limit of 50 comments per page (for someone not signed in??) had expanded to 100 and I never looked back.
        Don't know why anyone would want nested any more.

        I want to once again emphasize the importance of a good presentation for ACs.
        ...in particular, newbies who e.g. found something interesting via a search engine and showed up here and haven't yet tweaked their cookies.
        I think that you guys continue to be headed in the proper direction.

        -- OriginalOwner_ [soylentnews.org]