Fixed one more error in the mail server that caused connections to stay around on the mail server after KH clients dropped their connection. At this point, we haven't seen any more issues in the message communication between the server and KH, so a couple of us are meeting tomorrow with Bytemaster to discuss the design of the overlay network. This is common code that will be used by KH, BitSharesX, and other DACs as well.

Quote from: CrazyCriple on March 12, 2014, 11:58:12 AM

Quote from: dannotestein on March 11, 2014, 05:18:13 PM
We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)

Where can I find my public key in this client? I think I looked about everywhere :/

First, use the menu option "New Identity" to create a new identity. After that, select the menu option "Show Contacts" and click on your identity in the list to view the public key for that identity.

Quote from: dannotestein on March 11, 2014, 05:18:13 PM
We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)

Where can I find my public key in this client? I think I looked about everywhere :/

Quote from: dannotestein on March 11, 2014, 05:18:13 PM
We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)

I have two suggestions for linux version
1. rename the application to Keyhotee, because profile dir will change with different application name.
2. run strip -d Keyhotee before gzip it. The size of the file is too huge now.

We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)

We're planning to put out an alpha release tomorrow with crash reporting support, fixes for the duplicate mail issue, plus a couple other mail-server related fixes. The fixes to the mail server will require use of updated versions of Keyhotee, so we're releasing tomorrow so that we can release all three KH clients at once (Windows, Linux, and Mac OS).

Quote from: dannotestein on March 09, 2014, 02:03:47 AM
The crash reporter has been committed and we'll probably finish testing that tomorrow or Monday. My bug fix for duplicate messages didn't cover all the sources of duplicate messages, but I think I've found the remaining problem: insufficient granularity on time stamp of messages (stored as seconds rather than microseconds). Depending on what solution I go with, I may be able to get the fix in tomorrow. After that, we can move back to working on the mining/blockchain code again. Given that a lot of the remaining immediate work is related to the backend code, we've added a new network-experienced programmer to the team this week, previously it's mainly been me looking at those issues.

+5%
thanks for the update keep up the great work!

The crash reporter has been committed and we'll probably finish testing that tomorrow or Monday. My bug fix for duplicate messages didn't cover all the sources of duplicate messages, but I think I've found the remaining problem: insufficient granularity on time stamp of messages (stored as seconds rather than microseconds). Depending on what solution I go with, I may be able to get the fix in tomorrow. After that, we can move back to working on the mining/blockchain code again. Given that a lot of the remaining immediate work is related to the backend code, we've added a new network-experienced programmer to the team this week, previously it's mainly been me looking at those issues.

Yeah, I'm just waiting for it to become available. I'll opt for mail notifications or let people manually contact  each other in the meantime but of course that should be temporary.

Quote from: GodsCreation on March 08, 2014, 05:15:36 PM

Quote from: toast on March 08, 2014, 05:05:16 PM
Can we get an update on when the blockchain will be launched? That was supposed to be in early January and it seems like all the features being worked on right now are much lower priority... Can we get a p2p daemon without all the whistles and bells so other developers can start working on the KID ecosystem?

KIDARC will be only this month after lotsss of delay as well, were some other priorities I had come in between but as from this week I can work on it a lot again, there's not so much which needs to be done got everything running marketplace, jobboard, profile, voting etc. Just have to work on signup procedure and te Keyhotee integration for messaging.  http://kidarc.com/members/2

This is my point - how can you keep developing this without a working blockchain+daemon?

Quote from: toast on March 08, 2014, 05:05:16 PM
Can we get an update on when the blockchain will be launched? That was supposed to be in early January and it seems like all the features being worked on right now are much lower priority... Can we get a p2p daemon without all the whistles and bells so other developers can start working on the KID ecosystem?

KIDARC will be only this month after lotsss of delay as well, were some other priorities I had come in between but as from this week I can work on it a lot again, there's not so much which needs to be done got everything running marketplace, jobboard, profile, voting etc. Just have to work on signup procedure and te Keyhotee integration for messaging.  http://kidarc.com/members/2

Can we get an update on when the blockchain will be launched? That was supposed to be in early January and it seems like all the features being worked on right now are much lower priority... Can we get a p2p daemon without all the whistles and bells so other developers can start working on the KID ecosystem?

Quote from: kmtan on March 07, 2014, 04:51:03 PM

Quote from: dannotestein on March 07, 2014, 01:05:25 AM
I think I found a solution for the intermittent "duplicate mails" issue, going to commit a fix to the mail server tomorrow after I've given it some final thought. We're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here. Has anyone yet had a chance to try out the Mac client built by brownbear, drekrob, et al? It's located here: ftp://178.63.85.22/Keyhotee/MacOS/2014-03-06_02-02-21/

i would like to have a try..

this version crash during firmware opening ...i unable to save the crash reporter...

Quote from: dannotestein on March 07, 2014, 01:05:25 AM
I think I found a solution for the intermittent "duplicate mails" issue, going to commit a fix to the mail server tomorrow after I've given it some final thought. We're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here. Has anyone yet had a chance to try out the Mac client built by brownbear, drekrob, et al? It's located here: ftp://178.63.85.22/Keyhotee/MacOS/2014-03-06_02-02-21/

i would like to have a try..

Quote from: coolspeed on March 07, 2014, 03:43:19 AM

QuoteWe're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here.

Looking forward to it.

你对3I一定是真爱，对keyhotee不离不弃。我又相信爱情了。

You are quite dead-set on 3I.