How can Twitter-api generate unique, incremental IDs within an entity?
We're building a ticketing system for our customers (enterprise clients) and we're trying to come up with a way to have a sequential, unique ticket ID generation system that is also user-friendly. Unique ID generation is a fairly well-known problem…