Update: The other one was Reaped: Re: How can I capture the number between this HTML tag.

I just wanted to mention, the change announced Perlmonks.com and Perlmonks.net now redirect to Perlmonks.org seems to be having a positive effect. Just look at Newest Nodes; it has actual posts, with questions, now that the site is speedy again. I like to think there's a correlation. So, thanks to those who were involved in making it happen.

chatterbot *** The monastery has been quiet for 10 days 03:23:00 ***

Following up on Perlmonks.com and Perlmonks.net to redirect to Perlmonks.org

Thanks to the support of Leo Lapworth, Olaf Alders, and Robert from Perl NOC, this site is now served from behind the Fastly CDN. The IP addresses have changed to Fastly IP addresses.

The .com and .net domains redirect to perlmonks.org, to improve the caching of the pages.

If you access the site logged in, you should see no difference, as the pages pass through directly to the main machines.
Anonymous access should also be mostly unchanged except for AI scrapers.

If you notice any adverse changes, please post a reply here.

*Credit on our side goes to the irreplaceable Co-rion.

As discussed in Moving the site behind a CDN, we will soonish move forward with moving the site behind Fastly. In conjunction, the domains perlmonks.com and perlmonks.net will also redirect to perlmonks.org, to improve cache hit rate.

At least during the move the css.* domain will be unavailable, but as far as I understand the setup, we can later make css.perlmonks.org work again, especially for logged-in users.

For the time being, you can update your bookmarks to perlmonks.org and save the login cookies for that domain.

As for the timeline, the work is done by volunteers. I expect the DNS update and HTTP redirects to happen sometime next week.

Thanks to main work by Leo Lapworth and Olaf Alders at the Perl Toolchain Summit, we now have a setup that allows us to move the site behind a CDN ( https://www.fastly.com/ in fact ). Fastly does not require magic Javascript to execute on the clients, but will ideally still help to stem the deluge of scrapers. Together with this, there will be some likely changes:

The site will only be available under perlmonks.org. The other domains will issue HTTP redirects to that address. This means that you will have to check the hostnames in your tools and in your browsers. Using the hostnames to differentiate between user profiles will not work anymore.

The site pages will be cached for Anonymous Monk. We'll start out with a cache duration of 1 hour but will likely increase this. Fastly has an API, so maybe busting the cache for recently updated threads is possible. If you are polling Perlmonks without a login, you will likely see a more static response.

The timeline to move the site behind Fastly is to do it is likely in the next two to four weeks, depending on the availablility of myself and others.

# Be kind. Wait between fetches longer than each fetch takes.
...
Disallow: /*node_id=3989nCrawl-Delay: 20
[download]

Cheers
LanX

(via Tor, IP probably blocked because of greedy downloads ;-)

UPDATE

Never mind, I found a way to throttle wget and bend it to my needs :-)

I'd like to locally mirror this site for personal use. Need at least access to my thought processes of the last 2 decades.

Problem is that I don't want to put even more strain on the servers.

I looked at the wayback machine as alternative source and unsurprisingly it had problems accessing threads since "the AI" started its distributed denial of service attack.

I suppose a compressed tar ball would be in the range of 0.1 to 1.0 GB and could be offered as a torrent. (Unfortunately AI wouldn't be "I" enough to use that instead)

Hmm ... Alternatively to plain html maybe only the XML versions of the posts plus a mojolicious app running the search engine and rendering the posts.

Parts of this post rather belong to meditation, feel free to move it if appropriate.

My first page after logging in is the "Newest Nodes". And there I sometimes do not see any posts because the last one is older than a day. Sure there is a dropdown to show older posts. But, I think hitting the empty list is a bit discouraging to discussion. Can the posts "disappear" in 2,3 days instead? Or just show the last 10 posts irrespective of age, unless their age is ridiculously old? Unless there is a setting I am not aware of.

On the positive side, navigating the site is absolutely fluid. Thank you PM!

bw, bliako

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?

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

It is an old idea, but got some new life from Ideas for PerlMonks 2.0 (nearly a year ago).

• https://github.com/arunbear/monk_world
• https://github.com/arunbear/monk_world_api

Update 03-01-2026, Replaced demo with screenshots

• Threads
• Search
• A node