It only posts as fast as possible after something happens: "Nathan's post appears." You are just changing the initial condition from "Nathan's post appears" to "post #42 appears." I don't think there are so many people posting at the end of the first minute that it would consistently fail.
However, I have no idea if anyone is actually using a bot, this is all hypothetical.
It really depends on how in-demand the items in a particular sale are.
I can tell you that I’ve hit post 40-41 more than once while TRYING to post as fast as possible.
That’s also why I don’t think your theory above can work.
If the bot waits until post 40 to post, there is STILL going to be a fractional delay from the bot submitting the post, before it reaches the bf server. By the time the bot ‘sees’ post #40, there are likely 3-5 posts
already in queue ahead of it (and the randomness is that even the bot won’t know if there’s one post or 5 posts, because that’s dependent on exactly how many people hit Submit Post within that small timeframe (because the posts have already been sent, they just haven’t been registered in the server queue YET, but by the time post 40 registers, there are already other posts in queue), AND the delays from their PC/phone to the bf server, so a bot can’t even target “Submit post 4 posts before XX”).
***At least the new server distinguishes between fractions of seconds/milliseconds, unlike the old server that only counted the second a post registered, leading to Nate’s sales having 3 people all showing as Post #2, four people with post #3, four people with post # 4 etc.. I remember those days, going “Woohoo! I’m post #19. Wait… what the heck… I’m actually post #45”
, and that’s why it negates using bots.
All the bot can do, is post faster than a human can. By Nathan specifically NOT picking post #2 as a winner, it takes that advantage away. Beyond the first reply, I don’t think there’s any real way to hit a specific post number, even if the bot is targeting it.
