http://www.perlmonks.org?node_id=1040

This section is only for discussing issues pertaining to the PerlMonks web site. You can ask about how things work, or offer ideas on how the site could be improved, for example.

Unless the topic pertains to the PerlMonks web site, it does not belong in this section. If you're unsure, check out Where should I post X? and The Perl Monks Guide to the Monastery, or ask in the chatterbox.

PerlMonks Discussions
Let's be the albatross
2 direct replies — Read more / Contribute
by stevieb
on Oct 15, 2019 at 17:04

    Remove yourself from political thought, frustration from things gone by strict adherence to protocol and the overall 'set in my ways, so fsck everything else'.

    Perlmonks to me is a safe place. A place where I've been able to ask questions or talk about numerous programming languages, mathematical equations, statistical analysis and things I never figured a fellow Perl programmer would understand.

    Thing is, the Perl programmers here did understand.

    I have been welcomed here for all of my technical life essentially, and I've done my best to reciprocate that back. I have respect and admiration for those who are for, and opposed to what I think. That's the premise of PM to me.

    Everyone appears to want to divide PM into this or that. We don't do politics here; we are not divisive by nature, and we shouldn't behave as such.

    As well-versed, experienced (possibly Open Source) programmers (some of us with Perl as our star language), inclusiveness is key. Whether that means allowing 'other' languages here or not is not for me to say. I will say though that I was accepted here as something, so were you, so if you're asking questions or answering them: "Where were you in life when you ran into Perlmonks. What did you acquire from the site? What did you learn from the people there?"

    Pushing off those who ask questions unrelated is our business, and we've done it for years politely. Demanding and advocating a select subset of programmers based on language isn't our business.

    -stevieb

Inclusion of Raku on PerlMonks
6 direct replies — Read more / Contribute
by haukex
on Oct 14, 2019 at 09:52

    The document The Path to Raku includes this:

    Sites such as PerlMonks appear to be really Perl (aka Perl 5) focused, and could possible make that clear in their description, or change their description to specifically include Raku.

    Although it's true that most of the nodes posted on PM are about Perl 5, several of the gods have made it clear on several occasions that Perl 6 / Raku posts are welcome. So this node is just to point out that references to "Raku" should probably be included in the PerlMonks description, although I'm not yet sure what the best way to do so is.

    Also, I'm not sure if it's feasible to go back and change existing posts, but perhaps we should standardize a [raku] tag for post titles.

supersearch: how to match words?
5 direct replies — Read more / Contribute
by rsFalse
on Sep 20, 2019 at 11:56
    Hello, I tried to supersearch about "trie", but many other words occurred as search result. How can I set borders to the word?
Test post for <code> and <pre>
6 direct replies — Read more / Contribute
by siberia-man
on Sep 16, 2019 at 13:39
    This is new thread as a branch from the 11104437. Initially I've been said:
    Please use <code> or <pre> tags for code samples, otherwise PM interprets [...] as links.
    My post has had a code rounded by <pre> only. Later I modified it to apply rounding with <pre><code> to avoid the mentioned isue.

    I confirm that anything like [...] is converted to links. <pre><code> resolve this issue. However (for me personally) the <code> generates a monospace text in the tiny font size.

    This one is rounded with <pre> only:
    something having "word"
    within square brackets word
    
    This one is rounded with <code> only:
    something having "word" within square brackets [word]
    This one is rounded with <pre><code>:
    something having "word" within square brackets [word]
    This one is rounded with <code><pre>:
    <pre> something having "word" within square brackets [word] </pre>
FIXED: Missing vote button on Snippets page
2 direct replies — Read more / Contribute
by talexb
on Aug 14, 2019 at 15:35

    I found myself on this page just now, and, as one does, went to upvote one of the nodes. Except -- there was no Vote button.

    I checked that I was still logged in (there are monks who shall remain nameless that mention they get logged out ALL tHE TIME), but that wasn't the problem.

    Thoughts?

    Updated 2019-0815 @ 1052ET Thanks, the vote button has reappeared. Thanks everyone!

    Alex / talexb / Toronto

    Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.

