Enforcing Web3 user storage capacity limits - second iteration

[mbommerez]

The following describes the complete scope of the second iteration:

1. User notifications

Notifying users who are close or over their storage limit (usually 1TB)

• [ ] Potential changes to email template
• [ ] Potential changes to scheduling of email job

2. Admin notifications

Notifying admins who are the recent heavy users and who is over the limit

• [ ] Potential changes to email template
• [ ] Potential changes to storage usage brackets reported in admin overview
• [ ] Potential changes to scheduling of email job

3. Blocking upload access

Admins blocking access to APIs for people over the limit.

• [ ] Continuous calculation of used storage and date stamp exceeding that limit
• [ ] Usage of a grace period during which users can reduce storage or request higher quota
• [ ] Automatic blocking
• [ ] Detect fraudulent upload (by volume in short time, amount of time they have been a member, ..) ??

4. Request more storage

Users requesting a higher storage limit with the reason

• [ ] Form in the website to request more storage with explanation of project / reason why + amount desired
• [ ] Visualise incoming storage increase requests

5. Grant more storage

Admins granting a higher storage capacity to individual users

• [ ] Ability to grant this, grant a different amount or refuse request from admin.storage
• [ ] Automatic update of quota in user tags + notification email of this event (to user)

[JeffLowe]

Note: Regarding number 4 "Request more storage", a user request system is currently underway in Admin initiative. This will establish groundwork for user requests that are managed within admin application, as well as web forms displayed in web3 and nft.

[heyjay44]

@mbommerez I'm just doing a bit of a clean up and this covers some of the work we've been doing on pricing. Can I move this ticket into that project?