Meeting with Steve and Dustin to start off the morning. Dustin had a couple of questions on ways to track some of his internal code changes. We talked strategy for a bit. Steve then had a question on a client's custom label. It was duplicating one of the fields. We dug in and found that it was a sub inventory attribute that was virtually sharing an id number with another sub inventory attribute. It was appearing to duplicate the data due to the numbering of the attributes. Random error. We went in the backend and fixed it. We haven't had any other complaints about that, so we are assuming that somehow both attributes got assigned the same reporting number.

As Steve and I were fixing the sub inventory issue, we were talking about sales, customer support, and how we are hoping that these new server configurations are going to help us out. We also talked about getting someone to help Shari O. - she is getting buried and needs someone to help. We also talked about some other ideas to think about while we are breaking up the bus (analogy of getting people off the bus and onto their own motorcycles or cars - aka world building). Here are some of the quick notes:

- What about mini options for AWS servers... Currently we have multiple dedicated servers (with fixed number of processors, RAM memory, and fixed hard drives for storage). What if we took those bigger boxes and virtually broke out a new virtual instance for each of our clients. If it could work, it would be almost like a mini virtual dedicated box per client. Just an idea.

- Steve would really like to split out users from corporations (allows users to exist as their own entity and also as part of a master list). Then, we could bridge people over and across and allow users to jump between corporations as they get assigned. We currently can do this, within a single box or cluster. It would be awesome if we could do this on a universe or global scale. Any user (has a single account) and could be interconnected and/or have access to any other corporation (world) based on permissions and being bridged over. Think of home planets and bridging people from worlds to worlds. (digital passports and what not)

- Currently, we (adilas admin) are the only ones who can bridge users between corporations. If it went out further... we could allow individual parties to allow/invite other users to come in and help with any projects and also set connection durations (how long they could virtually stay). If we empower the users to create those relationships, that takes the load and the liability off of the admin adilas team. Good stuff.

- Steve really wants to help out workers and/or dependables

- We would really like add some visual upgrades - CSS and settings. As a side note, settings are going to be huge going forward. We are seeing at least four levels of settings - corp (world), group (system players), pages, and user settings.

- Steve and I were looking at some stats that Wayne had gathered for us... crazy to see those stats and this is just one month from the data 0 box. We would love to see all of the servers and all of the stats, side-by-side, and compare. That would be crazy.

- The deeper we get, the more settings and being able to toggle things on/off (custom setup options) are going to play in. We were even talking about new settings for ecommerce and companies that allow for new customer/client accounts to be setup. What fields do they want to show/hide, what ones are required, what special instructions, what names or aliases, what sort order, etc. Everybody wants crazy deep levels of control on how they set things up.

- Steve and I talked about the pros and cons of the black box options... on the one hand, we can configure any page to do whatever we want. On the other hand, if we go black box vs building a new setting, we have to do the same thing over and over again. Sometimes the speed of the black box option actually creates more work later on. The longer route is building a setting, but it then becomes easier to manage that later on, plus less duplicating code.