This section is only for discussing issues pertaining to the PerlMonks web site itself.
For example, asking about how things work, or offering ideas on how the site could be made better.
This is the first time I've been able to reach PerlMonks this year. To be fair, I've only been trying for the last two weeks and only once a day at around 20:00UT. But I try once and if the RAT page fetch times out I move on to other things. Is there an expectation that the page timeout issue will improve?
Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
This is a project I started working on in late October, before I knew that there's already a rework project in progress, i.e. Taking advantage of E2 improvements
You can designate a node to be your "preferred default node". Go to your User Settings and enter a node ID in the box labeled Preferred Default Page. (NB: this must be a node ID, not a node title.)
If you navigate to the node named default, it will redirect you to your configured default node. (If you have no node so configured, it will redirect you to The Monastery Gates.)
This "preferred default node" is also used on the Login page, as one of the suggested places you can go next, after logging in.
In the future it may be used for other things as well. Suggestions welcome.
The list of new CPAN modules looked stale to me so I checked on MetaCPAN and found that the last date with new modules is Sept. 30. This seems unlikely. Does our widget grab from MetaCPAN?
The way forward always starts with a minimal test.
At the risk of stating the obvious, Perlmonks response time has bottomed out again. For the last several days, 9 out of 10 page requests return with "perlmonks.org took too long to respond." Does anyone have any ideas how to solve this?
P.S. It took the better part of an hour just to submit this post.
"It's not how hard you work, it's how much you get done."
Selected parts of the site are now served from static HTML files instead of being dynamically generated on-demand.
The update process for these pages is still manual, so if you reply to an older node, do not be surprised if the reply is not visible to Anonymous Monk.
Currently, the export is from April 2025 and affects all users and replies up to node id 210000.
Ideally, this will reduce the load on the site so that logged-in human users can actually use the site.
See this recent post for an example: converting binary to decimal
All voting buttons for all nodes on the page are placed way off the screen because of the long lines in the initial node.
It seems the Function Nodelet links are broken: Instead of leading to substr, they lead to ?node=doc://substr which doesn't work (and even logs me out). First reported by adamsj in Chatterbox.
