"It would be good to change the title string at the top of the adaptor file to something like:
$:/plugins/thali/couchdb/couchdbadaptor.js" Will do. " the two parts seem to have meshed together quite nicely." It was a brain-twister, I must say, when I saw how the same code in Syncer was being used in two different contexts. First I'd hit a breakpoint in the browser's debugger, which was running one instance of Syncer, then as part of the same transaction I'd hit a breakpoint in the server's debugger which was running its own instance of Syncer. . "It would be great if it were possible to make the couchdbadaptor be sufficiently configurable to be generic" Agreed. That would make it much easier to understand how to implement other storage back ends. IndexedDB, for example, would be a good lightweight alternative to CouchDB or Couchbase. "It might be handy to arrange a Skype/Hangout if you've time to discuss the details" Sure, let's do that. I am in Eastern Daylight Time, send some times that work for you to [email protected]. Cheers, Jon On Monday, March 3, 2014 6:02:59 PM UTC-5, Yaron Goland wrote: > > BTW, just to a note from the peanut gallery but PouchDB support would > solve all our problems! As Jon mentioned we already use PouchDB as our > primary client. So switching it from 'server' mode to 'client' mode is > beyond trivial. > > > Also, to very briefly explain Thali. Thali is about letting users run > their own services on their own devices. So we would want to let someone > run TiddlyWiki on their phone. This wouldn't be static either. It would be > fully dynamic. They could edit to their heart's content and then using the > CouchDB protocol synch those changes either unidirectional (for a blog like > experience or to people who don't have edit permission) or bi-directionally > (for more of a Wiki style shared editing experience and for keeping their > own devices in sync, e.g. a change you make on your phone should show up on > your tablet, PC, etc.). > > > What Thali adds on top of vanilla CouchDB is our security model and Tor > support. The security model is, as Jon said, public keys. A user is a > public key. Period. That's it. > > > So when say my phone wants to synch some changes in my TiddlyWiki with > your tablet, my phone would open a mutual SSL/TLS auth connection. The > phone would present its public key as a client cert, the server would > present its public key as a server cert and now everyone knows who they are > talking to. Note that everything works the same in reverse. Your tablet > could reach out to my phone in which case the tablet is the client and the > phone is server. This is all done using self signed certs. No CAs. No DNS. > > > We use Tor to handle connectivity since Tor hidden services give us the > ability to penetrate firewalls/NATs and traffic analysis protection as well. > > > There is more to the Thali vision than just the above (remind me to > explain MVC for apps someday or how we exchange public keys) but this is > the TiddlyWikiDev alias, not the Thali alias, so I'll stop now. :) > > > Thanks! > > > Yaron > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
