From: worldoff9908@gmail.com   
      
   frg wrote:   
   >   
   > Archive moves soon to another provider and is currently disabled because   
   > of excess traffic requeasts from an unknown third party. Some forking   
   > bot or whatever seems to like to download gigabytes of data.   
      
   I'm guessing that the excess traffic issue is coming AI bot scraping.   
   Even when archives get moved, it may not be long before the AI scrapers   
   find that site, and start imposing their overhead costs there, as well.   
      
   I'm aware of several sites that are defending themselves against that by   
   putting their content behind a CloudFlare CAPTCHA.   
      
   One of the effects of sites with CloudFlare is that Seamonkey 2.53.22   
   isn't handling the CAPTCHA dialog correctly, and the only way to get to   
   the content of a site that's using that is to use another browser.   
      
   Right now, I'm grateful to have the old OpenWith extension installed, as   
   I use that extensively, and it's annoying that the developer has not   
   only quit developing it, but where the XUL/pre-Quantum has been removed   
   entirely.   
      
   Although I would love to see Seamonkey's capacities upgrade to be able   
   to support the CloudFlare CAPTCHA in a future release.   
      
   At the same time, I wonder if it would be feasible/possible to integrate   
   OpenWith into the Seamonkey code directly.   
      
   I recognize that the amount of necessary work for either one of those   
   may be significant, so I'm not complaining, and I will happily accept   
   whatever the devs produce.   
      
   Smith   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)