Like everyone, my mind and attention are all over the map, but over the years I see people using the CB (ChatterBox) like a chat application.
Do you just follow along as-is, or are there tricks to provide notify-send type pop-ups or something that just makes it easier? When I've spoken and have interest, I open a new browser tab to Enhanced Full Page CB
The CB has a wealth of good content, hilarity and just something I'd like to see outside of the webpage itself.
Has there been any past discussion on adding a Shadow Title to each post as part of the consideration process? Regardless of the posting guidelines, I see many posts where the title has no relation to the question. Comments?
There's never enough time to do it right, but always enough time to do it over...
I was just going through Nodes to consider, selected "reap" (for a node that was considered for reaping), hit submit and this was displayed:
You said "I've reaped your node [id://1149099]. Reason: [[stevieb]]: reap: homework question; no perl content " to johnrock47
I've gone to some effort to recreate the message verbatim: that's exactly what was displayed.
I have two points regarding this:
Whatever code that generates the [[stevieb]] part, was probably intended to generate a link to the monk who initially posted the consideration, (in this case stevieb).
While I was one of the monks who considered this for reaping (and I don't really have any problem being identified as such), I didn't actually reap the node. Perhaps the message should, more accurately, identify NodeReaper as the one doing the reaping.
Whatever code that generates the [id://1149099] part, was probably intended to generate a link also.
I don't recall seeing a message like that before, so I'm guessing it's new.
I can't see anything in Tidings about it.
It's potentially related to the experimental change (Reaped Nodes ...Aug 11, 2015 at 04:00 EST), but that's really just a guess.
This surprises me. On many occasions I’ve seen a Consideration requesting that an approved node be transferred to another section, so I assumed that a node, once approved, couldn’t be transferred via the “Move to:” option in the Approval Nodelet. Was I wrong?
I’m also surprised that moving a node should cancel its approval. Is this a bug, or is it the expected behaviour?
Recently Active Threads is organised into categories — Questions, Meditations, etc. — and each category has a title which links to the relevant section in PerlMonks. If, e.g., I click on Questions, it takes me to Seekers of Perl Wisdom.
A recent post by choroba has put Categorized Answers onto RAT. But clicking on that heading takes me only to a Super Search for “New Categorized Answers”, which finds nothing. Is this a broken link?
The [kobes://foo] and [kobes://foo] link shortcut used to point to a certain CPAN search server. It appears in hundreds of nodes. Those links are now broken. [kobes://XML::Twig] points to a Not Found page, and [kobes://] points to the webpage of Archimedes Math Schools. (Luckily, the argumentless form is barely used.) What should we do with these links, and their documentation? Leave broken as is and document that it's broken, leave broken except the argumentless form, redirect to some other CPAN search server, render as non-linked text, remove the shortcut, link to a faqlet explaining that that search server is gone?
FYI ... when I stumble-upon certain mainline sections, such as Meditations or Perl Monks Discussion, ... and for some (but not all?) threads listed on those pages ... I lately observe that the content is often manydays(!) out-of-date ... until I log in.
I think that this problem varies from one major-topic to another ... e.g. Seekers vs. Meditations vs. PMD.)
Specifically, I think that I am seeing “cache artifacts” that seem to vary(!) between “headline” pages and “particular threads” within a topic ... but, not necessarily consistently. Sometimes I think that I am seeing a “fresh” page, while sometimes I think that a “neighboring” page is, in fact, “very stale.” (I generally suspect that “the headline page” is the one, of the two, that is “very stale.”) Given that I dump my local browser cache many times a day, I do not believe that local-caching is the root cause of this problem.