Follow-up Comment #17, bug #66342 (group groff): On Monday, 2 February 2026 23:46:33 GMT Dave wrote: > Follow-up Comment #12, bug #66342 (group groff): > > The comment #8 questions are for all interested parties, since they involve > a change from everyone's previous proposals. So if anyone objects to my > attempted middle-ground proposal, it's either back to the drawing board, or > re-Rejecting this ticket. > > The goal is to get everyone to agree to an architecture before anyone spends > time coding it. But so far it's gotten neither yay nor nay from anyone. >
Hi Dave and Branden, I have had continual timeout connections to https://savannah.gnu.org since the weekend. Is it just me! :-) But from what I remember of your sensible comment #8 I was in agreement and stuck it on my todo list after 1.24.0 is out the door. If you have access to savannah please can you confirm this message (via the email route to savannah) has arrived. I have a hankering I may have triggered an anti ddos rule and got myself blacklisted, I believe the last time I successfully accessed the site at the weekend, firefox was mis-behaving, I left it to have my lunch and when I came back it was still using a lot of cpu and I killed it, but I wonder if during that high cpu it was hammering POST messages at savannah, which put me on "the naughty step". I have recently (my xmas present to myself) upgraded my internet connection to 500Mbs, so firefox misbehaving would be serious. Do you have an email address I can use to contact savannah admins who can help me get access again. Of course, it could be savannah is under a real ddos attack and I've just been unlucky not to get a connection slot. Cheers Deri _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?66342> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
