A user for a modpack has made a post saying their server was stuck waiting for 4 minutes while Cable Facade was trying to download configs from GitHub before it finally timed out the connection.

This is very not ideal for player/server owner experience. Enigmatica 9 modpack the player was using

My recommendation, upload a new mod version for each config change and do not pull configs from github. This probably would get you more points/downloads but it is a valid legit reason to upload more often. It would prevent unneeded network connections/slowdowns and be beneficial to people with bad or no internet.

The config could have an internal versioning so when mod updates and see config with older version, it will update the pre-existing config automatically with the new changes.

uploading a new version each time for a config change is more annoying that anything. but i'll listen to your recommendations

Be wary of GitHub thinking this connection is suspicious and rate limiting it. It could backfires that way as well.

Some people automate uploading to Curseforge and modrinth. I have a gradle task that does it for me that I click and it builds and sends the jar to the sites with proper tags and dependencies set. Some people do the same through GitHub Actions to do automatic jar uploads. That can help reduce the tedious work of releasing new mod updates.

actually there are hundreds of thousands of people playing with the mod. i'm so stupid

Best solution here imo is to have auto-updating configs, but yk.. have an actual timeout and don't stall the server.

i did that