14 ms·

Thanks and I don't mind at all! To be honest for the application I didn't want to expose a database serial (otherwise you'd know you're user #100, for example)

by abahlo 6y ago

Thanks and I don't mind at all! To be honest for the application I didn't want to expose a database serial (otherwise you'd know you're user #100, for example) or use UUIDs, so it's less about scale and more about obscuring ids. The library is well suited for huge scale scenarios nonetheless.

LaundroMat 6y ago
Why did you not want to use UUID's?
- abahlo 6y ago
  I already use UUIDs for various fields and didn't want the id to be confused with other fields. More of a clarity/style decision than technical.
  - tinus_hn 6y ago
    Unfortunately this means you get to make the same mistake as originally made with UUID: the static machine ID is a privacy leak.
    - abahlo 6y ago
      Is it? Not sure private ips are so sensitive, esp. the lower parts.
      - tinus_hn 6y ago
        If it’s unique it’s a privacy leak. I’m not going to debate that, it’s common knowledge. UUID was changed in the 90s to be a hash of this instead and later to just be a completely random number because there are so many bits the likelihood of a single duplicate being generated before the sun has swollen enough to consume the earth is slim so you don’t actually need these schemes to provide a unique number.
- deleted 6y ago
  [deleted]