Thanks Andy.... and Yes... I very much understand that in moving from suggesting a framework (sort of a battleplan)... to implementation (the first shot).... things may not go as expected.... and so I don't mean to suggest exactly how it should be done in every detail... but it may be the root to begin an evolution. What's important is to have some idea of where you're going (just as in the evolution of hypertext).But in my small way... I want to be at the party... and deserve a seat. All I started with is an idea that very small payments would be useful in a few areas especially.... and then started looking at its needs and implications. My patent is an early iteration of an idea... but contains a core element re account design.... and I can't afford any more patents.Tom CrowlOn Tue, Aug 18, 2015 at 10:54 AM, Andy Oram < " target="_blank"> > wrote:I'll make a high-level comment. What I see of radical proposals for new systems is that they need to play a balancing game. The idea you present is interesting and should live on, but you can't predict exactly how it will be done. Look at Ted Nelson and hypertext--it all came to pass, but not the way he expected. (Actually, Tom, you're filling in some of the infrastructure that Nelson wanted and never got.)It's nice to see that certain aspects of an implementation (such as the browsers you brought in) will work in theory, but I would avoid trying to get a whole implementation worked out from soup to nuts. It probably won't happen the way you think it will. The core idea is the thing to hit on over and over.Andy--On Tue, Aug 18, 2015 at 1:41 PM, Tom Crowl < " target="_blank"> > wrote:Andy... et al,Let me know if this adds clarity to what I'm talking about...Let's assume:
- A broadly available micropayment would be useful for various purposes across the web (advocacy, charity, journalism, etc.)
- A one-click capability is necessary for micropayment viability (as size of payment decreases... ease of execution must increase)
- Hence secure user identification is important for making that payment viable
- The pooled-user-determined account design is a useful "wallet" design for addressing the fixed transaction charges attached to the large variety of various payment sources used for deposit into that wallet
- Broad availability requires an ability to operate across multiple browsers and Internet-based identification sources
Hence: Just as Microsoft browser can interact with google gmail... and various other identity sources interact... SO must a wallet necessary for this type of payment.Moreover while such a system could be formed by agreement via the various "identification sources"... the "wallet" itself should be its own separate entity... and I strongly feel (not for technical but for socio/political reasons) that it should not be formed as a part of any bank or even the banking system itself... but separate from it... though obviously it would receive deposits via them.... just as payment would go out via various browsers and/or identification systems.That's what I'm talking about... not a stand-alone website or wallet. I've long felt... and it hasn't changed... that the micropayment is the key to a very important Internet institution.I'm not a programmer... I'm not a businessman... I'm a hodad (an old term for someone trying to pretend they're a surfer but are faking it all the way). I just think I'm a hodad who's on to something important. Its not only about the Future of Work, gov 2.0.. or anything else... its about the design of the net... and its future.P.S. As a hodad... I'm naturally interested in where my fraud is inadequate so that I might improve the illusion. SO... if anyone wants to let me know what I'm missing... I'm listening.Tom CrowlAndy OramEditor, O'Reilly MediaBoston, MA, USA 617-499-7479
Archive powered by MHonArc 2.6.19.