-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Log Google Analytics event for protocol on server URL change #2516
Comments
@opendatakit-bot claim |
Welcome to Open Data Kit, @nexusbr! We just sent you an invite to collaborate on this repository at https://github.com/opendatakit/collect/invitations. Please accept this invite in order to claim this issue and begin a fun and rewarding experience contributing to Open Data Kit! Here are some tips to get you off to a good start:
See you on the other side (that is, the pull request side)! |
Hello @nexusbr, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue? If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 5 days. If you've decided to work on something else, simply comment Thank you for your valuable contributions to Open Data Kit! |
ODK Central is designed to be secure out of the box. As options for supporting HTTP or not are being considered, it would be helpful to know what the ratio of HTTP to HTTPS servers used with Collect is.
Changes to the server URL go through
ServerPreferencesFragment.createChangeListener
. If the URL is valid, an analytics event should be logged with category "SetServer" and an action of either "HTTP" or "HTTPS" depending on the prefix of the URL (case insensitive).Additionally, we would like to know what servers are the same without compromising user privacy. To do this, we can log a hash of the full URL. See
WidgetFactory
for a similar example.The text was updated successfully, but these errors were encountered: