Last Comment Wins just ended and I have a new idea. Rules are simple again:
Be the last comment that gets a timestamp with .000Z and you win 10k sats + any zaps on this post!
So this means your reply needs to be inserted into the database at exactly the start of a second.
On desktop, you can check your timestamp after you replied by hovering over the relative time with your cursor like this:
The timestamp is not viewable on mobile yet unfortunately.

I consider this to be harder so I raised the bounty to 10k. I actually think no one will be able to achieve this within 3 days and after that, surely everyone will have given up ...
10,000 sats bounty
@MiddleWay correctly pointed out that I mentioned last comment but I wanted to write first comment. So the rules are actually:
Be the last first comment that gets a timestamp with .000Z and you win 10k sats + any zaps on this post!
reply
Thanks for the clarification.
What if one of your replies is the first, though?
reply
21 sats \ 4 replies \ @ek OP 31 May
Then I'll ignore it
reply
Lame.
You should have put in some fine print that we all have to zap you 10k if you're first.
Btw, do you know how to do this, or is it just going to be random?
reply
21 sats \ 2 replies \ @ek OP 31 May
Btw, do you know how to do this, or is it just going to be random?
One could collect measurements of the time you hit reply vs the timestamp that shows up to find out how early you need to be but there is jitter, clock skew and drift so I think it would still be mostly random.
reply
That’s what I figured from MiddleWay’s comment.
Still, someone should be able to greatly improve their odds compared to my 1/1,000 if they put some thought into it.
reply
21 sats \ 0 replies \ @ek OP 31 May
Being off by 1ms is going to hurt
Fortunately it's just 10k sats... for now...
reply
This is futile. I made a macro in AHK to click a mouse button at a given ms, but the delay to the database still seems random. Besides, the rules are clear that there will be no winner, because last .000Z has no time limit.
reply
0 sats \ 1 reply \ @ek OP 30 May
Oh, sorry, I wanted to say first comment that gets a timestamp with .000Z hence the title. Will create a pinned comment to mention this
reply
I still haven't figured out how to use the timestamp function
reply
Thanks for injecting fun into the mundanity of the sub!
reply
gab eth ni siht tog I
reply
siht*
reply
sknaht
reply
54 sats \ 1 reply \ @ek OP 30 May
Are you guys even trying or are you just randomly hitting reply? lol
reply
ylper
reply
That's fun
reply
Is that sarcasm?
reply
No, I made that comment really early, when this seemed like it might be fun.
reply
Fourth try!
reply
0 sats \ 0 replies \ @NRS 1 Jul
I like that
reply
lol
reply
shazam!
reply
Still trying!
reply
Let´s go for another try!
reply
884Z
reply
Third try!
reply
it is like a bingo, do say 'bingo'?
reply
reply
This is my second try ! Will see!!
reply
You know, I just had a random thought. I love SN, what about you guys?
reply
is this paid out yet?
reply
No, it would say paid like here then
reply
ONE HUNDRED Z
reply
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
reply
do we have the winner then! Or can anyone else do better?
reply
Only 0ms counts
Also, 8ms was and still is the best so far
reply
so will the nearest to 000Z win then?
reply
no
there is no time limit on this bounty
0 sats \ 1 reply \ @ek OP 31 May
37ms!
reply
reply
reply
0 sats \ 1 reply \ @ek OP 30 May
Not bad attempts, both were within 100ms
reply
I didn't meme it enough :(
reply
reply
I noted the time to enter in the previous bounty. I even put a reminder with alarm set in my mobile. But, I forgot and that's what I was thinking about 'how interesting was that post' for someone who is a lazy lad.
reply
Gosh yesterday I forgot.. let's see today.. 😅
reply
why not set the bounty at 10,000 BTC because it has no time limit, so you don't ever expect to pay it?
reply
What's your life expectancy? Because the last .000Z comment may arrive very very far in the future....
reply
That's impossible!
reply
Ha ha that’s funny!
reply
I think this is the closest so far!
.992
reply
Almost!!
reply
reply
First attempt
reply
Second attempt
reply
Third
reply
reply
reply
reply
reply
just arrived from the saloon to see this
reply
first comment? How to play?
reply
did I win?
reply
0 sats \ 1 reply \ @ek OP 30 May
lol, I honestly got scared for a second that the second comment already proved me wrong because I saw +00:00 at the end. But no, you didn't win. Your reply is off by 311 milliseconds.
reply
how to see the timestamp?
reply
what? This is going to be impossible... Unless someone writes a program for it..
reply
I imagine even with a program it's going to be hard due to network latency etc.
But I'm going to write a script to verify timestamps!
I understand it’s still running. Let’s see this time
What's the probability for a hit? 1/60? How does it compare with... let's say, dying of covid?
If I edit and save a second time, do I get another chance of winning?
Edit: Oh I now realise this takes ms into account, making it even more unlikely... 1/60000?
5 sats \ 0 replies \ @pk 30 May
deleted by author
reply
3 sats \ 0 replies \ @pk 3 Jun
deleted by author
reply
deleted by author
reply
deleted by author
reply
Yes, closest is still 8ms: #556470
deleted by author
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply
no bad! you were near with 47ms
reply
deleted by author
reply
deleted by author
reply
deleted by author
reply