Aart van Baren

@kineticsquid It will work, but there's currently no limit on the amount of active personal access tokens a user can have.

@marcdumais-work You need to sign the Eclipse publisher agreement to be able to create a namespace or publish an extension. https://github.com/eclipse/openvsx/blob/95d53c3f42c3d13e393ba4e6055acfcf700bcffa/server/src/main/java/org/eclipse/openvsx/LocalRegistryService.java#L422-L428 https://github.com/eclipse/openvsx/blob/95d53c3f42c3d13e393ba4e6055acfcf700bcffa/server/src/main/java/org/eclipse/openvsx/LocalRegistryService.java#L467-L474 You can create a basic "read-only" token by...

Ah, oke. There's a check in the webui: https://github.com/eclipse/openvsx/blob/95d53c3f42c3d13e393ba4e6055acfcf700bcffa/webui/src/pages/user/user-settings-tokens.tsx#L120-L131 I think we can remove this. Just have to make sure to check for a valid publisher agreement when a publishing...

@kineticsquid I don't know. What you propose is a complete new process.

@kineticsquid We can add the `premium` role to users. Users with the `premium` role can make a higher number of requests per second than regular users. This requires a database...

Ok, so this issue can be closed?

The rate limits are configured in `application.yml` https://github.com/EclipseFdn/open-vsx.org/blob/33ab99a88a17665765dad980e1b78833184cbb23/configuration/application.yml#L117-L120

If a client does 15 calls in the first 15 ms, then the client has to wait 985 ms to do the 16th call. There's no additional wait or timeout.

I'd say this is more for internal use. To monitor the system and set alerts for when it doesn't perform as expected (too slow, too many errors, etc.). You can...

@kineticsquid https://openvsx.grafana.net