- From: Steven Rowat <steven_rowat@sunshine.net>
- Date: Mon, 02 Sep 2013 12:59:23 -0700
- To: Michael Powers <michael@mpowers.net>, Web Payments CG <public-webpayments@w3.org>
On 9/2/13 9:30 AM, Michael Powers wrote: > Other projects (diaspora, pump.io, tent, et al.) are focused on new > protocols and architectures. That said, they can easily adopt RSS > and HTTP conventions above. That these other projects have not > been successful is not an unfair criticism of Trsst. We believe we > are the maximizing the possibilities of adoption through embrace of > existing standards. First: Michael, did you accidentally add one too many negatives in "That these other projects have not been successful is not an unfair criticism of Trsst." (ie., Did you mean to say: "...is not a fair criticism of Trsst.") Or is that what you meant to say? Also re the Trsst whitepaper: well-written and gave me a good overview of the system you're attempting to set up. http://www.trsst.com/paper/ As Melvin commented, the devil is in the detail, but I for one am happy that you've put the overview at such an abstract level, because those of us who don't write code (or at least in the languages in use here) need that in order to understand what is being attempted. Since you appear to be at a critical point with Kickstarter -- you might make it, you might not -- I'll comment that, from where I sit, what you're describing seems exciting and, at least on this overview level, well thought-out. I'll also say that if this system became successful (or even got to late beta) I'd most likely begin experimenting with it as a publishing platform. My guess is that others would do the same. I'll go one step further, and say that something like this needs to occur. Whether we're at a point of being ready for wide adoption I don't know; but the NSA privacy revelations have pushed so many people in this direction that now might be the time. Steven Rowat
Received on Monday, 2 September 2013 19:59:45 UTC