2 ms·
Just to be clear, it isn't that it's taking the top few listings and randomly marking as sold, but that the code is going out and retrieving what appear to be a
by joeax 9y ago
Just to be clear, it isn't that it's taking the top few listings and randomly marking as sold, but that the code is going out and retrieving what appear to be already sold listings (as stored in the urgencyMessageListings variable), and just injecting the top 2 from that array randomly in positions 1-5 in the main list (through a Array.splice() call).
While somewhat deceiving, it's not as bad as marking tickets that haven't sold as sold. Imagine if you were trying to sell your tix at the last minute, well that would be bad. (I've sold tix at the last minute before and that would scare me.)
- preinheimer 9y agoTo me the problem here is the transition: they appear available then are marked as sold. Had they appeared sold from the start, that would have been fine. But by transitioning them they've stated a timeline for their sale which is incorrect.