3 ms·

Hi, During this peer review we went with sheets as a convenience. If we were to continue, we would move to an open source db (e.g. mysql or similar) in a cloud

Hi, During this peer review we went with sheets as a convenience. If we were to continue, we would move to an open source db (e.g. mysql or similar) in a cloud instance, secured via ssl as well as ip firewall. Thanks for the feedback.

northwestcoder 6y ago
I'm not sure what you meant by static or legit. You can learn all about these various technology choices at appsheet.com - we want hacker news feedback just like this, btw. Thanks again.
dangus 6y ago
Right it’s secure in terms of the way Google and Appsheet handle data, but we are just handing over all our data to you? What organization is responsible for handling this data? Where is the privacy policy and terms of use? What stops you from just grabbing all the contact info you got in your google sheet and running with it? In terms of the static site, what I mean is that you built all this out but couldn’t be bothered to put the information onto the actual public web. A shared google doc or a Facebook post is not really a public website. The fact that the 30 minutes wasn’t spent to make a website just sets off all kinds of red flags to me.
- northwestcoder 6y ago
  "we are just handing over all our data to you?" that is in fact the requirement as outlined by the State of Washington Governor's office (Jay Inslee), document here:https://www.governor.wa.gov/sites/default/files/COVID19Phase2PersonalServicesGuidance.pdf https://www.governor.wa.gov/sites/default/files/COVID19Phase... - we made no assumptions about "what org is responsible for handling this data" and instead designed a "data roach motel". It does remain to be seen who would access the data in the event that the state of washington needed to "contact a bunch of restaurant patrons informing them of exposure". This app does not attempt to solve for that, in fact. "but couldn’t be bothered to put the information onto the actual public web" - that's a fair comment. We are approaching this in stages. I also have a bunch of restaurant contacts as well as technology contacts, and wanted a kind of "soft release". And if we had gone ahead and created a "proper website" we would get dinged for having gone too far too quickly, before a proper peer review. This approach seems like a good compromise in terms of sharing info but not being "too proper, too soon". Again, I do appreciate this feedback. Keep it coming.

northwestcoder 6y ago

I'm not sure what you meant by static or legit. You can learn all about these various technology choices at appsheet.com - we want hacker news feedback just like this, btw. Thanks again.

dangus 6y ago

Right it’s secure in terms of the way Google and Appsheet handle data, but we are just handing over all our data to you? What organization is responsible for handling this data? Where is the privacy policy and terms of use? What stops you from just grabbing all the contact info you got in your google sheet and running with it? In terms of the static site, what I mean is that you built all this out but couldn’t be bothered to put the information onto the actual public web. A shared google doc or a Facebook post is not really a public website. The fact that the 30 minutes wasn’t spent to make a website just sets off all kinds of red flags to me.

northwestcoder 6y ago
"we are just handing over all our data to you?" that is in fact the requirement as outlined by the State of Washington Governor's office (Jay Inslee), document here:https://www.governor.wa.gov/sites/default/files/COVID19Phase2PersonalServicesGuidance.pdf https://www.governor.wa.gov/sites/default/files/COVID19Phase... - we made no assumptions about "what org is responsible for handling this data" and instead designed a "data roach motel". It does remain to be seen who would access the data in the event that the state of washington needed to "contact a bunch of restaurant patrons informing them of exposure". This app does not attempt to solve for that, in fact. "but couldn’t be bothered to put the information onto the actual public web" - that's a fair comment. We are approaching this in stages. I also have a bunch of restaurant contacts as well as technology contacts, and wanted a kind of "soft release". And if we had gone ahead and created a "proper website" we would get dinged for having gone too far too quickly, before a proper peer review. This approach seems like a good compromise in terms of sharing info but not being "too proper, too soon". Again, I do appreciate this feedback. Keep it coming.