00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:02:48  * dignifiedquirequit (Quit: dignifiedquire)
00:04:52  * bradleymeckquit (Quit: bradleymeck)
00:09:11  * rendarquit (Quit: Leaving)
00:23:28  * dap_1quit (Quit: Leaving.)
00:28:04  * s3shs_quit (Quit: Computer has gone to sleep.)
00:43:22  * jasnelljoined
00:52:39  * Fishrock123quit (Quit: Leaving...)
00:55:43  * jasnellquit (Remote host closed the connection)
01:07:12  * jgiquit (Quit: jgi)
01:28:08  * s3shsjoined
01:30:57  * kevinsimperquit (Remote host closed the connection)
01:34:34  * brsonquit (Quit: leaving)
01:37:18  * WalrusPony1joined
01:37:33  * WalrusPonyquit (Ping timeout: 252 seconds)
01:48:00  * dap_joined
01:58:42  * dap_quit (Quit: Leaving.)
02:00:47  * jasnelljoined
02:06:16  * dap_joined
02:10:43  * dap_quit (Client Quit)
02:35:10  * tunniclmquit (Ping timeout: 260 seconds)
03:01:33  * ncthom91joined
03:08:39  * ncthom91quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
03:09:13  * jasnellquit (Remote host closed the connection)
03:19:51  * WalrusPonyjoined
03:20:21  * WalrusPony1quit (Ping timeout: 250 seconds)
04:41:42  * happy-dudequit (Quit: Connection closed for inactivity)
04:44:17  * toothrotquit (Ping timeout: 276 seconds)
04:46:05  * jgijoined
05:05:27  * s3shsquit (Remote host closed the connection)
05:06:09  * s3shsjoined
05:15:18  * WalrusPony1joined
05:16:32  * WalrusPony2joined
05:17:56  * WalrusPonyquit (Ping timeout: 272 seconds)
05:20:03  * WalrusPony1quit (Ping timeout: 255 seconds)
05:29:45  * s3shs_joined
05:30:03  * WalrusPonyjoined
05:32:06  * WalrusPony2quit (Ping timeout: 265 seconds)
05:32:35  * s3shsquit (Ping timeout: 264 seconds)
06:08:15  * jgiquit (Quit: jgi)
06:08:56  * jgijoined
06:25:59  * jgiquit (Quit: jgi)
06:44:24  * Damn3dquit (Ping timeout: 246 seconds)
06:45:12  * seishunjoined
06:52:40  * Damn3djoined
06:52:40  * Damn3dquit (Changing host)
06:52:40  * Damn3djoined
07:53:19  * WalrusPony1joined
07:57:06  * WalrusPonyquit (Ping timeout: 265 seconds)
08:02:59  * seishunquit (Ping timeout: 240 seconds)
08:05:35  * AndreasMadsenjoined
08:15:45  * kevinsimperjoined
08:22:32  * dignifiedquirejoined
08:27:06  * SergeiRNDjoined
08:32:16  * rendarjoined
08:49:36  * AndreasM_joined
08:52:14  * AndreasMadsenquit (Ping timeout: 260 seconds)
08:56:36  * rmgquit (Remote host closed the connection)
08:57:13  * rmgjoined
09:01:20  * rmgquit (Ping timeout: 244 seconds)
09:22:23  * SergeiRNDquit (Quit: Leaving.)
09:33:03  * AndreasM_quit (Remote host closed the connection)
10:02:42  * AndreasMadsenjoined
10:19:30  * rvagg_joined
11:24:27  * bnoordhuisjoined
12:11:13  * kevinsimperquit (Remote host closed the connection)
12:33:11  * WakiMiko_quit (Max SendQ exceeded)
12:34:12  * WakiMiko_joined
12:36:06  * kkaefer_quit (Ping timeout: 255 seconds)
12:37:22  * kkaeferjoined
12:38:10  * WakiMiko_quit (Max SendQ exceeded)
12:40:35  * WakiMiko_joined
12:40:38  * bnoordhuisquit (Ping timeout: 272 seconds)
12:52:45  * bradleymeckjoined
13:04:26  * bradleymeckquit (Quit: bradleymeck)
13:09:19  * kevinsimperjoined
13:13:30  * kevinsimperquit (Ping timeout: 240 seconds)
13:14:11  * bradleymeckjoined
13:36:20  * toothrotjoined
13:50:15  * bnoordhuisjoined
13:59:10  * s3shs_quit (Ping timeout: 240 seconds)
14:01:37  * happy-dudejoined
14:11:51  * toothrotquit (Ping timeout: 244 seconds)
14:17:34  * kevinsimperjoined
14:20:47  * dignifiedquirequit (Quit: dignifiedquire)
14:22:46  * kevinsimperquit (Ping timeout: 240 seconds)
14:50:36  * s3shsjoined
14:56:02  * SergeiRNDjoined
14:58:43  * s3shsquit (Remote host closed the connection)
14:59:19  * s3shsjoined
15:00:01  * ncthom91joined
15:05:57  * alexforsterjoined
15:17:36  * dignifiedquirejoined
15:19:21  * mmickoquit (Remote host closed the connection)
15:44:32  * jasnelljoined
15:47:15  * rmgjoined
15:48:37  * AndreasMadsenquit (Remote host closed the connection)
15:51:45  * rmgquit (Ping timeout: 250 seconds)
15:59:00  * avalanche123joined
16:11:35  * bnoordhuisquit (Ping timeout: 240 seconds)
16:14:12  * seishunjoined
16:24:36  * jhamhaderjoined
16:27:48  * avalanche123quit (Remote host closed the connection)
16:30:43  * avalanch_joined
16:35:42  * tuxboyjoined
16:40:25  <tuxboy>Hi. I would just like to know that when using uv_hrtime(void), then is the arbritary time in the past always same even if change to another computer (I need to know as I would like to create user ID's on a NodeJS server based on it). Thanks.
16:47:41  * zju1joined
16:47:50  * zju4joined
16:49:25  * AndreasMadsenjoined
16:49:59  * zju3quit (Ping timeout: 260 seconds)
16:50:08  * zjuquit (Ping timeout: 250 seconds)
16:50:24  * avalanch_quit (Remote host closed the connection)
16:54:05  * AndreasMadsenquit (Ping timeout: 244 seconds)
16:56:31  <alexforster>tuxboy: that's a very hard problem that you probably aren't going to be able to solve with just uv_hrtime – check out https://blog.twitter.com/2010/announcing-snowflake and other unique ID generators
17:02:51  * jgijoined
17:03:34  <tuxboy>Thanks for your reply. So uv_hrtime() is not returning nanoseconds since January 1, 1970 (or some other constant date)? I need the time nanoseconds so that I will not have two or more users with the same ID!
17:18:10  * bnoordhuisjoined
17:20:00  * rmgjoined
17:22:10  * davijoined
17:22:10  * daviquit (Changing host)
17:22:10  * davijoined
17:22:59  * bnoordhuisquit (Ping timeout: 264 seconds)
17:23:46  * jhamhaderquit (Quit: leaving)
17:32:50  * bnoordhuisjoined
17:34:21  * bradleymeckquit (Quit: bradleymeck)
17:35:37  * savardcpart
17:45:35  <alexforster>tuxboy: it is, but there's no way to sync two machines' clocks up to nanosecond accuracy. NTP can only do a few hundred microseconds IIRC. trust me, don't reinvent this wheel, it's the problem that that takes PHDs to solve.
17:46:36  <alexforster>*the kind of
17:53:38  * kevinsimperjoined
17:55:52  <bret>whats the accuracy of the sync outputs on benchtop equipment like signal generators and oscilloscopes?
17:56:45  * daviquit (Ping timeout: 246 seconds)
17:57:00  <tuxboy>@alexforster: Thanks. But I'm thinking that if I combine uv_hrtime() with a UUID then it will be unique enough. So is the arbritary time that uv_hrtime() is based on a time in history and based on the clock time?
17:58:09  <alexforster>UUIDv4 is enough, actually
17:58:10  * kevinsimperquit (Ping timeout: 250 seconds)
17:58:51  <alexforster>UUID = universally unique identifier, when generated with a good RNG (as UUIDv4 specifies), you will have a statistically unique ID for everyone without any coordination between machines
17:59:03  <alexforster>so if UUID's are alright, then your problem is already solved – just use a UUID generator
18:00:20  <tuxboy>But there is still a risk that I could two identical UUID's (I know the risk is small, but it still makes me worry)!
18:01:38  <tuxboy>Anyway, do you know how the abritary time in uv_hrtime() is defined?
18:06:02  * ncthom91quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:06:59  * romankljoined
18:07:45  * romanklquit (Max SendQ exceeded)
18:08:11  * brsonjoined
18:08:21  * jgiquit (Quit: jgi)
18:08:29  * romankljoined
18:13:22  * SergeiRNDquit (Quit: Leaving.)
18:15:46  * dignifiedquirequit (Quit: dignifiedquire)
18:16:12  * dignifiedquirejoined
18:17:45  * jgijoined
18:18:43  * jhamhaderjoined
18:21:29  * davijoined
18:21:29  * daviquit (Changing host)
18:21:29  * davijoined
18:45:55  * jgiquit (Quit: jgi)
18:48:11  * avalanche123joined
18:54:00  <Ralith>tuxboy: there is rather more risk of a rogue planetoid spontaneously colliding with earth
18:54:32  <Ralith>bodging together some ill-conceived custom thing is only going to make things worse, not better.
18:54:37  <alexforster>http://stackoverflow.com/questions/1155008/how-unique-is-uuid pretty good rundown
19:06:38  * AndreasMadsenjoined
19:12:40  * AndreasMadsenquit (Ping timeout: 272 seconds)
19:13:42  * jasnellquit (Remote host closed the connection)
19:13:53  <tuxboy>@Ralith: Actually then according to this blog (http://blog.tompawlak.org/generate-unique-identifier-nodejs-javascript) then the risk "Only after generating 1 billion UUIDs every second for the next 100 years, the probability of creating just one duplicate would be about 50%". That's a serious risk I would say!
19:14:50  <Ralith>you can say it all you like
19:15:27  <Ralith>it won't magically become true
19:15:38  <tuxboy>I would say it's enough to make me sleepless and paraniod!
19:16:43  <tuxboy>Anyway, do anyone know how the abritary number uv_hrtime() is based on is defined?
19:17:28  <Ralith>if that was true, you would not be able to step outside the door for fear of the various horrible things that could happen to you at any moment
19:18:11  <tuxboy>You are right, and that's how I got into computers :-)
19:27:53  * tunniclmjoined
19:28:33  * jasnelljoined
19:31:03  <tuxboy>I have just figured out the uv_hrtime() by calculating the seconds to hours and I get the uptime for the computer. I would be nice to something in nanoseconds since some date!
19:32:27  <tuxboy>I meant it would be nice to have something in nanoseconds since some date!
19:33:41  <tuxboy>But ofcourse I could add the uptime in nanoseconds to the time in milliseconds since 1970!
19:34:19  * ncthom91joined
19:34:28  <tuxboy>And then add an UUID ofcourse just to be sure!
19:36:37  <tuxboy>Then I would be able to sleep like a baby! Except that I probably will need more CPU power to do all that math!
19:38:43  <alexforster>oy
19:40:07  * AndreasMadsenjoined
19:41:42  * kevinsimperjoined
19:42:24  <tuxboy>If I also add the machine ID then it should be ok!
19:43:11  <tuxboy>I mean into a textstring ofcourse!
19:48:00  * alexforsterquit (Read error: Connection reset by peer)
19:48:05  * alexfors_joined
19:48:06  * kevinsimperquit (Ping timeout: 255 seconds)
19:56:24  <tuxboy>Oh I also need the add a core number, so "A" + milliseconds since 1970 + 'B' + uptime in nanoseconds since uptime + 'C' + UUID + 'D' + Machine ID + 'E' + cpu number + 'F' + core number
19:56:45  <tuxboy>That's should be secure enough!
20:04:28  * bradleymeckjoined
20:04:43  * jgijoined
20:09:55  <tuxboy>I'm thinking that if a calculate a SHA256 from that and convert into a number then I will the perfect ID number!
20:12:16  <nathan7>the hash will collide at least as often as a double-length UUID will
20:15:15  <alexfors_>a sha256 of all those things is effectively a UUID4
20:15:44  <alexfors_>your machine's random number generator uses all of those sources as entropy to give you random numbers, and then the UUID4 generator basically just gives you those random numbers
20:23:15  <Ralith>except your collision probability will have gone up a ton because you're doing a much worse job of massaging the data than the standard tools are
20:25:56  * avalanche123quit (Remote host closed the connection)
20:28:30  <tuxboy>According to the following then there should be no collisions: http://crypto.stackexchange.com/questions/3049/are-there-any-known-collisions-for-the-sha-2-family-of-hash-functions
20:30:54  <alexfors_>just as there are no known UUID collisions
20:31:01  * alexfors_changed nick to alexforster
20:31:07  * alexforsterquit (Quit: Textual IRC Client: www.textualapp.com)
20:31:25  * alexforsterjoined
20:33:50  <nathan7>tuxboy: SHA256 maps an infinite amount of bits into 256.
20:34:10  <nathan7>tuxboy: There are collisions. They're just unlikely.
20:41:08  * AndreasMadsenquit
20:41:34  * avalanche123joined
20:45:49  * mikeal_joined
20:46:01  <tuxboy>As far as I have heard then a SHA256 collision has never been found? But maybe I'm wrong!
20:46:17  <alexforster>that's because it's so statistically improbable that you don't have to worry about it
20:46:36  <tuxboy>You are fast!
20:46:39  <alexforster>same principle with UUID4 - you won't ever ever ever ever have a collision
20:47:31  <tuxboy>Ok, that's interesting. Thanks for your comments on this!
20:57:51  <tuxboy>Anyway, has there ever been made a mathematical proof that collisions can accour in SHA2?
20:58:01  <Ralith>it's trivially obvious
20:58:37  <tuxboy>So how is that obnious?
20:58:45  <Ralith>you cannot encode more than 256 bits of information-theoretic information into 256 bits
20:59:28  <Ralith>there are a finite number of SHA256 hashes, and there are an infinite number of possible inputs
20:59:56  <Ralith>therefore there must necessarily exist an infinite number of collisions for every hash value
21:00:17  <tuxboy>So there are no hashes that have collisions?
21:00:32  <tuxboy>I meant no collisions!
21:00:44  <alexforster>let's say you have 1024 things and 256 buckets - you can't fit all 1024 things into those 256 buckets, you can only fit a representative sample of them in
21:01:22  <tuxboy>Ok, that's logical!
21:01:37  <alexforster>same as if you have a 2873958172 byte file and you sha256 it, you can't fit all 2873958172 bytes into 256 bytes
21:02:00  <tuxboy>I haven't thought about that! But it's obvious that you are right.
21:03:04  <alexforster>but fancy math and probability says that it's effectively impossible to find two different files that sha256 into the same exact string of 256 bytes
21:03:16  * jgiquit (Quit: jgi)
21:03:38  <alexforster>*bits
21:04:24  <tuxboy>Thanks, that's interesting! So I will just leave out the SHA2 from my unique ID algorithm. Anyway, it's a bit scary that SHA2 is used for very serous security!
21:05:17  <tuxboy>I meant serious!
21:05:48  <tuxboy>So in theory Bitcoins can be hacked?
21:08:48  <alexforster>in theory? yes. in practice? no, since it's so hard (impossible) to find collisions
21:11:52  <tuxboy>Yeah or maybe untill someone finds a new way to think about it. They also said that for example the German WW2 Enigma machines could never be broken, and they said the same about RSA but quantum computers maybe will come to break them!
21:12:50  * ncthom91quit (Ping timeout: 240 seconds)
21:14:20  * ncthom91joined
21:16:25  <tuxboy>Anyway, I have other stuff to do now. But thanks for the conversation and info.
21:16:59  * Fishrock123joined
21:20:48  * daviquit (Ping timeout: 246 seconds)
21:32:02  * romanklquit (Quit: romankl)
21:43:06  * davijoined
21:43:06  * daviquit (Changing host)
21:43:06  * davijoined
21:45:38  * dap_joined
21:46:59  * ncthom91quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:49:51  * daviquit (Ping timeout: 246 seconds)
21:53:32  * jgijoined
21:54:14  * davijoined
22:04:12  * daviquit (Ping timeout: 246 seconds)
22:35:20  * jhamhaderquit (Quit: leaving)
22:43:35  * jasnellquit (Ping timeout: 240 seconds)
22:44:53  * toothrotjoined
22:47:07  * jasnelljoined
22:48:39  * seishunquit (Ping timeout: 240 seconds)
23:03:22  * bradleymeckquit (Quit: bradleymeck)
23:04:13  * tuxboypart
23:08:31  * jasnellquit (Remote host closed the connection)
23:11:32  * alexforsterquit (Quit: Textual IRC Client: www.textualapp.com)
23:31:49  * bradleymeckjoined
23:47:37  * bradleymeckquit (Quit: bradleymeck)
23:55:55  * rendarquit (Quit: Leaving)
23:56:15  * mikeal_quit (Quit: Connection closed for inactivity)