More specifically, cloudflare offers a caching layer with some embedded anti-malware measures.
It is not a complete solution, but it does deal with a number of botnet-induced performance issues. Also, they provide very significant defense against distributed denial of service if you will pay them $2400/year. But even the free service they offer provides some defense. The free service gets them some goodwill within the development communities, and also gives them a larger sampling and can give them earlier warning for new malware developments. It also supports the needs of the search engine organizations. A cost of the free service is less direct control over analytics, since the bulk of the requests will be going to their servers. It also only really works for static or near-static content. Another issue, though, is that the free service only crawls your site once a week. They have an API you can call to invalidate the cached copy of an updated page, but I have not been able to find anyone writing about configuring moinmoin to make that api call after a page is edited. Of course, one need not necessarily touch moinmoin itself to deal with this issue. You could, for example, build your own layer between moinmoin and cloudflare with some heuristics that detect changes and invalidate the cloudflare cache appropriately. But if this approach is the right approach it would suggest that moinmoin's documentation is so disorganized and the community is so unreachable as to make it a dead or dying piece of software. (And maybe it is, but that's not a call for me to make.) Meanwhile, I've got so many little projects going that just prioritizing them is something of a problem. And I've been finding that software projects in particular are becoming harder to understand because of issues like the above. So that's something we need to guard against. Thanks, -- Raul On Mon, Jul 13, 2015 at 11:45 AM, 'Pascal Jasmin' via General <[email protected]> wrote: > IIUC, and I could easily not, cloudflare is more like putting a firewall in > front of apache, rather than replacing MoinMoin. The firewall also acts like > a firehose. > > > ----- Original Message ----- > From: bill lam <[email protected]> > To: 'Pascal Jasmin' via General <[email protected]> > Cc: > Sent: Monday, July 13, 2015 1:06 AM > Subject: Re: [Jgeneral] cloud flare > > IIUC MoinMoin used by jwiki is susceptible to spams and is > beyond repair. However migration to another wiki engine requires > a huge effect. > > Пн, 13 июл 2015, JGeneral написал(а): >> I understand cloudflare has some builtin spam protection. >> >> >> ----- Original Message ----- >> From: chris burke <[email protected]> >> To: General forum <[email protected]> >> Cc: >> Sent: Monday, July 13, 2015 12:11 AM >> Subject: Re: [Jgeneral] cloud flare >> >> I do have plans to fix the wiki, but work has got in the way of getting >> this finished. >> >> The wiki gets hammered by spam bots, which is why it is in robots.txt, and >> why you see the slowdowns. >> >> >> On 12 July 2015 at 18:59, Raul Miller <[email protected]> wrote: >> >> > I notice that cloudflare has a free offering: >> > >> > https://www.cloudflare.com/plans >> > >> > With this, perhaps /jwiki/ could be removed from robots.txt - which >> > would greatly increase the usefulness of third party search engines, >> > for finding relevant J documentation. (I am noticing just how >> > painfully slow the wiki is, now.) >> > >> > This wouldn't necessarily do anything about editing speed, but I'm >> > noticing that wiki pages load very slowly (sometimes 20+ seconds) and >> > that makes me reluctant to read all that useful documentation. >> > >> > So I think this would be a good step in the right direction. >> > >> > Thanks, >> > >> > -- >> > Raul >> > ---------------------------------------------------------------------- >> > For information about J forums see http://www.jsoftware.com/forums.htm >> >> > >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm > > -- > regards, > ==================================================== > GPG key 1024D/4434BAB3 2008-08-24 > gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 > gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
