Quote from: inblue on September 06, 2017, 07:41:10 PM

Could we have a feature so that in the orphan list we can see which child has already been written to? Because it's a cumbersome task to compare all the names from the letters page to the list page, especially when there will be dozens of names, so I think it can either deter people from writing letters or they will at some point unavoidably write to someone who has already been written to, which is not an efficient way to fulfill the quota. I mean, anyone could still write another letter if they wish (and it's great for one child to receive more letters), but the ones with 0 letters should obviously be prioritized and somehow marked in the list.

By the way, it has been talked earlier about separating orphan functionalities and moving them away from the pool website. It seems like it's almost time to do that, but since the current user accounts are tied to the pool users, which is not the complete set of BiblePay users, I wonder how will you incorporate user accounts for writing letters and voting, while ensuring that the letters stay free from spam and vote manipulation.

Quote from: bible_pay on September 06, 2017, 01:44:22 PM

[...] and we will figure a way to designate Who is responsible for moving the escrow into action every month also, so as to alleviate myself from day to day activities. I would also like to make it so if someone runs off with the monthly escrow funds (IE they dont perform their function), the community can recover by itself and choose a different owner for that activity. (IE we might make it generate a new address and keypair when the panic button is pushed by the lead devs, etc).

Just an idea, maybe this can be solved (or at least the risk minimized) with some kind of a multisig setup?

Yes, first, on seeing which child is not written to yet, definitely, I am working on that. Part of the next feature is giving the ability to click on a Bio and show it in a window without navigating away. Im working on both of those things.

As far as moving the functions out of the pool, I have plans to move the orphan functionality eventually to a different subdomain, but, currently the support functions of the pool tie the behavior together, and, I really want to see what needs to be added to the pool for the masternodes before we go and start disconnecting everything (things like support for masternode polls and voting). This is a case where its more straightforward for us to harvest the IT requirements of the masternodes first, and then start splitting things out. So lets wait a couple weeks for the sanctuary features to start being merged into testnet and Ill do a re-discovery of IT requirements and look at that. In the mean time, view it as pool.biblepay.org is the "super pool" at the foundation, and Wests pool is the standard pool. I will work with him on having the ability to disable the orphan features on his end (we have a data driven menu).

I like the idea of the multisig.

Right now, Im working on the Inbound Orphan API.