2023-07-03 10:50:49 crc: is your domain getting hammered?

2023-07-03 10:51:22 its very slow right now and i wanted to look at the source for the older retroforth releaseses

2023-07-03 10:51:57 Yes

2023-07-03 10:53:32 did hn suddenly discover it or something?

2023-07-03 10:53:39 139 connections; 97.8 load average

2023-07-03 10:54:06 hmm, that's quite sudden

2023-07-03 10:54:24 i'm looking for some assembly references right now

2023-07-03 10:54:33 I paused incoming connections for a few minutes until it clears up

2023-07-03 10:54:36 also, is there no retroforth 5?

2023-07-03 10:58:18 retroforth 5 only existed briefly (it was my fork of tcn's retroforth 4, and was nearly identical IIRC); 6 replaced it very quickly after I took over development.

2023-07-03 10:59:29 fair enough

2023-07-03 11:01:50 you dont have the sources for the older versions on a repository, do you?

2023-07-03 11:02:01 i dont want to hammer the server to download the older ones

2023-07-03 11:07:55 setting something up for this...

2023-07-03 11:08:22 thanks

2023-07-03 11:08:52 the server is back up

2023-07-03 11:08:59 https://git.sr.ht/~crc_/retroforth-releases

2023-07-03 11:12:24 thank you.

2023-07-03 11:20:05 this will be a good reference

2023-07-03 11:29:39 I found & added a copy of my last retroforth 5 code; there's a small chance I might find something a little older when I get a chance to go through some old hard drives, but that won't be doable until the weather cools down (too hot to dig through boxes in the attic right now)

2023-07-03 11:46:52 ah, cool.

2023-07-03 12:09:05 hmm, its missing retro 2

2023-07-03 12:09:50 I updated it again (added retroforth 2, which I missed, toka (used in building retro10), rx (an experimental offshoot of retro8), and sedforth (which used parts of retroforth & sed to compile forth to assembly for linux)).

2023-07-03 12:10:09 also organizing into directories by version

2023-07-03 12:11:09 ah, very nice.

2023-07-03 12:13:59 Does anyone know where the increase activity came from?

2023-07-03 12:14:15 good question.

2023-07-03 12:32:51 I don't have any way to see (casket doesn't generate logs except when I'm testing significant changes, which hasn't happened in quite a while)

2023-07-03 12:40:39 I don't see anything in any news feeds or anything

2023-07-03 12:40:48 Or google search of recent pages

2023-07-03 12:42:00 I wonder if it's something like what happened to https://gmplib.org/ (if you look at the site they describe issues at top of page)

2023-07-03 12:42:21 "Around 2023-06-15, a project known as FFmpeg decided that it would be a great idea to clone GMP in their CI scripts, meaning that every one of their commits requested a compressed clone from the GMP servers. But, by Github's design, hundreds of FFmpeg forks automatically followed suit, themselves cloning the GMP repo."

2023-07-03 12:43:16 I doubt it's that but I also doubt there's some kind of intentional ddos, it's possible you got trapped in some kind of silly scraping script

2023-07-03 12:43:39 There's a lot of scraping activity at the moment, I know Twitter and a number of websites have deployed extreme counter measures to try and stop it

2023-07-03 12:43:54 (with questionable logic on Twitter's part but nevertheless)

2023-07-03 13:00:20 My guess would be scraping; normally if it hits hn or lobste.rs or similar the number of connections is notably higher

2023-07-03 13:01:04
ACTION is hoping the upcoming rewrite of casket's transfer code will help reduce the load issues