I’m not sure that they ever had any data because the data would probably suggest that management had the lowest productivity out of any employee. Middle management is filled with too many meetings, they’re all promoted to a level of incompetency, and have delusions that they contribute more towards the success of the business than the skilled people below them.
Great article, thanks! The last few sections really make it seem like a dumpster fire.
So, in simple terms, the value proposition is that the retinal scan will generate a unique ID of a person in the system and ensure that a person cannot be registered more than once. This will then allow the system to be used for tasks like authentication or ensuring fair distribution of tokens. Another potential use case mentioned is something like the administration of Universal Basic Income (UBI), whereby the system would verify that people receive UBI and cannot claim duplicate payments. You could also extend that idea to things like government ID.
The privacy concerns would probably prevent a roll-out in most Western markets, so it will be interesting to see if they can generate enough business in other markets.
I’m more interested in learning about who is paying the 25 WLD, how they have funded that, and how they plan to generate a return on the investment. There is already an upfront investment involved in developing the token, the “orb”, and the uses of the data, so what is the business model that generates revenue for them?
Agreed. As soon as a web service decides to prioritise revenue growth above the user experience, it’s over. This is usually in the form of an IPO, so if you happen to be a fan of a particular service, as soon as they start talking about going public, start looking for a free / open-source alternative.
Love it. AI incest is the perfect term for it haha.
The article by Wait But Why has always been my favourite reference guide for explaining the future of AI to friends and family: https://waitbutwhy.com/2015/01/artificial-intelligence-revolution-1.html