Looking at my settings node, I noticed the setting "Default XML ticker style". In the description area, it lists several "valid" options, including "rss". So, I set it to "rss" (without the quotes). At least for the noderep ticker, RSS is not produced. Is this a bug with the noderep ticker?
I have just posted Re: Issues with Split and it has a rep. of 0 showing in "Nodes you wrote" and when looking at it directly. However, when looking at it in the OP's Issues with Split it has a rep. of 5. Bizarre!
Historically, when you view one of your writeups (e.g. a CUFP post), you are given a form right there in which to edit your post if you wish. The form fields for that were in the same form as the node voting buttons. This enabled surprising behavior, described here. Therefore, I have removed the "edit" form from the main display view of your posts and pushed it off into a separate edit page. So now, if you visit one of your writeups, you won't see an edit form right there, but you will see an 'Edit' link in the upper right.
Update: Based on feedback from users such as BrowserUK below, I have added a user display option to have the writeup edit form directly on the display page, below the writeup, as previously. However, it is now enclosed in a separate form from the voting buttons, so that the "surprising behavior" can no longer occur.
I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
Today I noticed that clicking on my reply doesn't open it in the "Edit" mode, but in a new "Display View". I like the change, but I'd appreciate adding an "Edit" option among "reply", "msg", "d/l", and "select" on my nodes:
Having done some upvoting, I became curious about what my voting record was for a particular monk. I was surprised to be told that I had cast only 20 votes, the earliest in Oct 2015. I would have been surprised had it been only 10 times that number. I checked a thread from 2013 in which I was sure I had upvoted this monk and, sure enough, I can't vote on the node again. Checking another monk I am sure I have upvoted frequently, I again got only 20 votes. I have nothing in the limit fields and don't remember this behaviour. Shome mishtake shurely?
Is there any chance that the processing for the "code" tag might be "enhanced" to do tab expansion? I keep forgetting to run my code posts through my stand-alone script and the alignment of my comments comes out "wavy". I know picky picky...
There's never enough time to do it right, but always enough time to do it over...
I'm thinking primarily for SoPW (but I assume a change would affect all posting pages), does anyone think that it would have a positive effect if we had the formatting information (it's rather brief relative to having to scroll to the bottom of the page anyway) *above* the text box?
I'm not really a statistical type person so this isn't a request for action, but a request for feedback.
Now that the shady practices of XP-clipping have been brought to light?, I was thinking this could be the right occasion to address the shortcomings—whether perceived or actual—of the feedback and voting mechanisms, that is to say, to mull things over.
I'll start with a few ideas.
What if monks could cast two votes on any node: first strictly during the main voting period, the other available later (but no sooner than one voting period after the first). This would open up the possibilities of correcting mistakes, placing emphasis.
Reminder messages. A node that you've accepted has not been answered in 24 hours. A node you've frontpaged has no answer in 12 hours. (XP demerit elective.)
Preliminary votes ie temporary-votes ie fake-votes ie phantom-votes ie were-votes ie mere-hints. These votes disappear after a month or so. How's it going to work: somebody soft-votes to place your node higher in the thread, now other monks are more likely to vote on it, everyone's happy.
Monk of the Year. Get your pic (statue) on PM during the next year. (Best XP gainer wins the Trophy.)
<node id="218191" title="Re: File Parsing" created="2002-12-06 19:47:1
+4" updated="2016-05-14 12:52:02"><type id="11">
<p>[id://218008] should point you in the right direction.</p></field><
Extending Querying Saints in our Book, the script now includes Monk Levels, which helps when trying to group or order the data. More importantly, (if it indeed can be important) the query now includes XP Ratio, which is calculated by XP / Writeups.
Fabricated numbers of some monks and monks with no writeups are outliers that mess up the numbers. So, the query returns two sets of ratios, with and without exclusions. Perhaps a more complicated rule for outliers can be devised.