11 minutes, you probably counted 10 and it was 11 by the time you posted@antohan it should be 42 and not 43?
Even now you can see 10 mins gap between tuppet's post and my eranio one.11 minutes, you probably counted 10 and it was 11 by the time you posted
@Enigma_87 can you delete or repost that? I fixed a few things in mine including your pick, Skuhravy and ID being done.
Sure, edited it with your latest post.11 minutes, you probably counted 10 and it was 11 by the time you posted
@Enigma_87 can you delete or repost that? I fixed a few things in mine including your pick, Skuhravy and ID being done.
Good pick. He was a handy player and also pretty good on some of the early PES games.
Cheers mate. We had him down as a possible option both centrally and on the left. Had a great season with Udine which won him the call for EURO 2000.Good pick. He was a handy player and also pretty good on some of the early PES games.
I noticed that. I think the timestamp is just based on fixed minutes. So if someone posts at 11:30:58 and the next posts at 11:31:08 it will eventually show up as a one minute difference even though its only 10 seconds.Even now you can see 10 mins gap between tuppet's post and my eranio one.
edit : just changed to 11 for me.... bizarre
Nice pick. Was on my radar and a good one to watch on youtube for the drama
That seems reasonable for future drafts. Good call.I noticed that. I think the timestamp is just based on fixed minutes. So if someone posts at 11:30:58 and the next posts at 11:31:08 it will eventually show up as a one minute difference even though its only 10 seconds.
Actually in fairness for the future:
when we consider world wide latency and the server location, no one should get under 2 mins for their pick IMO. The lowest time anyone should get in fairness is 2 mins because depending on where you are in the world it might be literally impossible for the server to log your post at "0 mins" even if you literally pressed Reply <5 seconds after you saw your tag appear.
I remember that happened to me last draft. I had a post prepared and posted it literally the second my tag appeared but eventually the system logged it at ~2 mins later.
@2mufc0
@Physiocrat
I made a point of correcting it because I corrected others, not that it will make any difference bar maybe against two others.1 min fecks sake
Add 1 in mine and reduce 1 in his
But then, that difference in latency will always come into play whether trying to get 0 or 52.I noticed that. I think the timestamp is just based on fixed minutes. So if someone posts at 11:30:58 and the next posts at 11:31:08 it will eventually show up as a one minute difference even though its only 10 seconds.
Actually in fairness for the future:
when we consider world wide latency and the server location, no one should get under 2 mins for their pick IMO. The lowest time anyone should get in fairness is 2 mins because depending on where you are in the world it might be literally impossible for the server to log your post at "0 mins" even if you literally pressed Reply <5 seconds after you saw your tag appear.
I remember that happened to me last draft. I had a post prepared and posted it literally the second my tag appeared but eventually the system logged it at ~2 mins later.
@2mufc0
@Physiocrat
Can never be absolutely perfect of course but its quite obvious at the 0-2 end so simply make 2 the minimum and its the most fair at the low end.But then, that difference in latency will always come into play whether trying to get 0 or 52.
Potatoe potato, most likely.