>>/9810/
> delay
Note to self: it's in milliseconds, dummy! So don't use
> $ grab-site --concurrency=1 --delay=5-10 https://www.canterlot.com/ 1>4log1.txt 2>4log2.txt # random wait between 5 and 10 ms
> $ grab-site --concurrency=1 --delay=5 https://www.canterlot.com/ 1>5log1.txt 2>5log2.txt # wait for 5 ms
> $ grab-site --concurrency 1 --delay 5 https://www.canterlot.com/ 1>6log1.txt 2>6log2.txt # wait for 5 ms between requests

I went with a colossal wait time of between 5 and 10 seconds:
> $ grab-site --concurrency 1 --delay 5000-10000 https://www.canterlot.com/ 1>7log1.txt 2>7log2.txt
I'm almost certain that my computer will crash before it finishes.

> Calculate delay spped/bandwidth against whatever "too long" might be.
good idea

Some URLs from canterlot.com, not in WBM before today:
https://content.invisioncic.com/r257793/emoticons/default_ajsleepy.gif
https://content.invisioncic.com/r257793/emoticons/default_applecry.gif

 >>/9813/
> PrimeNet
Running file "mprime" (64-bit Linux binary) in GNU screen - it said:
> 19. Help/About PrimeNet Server...Worker starting...Setting affinity to run worker on CPU core #1 [and #2, 4 cores total]
> [Worker Mar 11 00:55] Running Jacobi error check. Passed. Time: 73.350 sec.
> [Worker Mar 11 00:56] Resuming primality test of M76804397 using FFT length 4M, Pass1=1K, Pass2=4K, clm=4, 2 threads
> [Worker Mar 11 00:56] Iteration: 4994 / 76804397 (0.00%).
> [Worker Mar 11 01:00] Iteration: 10000 / 76804397 (0.01%), ms/iter: 47.667, ETA: 42d 08:48
> [Worker Mar 11 03:41] Iteration: 210000 / 76804397 (0.27%), ms/iter: 47.566, ETA: 42d 04:01
Talk about long-running processes... https://www.mersenne.org/why_join/