http://time.is/

http://www.globalhandwashingday.org/

kek

>>57087782
They can't predict network latency so their time estimates cannot ever be correct.

I prefer time.gov

>>57087818

Please tell me this is a joke.

>>57087782
>Your time is exact!The difference from Time.is was +0.004 seconds (±0.076 seconds).

I'm 0.8 seconds ahead.

>>57087922
pls mr. futureman, who wins the election

Yes because I use GNU/Linux with ntpd.

>>57087869
You think handwashing is a fucking joke, m8?

Your time is exact!The difference from Time.is was +0.003 seconds (±0.060 seconds).

>>57087833
Your latency is displayed in brackets. Agree its a pretty useless measure.

>>57087833
>They can't predict network latency
Yes they can. Not perfectly accurately, hence the error bars, but they can certainly predict it within a very reasonable range

>>57088066
Yes. I just remove my hands after every use and attach new ones. How much of a poorfag are you?

>>57088183
I recompile my hands from the source each time it gets used.

File: 1476560576647.png (80KB, 500x421px) Image search: [Google]

80KB, 500x421px

>>57088202
I have no hands.

File: 1439835318214.jpg (11KB, 300x250px) Image search: [Google]

11KB, 300x250px

>>57087782
>tfw 5 seconds ahead

>>57087782
>Your time is exact!
>The difference from Time.is was -0.057 seconds (±0.073 seconds).

>>57087782
>Is your computer's clock accurate?
I run NTP

% ntpq -p 
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+y.ns.gin.ntt.ne 249.224.99.213   2 u   26 1024  377   15.409    6.136   3.619
+c-98-213-66-22. 199.102.46.72    2 u  830 1024  377   83.455    5.078  19.003
*clock.xmission. .XMIS.           1 u  345 1024  377   36.163    8.986   6.192
+triangle.kansas 128.252.19.1     2 u  155 1024  367  112.093    8.446   2.834

>trying to measure clock accuracy via HTTP/JavaScript
>dozens of milliseconds off

It says my clock is 14.5 seconds ahead. How do I fix that?

>>57090472
Install gentoo.

>>57090526
I'm already on Slackware.

>>57087782
>Your time is exact!
>The difference from Time.is was +0.036 seconds (±0.022 seconds)
Windows 10 master race.

>>57090572
Install systemd.

>>57090572
You need systemd-timesyncd

>>57090639
How can it be exact if 0 isn't even within the margin of error?

>>57090769
>>57090781
I'm not installing that.

>>57090808
Enjoy your shitty inferior system with a broken clock then

>>57090824
How is systemd superior when it has so many fucking security holes? I'm sure there is some kind of a time syncd package on slackbuilds anyways. I'll check it later.

>>57090872
>so many fucking security holes
systemd has far fewer security holes than the components it replaces, and a much better system of ensuring that a compromised component doesn't compromise anything else.

>>57090903
>sysemd is more secure than Slackware
Do you even know what Slackware is?

>>57090923
And of course slackbuilds and a nice slackbuild script for chrony so I'll stick to my nice and secure and stable Slackware install.

1.2 seconds ahead

>>57090942
>chrony
>specifically written to be suitable for computers with dial-up connections
You have fun with that

>>57091284
How would this effect anything? Do you not understand what protocols are?

>>57091284
http://chrony.tuxfamily.org/
>It is designed to perform well in a wide range of conditions, including intermittent network connections, heavily congested networks, changing temperatures (ordinary computer clocks are sensitive to temperature), and systems that do not run continuosly, or run on a virtual machine.

I see no issue.

>>57091366
You're using an ancient piece of software developed for an environment you aren't in.
Security holes are still being found in that program in 2016, despite it being stable for decades.
You're picking a garbage piece of software because of your own unreasonable biases against better alternatives, and then convincing yourself it's somehow more secure

>>57091419
>slackware is unsecure
Okay, pal. It's linux, there are plenty of other ntp packages on slackbuild. You have no idea what you are talking about.

>>57091419
>You're using an ancient piece of software
It's still maintained you dumbshit.

File: snapshot_21.30_[2016.07.29_03.03.46].png (3MB, 1920x1080px) Image search: [Google]

3MB, 1920x1080px

>>57087782
Your clock is 2.5 seconds behind

Your clock is 59 minutes and 55.6 seconds ahead.
Accuracy of synchronization was ±0.074 seconds.

>>57089925
M-masaka!

>>57091547
You should consider setting your timezone correctly.

>Your clock is 17 hours, 18 minutes and 22.0 seconds behind

System interrupts is rather high.... Wiping the drive with a fresh OS install didn't work.... likely the CMOS battery or some shit. Stupid shit.

>>57093151
What the hell, man?

sudo apt-get install rdate && sudo rdate -s time-a.nist.gov && sudo hwclock --systohc

Why even check with Time.is?

>>57087782
Your clock is 2.4 seconds behind.
Big fycking deal.

>>57087782
+0,7 seconds

>>57093151
Stop living in the past

Switched NTP server from time.windows.com to time.nist.gov. Went from 17.7 seconds behind to exact time. :)

>>57093215
>sudo rdate -s time-a.nist.gov && sudo hwclock --systohc
You're adding a few milliseconds latency there.

>>57087782
>Your time is exact!
>The difference from Time.is was -0.031 seconds (±0.070 seconds).
>>57093609
I used to use the default Windows one too and was off by like 30 seconds. Ever since switching to time1.google.com it's been fine for me.

2.5 seconds ahead, I sync with time.nist.gov.

>>57093672
After syncing now.
Your time is exact!The difference from Time.is was +0.000 seconds (±0.018 seconds).

>Your clock is 1 minute and 36.7 seconds ahead.
My care is 0.

>>57087782
Your time is exact!
The difference from Time.is was -0.045 seconds (±0.062 seconds).

FUK WIT ME

>>57089932
really triggers my autism senpai

File: fakyar.jpg (34KB, 704x528px) Image search: [Google]

34KB, 704x528px

>>57087782
>go to Time.is
>see this: "Your time is exact!"
>mfw

>>57087833

No measurements can ever be correct. It is possible however to estimate the error range and thus use said measurement productively.

Please contain your autism next time

Your time is exact!
The difference from Time.is was -0.029 seconds (±0.059 seconds).

Of course it is, I'm using NTP Pool on my domain controller.