New Newest Nodes default for Show nodes created within the past days ... Newest Nodes Settings
2 direct replies — Read more / Contribute
by Anonymous Monk
on Aug 11, 2019 at 15:20
    My suggestion is to make

    7 the

    New Newest Nodes default for Show nodes created within the past

    7

    days ... Newest Nodes Settings

reap, troll-feeding of reaped troll
5 direct replies — Read more / Contribute
by LanX
on Aug 03, 2019 at 09:55
    Dear monastery

    A fellow monk singlehandedly invented the reap category "troll-feeding", and keeps applying it as consideration.

    It's normally declined, but I'm wondering why so many people still consider this reap worthy.

    Or do people nowadays just always click reap when they see a consideration?

    I'm bringing this up, because this amounts to a silent change in policy which should be discussed.

    FWIW: I wrote this comment before the parent was considered, and it was not apparent for me that it's really worth reaping.

    But still, if we start inventing such categories it'll border at censorship, at least.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

It's been ten years ...
2 direct replies — Read more / Contribute
by afoken
on Jul 29, 2019 at 13:06

    Do you remember what happened today, 10 years ago?

    No, not my first posting, that was a little bit earlier, still as Anonymous Monk. (Probably this one.)

    Also not my first posting as afoken, also a little bit earlier.

    So, what happened?

    What happened? happened.

    Some script-kiddie has demonstrated that storing passwords in plain text was (and still is) a pretty stupid idea. Caught perlmonks with pants down.

    Promises were made:

    Closing the Hole

    PerlMonks admins are working with the Pair.com folks (who manage our hardware and connectivity resources) to evaluate and strengthen security on the servers. No information is available at this time as to the status of this effort.

    Strengthening Authentication

    The administrators are planning to implement hashed passwords (allowing more than 8 chars).

    Now guess the current state. Or, just test it: Enter your user name into What's my password?. Click the submit button. Open your mail box.

    This is what I received:

    From: vroom@perlmonks.org
    Subject: Password Mail
    Date: Mon, 29 Jul 2019 12:46:51 -0400
    X-Mailer: Perl script "index.pl"
            using Mail::Sender 0.8.10 by Jenda Krynicky, Czechlands
            running on perlmonks.com (216.92.34.251)
            under account "root"
    Message-ID: <20190729_164651_081604.vroom@perlmonks.org>
    
    Hey there.
    You or someone else has requested a password for your username or e-mail
    address.
    Before you freak out, take a few deep breaths and remember that it's YOU
    and not THEM who is getting this password.
    
    Here's your info:
    
    username: afoken
    passwd: *** DELETED FROM THE MAIL BODY ***
    human name: Alexander Foken
    
    love, the management
    http://perlmonks.org/
    

    CONGRATULATIONS!

    Perlmonks' pants are still down, ten years later.

    See also:

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
Quote another post
4 direct replies — Read more / Contribute
by Pascal666
on Jul 23, 2019 at 13:35
Reputation: -4 (+-0.5 -3.5)
1 direct reply — Read more / Contribute
by LanX
on Jul 19, 2019 at 23:32
Solving possible missing links
3 direct replies — Read more / Contribute
by talexb
on Jul 16, 2019 at 09:59

    This node was up for moderation recently, and the cause was bitrot (out of date links).

    Would it be useful to go through the node database, and do a check for external links to see if they can be updated in the same way?

    Alex / talexb / Toronto

    Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.

The on-going riddle wrapped in a mystery...
6 direct replies — Read more / Contribute
by footpad
on Jul 12, 2019 at 13:40

    The story of paco, as many experienced monks know, has long been an enigma in the Monastery, a source of ongoing curiosity and speculation (click through for more).

    Today, the speculation grew curiouser, as newly-discovered evidence seemed deepen the mystery:

    1. Begin by visiting the venerable's home node and noting the date of last visit.

    2. Next, note the post date of this node and then note its Approval nodelet values.

    Miracle? Impersonation? Gallifreyan shenanigans? Something else entirely?

    Who knows? \_(ツ)_/

    So...it remains a right mystery suitable for a lazy Friday hobnob over cherry pies.

    --f

    Update: Update links to nodes to help play the legend forward.

