5 ms·
This is known for a while and used to cause huge problems for our tracking: https://github.com/snowplow/snowplow-javascript-tracker/issues/499 https://github.co
by endymi0n 9y ago
This is known for a while and used to cause huge problems for our tracking: https://github.com/snowplow/snowplow-javascript-tracker/issues/499 https://github.com/snowplow/snowplow-javascript-tracker/issu...
- lotyrin 9y agoUnder the assumption that the same event fired from the same IP at the same time, with the same environment, etc. would be considered a duplicate in your system, I'd have designed this system to be idempotent-insert-only and use content-addressing instead of nonces for identity (event ID = suitably large hash of event data to avoid collision). If that assumption doesn't hold, then add your nonce to the event data (and thereby modify the hash).
- Shoothe 9y agohttps://developer.mozilla.org/en-US/docs/Web/API/RandomSource/getRandomValues https://developer.mozilla.org/en-US/docs/Web/API/RandomSourc... can be used to generate cryptographically strong random numbers. It's not as cheap as Math.random though.