Stories
Slash Boxes
Comments

SoylentNews is people

Meta
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

Related Stories

Site Update 17_2 193 comments

Okay, I know it's been a long time since we did one of these but life does intrude on volunteer dev time. Hopefully this one will be worth the wait. Bear with me if I seem a bit off today, I'm writing this with a really fun head cold.

First, what didn't make it into this update but is directly upcoming. Bitpay is still down on account of them changing the API without notifying existing customers or versioning the new API and leaving the old one still up and functional. It's the first thing I'm going to work on after we get this update rolled out but it will basically require a complete rewrite. Don't expect it any earlier than two months from now because we like to test the complete hell out of any code that deals with your money.

Also, adding a Jobs nexus didn't quite make the cut because we're not entirely sure how/if we want to work it. One thing we are certain about, it would not be for headhunters or HR drones to spam us silly but for registered members who have a specific vacancy they need to fill and would like to throw it open to the community.

The API still has some broken bits but it's been low priority compared to what I've been busy with. I'm thinking I'll jump on it after Bitpay unless paulej72 cracks the whip and makes me fix bugs/implement features instead.

There were several other things that I had lined up for post-Bitpay but I can't remember them just now what with my head feeling like it's stuffed full of dirty gym socks.

Now let's throw the list of what did make it out there and go over it in more detail afterwards.

  • Tweaked the themes a bit where they were off.
  • Changed or fixed some adminy/editory stuff that most of you will never see or care about.
  • Fixed a mess of minor bugs not worth noting individually.
  • Improved Rehash installation. It should almost be possible to just follow directions and have a site working in an hour or two now.
  • Added a very restrictive Content Security Policy.
  • Added a link to the Hall of Fame. It was always there, just not linked to.
  • Return to where you just moderated after moderating. (yay!)
  • Return to where you just were after commenting. (yay some more!)
  • Added a field for department on submissions. Editors get final say but if you have a good one, go for it.
  • Added a Community Reviews nexus.
  • Added a Politics nexus.
  • Added <spoiler> tags for the Reviews nexus in case you want to talk about a novel without ruining it for everyone else. They function everywhere though.
  • Changed really freaking long comments to have a scrollbar now instead of being click-to-show.
  • Massively sped up comment rendering on heavily commented stories.
  • Dimming of comments you've already read. (You can turn this off with the controls on the "Comments" tab of your preferences page if it annoys you.)
  • Added a "*NEW*" badge to new comments in case you don't like dimming but still want to easily see new posts. (Disable it the same place as above.)
  • Removed Nested, Threaded, and Improved threaded comment rendering modes (Necessary due to the changes required for the massive speed-up)
  • Added Threaded-TOS and Threaded-TNG comment rendering modes. (TOS is the default)
  • All comment modes now feature collapsible/expandable comments. (Without javascript)

Morning Update: Really digging the constructive criticism. Some quality thoughts in there. Keep them coming and we'll see how fast we can get a few done. --TMB


Comments Redux 113 comments

Continuation of: Site Update 2/27

So, the recent site update got a lot of news, and comments. Predictably, there was a lot of comments split on the fence both ways. I've been out sick and haven't been actively involved in SN in a few days, but I did review the updated changes on dev before they went out. I'm still not up to responding to you guys personally, and TMB/Paul have had things covered, so I'm just going to write a blanket story. So, let's open this and say THIS ISN'T THE FINAL SET OF HOW THINGS WILL BE. I'm leaving my comments above the fold to make it clear what's going on. I'd put that in a blink tag on if that was still in the HTML standard.

The changes to commenting were primarily driven on technical grounds. To do D1.5, the site had to load a mass load of comments and do server side processing to thread them. To give you an example, on a cold page load, before we apply caching a few points in the site would take over a minute to load, render and thread. The only thing that prevented the site from becoming unusable in 503s is that the frontend has a lot of caching. Even with that, we can't cache every single bit of the site at once. In a "cold cache" scenario such as after a varnish or DB update, the site would be borderline unusable until those caches could be loaded. So let me make this clear that this change wasn't a change for changes sake. There was (and is) a need to revamp the commenting.

We noted that this change was coming in other meta stories, and even had a landing article on dev for people coming to check it out. No one did. How we use commenting on dev and how we use it on production are two different things; you can't realistically test these things in real world conditions without updating production.

As TMB stated, we couldn't get the same behavior without making the site cry in the corner, and this was fairly extensively tested on dev before it went live. For older users to the site, you may remember this is not the first time we've changed comments, and rather predictably, the roll out of Improved Commenting actually was fairly buggy. This is a more drastic update.

Right now, we're going to keep improving and changing things to address as many things as possible. To that extent, there will be a daily article for at least this week if not longer to allow for feedback as we work to make things better. If, at the end of all the tweaking, we can't satisfy the vast majority of folks, a revert remains as an available option. We've built this entire site on listening to the community, and taking their feedback into account. That isn't going to change now. I'm hoping we've earned enough trust from you guys collectively to be allowed to at least experiment for a bit.

I'm going to leave the rest of the article for the dev crew to use. Due to personal real life issues, I'm likely not going to be around much, so if you don't see me, that's why. I have full faith in the staff in helping manage and keep things going.

~ NCommander

Hi! I'm martyb (aka Bytram) your friendly neighborhood QA/test guy chiming in with my 2¢ on the upgrade/rollout.

Firstly, I apologize that you are seeing ANY issues with the site upgrade. I took this update very seriously and was, unfortunately, only able to perform about half of the testing that I wanted to see done before we went live. That said, there are some issues that were reported that I had not foreseen, so this has been a learning experience for me, too.

Secondly, I'd like to point out what you are NOT seeing -- the many MANY changes that TMB and PJ made as a result of feedback arising from testing. That said, comments are THE thing that makes this site. It's not the timeliness or fine writing of the stories — as I see it, this site is all about providing a venue for discussion.

Look past the fold for the rest of my comments.

How to Get Back to the Moon in 4 Years, Permanently 56 comments

Howard Bloom has written a guest blog at Scientific American addressing the Trump Administration's plan to return to (orbit) the Moon. That mission would use the Space Launch System rocket and Orion capsule, which have cost $18 billion through 2017 but are not expected to launch astronauts into space until around 2023. Bloom instead proposes using private industry to put a base on the Moon, using technology such as SpaceX's Falcon Heavy (estimated $135 million per launch vs. $500 million for the Space Launch System) and Bigelow Aerospace's inflatable habitat modules:

[NASA's acting administrator Robert] Lightfoot's problem lies in the two pieces of NASA equipment he wants to work with: a rocket that's too expensive to fly and is years from completion—the Space Launch System; and a capsule that's far from ready to carry humans—the Orion. Neither the SLS nor the Orion are able to land on the Moon. Let me repeat that. Once these pieces of super-expensive equipment reach the moon's vicinity, they cannot land.

Who is able to land on the lunar surface? Elon Musk and Robert Bigelow. Musk's rockets—the Falcon and the soon-to-be-launched Falcon Heavy—are built to take off and land. So far their landing capabilities have been used to ease them down on earth. But the same technology, with a few tweaks, gives them the ability to land payloads on the surface of the Moon. Including humans. What's more, SpaceX's upcoming seven-passenger Dragon 2 capsule has already demonstrated its ability to gentle itself down to earth's surface. In other words, with a few modifications and equipment additions, Falcon rockets and Dragon capsules could be made Moon-ready.

[...] In 2000, Bigelow purchased a technology that Congress had ordered NASA to abandon: inflatable habitats. For the last sixteen years Bigelow and his company, Bigelow Aerospace, have been advancing inflatable habitat technology. Inflatable technology lets you squeeze a housing unit into a small package, carry it by rocket to a space destination, then blow it up like a balloon. Since the spring of 2016, Bigelow, a real estate developer and founder of the Budget Suites of America hotel chain, has had an inflatable habitat acting as a spare room at the International Space Station 220 miles above your head and mine. And Bigelow's been developing something far more ambitious—an inflatable Moon Base, that would use three of his 330-cubic-meter B330 modules. What's more, Bigelow has been developing a landing vehicle to bring his modules gently down to the Moon's surface.

[...] If NASA ditched the Space Launch System and the Orion, it would free up three billion dollars a year. That budget could speed the Moon-readiness of Bigelow's landing vehicles, not to mention SpaceX's Falcon rockets and could pay for lunar enhancements to manned Dragon 2 capsules. In fact, three billion dollars a year is far greater than what Bigelow and Musk would need. That budget would also allow NASA to bring Jeff Bezos into the race. And it would let NASA refocus its energy on earth-orbit and lunar-surface refueling stations...plus rovers, lunar construction equipment, and devices to turn lunar ice into rocket fuel, drinkable water, and breathable oxygen. Not to mention machines to turn lunar dust and rock into building materials.

An organization that Howard Bloom founded, The Space Development Steering Committee, has been short one member recently (Edgar Mitchell).


Original Submission

Site Update - Taking a Breather 62 comments

Martyb here once again with today's update on our site's update. I apologize that this is not as well written as my prior updates as exhaustion and outside issues are demanding of my time. I ask you to please bear with me.

Quick Recap: As you may recall, our servers were getting melted trying to serve up highly-commented stories. Further, this made for an unacceptably long delay between the time one would request a story and when it would finally get returned for display. Our devs have implemented alternative display modes, "Threaded-TOS" and "Threaded-TNG" which use a much more efficient means of processing comments and getting them to you. These changes went "live" on Saturday, February 25.

Like anything new, we expected there would be issues. We very much appreciate your patience as we tried to work through these as they were reported. And did you ever let us know!

Paulej72 (aka PJ) and TheMightyBuzzard (TMB) have been laboring mightily to keep up with the issues that have been reported as well as a few they found independently. Similarly, as their fixes have gone live, our community has had to deal with a changing landscape of "what happens when I do this?" To add to this, comments being such a major part of the site's purpose, there are "knobs" in several places where users can customize which comments are presented to them and how they appear. The permutations are many and wide-raging. As bug fixes have been made, the impact of changing these has had different effects over time.

I've been astounded at how much the community has been supportive of our efforts, how well problems have been described and isolated, and how quickly the devs have been able to fix bugs as they have been noted. Even more impressive was the discussion in our last update story on possible alternative means of implementing the <spoiler> tag. I'm proud to be part of this community — you rock!

Stories: While all this activity has been happening, stories have still been posted to our site for your reading and commenting pleasure. We are working with a reduced editorial staff at the moment. Us long-timers have been posting as we can, but I would like to personally thanks our new editors fnord666 and charon for their heroic efforts getting stories posted, and takyon for his continued efforts at providing well-written stories. I have noticed submissions from new folks as well, and the heartens me immensely! (Note: I hesitate to call out people in particular for fear I will overlook someone; any omission is purely my fault and I would appreciate being called out on it if I have failed to list your contribution.)

Plans: This development blitz has, however, come at a cost. For those who were with this site at its inception, there was a "day of rest" imposed on the developers who had worked basically non-stop trying to get our site up and somewhat stable. I have suggested a similar break to our dev staff. Recall we are all volunteers doing this in our spare time. PJ has plans coming up and will be unavailable on Friday and Saturday. From what I've seen, TMB is well nigh a crispy critter at this point and most certainly needs a break. And, quite frankly, I've put a lot of personal stuff on hold while working on this update and could use a break, as well. In short, we are tired.

So, PJ is around for a bit (in his free time while at work) for today and TMB is getting a well-deserved breather. NCommander is nearing burnout has been tied up with an outside project that demands his full attention and has been unable to help much. I'll poke in from time to time, but I really need some time off, too.

What I ask from the community is that we do something similar. Step back for a moment. Look at the forest and not just the trees. Play around with the different display Modes. Try setting a different "Breakthrough" and/or "Threshold". Things should be much more stable today, so that will make it easier to gain a "mental model" of what does what.

The other thing I would ask is for the community to pull together and try to address issues together. Someone posts an issue about struggling with having to click on all the little chevrons? Inquire about their user preference settings, and suggest a different value for Threshold/Breakthrough. My sense is that some are more adept at using the new features and they can help others to get a better understanding of how things work. With those issues addressed, we can more clearly identify and isolate underlying problems and focus our energies more productively.

tl;dr We're not done yet, we truly appreciate your patience and forbearance during this transition, we need a break, and you guys rock in helping others in the community understand and use the new stuff. As always, keep our toes to the fire — we are here for you — let us catch our breath and we'll be better able to move forward.

Continuation of:
Site Update 17_2
Comments Redux
Site Update: The Next Episode
Site Update - We're Getting There!

17_02 Latest Bug Fixes: UPDATED 89 comments

So the Dev Team has been hard at work fixing up issues with with the 17_02 release. We compiled all of your comments from the 17_02 Meta stories into a large bug and feature request list. We have been working on getting these issues fixed as soon as we can.

You may have noticed some changes over the last week that went out to fix some issues, and we just released some more fixes today.

Here is a list of the major fixes since the last story:

  1. Comment titles now act to trigger actions as well as the buttons.
  2. New icons for the buttons that are bigger and spaced out a bit more.
  3. Removed extra spacing for some of the modes when buttons are hidden. (Still needs some more work, but much better than before.)
  4. Changed how we set states for hidden threads so that the individual comments are not set hidden as well. This will lessen the number of clicks needed to open a comment in this case.
  5. Flat comment mode will now show a comment's children when look at comment (cid is set).
  6. Temp fix for Content Security Policy eating CSS when not on https://soylentnews.org.
  7. Domain Tags now show in comments.
  8. Fixed broken messages when looking at them from messages.pl.
  9. Fixed for @user: shortcut links that would eat a character after the ":".

And here are the latest updates:

  1. Editor fixes: added new lines to story editor and fixed topic tree popup issue.
  2. Fix for black on black text boxes in Grayscale theme
  3. Added SVG icons for buttons and CSS fixes to enhance look.
  4. Mod Points now back to UTC 00:10.
  5. Add # of children to collapsed thread title.
  6. Fix comment details to bring in the correct data which broke email and journal links.
  7. Add time to collapsed comment title.
  8. Fix select all button in messages.pl.
  9. Redirect returns to correct article.pl page after moderating.
  10. Updated CSP to fix issues. We still need to search for some inline JS that may need to be purged or rewritten to work correctly.

Continuation of:
Site Update 17_2
Comments Redux
Site Update: The Next Episode
Site Update - Taking a Breather
Outstanding Issues

So if you see any new bugs that you think are related to these changes, or just want to let us know about an ongoing issue, please feel free to comment below.

Here are the currently known bugs that we are working on:

Site Update - We're Getting There! 58 comments

Martyb here once again with an update on our progress with the site upgrade.

Our development team (paulej72, TheMightyBuzzard, and NCommander) have been hard at it trying to isolate and quash the bugs that have been reported. Having looked at some of the site source code (Perl) I can attest there are places where the comparison of Perl code to line noise is an apt description. Also, some of the code we inherited was written by, um, creative people who did not write the most readable code. Further the code documents what it does, but is just a wee bit short on the why. Translation: we have an amazing dev team here who have slogged many many hours trying to isolate and correct the issues that have arisen. If you've ever been bleary-eyed after a several-day coding sprint, you have an idea of things. I hereby express my personal thanks to the brain-numbing hard work these guys have put in for this site. And now on to where things stand.

We had an issue with getting a single comment to display correctly in "Flat" mode which appears to have been caused by issues with specifying the correct page it appeared in. Also, there was a rewrite of this code so things should be better, but watch out for regressions.

There are known issues with accessing the site via TOR most likely because we added a very restrictive Content Security Policy.

The new comment viewing modes "Threaded-TOS" and "Threaded-TNG" have been tweaked.

There is a strong voice to replicate the old "Threaded" behavior and it appears that may be feasible, now that we better understand how the community used it in the past. No promises, but it is being looked into.

We are close to making some changes for the defaults for Anonymous Cowards (non logged-in users), so if you have a preference, please speak up and make your voice known.

Oh, we have had reports of seemingly random 503 (Site Unavailable) errors. If you should experience one, please reply to this story with a description of what you were doing and a copy/paste of the entire error message. That will greatly help in our identifying, isolating, and hopefully fixing whatever gremlin is in the gears.

We have not forgotten about replacing chevrons with single/double plus/minus, but had some fires to put out that postponed action on these.

I expect I've left out a thing (or three) — please reply with a comment to (gently) remind us if you see a problem persisting, or if you find something new. it is most helpful to provide your user nickname, the date/time (and timezone), steps taken to cause the problem, and (ideally) suggestions on how you expected it to behave. Reports so far have for the most part been amazingly detailed and helpful — thanks!

Penultimately (I like that word!), I must express my sincere appreciation to the community who has been amazingly supportive and helpful in this transition. One benefit of the upgrade is you should see quicker page-load times on highly-commented stories. Our servers are experiencing a much lighter load to serve up those pages, too. Speaking of servers, I noticed that several of you have renewed your subscription to the site which is the primary way we can afford to keeps the lights on. Please accept my sincere and heart-felt thanks! The "Site News" slashbox has been updated to reflect our current situation.

Lastly, I must express my sincere gratitude to the community. I continue to be amazed at the breadth of knowledge that is freely shared here. Nary a day goes by that I don't learn something new. And many days when I am just blown away. Some long-held ideas have been challenged, and in some cases changed, thanks to what I've read here. Thank you!

Dev Note: Deployed a fix tonight for broken comment links that was due to yesterday's deploy. Alos deployed a partial fix for Flat comments and single comments. TMB will be working on getting it fixed up fully but I thought we needed what we had out now. -- paulej72

Continuation of:
Site Update 17_2
Comments Redux
Site Update: The Next Episode

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.
(1) 2
  • (Score: 2) by Appalbarry on Tuesday February 28 2017, @06:01PM (16 children)

    by Appalbarry (66) on Tuesday February 28 2017, @06:01PM (#472916) Journal

    THANK YOU!!! For killing this off. It ruined the site for me.

    Gee, imagine what would happen if a tech related discussion site made big changes to their front end, then refused to budge when users complained?

    PS Thank you as well for not enabling emojis and avatars.

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

      by DECbot (832) on Tuesday February 28 2017, @06:15PM (#472930) Journal

      I seemed to have missed the majority of the problems--not sure if it it was because I missed the window of opportunity or if it was because of my preferred theme (VT220)/discussion threading (D1/classic threaded-->threaded/TOS with -1/0 Threshold/Breakthrough). None the less, this is how beta should be done. Long live the beta! FUCK BETA!

      --
      cats~$ sudo chown -R us /home/base
      • (Score: 2) by NCommander on Tuesday February 28 2017, @06:29PM (1 child)

        by NCommander (2) Subscriber Badge <mcasadevall@soylentnews.org> on Tuesday February 28 2017, @06:29PM (#472943) Homepage Journal

        Honestly, the problem with beta wasn't so much the change itself, it was the utter disrespect to the community as they did it. If DICE had actually given a shit to the community, I probably won't have cared enough to help get SN off the ground.

        I wasn't thrilled with the updated comments on beta, though I did like the new article layout and such. That being said, the anti-JS crowd has always been a large group of old /., and here, and Beta was a giant FUCK YOU to them since even with the D2 discussion system, you could turn it off and get D1 (which is what we launched with here, and then had D1.5).

        --
        Still always moving
        • (Score: 2) by bob_super on Tuesday February 28 2017, @07:26PM

          by bob_super (1357) on Tuesday February 28 2017, @07:26PM (#472979)

          Don't forget the Trendy Whitespace Everywhere...
          Thanks for keeping SN content*-dense

          *quality of content varies by location.

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

      by NCommander (2) Subscriber Badge <mcasadevall@soylentnews.org> on Tuesday February 28 2017, @06:16PM (#472932) Homepage Journal

      We knew that changing commenting was going to get people to go to the Pitchfork Emporium and hunt us down. The only way we were going to do this was by making sure that we were communicating to the userbase as we did it. The loss of some functionality is unfortunate, but having the servers melting into slag is even worse. This is the first time in at least a year the servers aren't popping load warnings when we get a 100+ comment story, and the page load speeds have actually gotten to something resembling reasonable.

      The original fold/collaspe implementation was implemented in JavaScript and switched to server side rendering due to the fact our userbase is very anti-JS. For non-admins, I think there are a few bits of non-essential vestigial JS here and there. Admins get jQuery dynamically loaded as the admin interface requires it, and none of us can work up enough of a damn as only editors are affected.

      --
      Still always moving
      • (Score: 2) by cmn32480 on Tuesday February 28 2017, @06:46PM (1 child)

        by cmn32480 (443) Subscriber Badge <cmn32480NO@SPAMsoylentnews.org> on Tuesday February 28 2017, @06:46PM (#472958) Journal

        /me goes and cries in a corner 'cuz nobody loves us

        --
        "It's a dog eat dog world, and I'm wearing Milkbone underwear" - Norm Peterson
        • (Score: 2) by CoolHand on Tuesday February 28 2017, @08:14PM

          by CoolHand (438) Subscriber Badge on Tuesday February 28 2017, @08:14PM (#473004) Journal

          /me goes and cries in a corner 'cuz nobody loves us

          s'ok, cmn.... we have each other... *bro hugs*

          --
          Anyone who is capable of getting themselves made President should on no account be allowed to do the job-Douglas Adams
    • (Score: 2) by maxwell demon on Tuesday February 28 2017, @07:33PM (3 children)

      by maxwell demon (1608) Subscriber Badge on Tuesday February 28 2017, @07:33PM (#472984) Journal

      BTW, the related links have a scroll bar now. On this very story.

      --
      The Tao of math: The numbers you can count are not the real numbers.
      • (Score: 2) by paulej72 on Wednesday March 01 2017, @01:47AM (2 children)

        by paulej72 (58) on Wednesday March 01 2017, @01:47AM (#473169) Journal

        That has been around for a year. NCommander diatribes were causing the box to over flow with too many links. We felt that the easiest way to fix it was to limit the box with a scrollbar. It only happens when the story has lots of links.

        --
        Team Leader for SN Development
        • (Score: 2) by maxwell demon on Wednesday March 01 2017, @07:12AM (1 child)

          by maxwell demon (1608) Subscriber Badge on Wednesday March 01 2017, @07:12AM (#473233) Journal

          I never felt there was something to fix. If the link box is large, it is large; so what? But the scroll bar is annoying. Even more so if, like in this case, there's a ton of white space below the box.

          --
          The Tao of math: The numbers you can count are not the real numbers.
          • (Score: 2) by paulej72 on Wednesday March 01 2017, @11:53AM

            by paulej72 (58) on Wednesday March 01 2017, @11:53AM (#473266) Journal

            Some stories were the opposite. The Related links was much much longer than the story and thus pushed the comment top bay below the story. I really don't think we will change this.

            --
            Team Leader for SN Development
    • (Score: 2) by takyon on Tuesday February 28 2017, @07:49PM

      by takyon (881) Subscriber Badge <takyonNO@SPAMsoylentnews.org> on Tuesday February 28 2017, @07:49PM (#472993) Journal

      PS Thank you as well for not enabling emojis and avatars.

      Lol wut 😂😂😂😂😂😂👌

      --
      [SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
    • (Score: 2) by butthurt on Tuesday February 28 2017, @07:49PM (1 child)

      by butthurt (6141) on Tuesday February 28 2017, @07:49PM (#472994) Journal

      It's long been possible to have Unicode-style emoji in the bodies of comments and stories.

      /article.pl?sid=15/05/14/1140253 [soylentnews.org]

      • (Score: 2) by Appalbarry on Wednesday March 01 2017, @02:28AM

        by Appalbarry (66) on Wednesday March 01 2017, @02:28AM (#473181) Journal

        Guess that demonstrates just how much attention I pay to emojis. I'm just one of those old timers that think we got by JUST FINE with words, and paragraphs, and sentences.

    • (Score: 2) by romlok on Wednesday March 01 2017, @03:50PM (2 children)

      by romlok (1241) on Wednesday March 01 2017, @03:50PM (#473345)

      Shamelessly attaching my comment to the FP, as my complaint is related to scrolling:

      On narrow displays, the "Post Comment" box (technically, the "generalbody" within the "post_comment") has a horizontal scrollbar, which on narrow displays causes this textarea to be wider than the visible area, and so scroll horizontally as you type.

      The cause appears to be that the non-wrapping "Allowed HTML" line is now so long that it pushes the minimum width of the box beyond what I normally allow.
      Semantically speaking, they should really be styled

      s within a

      • , but a quick fix would be to add a space before and/or after each separator.
      • (Score: 2) by romlok on Wednesday March 01 2017, @03:55PM (1 child)

        by romlok (1241) on Wednesday March 01 2017, @03:55PM (#473349)

        Dag nabbit! Even as I was typing that out I was thinking, "make sure to preview this to make sure you work within the site's HTML parser."
        But did I? Noooooo!

        Try again:

        Semantically speaking, they should really be styled <li>s within a <ul>, but a quick fix would be to add a space before and/or after each separator.

        • (Score: 2) by paulej72 on Thursday March 02 2017, @02:31AM

          by paulej72 (58) on Thursday March 02 2017, @02:31AM (#473685) Journal

          Yeah that needs some fixing. That is a direct dump of the var from the db. It should be styled in some manner. This is a fairly easy fix so it may come soonish, but it will be after we get the big bugs out of the way.

          --
          Team Leader for SN Development
  • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @06:11PM (13 children)

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

    Cuz somebody has to. No request other than restoration of "nested" comment display option. All good otherwise. You guys rock.

    • (Score: 2) by NCommander on Tuesday February 28 2017, @06:17PM (6 children)

      by NCommander (2) Subscriber Badge <mcasadevall@soylentnews.org> 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
      • (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) Subscriber Badge 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]

    • (Score: 2) by The Mighty Buzzard on Tuesday February 28 2017, @10:43PM (4 children)

      I think I may do that tomorrow and see if I can rework the old Improved Threaded javascript on it for them as like javascript. Mind you, this ain't a promise. I suck the balls at javascript on account of hating its breathing guts too much to ever get any practice in with it. Just creating a Nested mode should be dirt simple though. It's essentially exactly the same as Threaded-TNG but with Threshold restored, so I can reuse most of the already written code.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
      • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @11:46PM (3 children)

        by Anonymous Coward on Tuesday February 28 2017, @11:46PM (#473120)

        Um... I read the site with javascript disabled, so any solution involving (browser side) javascript will not help me and others like me.

    • (Score: 0) by Anonymous Coward on Wednesday March 01 2017, @02:44AM

      by Anonymous Coward on Wednesday March 01 2017, @02:44AM (#473191)

      The onion site often responds with only the meta section or the breaking section with no real way to get out. Even manually changing the URL has no effect on that but usually a bit of time, say 10 minutes or so, followed by reload brings up the right section of the site.

      Otherwise, it's much improved.

  • (Score: 5, Insightful) by jelizondo on Tuesday February 28 2017, @06:13PM

    by jelizondo (653) on Tuesday February 28 2017, @06:13PM (#472928)

    Regardless of how the site looks in the end, I want to congratulate the team for doing a lot of work and being willing to undo some of it in light of the opinion of a majority of soylentils.

    The ample communication with the team and the response gives me high hope the site will last a long time thanks to the efforts of this great team.

    Cheers!

  • (Score: 2) by DeathMonkey on Tuesday February 28 2017, @06:21PM (4 children)

    by DeathMonkey (1380) on Tuesday February 28 2017, @06:21PM (#472936) Journal

    Any word on Nested view?

    There is a workaround (setting Breakthrough/Threshold to a lower value) but I feel like it's a popular enough view mode that it deserves a place in the drop-down list.

    • (Score: 2) by NCommander on Tuesday February 28 2017, @06:23PM (3 children)

      by NCommander (2) Subscriber Badge <mcasadevall@soylentnews.org> on Tuesday February 28 2017, @06:23PM (#472937) Homepage Journal

      I'll have to check with TMB/Paul but we might re-add Nested as a threading mode that basically does that on the back end to emulate the old behavior. That being said, we've had trouble figuring out what exactly the difference between Threading and Nested was. The backend code for this is/was absolutely convoluted, and the only thing was clear was it did pagination (which is now present in all modes)

      --
      Still always moving
      • (Score: 2) by DeathMonkey on Tuesday February 28 2017, @06:36PM

        by DeathMonkey (1380) on Tuesday February 28 2017, @06:36PM (#472951) Journal

        Pretty similar to Threaded with the Breakthrough/Threshold at 0 I think. When it hit a -1 instead of the collapsible tree it would just have a link saying "X replies beneath your current threshold." If I felt like reading the flamebait and any rebuttals I would middle-click this and it would open the whole collapsed sub-thread in a new tab.

        It appears to still work on /. if you want to compare...

      • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @09:45PM (1 child)

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

        For me, nested gave 50 comments per page.

        improvedthreaded (and now the new default) gives 100 comments per page (with the proper highlightthresh).

        It's been a long time since nested wasn't inferior.

        -- OriginalOwner_ [soylentnews.org]

  • (Score: 2) by aristarchus on Tuesday February 28 2017, @06:44PM (10 children)

    by aristarchus (2645) Subscriber Badge on Tuesday February 28 2017, @06:44PM (#472956) Journal

    Messages: Notification of reply. The link results in

    OK

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Anyone else encounter this?

    Also, I love how karma and mod points have been wildly fluctuating during this process. It has taught me to once again realize the impermanence of all things.

    --
    #freearistarchus!!!
    • (Score: 2) by paulej72 on Tuesday February 28 2017, @06:49PM

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

      We know of a few of these errors, but we have not been able to track them down. Our error logs are not showing the specific errors.

      Also the karma and mod points should not be fluctuating, other than by changes due to mods that are made against you and mods you spend.

      --
      Team Leader for SN Development
    • (Score: 2) by The Mighty Buzzard on Tuesday February 28 2017, @10:56PM (8 children)

      Are you by chance reading in Flat mode? Because single comment requests in Flat mode is what I'm on at the moment.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
      • (Score: 2) by aristarchus on Tuesday February 28 2017, @11:30PM (7 children)

        by aristarchus (2645) Subscriber Badge on Tuesday February 28 2017, @11:30PM (#473114) Journal

        Why, yes, O Buzzard of Might! How prescient of you! I will try to move on from Flatland to have some points.

        --
        #freearistarchus!!!
        • (Score: 2) by The Mighty Buzzard on Wednesday March 01 2017, @12:21AM (6 children)

          I have no idea what the points thing is. That's just a script that runs once a day and sets the points column of the users table to 5 if your member-since date is over 30 days in the past. Has nothing to do with the web coding. Speaking of, it should have just run a few minutes ago.

          --
          My preferred pronouns are wetback/faggot/cunt. Your move.
          • (Score: 2) by aristarchus on Wednesday March 01 2017, @06:55AM (5 children)

            by aristarchus (2645) Subscriber Badge on Wednesday March 01 2017, @06:55AM (#473229) Journal

            Is my clock off? Alright. As of a few hours ago, well past the UTC reset for mod points, my magazine had 3 points. I do not recall having been logged in or using mod points since the designated refresh. I used one of them to upgrade a comment, just to test. Went down to 2 remaining. So far, so good. But now, some few plus a few more, I have my full load of 5 mod points! Not that I want to use them to downmod jmorris or anything, but this is not normal behavior.

            Yesterday, my ranking dropped four points, and then later came back up, with no apparent changes in mods to my posts. And then it came back up, again with no relevant changes. I am puzzled! But then, that is normal for a philosopher, even one 2400 years old.

            Messages about replies still throw an internal server error. But only recent ones, it seems? Sorry to not be more help.

            --
            #freearistarchus!!!
            • (Score: 2) by aristarchus on Wednesday March 01 2017, @08:16AM (4 children)

              by aristarchus (2645) Subscriber Badge on Wednesday March 01 2017, @08:16AM (#473239) Journal

              Get same "internal server error" when clicking on "parent" to a post. Hmmm. Is it just me?

              --
              #freearistarchus!!!
              • (Score: 2) by paulej72 on Wednesday March 01 2017, @11:57AM (3 children)

                by paulej72 (58) on Wednesday March 01 2017, @11:57AM (#473267) Journal

                if you are using Flat mode, you will for now. We got the bug mostly fixed, but need some more time to get it working properly, and then we need to test to make sure it still works for older stories.

                --
                Team Leader for SN Development
                • (Score: 2) by The Mighty Buzzard on Wednesday March 01 2017, @01:06PM

                  No worries on older stories. They still have to use the old, slow mode because they don't have the children or opid columns populated.

                  --
                  My preferred pronouns are wetback/faggot/cunt. Your move.
                • (Score: 2) by aristarchus on Thursday March 02 2017, @02:27AM (1 child)

                  by aristarchus (2645) Subscriber Badge on Thursday March 02 2017, @02:27AM (#473681) Journal

                  Seems to be fixed! Good job, dev team(s)!

                  --
                  #freearistarchus!!!
                  • (Score: 2) by aristarchus on Thursday March 02 2017, @05:18AM

                    by aristarchus (2645) Subscriber Badge on Thursday March 02 2017, @05:18AM (#473749) Journal

                    Oh, and now (when did this happen? Not UTC 00:10!) I have mod points. As Alice said, "Curiouser and curiouser!"

                    --
                    #freearistarchus!!!
  • (Score: 2) by Gaaark on Tuesday February 28 2017, @07:11PM (4 children)

    by Gaaark (41) Subscriber Badge on Tuesday February 28 2017, @07:11PM (#472970) Homepage Journal

    Okay: there are problems with tablets that are probably harder to solve.

    I want to give 3K thumbs up to the guys (gals? He/She/It/Shim?) doing the hard work.

    As per stuff like *spoiler and *URL, on a tablet, it would be sooooo much easier to be able to click a button and put your URL (especially!!!!!!) or even a spoiler or bold marking without having to go through the tablet fecking fuck (errrr... i mean gui) to do it.

    Typing out 'less than' URL: url you want'closing less than/more than' is a pissing pain on a tablet: i'm talking: cancerous, problem with the pissing, pain in the pisser. On A TABLET!

    Once back into normal browser mode, it isn't that hard to type 'quote' '/quote', or URL: etc.

    I think everything else is GRRRREAT! You are all doing fabulously.

    The changes are amazing.
    I thank you.
    Applause, because you may not understand: if i had a million dollars, i'd buy a green dress (for Ethanol: just because) and i'd purchase a lifetime subscription.

    The work you do is appreciated, and i love the site (less so on tablet).

    Fuck slashdot....fuck Andrew DICE /.

    --
    --- That's not flying: that's... falling... with more luck than I have. ---
    • (Score: 2) by frojack on Tuesday February 28 2017, @07:42PM (1 child)

      by frojack (1554) Subscriber Badge on Tuesday February 28 2017, @07:42PM (#472988) Journal

      is a pissing pain on a tablet

      Exactly This.

      But on a tablet, or phone, you can usually solve this by installing a different/additional keyboard and pay the price of switching keyboards (three taps on my particular phone) once each time you visit sites like SN, rather then once each time you post.

      On my particular device, the factory keyboard actually works better than my preferred keyboard (Google's "Gboard").

      --
      No, you are mistaken. I've always had this sig.
      • (Score: 2) by DECbot on Tuesday February 28 2017, @08:44PM

        by DECbot (832) on Tuesday February 28 2017, @08:44PM (#473026) Journal

        I solved this with an old folding bluetooth keyboard. (old as in 'HP iPAQ' & 'Palm TX' era)

        I get much better typing speeds on that thing and a detachable stand for the tablet too.

        --
        cats~$ sudo chown -R us /home/base
    • (Score: 2) by The Mighty Buzzard on Tuesday February 28 2017, @11:00PM (1 child)

      You can just paste the URL in if you like. The servers convert it to a clickable link automagically. Watch: https://www.youtube.com/watch?v=6WpMlwVwydo [youtube.com]

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
      • (Score: 2) by Gaaark on Wednesday March 01 2017, @12:54AM

        by Gaaark (41) Subscriber Badge on Wednesday March 01 2017, @12:54AM (#473152) Homepage Journal

        Yeah, I found that out just today when I was going to be lazy and just paste it without the formatting.

        D'oh!

        Now I like the changes even more! :)

        --
        --- That's not flying: that's... falling... with more luck than I have. ---
  • (Score: 2) by butthurt on Tuesday February 28 2017, @07:23PM (12 children)

    by butthurt (6141) on Tuesday February 28 2017, @07:23PM (#472976) Journal

    On the old site, after I posted a comment I would be taken to a page that showed my comment, with the story above. By reloading that page, I could readily see whether anyone had replied. On the new site, I'm taken to a page that has the story and everyone's comments. I can, of course, search within the page for my own and, having found it, click on its number to get to the page about it. That takes a little bit more effort, though.

    • (Score: 2) by bob_super on Tuesday February 28 2017, @07:31PM (3 children)

      by bob_super (1357) on Tuesday February 28 2017, @07:31PM (#472982)

      It takes me to the offset my new comment on the story page.
      Clicking the comment number there, gets you back to that comment-specific page.

      I prefer to be back to the story, it saves me the extra click. Change approved!

      Inline commenting would be even better (still could scroll to read/copy/paste from the whole thread), but I like the incremental improvement.

      • (Score: 2) by DECbot on Tuesday February 28 2017, @08:51PM (2 children)

        by DECbot (832) on Tuesday February 28 2017, @08:51PM (#473031) Journal

        I tend to fall in the "No Javascript" crowd, but I'd think the inline comment would be a great feature for those who feel secure in their JS environment setup and the new page a great backup function for when JS is disabled. Sites that cannot run without JS I feel are broken, but light use of JS for design or function purposes are nice. That said, heavy JS use with unfettered JS/Flash access for advertisers and CDNs and other third/fourth/fifth parties is not acceptable website design.

        --
        cats~$ sudo chown -R us /home/base
        • (Score: 2) by paulej72 on Wednesday March 01 2017, @01:55AM (1 child)

          by paulej72 (58) on Wednesday March 01 2017, @01:55AM (#473171) Journal

          But commenting is not a light use of JS as it needs to send and receive data from the server. This means ajax or soap or some other stuff to send the data back and forth.

          I just deployed a fix for the redirects that will bring you back to your comment when you are not on page 1. The page var was not getting passed through the posting process properly.

          I hope this helps.

          --
          Team Leader for SN Development
          • (Score: 2) by Pino P on Wednesday March 01 2017, @04:51PM

            by Pino P (4721) on Wednesday March 01 2017, @04:51PM (#473383) Journal

            Could "Reply to This" open the comment form in an iframe inside the existing page?

    • (Score: 2) by takyon on Tuesday February 28 2017, @07:53PM

      by takyon (881) Subscriber Badge <takyonNO@SPAMsoylentnews.org> on Tuesday February 28 2017, @07:53PM (#472995) Journal

      Like bob said, it should take you right to the comment you just made. Maybe just make a rapid middle-click on the #472976 link, and then continue reading other comments on the story. Then close that tab and leave the other one open.

      This behavior might be a good place for a new user setting [soylentnews.org], however.

      --
      [SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
    • (Score: 2) by VLM on Tuesday February 28 2017, @08:06PM (2 children)

      by VLM (445) Subscriber Badge on Tuesday February 28 2017, @08:06PM (#473002)

      On the new site, I'm taken to a page that has the story and everyone's comments. I can, of course, search within the page for my own and, having found it, click on its number to get to the page about it.

      This is an inconsistency in the new design that goes beyond mere stylistic issues.

      I disabled dimming of "read" posts because even in my shit-post-iest moments I do the others the honor of re-reading the entire thread before diving in and writing something to be as on topic and well placed as possible. In the unlikely event its not a good post, at least it wasn't for lack of trying. I figure if thousands have to read what I post, I have the obligation to at least (re)read a couple posts to keep things on track, make it more worth reading than if I just jumped in talking without listening.

      So that's an inconsistency in the new design, in that its good that you get encouraged to re-read the gist of the discussion via scroll placement, but the new design should also by default not dim, because not dimming also encourages re-read via not screwing up contrast.

      In summary I think better posts come from (re)reading more posts and the new design is somewhat inconsistent about that overall goal.

      Although if the worst thing I can find to complain about is I toggled exactly one default setting, well, that's a pretty successful redesign overall.

      • (Score: 2) by The Mighty Buzzard on Tuesday February 28 2017, @11:24PM (1 child)

        That's not an inconsistency if you're not taken back to your comment in the entire page of comments, it's a bug. When you comment it should always take you to the comment you just made.

        --
        My preferred pronouns are wetback/faggot/cunt. Your move.
        • (Score: 2) by VLM on Wednesday March 01 2017, @03:08PM

          by VLM (445) Subscriber Badge on Wednesday March 01 2017, @03:08PM (#473320)

          Huh I very specifically tried to reproduce my poor bug report and failed. File it as unreproducible. Maybe someone was messin with it while I was messin with it originally. Could be just bad luck.

    • (Score: 2) by paulej72 on Wednesday March 01 2017, @01:57AM

      by paulej72 (58) on Wednesday March 01 2017, @01:57AM (#473172) Journal

      There was a bug, that is now fixed, where if you posted on any page > 1 you would not be sent to your new comment.

      I hope this remedies your issues.

      --
      Team Leader for SN Development
    • (Score: 2) by TheRaven on Wednesday March 01 2017, @02:33PM (2 children)

      by TheRaven (270) on Wednesday March 01 2017, @02:33PM (#473311) Journal

      This doesn't scale well to many comments, but fortunately you get an async notification in the message centre for replies. Unfortunately, the UI there is a pain and doesn't make it easy to tell the difference between replies to different posts in the same thread without opening them all in new tabs and closing the redundant ones.

      Going back to the main story is a massive waste of bandwidth for me, because (in the absence of in-page commenting) I don't want to lose my place when I comment so I always open the comment window in a new tab. At the end, I then have two pages open pointing to the same page, so I close one. Worse, the new one marks all of the new comments above where I was reading as read, so I don't get any benefit from the ugly '*NEW*' annotations everywhere, because a bunch of new comments are tracked as old as a result of this misfeature.

      --
      sudo mod me up
      • (Score: 0) by Anonymous Coward on Wednesday March 01 2017, @03:36PM

        by Anonymous Coward on Wednesday March 01 2017, @03:36PM (#473335)

        Worse, the new one marks all of the new comments above where I was reading as read, so I don't get any benefit from the ugly '*NEW*' annotations everywhere, because a bunch of new comments are tracked as old as a result of this misfeature.

        Check carefully, because that doesn't sound likely.

        1st, that would be a bug, as we were told (in the 1st article about the comment changes, IIRC) that posting comments would not affect the *NEW*/fading behavior. (Is there a "noupdate=1" parameter in the URL after you comment?)

        2nd, since the *NEW*/fading are controlled by a single comment ID, with all older comments faded and all newer comments *NEW*ed (subject to settings, of course), I can't see how such a bug could only affect comments above where you were reading.

      • (Score: 2) by butthurt on Wednesday March 01 2017, @04:24PM

        by butthurt (6141) on Wednesday March 01 2017, @04:24PM (#473362) Journal

        > [...] you get an async notification in the message centre for replies.

        Yes, except when commenting anonymously.

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

    by frojack (1554) Subscriber Badge on Tuesday February 28 2017, @07:31PM (#472983) Journal

    What is the intended purpose of the Spoiler tag?

    We've already seen an example [soylentnews.org] it being re-purposed to get lengthy attribution boilerplate out of stories, and it seems likely it even more variations on that theme may arise over time.

    Was this the intent? If so, would there be a better name than "Spoiler", or perhaps allow user supplied alternative titles?

    --
    No, you are mistaken. I've always had this sig.
    • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @08:34PM

      by Anonymous Coward on Tuesday February 28 2017, @08:34PM (#473021)
      IIRC, the tag was introduced for...

      ...those who wanted to be able to post reviews 🎥

    • (Score: 2) by The Mighty Buzzard on Tuesday February 28 2017, @11:26PM

      For this:

      Snape kills Dumbledore!

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
  • (Score: 2) by Celestial on Tuesday February 28 2017, @07:39PM (3 children)

    by Celestial (4891) Subscriber Badge on Tuesday February 28 2017, @07:39PM (#472987) Journal

    I browse with Threshold at "1" and Breakthrough at "1" using the Threaded-TOS style. I previously used the Improved Threaded style. If the comment at a start of a thread was rated "0" or "-1," it would be hidden, but I would still see responses rated "1" or above. I noticed this morning that now I see all originating thread comments rated at "0" (not sure about -1), if someone posts a responding comment rated "1" or above. I changed my Threshold to "2" and Breakthrough to "2" to see, and the same applied there. I could still see "0" rated originating thread comments if someone responded with a comment rated "2" or above. An example would be here [soylentnews.org].

    Is this change intentional?

    • (Score: 2) by tangomargarine on Tuesday February 28 2017, @10:46PM

      by tangomargarine (667) on Tuesday February 28 2017, @10:46PM (#473087)

      The most irritating thing for me (either here or on The Other Site), is it seems like every time there's an update, I have to go twaddling the settings to get my damn visibility/expansion thresholds fixed back to the way they were before.

      --
      "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
    • (Score: 2) by The Mighty Buzzard on Tuesday February 28 2017, @11:35PM (1 child)

      That was a conscious design decision to have Breakthrough override Threshold. Previously you could have a gerzillion +5 comments in reply to a -1 comment and you would never see them set at 1/1. Technically I think we could still show the Comment Below Threshold message instead of the comment subject and expand the tree out below it to the +5s, but it provides contextual information as to what the +5s are replying to to show the subject.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
  • (Score: 2) by pkrasimirov on Tuesday February 28 2017, @07:46PM

    by pkrasimirov (3358) Subscriber Badge on Tuesday February 28 2017, @07:46PM (#472991)

    Keep up the good work!

  • (Score: 2) by takyon on Tuesday February 28 2017, @07:57PM

    by takyon (881) Subscriber Badge <takyonNO@SPAMsoylentnews.org> on Tuesday February 28 2017, @07:57PM (#473000) Journal

    If you have any feature requests or bug reports for my extension (link in sig), put them here.

    I am looking at:

    • Title button for journals
    • Correct cancellation of dialogs (like URL button)
    • Spoiler tag button
    • Change STRIKE to DEL
    • Dept. field handling in Save Draft feature
    • Possible Quote This enhancement
    • Possibly right-aligning the *NEW* text
    • Any bugs caused by new nexii
    --
    [SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
  • (Score: 3, Interesting) by Immerman on Tuesday February 28 2017, @08:28PM (1 child)

    by Immerman (3985) on Tuesday February 28 2017, @08:28PM (#473017)

    This is a bit off-topic, but since we're being Meta...

    It would be *really* nice if when following an "in reply to your comment" link from the Message Center, you had the option to "unfold" the comment thread that preceded the comment, rather than using the immediately relevant comment as the head. Heck, you could even just link to the comment in-place in the original story page.

    As it is, it makes any sort of serious conversations really annoying, since you have to go to the original story page and search for the comment in question to get more in-depth context, refer back to previous points, etc.

    In-place replying would be really nice too, for basically the same reason, but I can see how that might be a lot more demanding, and at this point I've acclimated to having to open a new tab to make a reply. And that's not nearly as annoying, since you're already at the relevant place in the main comment thread for reference.

    • (Score: 2) by The Mighty Buzzard on Tuesday February 28 2017, @11:38PM

      I've thought that before too. Remind us a month or two from now when we're through with the bugs/bitches fixing from the upgrade and have bitcoin payments working again and I'll see if I can work something up for that. May be nothing but a link to the top of that thread that you can open in another tab but there should be a handy way to view it without having to hit the back button.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
  • (Score: 2) by RedBear on Tuesday February 28 2017, @08:49PM (2 children)

    by RedBear (1734) Subscriber Badge on Tuesday February 28 2017, @08:49PM (#473029)

    Preface: As always I want to recognize that the admins are doing great things with only the sweat of their virtual brows to show for it. I thank you all for the time you put in.

    A lot of the things I immediately hated about the update were rapidly fixed. Some others were acknowledged, but haven't yet been fixed. Some things I fear may become permanent, which gives me a great deal of stress at the moment. I'm trying to be patient, and trying to accurately lay out what issues remain.

    The "Comment Below Threshold" is still in bold, which looks very awkward. I think paulej72 has acknowledged and will fix this when he has the time.

    There are still a significant number of differences between the info displayed for collapsed comments now versus before. Username (4557) posted a good screenshot that shows many of them.
    Link: http://oi67.tinypic.com/2cgo6zd.jpg [tinypic.com]

      - Subject of a collapsed comment is no longer a link. It used to be. I liked that. Others liked it. I even used it a few times.
      - The light vertical lines that helped visually connect parent posts with different layers of child posts have disappeared. The collapsed child posts can now tend to look kind of lost in empty space.
      - Collapsed comment is now [ Subject (Score: N) by Author ] rather than [ Subject by Author (Score: N) ]. This is quite awkward to read, and the latter (earlier) form mimics the way the (Score: N) is at the end of the subject line in the red header bar. I would really like this to return to the way it was.
      - UIDs are still being displayed in the collapsed comments. Why? This is an unnecessary detail that can be discovered by expanding the comment.
      - Collapsed comments no longer show day/date/time as they used to. I would like that info to return if possible. Except instead of full length days and dates like [ Saturday February 26 2015 @12:4AM ], why not think about using a more compacted (and more consistent in length and more readable) format such as [ Sat 26 Feb 2015 @12:4AM ].

    I saw this bug the last time I laid all this out in another comment: When I type [ @ 1 2 :3 4 A M ] like I did above and then preview my post, I see [ @ 1 2 :4 A M ]. The site seems to be eating the character immediately after the colon. The spaces in this example were just to try and avoid triggering the bug, but it's actually still there. In this example the bug is eating the space character after the colon when I preview the post.

    I know how to disable comment dimming, and I know about the setting to mark new posts with [ *NEW* ]. I will still argue that the dimming is a flawed idea that should die. Surely there is a different way to mark new posts visually that will work even for the color blind and those who use other themes. The dimming is done through the use of opacity modification which also modifies the text opacity. So even with a very delicate adjustment in opacity, it ends up making the user feel like there is something wrong with their display (or worse, their eyes). By the time you've toned down the opacity change to the point where it isn't jarring, you've reached a point where it's nearly impossible to tell the difference between new and old posts. And that's for someone who isn't color blind. So ultimately, what's the point? There has to be a way to use CSS to insert a simple visual marker of some kind in "new" posts that will work even for color blind users without being obnoxious. What about making a CSS border one pixel thicker on new posts, or something similar? Or make the font in the red bar one size larger.

    The chevrons are still far less attractive and more awkward to use than the lovely plus/plusplus/minusminus boxes. I'm experimenting with changing the view style to work around the awkwardness of how the chevrons function, but I'm not happy yet.

    The auto-expanding spoiler tag that moves everything around? Yeah, have to give that two thumbs down, Siskel & Ebert style. This isn't IMDB.

    I think I do kind of like how the (Score: N) is in a reduced font size compared to the subject. I like that it's subtle and not overdone.

    Everything that was horribly wrong with the red and gray bar contents initially was entirely fixed early on. Hurrah!

    Many thanks to all admins especially the attentive TMB and paulej72.

    --
    ¯\_ʕ◔.◔ʔ_/¯ LOL. I dunno. I'm just a bear.
    ... Peace out. Got bear stuff to do. 彡ʕ⌐■.■ʔ
    • (Score: 3, Informative) by The Mighty Buzzard on Tuesday February 28 2017, @11:58PM

      The "Comment Below Threshold" is still in bold, which looks very awkward. I think paulej72 has acknowledged and will fix this when he has the time.

      That's fixed in the repo already, it just hasn't been pushed live yet.

      I will still argue that the dimming is a flawed idea that should die.

      You're quite entitled to that opinion. Mine is that it's the best thing since sliced bread for quickly being able to spot new posts. It's a good thing that we can both have our wishes accommodated.

      Adjusting the *NEW* functionality to also increase the RGB values (affecting brightness not hue, so colorblind people will be able to see it just peachy) of the subject bar a bit is on the slate but it will take tweaking every single theme to do.

      For that matter, everything else you mentioned is on the slate to be tweaked or entirely redone. It's the work week though so time is less available for paulej72 than on the weekends. Me, I just took a day off after a week and a half of coding 6-12 hours every day so my brain wouldn't explode. We're good but we aren't quite miracle workers. We'll get things sorted eventually.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
    • (Score: 2) by paulej72 on Wednesday March 01 2017, @02:15AM

      by paulej72 (58) on Wednesday March 01 2017, @02:15AM (#473174) Journal

      The Comment Below Threshold issue should now be fixed. All of you other will be taken into consideration. I expect many of them will be implemented.

      Getting the title of the comment to toggle to collapsed state may be a bit harder to make happen as it would need to be tied to the element that toggles the CSS to change. This is currently a label tided to a hidden checkbox. The title and the control might need to be next to each other for this to happen.

      --
      Team Leader for SN Development
  • (Score: 2) by DannyB on Tuesday February 28 2017, @09:37PM (3 children)

    by DannyB (5839) on Tuesday February 28 2017, @09:37PM (#473046)

    What is the difference between Threaded-TOS and Threaded-TNG? It is not immediately obvious.

    Maybe tooltips or explanatory text in the preference pages might be helpful?

    • (Score: 2) by The Mighty Buzzard on Wednesday March 01 2017, @12:00AM (2 children)

      TNG is basically Nested without Threshold and with the Expand/Collapse chevrons tacked on. Every comment tree gets fully branched out with Breakthrough determining if individual comments are in an expanded or collapsed state.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
      • (Score: 0) by Anonymous Coward on Wednesday March 01 2017, @03:03AM (1 child)

        by Anonymous Coward on Wednesday March 01 2017, @03:03AM (#473196)

        Today the onion site is not showing the CSS chevrons to click to show the nested comments. The post titles are indented but nothing is shown in the indented space to click on. Likewise the comments that are folded are unaccessible because they are not hyperlinked. There the folded comment titles could use some formatting, maybe a colored background, to differentiate them from the text of the comment above them.

        Performance seems much improved.

  • (Score: 2) by Marand on Tuesday February 28 2017, @09:49PM (2 children)

    by Marand (1081) on Tuesday February 28 2017, @09:49PM (#473061) Journal

    When I get a message about a comment reply and attempt to follow the link to see the response, it's linking to the top of the page instead of to the page's #commentwrap anchor. Not an issue for short summaries, but it definitely stands out with longer articles like these meta ones. Same happens when following links to comments from the user pages.

    It seems like the links in these places should point to the comment anchor instead of starting at the top of the page and forcing the user to scroll past the summary. It's the difference in getting pointed here [soylentnews.org] or here [soylentnews.org]. (From the older meta article.) The latter is much more usable.

    • (Score: 2) by The Mighty Buzzard on Wednesday March 01 2017, @12:01AM (1 child)

      Cheers, it's on the slate to fix.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
      • (Score: 2) by Marand on Wednesday March 01 2017, @01:03AM

        by Marand (1081) on Wednesday March 01 2017, @01:03AM (#473155) Journal

        Awesome, thanks. I don't even know if the behaviour had changed with the update or if it always did that, since the summaries are usually short enough that it's practically the same thing.

  • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @09:53PM (17 children)

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

    I'd like to request that markdown support [wikipedia.org] be added in the next major release of the software.

    Practically every other site on the net supports markdown now. Besides standardization there is a lot less typing - for example italics are just * characters like *this* instead of full-blown open and close i tags.

    • (Score: 3, Insightful) by tangomargarine on Tuesday February 28 2017, @10:42PM (13 children)

      by tangomargarine (667) on Tuesday February 28 2017, @10:42PM (#473083)

      Practically every other site on the net supports markdown now. Besides standardization there is a lot less typing - for example italics are just * characters like *this* instead of full-blown open and close i tags.

      There is no clearly defined Markdown standard, apart from the original writeup and implementation by John Gruber, which some consider abandonware.[17][18] This has led to fragmentation as different vendors write their own variants of the language to correct flaws or add missing features.

      If it's opt-in, okay whatever, but keep your auto-manglement out of my defaults.

      --
      "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
      • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @11:05PM

        by Anonymous Coward on Tuesday February 28 2017, @11:05PM (#473102)

        Automanglement like eating < signs?

      • (Score: 0) by Anonymous Coward on Tuesday February 28 2017, @11:37PM (6 children)

        by Anonymous Coward on Tuesday February 28 2017, @11:37PM (#473116)

        You seem to be implying that markdown isn't really standardized.

        I could see how a naive reading of those quotes would lead you to believe that. But that would be an incorrect reading. It is true that various sites have indeed added their own extras in order to support extended functionality. But soylent isn't the kind of site that has much in the way of extended functionality. Hell, much of what is in baseline markdown doesn't even exist here - for example there isn't even support for drawing a horizontal line. So no, the standard baseline for markdown is more than enough for soylent's requirements.

        • (Score: 2) by The Mighty Buzzard on Wednesday March 01 2017, @12:03AM (5 children)

          If you really, really want to be able to insert a <hr> tag, we can do that. In like two minutes. It's just not a highly requested feature.

          --
          My preferred pronouns are wetback/faggot/cunt. Your move.
          • (Score: 0) by Anonymous Coward on Wednesday March 01 2017, @12:47AM (2 children)

            by Anonymous Coward on Wednesday March 01 2017, @12:47AM (#473149)

            woosh!

            seriously, you have huge forest-blindness problem

            • (Score: 2) by The Mighty Buzzard on Wednesday March 01 2017, @02:23AM

              Man, I been coding for I can't remember how long over the past few weeks. You could throw a brick at me and I'd be like "huh?".

              --
              My preferred pronouns are wetback/faggot/cunt. Your move.
            • (Score: 2) by tangomargarine on Wednesday March 01 2017, @03:41PM

              by tangomargarine (667) on Wednesday March 01 2017, @03:41PM (#473339)

              Being a software developer is a constant battle to figure out what the user *really* wants. In this case, the OP is apparently too lazy to type chevrons?

              Q: I can't do this one specific thing.
              A: I can implement that one specific thing for you. Next?

              --
              "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
          • (Score: 2) by TheRaven on Wednesday March 01 2017, @02:39PM

            by TheRaven (270) on Wednesday March 01 2017, @02:39PM (#473314) Journal

            No, that's not what he's saying. He's saying that he wants to be able to type in a markup language that is designed for humans to type, rather than one that is designed to be machine generated. He points out that his preferred markup language doesn't support nice syntax for everything that HTML supports, for example horizontal rule, but that most of what it doesn't support is irrelevant for a site like Soylent. i.e. adding hr is precisely the opposite of what he actually wants.

            I'd second the vote for Markdown, by the way, with a preference for GitHub flavoured Markdown [github.com], which anyone that has used GitHub is likely to be familiar with.

            --
            sudo mod me up
          • (Score: 0) by Anonymous Coward on Wednesday March 01 2017, @03:53PM

            by Anonymous Coward on Wednesday March 01 2017, @03:53PM (#473346)

            Honestly, there've been a couple times I really wished we had <hr> available, when I had both a direct reply, and a long semicoherent tangential ramble, and wished to clearly delineate them so sane people new when to stop reading. Or if I'm writing a big long post with footnotes, to clearly delineate footnotes from paragraphs. I just ended up using a line of -------------------- or ***************** or some such, but an <hr> would have been nicer.

            Guess I should submit a feature request on github in a few weeks, once the devs have cooled off from this commenting business.

      • (Score: 2) by Marand on Wednesday March 01 2017, @01:27AM (4 children)

        by Marand (1081) on Wednesday March 01 2017, @01:27AM (#473163) Journal

        How about Asciidoc [asciidoctor.org]? It wasn't created by a prominent Apple fanboy so it's not as well-known, but it's mature — predating markdown by a couple years, in fact — more consistent, has actual conformance tests [asciidoc.org], and isn't "abandoned" and forked a million ways. It also has more formatting options available. I think we'd only need a subset, though, because the full asciidoc spec would be overkill.

        Also, I agree about it being opt-in, at least for existing accounts. People's existing settings should never be changed unless there's a damn good reason for it. However, changing the default for ACs and newly created users is fair game. Make a new account, get the new default; use an account that predates the change and nothing changes.

        • (Score: 1, Interesting) by Anonymous Coward on Wednesday March 01 2017, @07:30AM (3 children)

          by Anonymous Coward on Wednesday March 01 2017, @07:30AM (#473234)

          Which has no real user-facing advantages and nobody knows it. Cool, eh?

          • (Score: 0) by Anonymous Coward on Wednesday March 01 2017, @04:10PM (1 child)

            by Anonymous Coward on Wednesday March 01 2017, @04:10PM (#473355)

            He does point out in his other comment about asciidoc that it uses the conventional _italic_ and *bold* conventions, whereas markdown uses weird *italic*/_italic_ and **bold**/__bold__, so that looks like a real user-facing advantage to me, but the reality is that, like VHS, markdown won (presumably because of ascii-pr0n?), so now everyone's using it regardless of merit.

            If I were doing my own documentation for a project, I'd seriously consider asciidoc, but for a commenting system meant to be used by thousands of random people, popularity beats technical merit.

            • (Score: 2) by Marand on Wednesday March 01 2017, @08:23PM

              by Marand (1081) on Wednesday March 01 2017, @08:23PM (#473488) Journal

              There's actually quite a few user-facing advantages; if you're interested, check my reply to that AC [soylentnews.org]. That's not everything, since I was trying to limit it to things that I think could be useful in a comment system, but I think there's enough benefit that it would be worth at least considering it for its merits instead of just going with the PHP of lightweight markup. Also, there's enough similarity that people familiar with markdown should be able to use it without any major troubles. All you'd need is a cheat sheet link to some basic formatting symbols and you'd be good to go.

              I'll admit I prefer asciidoc, because Markdown has enough inconsistencies and annoyances that I started preferring to use adoc instead of md where possible, but I don't have any strong preference for use here, because I think either one would be an improvement over our current options. I only mentioned Asciidoc as a possible alternative because of the remark about Markdown's fragmentation and issues with its undefined behaviour, and the possibility that it might be easier to implement a parser for the parts of it that would be relevant for commenting.

          • (Score: 2) by Marand on Wednesday March 01 2017, @08:07PM

            by Marand (1081) on Wednesday March 01 2017, @08:07PM (#473473) Journal

            Which has no real user-facing advantages and nobody knows it. Cool, eh?

            Just because you don't know it doesn't mean nobody does. It's used for the git documentation [github.com], O'Reilly accepts it for books, and Github accepts it for documentation, READMEs, etc. as well as Markdown.

            As for user-facing advantages for asciidoc over markdwon, here are a few:

            * Using _ for italic and * for bold makes more sense than * and **, and makes bold+italic (_*foo*_) both shorter and clearer
            * Superscript (^foo^) and subscript (~foo~) are explicitly defined in asciidoc, but not in Markdown.
            * Support for horizontal rule with triple single-quote (''')
            * Checklists with [*] syntax
            * Link syntax is both simpler and less likely to result in parsing errors. asciidoc links are in form of example.com[Link Text] whereas Markdown uses [Link Text](example.com), which causes problems when a URL has parentheses in it. Having to manually replace parens with %28 and %29 in Wikipedia links is annoying with Markdown, for a real example of why this matters.
            * Code blocks are marked by a matching line of dashes (such as ----) at the beginning and end of the block, whereas Markdown uses 4 spaces on each line. That means you have to change the actual code blocks to suit Markdown, but with Asciidoc you can dump the code without modification. The spec also explicitly defines a syntax for syntax highlighting, if needed, but in Markdown it's non-standard.
            * Passthrough blocks (++++) allow selective embedding of HTML in cases where you need direct control

    • (Score: 2) by The Mighty Buzzard on Wednesday March 01 2017, @12:11AM (1 child)

      Heard. No idea how long it'll be though. Bitcoin payment rewrite is the first thing on the slate for a minor update a month or two from now then fixing other bugs. Adding features isn't likely to happen before the end of the summer at the earliest. Unless we start paying me to put in five eight hour days a week, I'm not going to once we're finished polishing the current update.

      --
      My preferred pronouns are wetback/faggot/cunt. Your move.
      • (Score: 2) by Marand on Wednesday March 01 2017, @01:17AM

        by Marand (1081) on Wednesday March 01 2017, @01:17AM (#473159) Journal

        While I'm on board with the idea of using allowing another type of formatting mode vs. the all-or-nothing "html or not" options we have now, I'd argue that AsciiDoc [wikipedia.org] would be a better choice to implement. It has similarities to Markdown in that it's a human-readable format that is used to apply markup, but unlike Markdown it's a more reliable format because it has a stricter standard and even has conformance tests [asciidoc.org].

        It's also generally more sane to parse, I believe. For example, asciidoc uses _foo_ for italics and *foo* for bold, whereas Markdown's ridiculous design is to use *foo* for italics and **foo** for bold. There's a quick reference [asciidoctor.org] for an idea of what sort of things you can do with full asciidoc support.

        Full asciidoc support would be overkill, but a useful subset of its formatting rules could be really good for commenting.

    • (Score: 2) by Marand on Wednesday March 01 2017, @01:06AM

      by Marand (1081) on Wednesday March 01 2017, @01:06AM (#473156) Journal

      As a workaround you could use ham-mode [github.com] for emacs, coupled with Firefox's "It's All Text" addon. IAT adds a button to let you edit textarea input in an external editor and updates the textarea when you save the temporary file, and ham-mode in emacs lets you write markdown and it auto-converts to HTML on save. When combined you can write your comments in markdown but get HTML that renders mostly like you'd expect.

(1) 2