New member Introduction
1 direct reply — Read more / Contribute
by kuboos
on Jul 08, 2019 at 15:47

    Hello my fellow monks, I am new to this forum. I have been using perl now for a few years. I stopped using the language about 5 year ago. I have my regrets for doing that. Now i am learning everything from scratch. Well i hope it will be fun doing that with the companionship of other monks.

    I wish to learn and contribute to this community and if possible to Perl itself. I am high impressed with the level of documentation found here. I know i have some more reading to do and i hope i can commit myself to study and learn.

    Once again i humbly greet you all and wish to learn from you all.

ChatterBox XML Ticker randomly throwing messages away
1 direct reply — Read more / Contribute
by choroba
on Jul 04, 2019 at 12:01
    This has been discussed in the ChatterBox several times, but it hasn't been mentioned in a more permanent manner.

    I've created a ChatterBox client pm-cb-g that uses the New Chatterbox XML Ticker. When posting, sometimes the message is not displayed, but when I try to submit it again, I get back the dreaded Whoa, Cowboy! You said that already. Don't 'reload'? So somehow, PerlMonks thinks the message has been sent by me, but it doesn't display it.

    It's never happened when posting from a browser.

    I have a suspicion it's related to the fact one of our servers has a wrong timezone setting. When the message gets processed by it, the wrong timestamp makes it too old (or too far in the future) to be displayed. I tried to study the relevant nodes (chatrepeated and repeatedchatter), but my pmdev-fu is to weak. Can anyone help? Would it be possible to fix the timezone on the server so I can at least disprove the suspicion?

    I usually append #2, #3 etc. to the message when reposting it to prevent the Whoa cowboy effect. My personal record is #7, the last message was posted via the browser as I lost patients.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
New Feature: Usergroup-Private Threaded Discussions
No replies — Read more | Post response
by jdporter
on Jul 01, 2019 at 13:44

    We have a new feature: usergroup-private discussion threads.

    This lets members of groups (such as pmdev) have threaded discussions, just like in the regular sections, but completely unvisible to anyone not in that user group (aside from gods, of course).

    Up until now, user groups have always used wiki nodes for intra-group discussion; but wikis are pretty suboptimal for this purpose. (They remain useful for other purposes, such as collaboratively maintained documentation.) The esteemed chromatic made such as observation way back when the concept of the wiki nodetype was first proposed:

    IMHO wikis are best suited to accumulating community resources and keeping them relevant. I do not think that for general discussion that a wiki makes more sense than the usual noding. But if a topic comes up often, summarizing it in a wiki would make sense.

    So this new feature is intended to replace the use of wikis for discussion.

    If you're a member of a user group, try going to the group's page (janitors, pmdev, breathers of fire, etc.) and see what's at the bottom.

    One main way in which these threaded discussions are different from the regular sections is that nodes are not votable and will always have reputation zero — the idea being that it wouldn't be fair for a monk to be able benefit monetarily from posts which are not accessible to the general public.

    Consequent to that, replies are always shown newest first.

    Whenever someone posts a direct reply to a group which is essentially a top-level post under a group it sends a message to all members of the group, something like this:

    There is a new comment on pmdev by jdporter...

    This idea was initially floated and developed in Create new [pmdev]-only section "Pmdev Discussion" and Create new [gods]-only section "Gods Forum". But note that the final implementation of the feature did not adhere to the designs suggested in those threads.

    If you're in pmdev, you can see a technical description of the implementation by visiting the new nodetype usergroupnote; scroll to the bottom to the documentation.

    I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.

Discussion Item
Title:
Give us your input:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.