Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Alt's patch was added in this weekend, sorry I didn't see this thread earlier to report it here. Please use 0.6.2 (on windows) or 0.6.1 (others): http://invictus.io/keyhotee.php今晚试用了0.6.0
结果只要一点击联系人的名字，就报错退出
诶。。
maybe it is for keyhotee founder?I think you were reading about an early concept of helping to fund future development via "DAC angels". The idea was that holders of 1000+ PTS would create and contribute to bounties to further DAC development (which would in turn increase the value of PTS). This concept can still be employed, of course, when a group of PTS holders is particularly knowledgeable about something they want created for a DAC or to support the ecosystem, but mostly this idea has been subsumed by AngelShares which achieves a similar objective through a different mechanism (this is just my view, however).
Authorizations aren't on the blockchain. Authorizations are only known locally to the two clients who have authorized each other. Authorization will be used for things like direct connect communication and sharing a set of deterministicly computable keys between a pair of users. Authorizations are part of the KH-specific message protocol which can be used by any KH-style client....
I think you've missed the current division of work: Eric Frias and I are now working on the generic blockchain code which will be used for Keyhotee and other DACs, while the guys in Poland (lead by vogel67) are working on the GUI side and Keyhotee-specific backend requirements (e.g. system-specific messages like authorization requests, etc). These are independent efforts proceeding in parallel, mostly.
...
Thanks for the update! Are authorizations stored on chain? It seems like there will be a huge number of application specific data elements needed for new apps that use KIDs, but I imagine most of this will either be off chain or on a separate app-specific chain rather than the KID chain. Am I far off from the design plan here?
Option 1: Release a MVP consisting of a client with a CLI/RPC interface and a working blockchain ASAP which does nothing but register and look up names.I think you've missed the current division of work: Eric Frias and I are now working on the generic blockchain code which will be used for Keyhotee and other DACs, while the guys in Poland (lead by vogel67) are working on the GUI side and Keyhotee-specific backend requirements (e.g. system-specific messages like authorization requests, etc). These are independent efforts proceeding in parallel, mostly.
Pros:
* Let outside developers start integrating Keyhotee.
* Let people starting marketing Keyhotee outside of these forums
Cons:
* "Keyhotee is ready!", but no user-friendly interface or any advanced functionality
Option 2: Delay launching the blockchain further but have a clean, feature-full application to interact with it soon after it launches.
Pros/cons: The opposite of pros/cons from above.
This poll is part of my status update in this thread: https://bitsharestalk.org/index.php?topic=3598.0
0.6.1 /Win7/32/ :For anyone who encountered the above error with 0.6.1,there is a fixed version here:
0.6.1 /Win7/32/ :Yes, someone reported this on the error thread already, the problem is the new Windows installer didn't include VS2012 runtime libs. We should have a new version up in a few hours that corrects it on machines that don't have it installed already.
This is not a bug but i do not know where else to put it.Looks like the new windows installer grabbed the wrong copy of libeay.dll (one that required VS2010 redistributable) and I guess you're not finding the proper version. I'll try to put up a new windows version today that doesn't require it.
When trying to run Keyhotee version 0.6.1 on Windows 8.1 x64 I got error missing MSVCP110.dll. When trying to install fix with libraries: "A newer version of Microsoft Visual C++ 2010 Redistributable has been detected on the machine."
After manually downloading missing dll getting 0xC000007B application error.
Trying to find solution now, not sure is it a problem only on my machine or global.
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.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 :/
I've been analyzing the relevant code for the past two days, and I *think* I know the problem and a solution. It's going to require a minor tweak to the mail server, so I'm going to make the change tomorrow when I'm better rested (working thru a cold for a couple of days).We've had a github issue open for this one for a bit, as it's been reported in the past. But it's an intermittent bug that's hard to duplicate (and therefore hard to debug). Once you get it, it repeats, but we haven't had it occur on our systems lately to debug it. We certainly haven't forgot it, we consider it a high priority issue.
I updated the details in the issue link you gave me. But what about my another issue?QuoteThese problems still exist:
1. Every time I launch the application, it receives several mails (the same ones every time) which are marked unread.
You can get my public key in my signature. Have you ever checked it in your server's blockchain? I think we need to figure out whether the issue is caused in sender or blockchain server or receiver (my client).
