Interesting ideas, indeed! However, I'm not sure if you can really implement a "generic namecoin-enabler". After all, namecoin itself is that kind of generic piece. The code to integrate it into Bitmessage or any other application is not so complicated (just opening a local HTTP connection to perform a JSON-RPC call). If your target application is written in a different language than the "plug in", you need "glue code" anyway - and my code is in fact not much more than this anyway. However, at least of the application is in Python (as Electrum is?) you can just copy the code over and all you need to do is merge it to the UI.moa wrote:It does raise the interesting point to ponder what a generic namecoin-enabler plug-in/add-on might look like ... e.g. I see people are configuring Thunderbird to use BM-protocol http://www.youtube.com/watch?v=ppk_zzjZRIgso a namecoin id/ enabled Thunderbird or any email client and once you start down that path ... then the possibilities seem to increase considerably for using this technique for authenticated messaging of many kindsI think the basic interfacing code to do RPC calls is (somewhat) reusable. Do you think it would make sense to abstract it even more so that one file can be copied to a new project without any changes? This would basically just mean removing the BM specific configuration routines and putting them into another file.
Do you think it would indeed be a good idea to try integrating that into Electrum? I can try that out - although I've so far not yet used it at all.