Skip to content

[Important] Register your application and get API Key - (Prevent API Overload) #7

Description

@softmarshmallow

Important notice (ACTION REQUIRED)

Recently, lots of abused usage of free bridged cloud services are detected. To keep providing the service free for everyone, we decided to force application registration to use bridged.cc services.

Register your service here -> https://grida.co/cloud/cors/register

  1. service / account registration
  2. get your api key in 24H
  3. update your bridged.cc service call to use registered api key
  4. unauthorized request will be blocked from Oct 10 2021
  5. OR Use this hotline to contact us - join slack
curl -XGET -H 'x-cors-grida-api-key: your-api-key-here' 'https://cors.bridged.cc/https://grida.co'

Please join our community slack for latest updates / any questions, via this invitation link

History (From here, it's an informative document, your action is not required)

(July 4 2021)
As noticed, we've started blocking unregistered applications order by most frequently accessing. currently 6 hosts are blocked to use our proxy service, waiting for the organizers to contact us. (with no contact, these blocking will remain permanent) - gridaco/base#31

(June 29 2021)

(June 2021)
Request per month skyrocketed, reached up to 2 billion requests. We decided to make the service available to authorized app only, preventing abused & anonymous usages.

(May 2021)
Currently cors services is being called maximum rate of 100,000 request per hour globally, Which the financing issue is held cause of this.

We want to keep this service free and public, open to everyone and we'll need to limit max request per hour per ip or account on free tier to do this.

We're thinking of 10,000 request per hour per ip/account will be an adequate quota to provide as a free tier.

I'll keep this thread open and get feedbacks for this idea.

Current action items are.

  • Add statistics to services so we can find if there is a abusing usage of this serviec. (too many request for few clients - we don't want this to happen)
  • Write privacy policy for statistics data collecting

Problem still lives.

  • How to tell current develooers that this service will be updated? - we don't have there email address or nothing.

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions