You can try it out with "daniel" or "id/daniel" if you want.You can always simply distribute the necessary files with the project.domob wrote:Is it ok if I use that package (jsonrpc)? Apparently it is not installed by default with Python on my system, and I also wasn't able to locate the right Debian package right-away (if there even exists one). So I'm not sure how easy it would be for potential users to install it as additional dependency...? Or is this easier with Windows, and only Debian's "fault"?
EDIT: Don't mind, I'm rolling my own implementation based on rpcClient.py in nmcontrol directly with sockets. I wasn't able to figure out how to tell jsonrpc not to block and ask for user/password on the console when the authentication info is wrong, which is unacceptable behaviour in my case.
Good job :pdomob wrote:Update: The code I just pushed to the repository (see link above for the Bitmessage forum thread or use https://github.com/domob1812/PyBitmessa ... amecoin-id to view it directly) has a UI for editing the connection settings, plus implements nmcontrol support as additional backend. Please try it out and let me know what you think! Do you have any more suggestions on what the patch should do additionally? IMHO, these are all the basic features necessary - and also according to the bounty criteria. (But if there are good suggestions, I'll be happy to implement them!)
After some others have tested the code, too, I'll try to get it into the official bitmessage code.
Yes and no :pdomob wrote:@khal: Do you plan to support id/ directly in nmcontrol? I now just use "nmcontrol data getValue" to fetch the value and then parse it myself (as with namecoind) to check whether there is a "bitmessage" field. That seems straight-forward, but I'm curious whether or not you want to implement identities in nmcontrol in the future directly. (Possibly if some more advanced stuff gets added, or for things like the "get signed bitcoin address for each customer" example in the wiki.)
Code: Select all
nmcontrol data getJson bitmessageWell, my question was mainly out of curiosity. I'm just fine with the "data getValue" query, as you mention it is pretty trivial to get the bitmessage address out of it if there is one. Furthermore, since I also support namecoind directly, I have the code to handle the "raw" value anyway. So actually I'm not planning on switching for my bitmessage patch.khal wrote:Yes and no :pdomob wrote:@khal: Do you plan to support id/ directly in nmcontrol? I now just use "nmcontrol data getValue" to fetch the value and then parse it myself (as with namecoind) to check whether there is a "bitmessage" field. That seems straight-forward, but I'm curious whether or not you want to implement identities in nmcontrol in the future directly. (Possibly if some more advanced stuff gets added, or for things like the "get signed bitcoin address for each customer" example in the wiki.)
As the id namespace has no special feature, for now, I'll only add a json fetcher in the data plugin :In case of no "bitmessage" record, it'll return False I guess (with current code for fetching). Should it return something else that is a valid json string ?Code: Select all
nmcontrol data getJson bitmessage
I took a glance at the code on Sunday and it looked very good. Hopefully I will be able to test tomorrow.domob wrote:Update: The code I just pushed to the repository (see link above for the Bitmessage forum thread or use https://github.com/domob1812/PyBitmessa ... amecoin-id to view it directly) has a UI for editing the connection settings, plus implements nmcontrol support as additional backend. Please try it out and let me know what you think! Do you have any more suggestions on what the patch should do additionally? IMHO, these are all the basic features necessary - and also according to the bounty criteria. (But if there are good suggestions, I'll be happy to implement them!)
After some others have tested the code, too, I'll try to get it into the official bitmessage code.
Thanks! I'm looking forward to "independent input".phelix wrote:I took a glance at the code on Sunday and it looked very good. Hopefully I will be able to test tomorrow.
As soon as I get some (and it is positive) I'll apply for merging into stock Bitmessage.That would be great! What about even adding a whole set of possible options for identities (as described on the wiki)? Like real name, email address, bitmessage, bitcoin address, namecoin address, PGP fingerprint?snailbrain wrote:excellent work .. we can add bitmessage field to configure names part of qt (to make it very easy)
was waiting for any bug reports and minor fixes before doing anything else on it.. but we could have ID Tab, with all that toodomob wrote:That would be great! What about even adding a whole set of possible options for identities (as described on the wiki)? Like real name, email address, bitmessage, bitcoin address, namecoin address, PGP fingerprint?snailbrain wrote:excellent work .. we can add bitmessage field to configure names part of qt (to make it very easy)