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
We have been using biri on our website to assign an ID to a user before they contact our API to determine if they have accessed our service before.
We send the ID generated by biri (if it is supported in the client) to the API and it records the first usage of that ID with the user-agent supplied in the header.
We have found the same ID used by different devices - once from Chrome on a Samsung mobile, and then again on Safari on an iPhone. From what I understand of biri, the ID is unique to the device and this should not happen.
Am I misunderstanding something?
The text was updated successfully, but these errors were encountered:
Hmm. This is a problem. The ID from WebRTC may not be as unique as expected due to its length. Maybe combining Biri with more standard approaches will help solve this.
We have been using biri on our website to assign an ID to a user before they contact our API to determine if they have accessed our service before.
We send the ID generated by biri (if it is supported in the client) to the API and it records the first usage of that ID with the user-agent supplied in the header.
We have found the same ID used by different devices - once from Chrome on a Samsung mobile, and then again on Safari on an iPhone. From what I understand of biri, the ID is unique to the device and this should not happen.
Am I misunderstanding something?
The text was updated successfully, but these errors were encountered: