The patch passes all the module's current tests and works for us. It took our CPU load from being pegged at 75% all of the time to being idle. So, if you're using Cache::Memcached, and the ->stats method (which isn't in the XS version of the module) then you might want this patch.
On that note - who is maintaining Cache::Memcached? The last release was in 2012. This isn't a high river module, but any app of significant size or age is *probably* using it and if they're using the ->stats method then ... Sure there's the ::Fast version, but I suspect this version is in a lot of places.
So if you know someone who knows someone who can prod the current maintainers then please point them at this post/patch. If you're using Cache::Memcached then perhaps try out this patch as well.
]]>Robert asked my if I would be OK with it being the official static archive, which I said is fine but bear in mind the caveats (again, as per the README).
]]>BPO is a shitshow, you should email me directly - LEEJO on CPAN will find you an address, or raise an issue on the github repo.
]]>The second issue is that I haven't cleaned up links in author pages that refer to dists that have no bugs - again I will fix those later. If a dist has no active/resolved/rejected bugs then those are invalid links (I may just add a custom 404 page).
]]>The static archive is a git repo, hosted using github pages. The repo can be found at https://github.com/rt-cpan/rt-cpan.github.io and it has a README that explains how the archive is/was built and URL structure.
The archive is generally complete, it will be updated one more time before the end of February this year. If you discover any issues then please raise an issue using the github link above. If you need to search the archive then you can do that using the gihub link above also, or git clone it and use the command line.
Happy New Year!
]]>In the reddit comments, brian d foy mentioned Léon's WWW::UsePerl::Server, a module to host the use.perl.org archive.
I grabbed the archive, Léon's module, installed all the deps, got it up and running after hacking the module to work with the latest Catalyst, then combined some sed, awk, perl, SQL to create a static version of the site with URLs that allow it to function correctly: https://use-perl.github.io/. Note that the change in the URL structure to get it to work a) as a static site, and b) on github pages, means that any "permalinks" that might exist elsewhere in reference to it will need manual fiddling to get to the page in question - the URL structure should be relatively obvious however.
The site is 99% there. There appears to be some mojibake, which I suspect is in the original mysqldump file but haven't confirmed. I also need to fix some self references to use.perl.org that are in entries/comments, stripping them out so they resolve to the current domain. But it's 99% there - about 40,000 blog entries, a lot of Perl, a lot of interesting history.
It's all in a git repo at https://github.com/use-perl/use-perl.github.io, which you can use if you want to search the content (it is now static afterall). Or file a PR or fix.
Happy Xmas spelunking
]]>
Most Active Authors (All Time):
Most Active Authors (2016 onwards):
Most Active Months:
Total Post Count By Year:
I haven't bothered going back pre-blogs.perl.org (i.e use.perl.org, which this site essentially replaced[1]), and I don't think the figures show us anything surprising; there are myriad reasons for the drop in traffic that can probably be explained by one or more of the following:
The last one is probably the most interesting argument. I pay little attention to facebook, linkedin, twitter. Medium is trying (and failing?) to eat up all the blog content. irc.perl.org is a ghost town, reddit is reddit, ironman rusted, what else have I missed? Probably loads.
I hesitate to use the phrase "echo chamber" as it doesn't seem accurate, it's more like we're in a dozen or more smaller echo chambers. Anyway - I don't think you can claim to be in a echo chamber if nobody is actually saying anything, which appears to be the inevitable end state given the above figures. This is merely an observation, I'm not appealing for change. And If I were appealing for change then it would probably be of the type: write less often, but more.
[1] use.perl.org is difficult to get info out of now, it's basically dead. A lot of content is lost - what happens when blogs.perl.org enters the same state?
]]>