"Transparent: anyone can make a copy of the register at any time and keep their own records as a check to ensure user holders match the register's list."
'The Ozzie Thing': might the acceptance of cragv's model pivot on (a) putting in place a clearly-understood-and-sufficient back-up system (to be discussed and designed) and (b) the inclusion forthwith of some non-IndiaMikeZulu players into the group that manages the back-up system?
That is, it is wise for Ian and Mark and Cragv to see that others may see a 'creeping centralisation' goin' on here!
Thanks Mark, the idea of unintended centralisation around we Aussie players is something I hadn't considered. Here are some thoughts related to this that may help allay fears (sorry about the mini-essay):
Why the Un-Ex is a spreadsheet and why this is temporary:In its current form as a shared spreadsheet, the Un-Ex is admittedly clunky and a little annoying to use. It is only intended to be a proof of concept to ensure everything fits together (something we're currently working out in this very discussion). Once it is sufficiently functional and we're satisfied that the Un-Ex trading process is clearly defined (we're pretty much at that point right now), design and construction can begin so the Un-Ex can live on an actual database that is hosted on a secure and reliable website.
I intend to facilitate this myself (but anyone else is very welcome to do it instead, honestly!) and currently plan to use the same web host I've been dealing with for 5+ years already. They're certainly not cheap, but they're reliable and have excellent tech support with offices in both the USA and Australia. Security, bandwidth and availability are the key parameters in selecting an appropriate host.
I plan on writing a database on which the Un-Ex can run with a long-term view of being able to handle an order of magnitude more traffic than the trickle we see at this early stage of the project. It's a serious investment of a LOT of my time so I'm not taking it lightly! The Un-Ex in its spreadsheet form constitutes part of my database design planning, where we can use it and modify things as needed until it all clicks neatly together. At that point, I'll be ready to build a database with a clearly defined scope.
Related to this, let's address transparency and data redundancy (backups):
Transparency: in its current form, anyone can open the Trade Tracker, click the File menu and then click 'Make a Copy'. That saved copy is yours to use and change and test and poke and prod and investigate. There is nothing hidden and nothing locked from your eyes, you can look and test to see that all calculations work correctly and that there's no funny business. Indeed, you can click on the cell of any sheet (including hidden sheets) on the live sheet and can see the formulas that drive the whole thing. There is nothing hidden here and I've purposefully kept scripts out of the sheet given this is an experimental form of a database design that is to come!
In its future database form, 'editor' and/or 'review' user roles can be created for any/all Trusted Traders who wish to log into the server to view code. For anyone with the aptitude to help develop and maintain the database and front-end once it's live, administrative roles can also be created. We the community own and run this show, there are no barriers or restricted access areas here.*
*The one simple exception to this is where areas are already completely viewable but locked from editing. Anyone can view the Members tab on the Trade Tracker but noone can edit it. By later tonight, the page will be fully automatic and should require no change or intervention. Names, trade and DVC totals, merchants, and so on are automatically added and calculated based on the action in the Trades tab.
Backup System: in its current form, Google Sheets runs on Google's own servers, which have humongous resources behind their availability and data storage. Google Sheets keeps change revisions and allows roll-backs to any previous version of the spreadsheet. In addition, Google Sheets has the option to be stored locally on the Google Drive owner's computer and/or mobile device. In further addition, I handle electronic data for a living. I use an encrypted and automated commercial cloud backup service that includes my Google Drive folder. This service also saves versions, so there's a secondary point of roll-back redundancy. If I were to abruptly disappear from this group and stop responding to messages and phone calls (death, mental instability, sudden and severe change of circumstances, etc.), any of you can make a copy of the spreadsheet in its current form and could then run it from your own Google Drive. Share the new link with the rest of the Un-Ex group and my involvement will be simply historical. Yes, it's that simple!
In its future database form, the web host I intend to use (Quadra Hosting, for anyone wondering) has their own impressive, redundant storage processes in place. In addition to this, I personally make a full backup of my websites on a monthly basis and an automated, incremental backup of my websites on a weekly basis. This is encrypted and stored on my commercial cloud backup service, so if the web host fails and their backup fails and my local backup fails and my secondary backups fail, I still have everything to within a week on my cloud storage account. If I were to abruptly disappear once the website is up and running, I plan to already have created a few administrative accounts for various other skilled people here on the Un-Ex (IanRidgewell and guyinanutshell come to mind as I've had numerous technical discussions with both). These trusted traders could keep things running until others could be roped in if/as necessary - and that's just today, while we're still teeny tiny!
For any/all of the above, transparency and redundancy is key to how I consider and build things. There is nothing that I'm currently doing with the Un-Ex that you guys aren't aware of, and that's the way I like it!
Questions and ongoing discussion welcomed. Cheers.