-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gsheets Backend and Lack of Approval Process #27
Comments
A. There is no discernible latency issues when benchmark testing conducted. Additionally, with the readdition of serviceworkers, it will load instantly upon future visits. |
Not sure why you closed this issue when those problems still exist. The list still takes several seconds to load for me (performance is terrible on my phone once loaded as well) and I can still edit the gsheet without any approval. Please reopen this issue. |
The file 'sw.js' will help with the very minor latency issues you're
experiencing, but we removed it temporarily to avoid issues affecting
certain Android browsers. I'll re-open the latency issue, but it's really
not any slower than most any website. As for Sheets, the intention has
never been to leave it open for free reign. It will be open, but require
approval for additions. That is/has always been the plan. It's a matter of
turning a switch.
…On Wed, Jun 28, 2017 at 6:06 AM Travis ***@***.***> wrote:
Not sure why you closed this issue when those problems still exist.
The list still takes several seconds to load for me (performance is
terrible on my phone once loaded as well) and I can still edit the gsheet
without any approval.
Please reopen this issue.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABnnId4FlyebWh9shwdyng8vMMr3RIU6ks5sIiWxgaJpZM4OGnC->
.
|
Using gSheets as a backend will cause latency issues.
The lack of any verification or approval opens this app up to serious security issues.
The text was updated successfully, but these errors were encountered: