It's easier just to avoid it all together as you suggest - so that's my decision.
That's how I am going to take responsibility for my own actions.
Yep, the little SimPeople magic "everything just works" videos they provided were really horrible. Might as well said it runs on PixieDust. Going through the wiki and writing code against it was the only way I really began to understand the system in any real sense. In my opinion they would have been better comparing it to bank statements and checks. Your ripple balance represents how much money you have at PlaceXYZ and you can use that money anywhere that takes checks from PlaceXYZ. A very long time ago that used to be the way US banking worked. I could buy groceries at the grocery store with a check, but only checks from the one big bank in town.
I think ripple is an interesting idea, and there is potential for some sort of ripple system to work in the future. But I do not like the reliance on XRP, I think ripple would be better without them, and I find it unnerving how much information is available to everybody. I do not want just anybody to know every single transaction I have ever made, all conveniently linked in one place. I guess there are ways to hide your identity by using multiple accounts, but that totally disrupts the whole trust network and is not very convenient.
Yeah... the whole bank analogy breaks down once you throw in "and BTW all your balances are visible to everyone". This is simple enough for bitcoiners to grasp, but not soo much for civilians.
UPDATE: This can be fixed with "hot" and "cold" wallets, or in this case "public" and "private" addresses, but the last thing that is needed is another level of convolution.
I use Websockets from firefox just fine - why the limit to Chrome?
Not a limitation, just a preference. Should work well with all browsers... even IE10 *puke*
I like python fine, and will likely play with it too, just figured more people would like to see a javascript sample. The echo page is cool too, but it doesn't provide the pointers mine does (like how to tip). Neither of them handle cross-domain invocations. Both chrome and firefox prevent that without reverting to lower level requests. I've heard that the fix is to explicitly allow it on the webserver to avoid the errors, but few service providers allow that level of tweaking. Might give this a shot as soon as I get enough NMC to start a .bit domain.
Ripple discussions tend to heat up a lot here anyways, this is almost civil in comparison!
Bummer ripple is so taboo here. I had hoped to bring up some of my questions and thoughts to a larger community, but it sounds like I'll stick to the smaller ripple boards for the foreseeable future.