Karma Exchange
|
In his book Small Pieces Loosely Joined, David Weinberger observes that the web allows people to “try on” different personalities. Examples he cites include eBay sellers and web loggers. He suggests that trial and error lets people find the voice that works best for them This is an interesting point that deserves more than passing notice. The point of this design study is to discover and code the protocols which best serve our collective, yet personal, economic needs. In the economy we love to hate, one is expected to be well educated, well rounded, well spoken and well placed. Like any superstar, it’s a rare person who has all those traits. And that’s what should raise our hackles. The “real” economy is based on an unrealistic model of how people learn and grow. Further, it measures workers against an impossibly complete package for the employer – not the talented programmer, project manager or accountant the company needs, but the model employee that managers want to surround themselves with. Since the Internet invites us to try out different personas – and possibly improving on each one, our economic design should provide that possibility. How does the Xpertweb mentorship model allow such variability? The mechanism is twofold. Mentors are rewarded only to the extent their support is valued by their students, and each Xpertweb user may have as many mentors as they wish, creating a new Xpertweb persona each time. The only impediment to changing mentors is that, like any Xpertweb provider, each person’s new persona must earn a reputation from scratch. Until respect is earned from experienced purchasers, each persona must undertake an apprenticeship of lower income and volume. This flexibility would be impossible if Xpertweb were a conventional enterprise. Mentors would be unwilling to allow their students to move on to other mentors and that preference would be formalized as policy – because they could control the payments moving through the system. The virtues of an unmanaged transactions system echoes the virtue of open source software – responsive because there’s no management to be unresponsive. |
On Thoroughness
|
Unlike most blogs, this is a series of essays – a word whose root means attempts. My attempt is to describe the web application a tiny group of us is developing called Xpertweb. I’m just too hurried or inarticulate or egotistical to make it a series of short entries. This idea seems to want breathing room and its architecture is just quirky enough to need background. Or so it seems to me. As a result, this blog is so thorough that it’s pretty unapproachable – maybe that’s just part of our reader deflection program. There are so many people more observant and talented than I, who point to all the links worth linking and who keep you current on what’s going down, that I’m concentrating on this P2P microeconomy design study. That’s a little disingenuous. The design was laid down some time ago and we’ve been hacking code longer than I care to admit. I hope the specification is even-handed enough that we haven’t missed anything crucial. Certainly, it’s not too late to change the few Xpertweb parameters that are hard-wired. But there’s not much hard-wired. Everything in Xpertweb is voluntary, which makes it the inverse of the current Economy of Compulsion described on Sunday. There are specific elements that cripple software or web applications:
By addressing all those factors, we hope to make the Xpertweb application responsive to its users. The only thread that even slightly directs user behavior is the relationship of experienced Xpertweb users to less experienced users. Each user of the protocols is expected to mentor others in their use. Each mentor will have an understanding with the newbie that there are certain ways to behave in this boutique economy. The mentor will spell out those standards and the new user will agree to convey those standards to other new users when the time comes. So the Mentor Agreement is the core of the Xpertweb experience. Although the agreement is only between the user and her mentor, it specifies the standards under which the user purports to be operating. Its logical concerns are:
Word of ActionXpertweb is a formalized word of mouth describing visible actions. The Mentor Agreement is the only tangible obligation made by an Xpertweb user. The expectation is that these mutual commitments will be passed along in a natural way, as skills once were passed from parent to child – we all were once millers and bakers and smiths and wrights. With any luck, it will look a lot like a guild. |
What Are We Doing Here?
|
The other day, I suggested that a valid design criteria for an economy would be to base it on bloggers’ values: openness, exposure and candid discussion of our offerings, a compilation of our justifications for and our collective estimation of the quality of our respective offerings. But what if we turn that around? Instead of imposing blogger values on meatspace, what values from meatspace might we take on, as representative of the collective values of web loggers? Tonight I caught the end of PBS’ Ken Burns documentary on the life of Thomas Jefferson. It concluded with these words:
Do we have anything more important on our agenda? Do we have the right to such lofty goals? Do we have the stomach for them? Is web logging the forum to take on Jefferson’s challenge? Oh, what the hell. Why not? The challenges to the human spirit have always been economic, and the tyranny that scarcity economics invariably leads to. It’s not surprising that my view is that those imperatives can be embedded in a set of values and transactional forms adopted to express those values. The people using those forms can hardly presume to change the “machine of the law,” but it can route around undesired compulsion under the law using the tipware protocols I described yesterday. Just a thought. |
Blessed are the Geeks
|
Reflecting on this Sunday after the Microsoft Absolution, I’m reminded of the distinction between personality types: Pushers vs. the Pullers, Daniel Quinn’s distinction between the Takers and the Leavers; the current line between the Geeks and the Suits. In the middle ages, there were the peasants vs. the “nobles” (John Perry Barlow’s “The divine right of thugs” comes to mind). Geeks like to do stuff that’s useful and often worry about the pay later. Suits like to control stuff that’s useful and compel others to pay more for it than they pay the geeks. Nice gig. Howard Bloom has made a strong argument that the dominated become aggressive when they become the dominators, so the distinction may have more to do with roles than personalities, but that may make this an even more worthwhile inquiry. What might a new microeconomy do to break down these distinctions rather than reinforce them? It’s unlikely that any amount of teaching, preaching or reaching out will work – those have always failed. Government policies and books and morality plays don’t work. Religion seems a Dominator’s dream, so rigidly does it subject its followers to the whims of its leaders. Given all that, are there any protocols in our economy that should be included in or excluded from our little design? You Can’t Steal a GiftLet’s look at the protocol called compulsion. Our economy and our rule of law are based on compulsion, as have been all societies. The western world has raised compulsion to a Kafkaesque level, essentially saying:
Is compulsion the source of customer dissatisfaction? Sure it is, especially with intangible services. Phones and cable TV and subscriptions and travel and lodging are all based on making bandwidth or physical space available to you, on the assumption that the availability has intrinsic value. Individual vendors may have generous refund policies, but that’s at their disgression. The fine print says that if you sign up, you’re compelled to pay until some period after your written cancellation. That’s how it’s always been. But now there are alternate models – the work of waitpersons and street musicians and bloggers is valuable but unstealable. Open source software and closed source shareware and most Internet browsers are unstealable. Gene Lees wrote a fine book about Jazz called You Can’t Steal a Gift. Naturally, most laws are broken due to economics – and the temptation to steal what’s stealable. Could our little P2P microeconomy make some of this stealing impossible, perhaps reducing the power of compulsion? The solution for theft and compulsory economics should be based on code designed around the shareware model. Lawrence Lessig’s doctrine is that code can have a power comparable to law. Under the shareware model, all work would be delivered in advance with no compulsion to pay, as in Xpertweb. (Unlike shareware, Xpertweb requires the receiver of the work to declare its value – anything above a failing grade requires a payment between 50-100% of the asking price.) Xpertweb users will live in two economic operating systems, the large one we love to hate and their P2P forms-based shareware model. For the Xpertweb portion of their lives, they’ll deal with people ranked as experts by their previous customers. They’ll find their expert by looking in an RSS index for people who’ve done similar projects before and who know more about their problem than they do. This is the embodiment of Bill Joy’s axiom that there are always more smart people outside your company than within. Both the buyer and the seller know the expert’s work is shareware. By knowing each other’s reputation, thay share some assumptions. They assume that this gig is not a big hassle for the expert, who may be customizing previous solutions, so he’s not risking a lot on this task. The buyer knows the seller is motivated first by the grade and secondarily by the fee. The presumption is that this is indeed an enjoyable and responsive economic OS for both parties. The peer-to-peer transaction model favors the geek over the suit (who’s nowhere to be found in the deal). This transaction is as unstealable for the suit as it is for the buyer – an expression of a gift economy with contingent price tags. Blessed are the geeks, for they shall inherit the next RFP. |
Open Data, Open Resources
|
Phil Windley, CIO of the state of Utah, gives us a wealth of insights we usually don’t hear from people managing “big iron” systems. I hope he won’t mind me reprinting this report from last Monday: I did a little reading at lunch in The Transparent Society by David Brin. Brin sets forth the following and calls it an “accountability matrix:”
His contention is that people see boxes (1) and (2) as good and boxes (3) and (4) as bad. What society needs is boxes (1) and (3) since that creates accountability. Further, society should eschew boxes (2) and (4) since that pits citizens against each other in “an arms race of masks, secrets, and indignation.” This point speaks directly to the data issues we’ve been looking at in this design study. Let’s imagine an economy entirely made up of bloggers. Do bloggers worry about there privacy? Not really. In addition to the blogger’s URL and email address, any industrious reader can dig a little and know where a blogger lives, her phone number, etc. Bloggers willingly give up their anonymity in the interests of the truth they wish to share.
In the blogger economy, Brin’s boxes (1) & (3) would be part of the transaction software, and boxes (2) & (4) would not. Further, the likely features of the software would be:
It’s hard to beat the blogger ethic as a guideline for our design study. It will be easy for individuals to adopt such protocols but very hard for corporations, which think their value lies in what the hide from others. They’re only now beginning to guess that their value is in what they expose to others. |
The Gordian Data
|
There’s a famous story about the eastward blitzkrieg of Alexander the Great through Asia Minor. On a narrow isthmus at the town of Gordia, on the only road to the east, there was a wagon left by the legendary Gordius, which had stood there time out of mind. The crossbar of the yoke was tied with cornel bark rather than rope, as they usually were, to the bar attached to the cart. Untypically, this knot was of mind-numbing complexity and size. Legend had it that Asia Minor would never fall to any conqueror who could not unravel this knot. As was the tradition, Alexander was led to this puzzle, which had stumped all who went before him, none of whom were successful in taking Asia Minor. Impetuous Al took one look at the massive snarl, shrugged, and cleaved it with a blow of his sword. It seems that with oxbows as with life, the direct, unorthodox approach is often the best. We need to cut through a lot of mystery that surrounds data management, especially as it lives on the web. Actually, the RSS standard is pointing the way to the future of most data on the web, and RSS may be the means to cut through the Gordian Data problem. The standard for large data-driven web sites is to connect the web (html) server to a separate data server, which supplies the data to be displayed in the user’s browser and which stores the data provided by the user. Special code in the web page triggers a Common Gateway Interface (CGI) which talks to the data server and gets and puts the required information. Every time the user hits such a web page, there are two events: fetch the web page and fetch the data to be displayed on the web page. When the web form is submitted, there are another two events, tell the page you’re done and move the data to the data server. Data for the Rest of UsInterestingly, a web page is a database. It contains information which, when requested by an authorized user, is served to the user. It’s not elegant and it’s useless for large data sets, but it still has all the characteristics of a data base. Until the world wide web, there never had been a public data record like a web page. The web’s breakthrough was to totally expose some set of useful data to anyone, without restriction. who had the web address. This was, I submit, a bigger deal than even we web junkies acknowledge. My mantra is that proprietary data is the root of tyranny. If information has no use, it’s not considered data. But if it has been elevated to data status, it’s needed by somebody and protected by someone else. Whether it’s a driver’s license record, Visa account or the Most Wanted List, when you need to have the data you are subject to the demands of the party controlling the data. It is what gives governments power over their subjects and police the power to make your life a mess. It’s why it’s bad form for a government to detain its citizens without putting them on a public data list so others can see what’s going on among their peers. The Data ProblemWhen you build a data base, you need a trained data guy who will use specialized software to design the data forms and connect them to the data base, which is usually a table with a header row of the data types and another row for each record (person or property or airline flight). Sounds good, but the problem is that the tools are quite specialized and each data base is custom-built for its owner. That means it’s hard for another designer to step in and modify the data base, since it’s a little like a computer program. This means the data base owner is dependent on the designer, which he doesn’t want to be, and the designer is an indentured servant to the owner, which he doesn’t want either. So we’ve got an ungainly data source that’s available to everyone and buildable by almost everyone’s niece – the web page. And we’ve got a cumbersome, expensive specialized tool understandable by only a few and fully understood only by the designer. Where’s the middle ground? The data problem is really two problems: interface and data integrity. Data for the Rest of Us needs a lot of people who know how to design a useful interface with low cost tools. That would be web design. Since all data is finding its way onto the web, we’re making the web page our default interface standard. That leaves the back end data problem. There are thousands of people who will design you a web page, but hardly any of them can even spell “data”. Most owners of data bases want to get information from their customers, not just digitize their brochure. The best that small outfits can usually get from their designer is the ubiquitous web-to-email tool which dumps the info they want into their inbox. If you want something useful, you’ll spend more than a small outfit can, or use one of the one-size-fits-all solutions, which locks you in to a single vendor. Find Your RSS with Both HandsThe RSS solution is elegant. It codes your info as categorized text using XML tags like <title>Jaws</title>, <director>Spielburg</director>, etc. And it puts it right on the web where anyone can see it. Since it’s just text, it can be written by many tools, and because it’s systematically tagged, machines can read the data and slice and dice it, just like a “real” data base. The problem is that “the Rest of Us” and our web designers still need an expert to customize the RSS feed for our purpose. RSS is real progress that stops just a little short for anyone but bloggers and news syndicators. The Gordian breakthrough is to store data right on the user’s web site using XML as the data store. Suddenly any web designer is able to design the data input form, if they have a tool to parse their preferences into PHP code. XWriter.phpThis fall, you’ll be able to download an open source script that lets a web designer add data tools to their web sites. The only skill they’ll need are these:
That’s it. XWriter adds the needed PHP code to your web page, puts the page where directed and opens it for testing. XWriter was developed for creating and modifying Xpertweb forms but its uses are so broad it’s been enhanced for use on any PHP-equipped site. The XWriter tool is being developed by Hurai Rody, who has done a great job working on a strange concept. We’re indebted to him. |
Money for the Rest of Us
|
Before I got off on my rant about our rights as soldiers in the New Continental Army, I had promised that we’d explore Xpertweb’s Open Resource model of collective rewards:
The voluntary 5% payments are based on the principle that mentors are doing something that benefits every person whom they inspire to join the web of experts. The first question to ask, from a systems engineering standpoint, is whether we support the concept of hierarchical rewards. The Xpertweb model is based on a view of the macroeconomy as an Economic Operating System (EOS) that we the users have the right to revise as we see fit. A well-publicized feature of the current economy is that some of its users get very rich while most scrape along. We’ve observed that’s because some people are in a position to design the EOS subroutines, but most are not. What they design are accounting systems which are controlled by the companies they form, to which employees and buyers approach as humble clients, with no say in the subroutines they need access to. Just because the old OS has hierarchical rewards, should the new one? If so, how should they be set up and managed? And what the hell is a hierarchical reward system, anyway? Let’s examine those questions in reverse order Hierarchical Rewards for Higher Arc-ersWhat are Hierarchical Rewards? Anyone who gets money while they sleep (like pension payments or investors) is living off the work of others. In a steady-state model, the payments are fair because the retirees invested money in productive assets which owe them a cut of the later action – think of it as money with a memory. But people who are way more prosperous than average are those who, like Bill Gates, have developed a toll on others’ efforts way out of proportion to the effort and money they invested in their toll booth. Capitalism says that’s A Good Thing, since it’s so hard to organize ordinary people so they do something productive. Employees aren’t so sure that the salary spread is based on relative contributions, as suggested by this analysis of financial industry salaries for clerks through controllers in 2001:
Hierarchical compensation rises steeply at upper management levels and, as reported everywhere else, spectacularly among those eligible for stock options. Each level gets paid at multiples of the previous level. This is the defining characteristic of hierarchical rewards. How should Hierarchical rewards systems be set up and managed? There has never been a standard for how to design the really amazing wealth hierarchies – they’re designed by the beneficiaries and are subject to the vagaries of the market, at least in theory. At those levels, professional management is pretty astute and likely to succeed, since…
That’s all there is to it – end of story. The Set-up But we’re proposing to design a hierarchical rewards system, well, systematically. So the same rules must apply to every participant, presumably through revisions, so the code is backwards-compatible. Xpertweb’s goal, like any meme, is to expand the population of true believers. So, if it’s appropriate to feature hierarchical rewards, they must reward those who increase its population. The algorithm is simple: everyone you mentor will send you 1% of purchases bought or sold as long as they appreciate what you’ve done for them. That’s a meaningful contrast with Ye Olde Economy: Hierarchies in the current EOS are lock-ins. Every organization in our society is locked in to paying the Microsoft tax. If they grow disenchanted with XP’s nagging, they still will be forced, one way or another, to pay for the next upgrade, as long as they are committed to the Microsoft koolaid. Since there’s no Xpertweb Inc., Corp., Amalgamated, or LLC, there’s no one to pay money to except your mentor and the 4 other mentors who are responsible for the chain of mentoring that introduced you to the system. Each month, you pay your mentor support chain based on how you rate your mentor and how each of those mentors rate their mentor. At any time you may start to work with another mentor and start to pay your 5% to a support chain you prefer. Managing the Hierarchy Hierarchies are always managed in Ye Olde Economy, which is why they work so well for those who benefit from them. In a systematically designed hierarchy, there can be no way to change the rules for paying the participants, so there can be no management of the hierarchy. This is the Xpertweb model. Every transaction can spin off as much as 10% of its value to the participant’s 5 mentors, on a voluntary basis. Those who prefer lock-ins need not apply. Like the sellers and products tracked by the Xpertweb protocols, happy campers pay as suggested. Buyers and “mentees” determine quality ratings and advertise it to their successors. The rewards may be absurdly high, but the quality of services can never be questioned. Should Xpertweb’s Designed Economy offer Hierarchical Rewards? This is the central design question. Probably the self-generating reputation index is enough of a benefit to attract new users. But the system asks a lot of users – more than any commercial system would: you must have your own web site. You need to upload your starter kit via FTP. Where will you get a starter kit? If it’s only available from a central site, that site is a business that must charge for its service and, if the service is well received, will increase the price as it becomes a necessity. No, there must be a mentor for each new user. Any user must be equipped to be a mentor. That means that the skill set for any user is broad. A mentor will be needed to set up every new user. Why would someone doall this? The immediate attraction is to get paid something by several generations of new users, maybe a lot. The payoff is a sense of community, IF the users relate to each other as carriers of a shared, successful meme. Xpertweb User Skill Requirements
The PayoffAll those skills are the responsibility of the mentor. Let’s pause for a minute:
Run The Numbers – This is the Scary PartAs part of their training, each new user is expected to buy and sell stuff and train others, to master the 9th and 10th skill requirements. Every new user buys or sells a total of no less than $100 every month for a year. They can buy $50 of stuff from someone and sell $50 to someone.The point is that they will have a reason to use the software every month for a year. This activity will require the new user to send up to 1% – $1 – to each of her 5 mentors every month, requiring her to rate her mentors and to use the forms which manage her mentor ratings and support fees. Each user is expected to witness the mentoring of 4 other new users during their first 4 months. The mentoring is done by the new user’s mentor, but by the time it’s done, she can do it herself. This means that that her “mentees” will also be buying and selling a total of $100 each month, also for a year. The Amway PartOK, the issue is in front of us. Do we have the right to do this? Don’t we need permission to establish our own distributed shared-source data base? Are we allowed to send money to each other according to a published but non-obligatory set of rules, with no company approving and managing our transfers? If everyone trains 4 users, who train 4 others, etc. and each of those sends/receives $100 per month, everyone will get $1 a month from 4+16+64+256+1024=1,364 people = $1,364 per month, after about a year. They will also learn that 1% of all receipts are paid to their qualifying mentors, so they send another $13.64 to each mentor. After about 2 years, the theoretical total is $1,464 paid by 1,364 people to each mentor = $19,969 per month. That’s a lot of mentor motivation.When people start using the protocols for real work, the numbers get much larger. What’s Wrong With this Picture?This is a lot of money to contemplate, especially moving among a loosely affiliated bunch of people with no obligation to do anything until and unless they’re satisfied with the value they’ve received from sellers and mentors. Who knows if any of this will really happen? No One. It’s an experiment! It’s not venture-funded, so we can design a system with an unknown outcome. There’s no cost to keep the system alive until it gets traction, so it doesn’t have to take off immediately. There’s time for people to play around with it and see what works and what doesn’t. The forms publish all the cash flows through the system so, when the process does get traction somewhere, it will be known to everyone. We can’t know ahead of time if the protocols trigger the expected actions. But when there are actions, we’ll all know it immediately. That’s when we the Xpertweb users will discover what uses we’re putting it to. |
All We Have to Fear is Manipulation Itself
|
When you feel fear in a media-driven society, chances are it’s because someone wants to scare you. As previously conjectured, fear is usually the product of a media message. The message is certainly calculated, perhaps cynical. At its most benign, it’s to sell you a hygiene product to avoid the purgatory of those who smell, look or taste human. If political, the message is surely cynical: to alarm you over a non-issue so convincingly that you reward the manipulator of your emotions with your vote or worse – another of your dwindling freedoms. There are two kinds of people in a society: those who expect to work for whatever shows up and those who just know they can get others to do for them what they cannot or will not do themselves. The latter kind must manipulate the willing workers to be served as they expect, with fear as the best tool for the job. Let’s break that down. In my recent Viet Nam recollection, I suggested that we pay too much attention to scary but improbable anecdotes and too little to our real lives and loves. Perhaps our innocence has been stolen by terrorists, but our energy is being drained by politicians. They can do it because we’re wired that way. To be fair, the politicians face their own greatest fear: another major attack will expose their lack of control of this conflict. Their fear, then, is for their political security and not the security of their fellow citizens. All they have to sell us sell is the illusion of control over a chaotic world. We are the WarriorsA war on terrorism is a war of terrorism. Who are the front line soldiers in a terrorist war? It’s you and me, untrained guerilla fighters moonlighting on the front lines of a nasty, random conflict. It’s not our troops who bravely take the conflict to the nations harboring terrorism. We are the Continental Army on the barricades of this conflict. As the front line warriors, perhaps we want some voice about how this battle will be joined. For instance, we might accept the fact that some of us are going to be killed and wounded. Not many of us, certainly, and very improbably any one of us, but some of us. Now if we’re willing to be real patriots and warriors – to die or bleed for this cause – maybe we want to tell our elected “leaders” about our preferred terms of engagement. Here’s one view: Poiticians Terrorism Briefing
Get Real, Go OnlineOf course I’m dreaming a utopian vision. Politicians won’t do this because they are the worst of the people who excel at getting others to do things for them. And they’ve got the best means to do it – subjugation. Only technology (web applications) can save us from the 226 year slide from a barely governable oligarchy of propertied, rebellious white guys to a manipulated herd of materialists. But who’s going to build these web applications? We will. If Mitch Kapor can spend $5 million on the OSAF PIM, surely we can find a way to build specific, purpose-built global connectors:
Howard Bloom points out that confusing times can make you fee |
Low-Level Code
|
All this tiresome talk about accounting systems must seem too detailed or obsessive, but that’s where it all starts. Every one of us works for an accounting system – we’re really that shallow. Because accounting systems are the baseline for our behavior, it’s the high order bit for our design study. Again, our definition of an accounting system, from October 22:
We’re not designing an economic utopia because they don’t exist. Our Xpertweb protocols must work in a world of short-sighted, self-centered competitive people. People who care most about the how well the money moves among the participants and how much of it lodges in their account. Once that confidence is established, people will do what they have to do to get their fair share. They may work on their quality, if quality is measured and published. There are 2 kinds of money that fall out of an Xpertweb transaction:
These payments correlate to the 2 kinds of money common in the larger economy:
There’s an interesting distinction here. In the traditional model, everybody’s goal is to receive automatic money – money based on capital that shows up as a pension, royalty, residual, dividends, stock sales, etc. All of those exist because some corporation has employed people to generate more cash flow than the people cost, generating retained earnings. The profits themselves may be available to generate automatic money but usually it’s based on the willingness of stock speculators to pay more for a piece of the company than the last owner of that piece paid. So the interesting money in Ye Olde Economy is not type 1, wages and sales, but the money that wasn’t paid for employees or parts, and was transformed into assets that can be bought, sold, mortgaged and fretted over. It is frozen work, generated by capitalizing a vibrant event – production – and turning it into a static thing. It is the genius of capitalism to develop that financial alchemy, for it made it possible to turn the fruits of past successes into the possibility of new success. The interesting money in our Xpertweb microeconomy is not static but dynamic. Where in Ye Olde Economy you try to accumulate assets which will pay you a dividend or might increase in value, Xpertweb wealth is the flow of tens or hundreds or thousands of people sending you a dollar or ten each month. These myriad peer-to-peer payments cannot be intercepted or devalued or traded to someone else like assets can. They are not fungible, as the lawyers say – not convertible to another form or easily conveyed to another. Importantly, it is not practical for a clever person to re-direct these myriad payments to themselves. For the successful mentor, having mentored successful others who mentor likewise, these payments are incessant, continuous, and cannot be avoided. Every day, one-thirtieth of their mentee pool deposits a few dollars into their bank account. This is a change in kind, not just amount. Where we currently seek to amass several significant assets, each of which may rise or fall with the market, Xpertweb proposes to deliver myriad streams of inconsequential amounts. Next time we’ll look at the math behind these payments. |
