A couple of suggested changes. I propose that if a node not under considereation hits the same level of downvotes required to trigger auto reaping, the node content should be automatically hidden, a message displayed warning readers that it's quality/relevance is in question, a link would allow reading the original. Something along the lines of:
This node was taken out by the NodeReaper on Jul 16, 2017 at 09:42 BST
Reason: [NodeReaper] - Post contents hidden due to sufficiently negati
You may view the original node and the consideration vote tally.
I was a happy user of the #cbstream IRC ↔ PM client that makes the ChatterBox feel and behave like the IRC. But then sometimes broke (as it happened time to time), but ambrus hasn't been around for the last three weeks to fix it. So I wrote a simple ChatterBox reader myself. At the moment, it only reads, and I'm still not sure I want to add the ability to write to it. It uses the new CB XML ticker (as I skimmed over the other CB clients, they all seem to use the old one). If you want to use it, or just check the code, you can find it on GitHub.
<tr class="post-body post_body">
<ul><p>Fellow monks, could you try going to <a href="?node_id=1040">Pe
+rl Monks Discussion</a> and seeing if the following renders as actual
+ input boxes?</p>
<p>Because that is what is happening ...</p></input></input></ul>
The current link from SSCCE points to node # 1177743, which is a page containing only one thing: a link to node # 1177642 -- the page that actually describes what an SSCCE is. The handy syntax link is great, but could it be updated to point directly to the page? I don't really see the point of the intermediary page, and I fear that some newbs who click to it won't manage to click through to the real doc. Studies about page depth and retention show ... , etc. and the link doesn't exactly stand out.
Can we do away with the intermediary page and update the link?
The way forward always starts with a minimal test.
Since I made some mistakes in formatting, I then immediately went to change the formatting to what's below. When I hit the update button, nothing happens. It doesn't update and doesn't reload the page, but it does show the button was pressed. I'm using Firefox on Android.
I'll try again on a desktop computer, then report back.
The details of Modern Perl can be found in other reviews on PerlMonks. As it is freely available and anyone can look at the chapter descriptions, I won't review those here.
What I want to point out is the usefulness of this book for teaching best practices. The basic Perl part of the book isn't strictly necessary as this is covered in perlintro. However, many of the best practices cannot be found in perldoc or can't be found easily.
Such chapters as 2 and 7-12 are gold mines for best practices, many of which are difficult to find elsewhere unless searching specifically for them. Such things as the best community websites, Moose, style, exceptions, testing, warnings, reliability, security, idioms, things to avoid, and other tips are all considered in an uncluttered format, simple to understand and free to read (although you may want to donate on onyxneon.com).
Enjoy this modern, free, effective best practice guide.
The added text also appears at the end of the Cabalists’, Find Nodes, Settings, and Leftovers Nodelets.
The rendering problem is common to all the nodes in the thread, so presumably the arrow in the node title is the trigger? I see the problem on both Chrome and Firefox1, whether I’m logged in or viewing anonymously.
Has the node from marinersk been reparented after the fact? Or is there a bug lurking somewhere in the code, or is there (shudder) a database inconsistency? Did anybody else experience such erroneous messages?
Like this but there are strikes thru the break tags
I have a file with rows of data which are typically like</br> Attr num
name="Created" desc="Time file was created." type="t" ord="3" value="2
03T11:27:23+01:00"</br> I want to analyse this so that I can get a has
data like </br> Attr num ->101</br> Name ->Created</br> Desc ->Time f
I just tried to create a link to part of my scratchpad where I placed an id=. I tried [id://637756#laundry|my pad]. It did not munge. I just got [id://637756#laundry|my pad]. I would really like to link to tags with ids. For example, if I give an id to a section of my home node, I can link to just that section. Pretty please?
Update: It looks like I can not add ids to the html elements. They do not make it to display. 8(
No matter how hysterical I get, my problems are not time sensitive. So, relax, have a cookie, and a very nice day!
Somehow we need to contain this. This is a great very polite forum that people with real questions come and search for answers. I comparison to other forums people here do help and not judge if their skills are not super or their knowledge on experience is high. Everyone of us was a beginner and we/I are still beginners in areas where other can strive.
Any way in conclusion, this forum is great but people like Anonymous Monk who hide behind anonymous profiles can post what ever they want and mess the reputation of this forum.
I would propose if possible to constrain Anonymous Monk from replying on questions, he should be still possible to post and read any questions but what about not been able to post a reply if he is not a registered member?
What do you think, would that maintain somehow this problem?
Seeking for Perl wisdom...on the process of learning...not there...yet!
There is a message if a considered node gets reaped or edited, and the node is noted with this, including a link to the tally. If the node does not get reaped or edited, there is no message and the node is not noted.
It would be nice to know the result of a consideration regardless of the outcome. Also, when viewing a node, to see if it has been previously considered and what the tally was. Beside being interesting, it can prevent a second consideration of the same node.
Just tried something that occurred to me because I though I could find a large bug. It only partially worked, so I guess it's at best a small bug...
Basically, I tried opening the same node in multiple tabs of my browser prior to voting on it. Since the voting options stick around in any tab opened prior to actually voting on a node, and curious if the programming behind the scenes actually just hid them from the account that already voted after the fact to prevent multiple votes, or if it did any kind of back end checks to see if that specific account had already voted on the node, I gave it a try.
From what I could observe, my first upvote did increase the rep of the node, but my second upvote did not. I'm not sure if there is any wonky behavior involving XP for either the voter or the vote-ee, but I did notice that my number of votes left for the day decreased in both cases.
So based on that, I'm calling it a small bug, since really if someone tries to do this maybe they should lose the vote(s) to oblivion anyway (assuming that's all that happens). I figured I'd report it none the less, since sometimes I have an annoying habit of trying to "break" things like this on purpose. Trust me, I'm a video game designer's/programmer's worst nightmare, after beta testing and post release or course. :-)
UPDATE: My bad, disregard based on my response to soonix below. That's what I get for taking non-current data at face value, and just generally not thinking through what I was actually observing. I should have seen my number of votes decrease by two instead of one the second time if what I said were actually true.
Just another Perl hooker - Working on the corner... corner conditions that is.