From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tommy Kelly Subject: Re: MobileOrg on DropBox for Teams Date: Sun, 28 Nov 2010 09:54:37 -0600 Message-ID: References: <1290886276.2657.1407442493@webmail.messagingengine.com> <1290955261.27101.1407521573@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=56878 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PMjac-0003ur-Ce for emacs-orgmode@gnu.org; Sun, 28 Nov 2010 10:54:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PMjaa-0007ya-4R for emacs-orgmode@gnu.org; Sun, 28 Nov 2010 10:54:58 -0500 Received: from lo.gmane.org ([80.91.229.12]:50837) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PMjaZ-0007yB-N0 for emacs-orgmode@gnu.org; Sun, 28 Nov 2010 10:54:56 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PMjaX-00008h-Ux for emacs-orgmode@gnu.org; Sun, 28 Nov 2010 16:54:53 +0100 Received: from cpe-70-112-150-104.austin.res.rr.com ([70.112.150.104]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 28 Nov 2010 16:54:53 +0100 Received: from tommy.kelly by cpe-70-112-150-104.austin.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 28 Nov 2010 16:54:53 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org "Richard Moreland" writes: > ... I'm not sure how your account sharing is setup: if you are all using > the same credentials, you will probably run into trouble. ... > ... > The other option is to let each user have their own Dropbox account and > simply share folders from a master account to each person. DropBox For Teams is a third option[1]. Teams gives you a block of shared space and a set of accounts (each with their own authentication credentials) that share that space. The entry level is 350G of space and five accounts. >From an authentication point of view, it acts just like each user having their own DB account. However, the difference is that with Teams, everyone has access (assuming the sharing allows it) to the full 350G of space[2]. Actually ... I've just realized that there's no problem. Every user *can* have their own MobileOrg at the DB root, provided they don't share it with anyone else. In fact, even if they did share it, it would merely appear in someone else's view with a number appended to the name (just as happens right now if there's already a MobileOrg folder in DB when MobileOrg first starts). But then I don't know what the iPhone client would do if it spotted multiple genuine MobileOrg "(n)" folders at the DB root. But I think the general solution -- in a DB for Teams environment -- would be to recognize that the entire DB space is being shared among separately authenticating users, a la a set of unix home directories. I'm willing to bet that as Teams develops (it must still be in beta, hence it not being advertized) its multi-user-ness will become more obvious and demanding of app support. OK - conclusion. No change needed on anything right now. It's all good[3]. Tommy [1] We've been using it for over a year now but AFAICT it's still not being advertized. [2] Compare an entry-level DB for teams -- five users, 350G of space -- with five completely individual accounts, each with 70G. If no one is sharing anything (and DB is being used by each user merely only to sync personal data among multiple machines) then they're pretty much the same thing, assuming an even share of the 350G in the Teams case. But when sharing, Teams is better. With Teams, the maximum shared space is 350G, whereas with the individual accounts the maximum is still only 70G. [3] But if the Teams edition is to be embraced, then making the location of the MobileOrg files controllable *from within the setups of both emacs and the mobile device* (as opposed to after setting up, via a move of the folder) is probably advisable.