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
Probably we can't check thoroughly the data before it's being uploaded to google storage, in the same server, for performance reason, so the currently planned architecture is that:
The data is uploaded to google storage in "private" mode. Nobody would be able to access this data, not even the uploader.
A request to check this data is pushed to a queue.
The data is checked by another background process.
If the data is deemed correct, its access control is switched to "public".
The process needs to be fast enough that the user doesn't have to wait more than 1 minute.
When we switch to a WebSocket architecture (issue TBD) we can provide progress updates to the uploader.
To prevent uploads of malicious or unwanted content, we should checking on uploading that profile data match what is expected (format, content...)
The text was updated successfully, but these errors were encountered: