New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
HetrixTools - Blacklist/Uptime Monitors Giveaway for your new Black Friday servers!
This discussion has been closed.
Comments
@Luke007 I still don't get it. Where do you check the timedifference? I just see a timestamp with only hours and minutes "HH:MM" for the post. Could you be more precise please?
@nullnothere hitting the bull's eye always
@cxg By checking the clock, I calculated how many seconds before the scheduled time, I should click the comment button
noble!
@nullnothere are you using bot? lol
I wish... it's a fair bit of luck (and of course totally dependent on how many others are participating at the same time, which one has no clue on until after the time has passed). Very tricky but challenging and interesting nevertheless.
I AM a bot
I think even using a bot is hard because the timing is not precise (or so I think anyways).
Maybe I am thinking to complicated. But when I click the comment button it instantly shows up. So the timedifference is close to 0s. 🤔
Thinking of making a comment bot
It likely in the low 10's-100s of milliseconds depending on how "far" you are from the nearest Cloudflare POP. This is why you need to click and do some tests before you can get a sense of click when to make it hit the server (and show up timestamped) at hh:00:00s.
Lots of folks here have been fine tuning their timing (which is going to vary by a lot when many people are also competing to post, which is what makes this particularly hard to get right by the rules of the contest).
This is what @Luke007 was "testing" with his latency posts.
If you read through some of the earlier posts in this thread, you'll find some good advise on how to get better at timing (etc.) by the venerable FAT32. You can go from there and do some tests to improve your post-accuracy times.
Hope this helps.
I must admit, @HBAndrei was really inventive on how he came up with this event. It is so crazy and so beautiful at the same time. One can't stop but appreciate it how bots are quite useless, while the simplicity and effectiveness of it all is mind-blowing.
i am bored,and i am/will trying to help the person who posted the latest comment in the next hour (the last comment in the next xx:00)
Though bot can't assure your victory, it helps if you have slow reflex.
Thanks @nullnothere, I believe I understand the concept. I just don't see the posts timestamped that accurately. Switch from mobile to desktop view but the timestamp for the post is only with minutes accuracy. So the idea is to post close to a minute boundary and then check if it was timestamped within the same minute or after that. Or do I just miss a setting that enables timestamps with seconds?
You need to view the html page source to get the seconds details. Not ideal. But that's how I try to find.
View source and you'll see the timestamps to the nearest second. The challenge is to figure out when to post so that the server records it in the NEXT second. So you post at wall clock hh:59:59.850 (i.e. 850 millisecs) and the server records it as hh+1:00:00 but maybe if you post at hh:59:59.600 (600 millisecs) the server records as hh:59:59. This will give you a clue to your latency to server and when to time the post so that it "pushes" to the next second on the server.
Of course this will vary with load and number of comments coming in at the same time - hence the variance and difficulty to "botify" this whole game.
Thanks @plumberg and @nullnothere for clarifying.
Now get ready 😁
c2b5e35b55bd3b60fbd8bff2e2e8e7fa for @Kebab
d826e991e67f6f1edd578ce42a5aebb2
442a551a0d76083cb823a474f7718ed7 for @cxg
11dd600aa051192dfb57d5425d13e963
442a551a0d76083cb823a474f7718ed7
a1f0d205d345ca311d9edaa042f41b85
870d391b349ecfe41fa431d587662d79
9febe1ddb63aaf22b710e75aed38a80d
you posted the wrong public key. You should use this key: d826e991e67f6f1edd578ce42a5aebb2
@gbzret4d - you're all set for now
@plumberg said:
Thanks for helping me out 😀
@gbzret4d Will try yours in the next round
Don't - he's already won. Use it for someone else.
@gbzret4d - looks like you missed catching up on your tags.