Jaap,
Thanks for testing. The reason rosettadiagnostics requires the e-mail pass in the arguments is we use it to check if an account exists with rosetta or not first, and that lets us make the decision on replying with the right narrative if a Rosetta account needs to be created or not.
I was thinking the way this could be implemented from the GUI is we put two more buttons on the DC page (Rosetta Diagnostics, and Set-Up Rosetta), and we use the same info populated on the page (the user and pass) to call the function, and we show the result in a messagebox.
Then in this next baby step, we can change the directions for new users to be something like : Install boinc, Click Set-Up Rosetta, Click Associate... etc.
On the nice UI pages etc, I was thinking we might be able to store more schema info in IPFS, and create a "Menu" object. It might be possible for me to add menu items that point to business objects. That would be an IPFS-driven menu system. Then the menu in the wallet is extended by what menu records exist; and we link for example "Gospel Link" to the Gospel Link List (from the Menu value for gospellink).
Havent though about letter writing yet, but I thought of what might be a good one: Our expenses and revenue being stored in IPFS. If we make an object for expense and one for revenue, we could port whats in the pool accountability over to the wallet. I think in order to do that, the permissions must be done first, otherwise hackers will deface the records (and that would of course is not an option for the accountability records). They have to be readable by all, but writable by the authorized signer.