You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
If a user uploads beyond the free tier (25GB) limit, which includes the hourly (3GB/h) and daily (10GB/day) limits the bridge will send rate limit errors, these should be identified and handled. With this endpoint we can then inform users that use the community app that they can't upload anymore due to this limit. Currently the free tier structure is a mess as (1) erasure encoding extra size is not taken into account and (2) the free tier simply doesn't work for many people.
MeijeSibbel
changed the title
Handle bridge rate limit related to free tier
Handle and pipe bridge rate limit error related to free tier to goobox-community-gui
Jan 14, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If a user uploads beyond the free tier (25GB) limit, which includes the hourly (3GB/h) and daily (10GB/day) limits the bridge will send rate limit errors, these should be identified and handled. With this endpoint we can then inform users that use the community app that they can't upload anymore due to this limit. Currently the free tier structure is a mess as (1) erasure encoding extra size is not taken into account and (2) the free tier simply doesn't work for many people.
storj-archived/bridge#505
storj-archived/storj.io#90
The text was updated successfully, but these errors were encountered: