G'day perldigious,
"Now you made me feel unrepresented and infrequently used kcott. :-)"
Oh, no! Well, we can't have that now, can we?
:-)
Your poem, Posthumous Apologies to Edgar Allen Poe
— which, incidentally, I upvoted, along with 25 others (at the time of writing) —
was posted too early to be in the range of the Newest Nodes snapshot.
Congratulations on
Posthumous Apologies to Edgar Allen Poe's
high Reputation.
Looking at Perl Poetry,
I see gaps, typically lasting weeks, and somtimes months, between posts;
your own, Posthumous Apologies to Edgar Allen Poe,
was the first post in over four months, and there hasn't been one since (at the time of writing).
I think "Infrequent" is a reasonable description.
[Aside:
Your link to Poetry, actually returns the home node of a monk named Poetry.
I suspect your markup has '[Poetry]';
understandable, given the Section link names at the top of your page, but wrong.
I've had these types of name collisions in the past:
to avoid any chance of future, such collisions, I use the node's ID, like this:
[id://1590|Poetry] ⇒ Poetry (Perl Poetry) and
[id://1075685|Poetry] ⇒ Poetry (a monk named Poetry).]
PMD, along with SoPW and others,
were not mentioned because they did have entries
and I was writing about Sections that didn't.
This is why your eagle-eyed
Number of replies shown in Monastery Gates incorrect?
— which, incidentally, I upvoted, along with 17 others (at the time of writing) —
wasn't mentioned.
Congratulations on
Number of replies shown in Monastery Gates incorrect?'s
high Reputation.
[Aside:
Your PerlMonks Discussion link is also stuffed:
it resolves to a Super Search page.
The problem is similar enough to the last to have the same fix,
yet dissimilar enough to not include a monk named "PerlMonks Discussion".]
[Aside:
Having bagged two of your three links,
I thought I'd better say something positive about the third, which does appear to operate correctly.
As before, you can remove any chance of a name collision by using a node's ID,
e.g. [id://861371|Ken] ⇒ Ken (my home node).]
Hopefully, that resolves the representation issue;
frequency may be in the hands of a Muse or two.
:-)