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
It would be nice to see how many badges are still in use. One way to do such a thing is adding the MAC address as an optional parameter to API requests.
Note that the badges will only do this after the user of the badge accepts the opt-in. Most badges will still contact hatchery without identifying information.
For the badges that do provide this info: the badge will add ?deviceemac=112233445566&devicetype=mch2022 to the end of all of it's API calls, with the 112233445566 part of course being unique per badge, it's probably going to be the MAC address. These parameters should not be used for any function except logging usage.
The text was updated successfully, but these errors were encountered:
It would be nice to see how many badges are still in use. One way to do such a thing is adding the MAC address as an optional parameter to API requests.
Note that the badges will only do this after the user of the badge accepts the opt-in. Most badges will still contact hatchery without identifying information.
For the badges that do provide this info: the badge will add ?deviceemac=112233445566&devicetype=mch2022 to the end of all of it's API calls, with the 112233445566 part of course being unique per badge, it's probably going to be the MAC address. These parameters should not be used for any function except logging usage.
The text was updated successfully, but these errors were encountered: