-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Mark user owned probes in API responses #541
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
In the dashboard, add a new section "Privacy" below "Account details" with a single on/off setting "Make my probes public" and description "If enabled, your probes will be automatically tagged by On the API, add the tag to all user's probes if the user has the setting enabled. |
We should now update the CLI and web. Not sure if Slack makes sense though |
If the user is authenticated when making a new measurement we should clearly mark the probes he owns in the response.
Probably a system tag? This way the user could query his own probes directly as well.
Once the API supports it we can add markers to all of our tools.
Context jsdelivr/globalping-cli#128
The text was updated successfully, but these errors were encountered: