Dont get me started on the number of times Signal/formerly Skype opened up a dialog in-the-midst of me typing and me accidentally accepting a call because i happened to write 'space' at that moment in time
That depends a lot on many factors and thus I dont like generic statements like that which tend to be more focused on a specific database pattern. That said everyone should indeed be aware of the potential tradeoffs.
And of course we could come up with many ways to generate our own ids and make them unique, but we have the following requirements.
- It needs to be a string (because we allow composing them to 'derive' keys)
- A client must be able to create them (not just a server) without risk for collisions
- The time order of keys must not be guessable easily (as the id is often leaked via references which could 'betray' not just the existence of a document, but also its relative creation time wrt others).
- It should be easy to document how any client can safely generate document ids.
The lookup performance is not really such a big deal for us. Where it is we can do a projection into a more simple format where applicable.
It matters because it helps the "Elon Bad" storyline, that seems to be the connecting thread between all these "reports" whether about SpaceX or Tesla by some news outlets which dont even do the due diligence of putting the stories into any kind of perspective or try to find out if the implied premise of the headline is true or should even matter to the casual reader.
Would love to have a look at that show based on that description. Alas, as is the way in 2025, no streaming services here have it, looking for it on Amazon was not helpful either (and offered some embarrassing suggestions instead).
In that case it would be evil not to look further afield. I only trust large American media companies of course, so in this regard I would look to RDDT ( https://www.nyse.com/quote/XNYS:RDDT ) for guidance at this so-called "megathread":
reply