*sigh*
Here we go again.
*grabs more btc*
Topic: [ANN] SpreadCoin | Decentralize Everything (decentralized blockexplorer coming) - page 309. (Read 790417 times)
May 11, 2015, 04:14:58 PM
May 11, 2015, 11:38:18 AM
I was a huge advocate of Protonmail but since they still havent Opensourced the project I have lost much love for the project. I now use https://tutanota.com/ Free encrypted mail, with Andorid and IOS apps as well, O yea its opensourced also
May 11, 2015, 10:33:48 AM
May 11, 2015, 09:56:46 AM
How's the development coming along, georgem? Busy weekend?
Yes, currently I am diving deep into Qt functions.
I am improving the looks and functionality of the wallet.
Well done, thank you.
May 11, 2015, 09:54:01 AM
How's the development coming along, georgem? Busy weekend?
Yes, currently I am diving deep into Qt functions.
I am improving the looks and functionality of the wallet.
May 11, 2015, 09:53:13 AM
Small Mistake, when you said you made the Epoch Time from int32 to int64, you just delayed the death, so instead of 2034, it will be 4068
Otherwise, you just did a delay, nothing more
Otherwise, you just did a delay, nothing more
for every bit you add, you double the previous limit... your math kung fu is off a bit :-)
May 11, 2015, 09:48:22 AM
It's not FUD, I am just telling that the work patched is wrong, the word delayed is correct
Yes, so is every hashing or crypto algorithm, by providing just a large enough "hurdle" (delaying & keeping the hacker busy for a few billion years.
)... Those algorithms are not perfect. They are not built for eternity.
The goal in cryptography is to just always move the problems far far into the future.
So it's ALL about delay.
And billions of years is so long of a delay, it could be considered permanent for now.
My macbook battery would never last that long.
May 11, 2015, 09:21:12 AM
It's not FUD, I am just telling that the work patched is wrong, the word delayed is correct
May 11, 2015, 09:48:02 AM
How's the development coming along, georgem? Busy weekend?
May 11, 2015, 09:43:46 AM
It's not FUD, I am just telling that the work patched is wrong, the word delayed is correct
Yes, so is every hashing or crypto algorithm, by providing just a large enough "hurdle" (delaying & keeping the hacker busy for a few billion years.
)... Those algorithms are not perfect. They are not built for eternity.
The goal in cryptography is to just always move the problems far far into the future.
So it's ALL about delay.
And billions of years is so long of a delay, it could be considered permanent for now.
May 11, 2015, 08:35:45 AM
Small Mistake, when you said you made the Epoch Time from int32 to int64, you just delayed the death, so instead of 2034, it will be 4068
Otherwise, you just did a delay, nothing more
Otherwise, you just did a delay, nothing more
May 11, 2015, 09:41:37 AM
It's not FUD, I am just telling that the work patched is wrong, the word delayed is correct
Yes, so is every hashing or crypto algorithm, by providing just a large enough "hurdle" (delaying & keeping the attacker busy for a few billion years.
)... Those algorithms are not perfect. They are not built for eternity.
The goal in cryptography is to just always move the problems far far into the future.
So it's ALL about delay.
May 11, 2015, 09:30:16 AM
Small Mistake, when you said you made the Epoch Time from int32 to int64, you just delayed the death, so instead of 2034, it will be 4068
Moving from int32 to int64 doesn't just double the value range,
in fact it multiplies it by 2^32, so it then becomes about 4.2 billion times larger.
Insanely larger:
Approximately 292 billion years from now, at 15:30:08 on Sunday, 4 December 292,277,026,596"
so instead of 2034, it will be 4068
Also, you have to start the counting from the year 1970, not from the birth of jesus christ!
Otherwise, you just did a delay, nothing more
Infinity only exists as a mathematical concept, everything else has its inevitable demise "just delayed": http://en.wikipedia.org/wiki/Heat_death_of_the_universe
May 11, 2015, 09:06:10 AM
Small Mistake, when you said you made the Epoch Time from int32 to int64, you just delayed the death, so instead of 2034, it will be 4068
Otherwise, you just did a delay, nothing more
Otherwise, you just did a delay, nothing more
Besides, it's 2038, with an extension to 2106 with a certain flag.
"Most operating systems designed to run on 64-bit hardware already use signed 64-bit time_t integers. Using a signed 64-bit value introduces a new wraparound date that is over twenty times greater than the estimated age of the universe: approximately 292 billion years from now, at 15:30:08 on Sunday, 4 December 292,277,026,596"
http://en.wikipedia.org/wiki/Year_2038_problem
Why try to FUD and point out the "already stated on the OP"? Will SPR loop around negatively in 2038 or 2106? No. So the new problem is called the "year 292,277,026,596" problem. Even if it's only 2000 years, be very worried about that.
May 11, 2015, 08:02:46 AM
please give me a peer address SPR.
i m not syncing...
i m not syncing...
Put this in your conf file:
Code:
addnode=5.35.253.206
addnode=94.23.23.194
addnode=52.17.253.8
addnode=37.59.18.108
addnode=94.23.23.194
addnode=52.17.253.8
addnode=37.59.18.108
I am currently working on an improved wallet (new features + better connectivity etc),
when it's ready you won't need to add nodes like that anymore.
Stay tuned.
May 11, 2015, 07:56:06 AM
please give me a peer address SPR.
i m not syncing...
i m not syncing...
Check thread around 4-6 May
https://bitcointalksearch.org/topic/m.11282187
May 11, 2015, 06:52:54 AM
please give me a peer address SPR.
i m not syncing...
i m not syncing...
May 10, 2015, 07:37:59 PM
Front page on trex should spark some interest into this great project.....Im sure its caused some new faces to at least look into Spread
May 10, 2015, 04:22:23 PM
sick dump, like it
May 10, 2015, 07:36:14 PM
E1ghtspace should be able to start working on the VPS video next week 
Jump to: