Greasy Fork

Seems your script stay at the "Fetching" state....

Seems the old problem is coming back again ... Have you met met the error that greasyfork displays "We're down for maintenance" these days?

This message seems to mean that you have met a per-IP rate limit (see GF discussion #233126), maybe you're adding/removing many scripts in a short time. So if you are meeting this error, try to wait for a while and try again.

If you're not meeting "We're down for maintenance" then maybe there's another bug in script. May you provide me the console log?

Seems not related to "We'r down..." or too many adding script...
Your menu stay grayed (but for your script, i see the "V" next its name )

Here one console error around your script (seems fails to put it here, i don't remember how to post code in this forum..):

Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
window["__f__lvu56rg1.7jh"]/ https://greasyfork.org/fr/scripts/439699-greasyfork-script-set-edit-button:84
m https://greasyfork.org/fr/scripts/439699-greasyfork-script-set-edit-button:78

Could you please provide me the screenshot of console?

You can upload images by using the button under the comment text box (like this comment submitted by me).

Also, before taking screenshot, remember to click on the error message in console to expand the folded error message, so I can see the full tracing information for the error.

Yet, it seems there is a problem to add image here...

Seems a pb of size:
"doit être inférieure à 200 ko (la taille actuelle est 529 ko)"

It seems the error you reported yesterday (in orange rectangle with purple underline in it) is not associated with my script, it seems belongs to another userscript.

Another error (in blue rectangle) is from my script, which shows GFScriptSetAPI.getDocument in my script received a response with status code of 503, which seems like the same error of "We're down for maintenance". You may find this error is thrown in line 167 if you reveal my code.

Since you have a large amount of script sets, it seems hard to avoid touching the rate limit while the script is fetching script sets. Maybe reducing some auto-sync could be helpful, but that also increases the risk of script set data being different between browser and GF server. What do you think?

Alternatively, slowing down the fetching process may also help, but since I don't know the exact rate limit of GF it's hard to set an appropriate speed, and of course, the script will become much slower.

1 - I tested to disable the other script:
"[TS] Citrus GFork v.1.1.49 Fix by KONF (Marqued) + Decembre fix"

Same problem.

2 - "Maybe reducing some auto-sync could be helpful"
I don't know ;-)

Maybe i can delete some sets....

I have deleted some sets.
In Quantum, always Fetching PB.
BUT, Strangely, with Waterfox Classic, your script work normally...

If i use this CSS, i can use your buttons (i enable them without "fetching" process ending).
But i have not always the "V" before all the sets labels (fetching PB):

#script-favorite select#favorite-groups {
display: inline-block !important;
height: 22px !important;
width: 100% !important;
min-width: 20vw !important;
max-width: 20vw !important;
pointer-events: all !important;
filter: grayscale(0) brightness(1) !important;
opacity: 1 !important;
}
#script-favorite [style*="pointer-events: none;"],
a[id="favorite-add"] {
display: inline-block !important;
margin: 0px 0.5em;
filter: grayscale(0) brightness(1) !important;
opacity: 1 !important;
pointer-events: all !important;
}

I have posted to the GitHub's Greasy Fork:
Too many "Down for Maintenance" since a long time
And here :
Am i alone to have Difficulty to login in Greasy Fork

And Jason say it seems the " down for maintenance" problem is from the use of your script.

Jason:
"for you specifically, from the logs I can see you're hitting the rate limiter. I'm seeing some bursts of 50 requests per second to URLs like /fr/users/8-decembre/sets/NNNNN/edit, which I would guess is from one of your installed scripts"

Work great seems your last update:

Read:
Thanks for @JasonBarnabe 's API support

Thanks a lot!
:-)

I've read all of these. Great thanks for you too：）