duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #02633
Re: Dropbox API key WAS: Fwd: Re: [Question #256351]: Error with dropbox backend after upgrade to 0.7.0
On 18.11.2014 14:31, Michael Terry wrote:
> I'm assuming an individual API key has usage limits? Which, if the dropbox
> backend for duplicity becomes hugely popular, might cause a problem.
afai read it
https://www.dropbox.com/developers/reference/tos
they merely use the keys to block, they feel the access is in violation of their terms - or limit, if it impacts their infrastructure. so ordinary api access controlling.
>
> Why not a combo? Allow #3, but also provide a default key. As for whether
> we use the original key or our own, I don't particularly care. It doesn't
> change where the files are stored, eh, so we can even change it down the
> road if we like.
yes, let's combine. i'll add in some i created, but will allow them to be overwritten by env vars.
..ede
>
> -mt
>
> On 18 November 2014 06:31, <edgar.soldin@xxxxxx> wrote:
>
>> Mike? your vote? ..ede
>>
>> On 14.11.2014 17:05, Kenneth Loafman wrote:
>>> My fault, I removed it. It was the original dev's key.
>>>
>>> I would go with 2 or 3. Slight preference for 3.
>>>
>>> On Fri, Nov 14, 2014 at 7:20 AM, <edgar.soldin@xxxxxx <mailto:
>> edgar.soldin@xxxxxx>> wrote:
>>>
>>> maybe a missing patch from after splitting.
>>>
>>> Ken: what'd you say? three options:
>>> 1. readd the original dev's key
>>> 2. create an own, one of us controls
>>> 3. externalize them as env vars for users to create themselves
>>>
>>> i'd prefer 1. ..ede
>>>
>>>
>>>
>>> On 14.11.2014 14:16, Michael Terry wrote:
>>> > I don't remember intentionally doing that.
>>> >
>>> > On 14 November 2014 06:37, <edgar.soldin@xxxxxx <mailto:
>> edgar.soldin@xxxxxx> <mailto:edgar.soldin@xxxxxx <mailto:
>> edgar.soldin@xxxxxx>>> wrote:
>>> >
>>> > see below.. ede
>>> >
>>> >
>>> > -------- Forwarded Message --------
>>> > Subject: Re: [Duplicity-team] [Question #256351]: Error with
>> dropbox backend after upgrade to 0.7.0
>>> > Date: Mon, 03 Nov 2014 13:21:58 +0100
>>> > From: Edgar Soldin <edgar@xxxxxxxxx <mailto:edgar@xxxxxxxxx>
>> <mailto:edgar@xxxxxxxxx <mailto:edgar@xxxxxxxxx>>>
>>> > To: duplicity-team <duplicity-team@xxxxxxxxxxxxxxxxxxx
>> <mailto:duplicity-team@xxxxxxxxxxxxxxxxxxx> <mailto:
>> duplicity-team@xxxxxxxxxxxxxxxxxxx <mailto:
>> duplicity-team@xxxxxxxxxxxxxxxxxxx>>>
>>> >
>>> > Ken, Mike,
>>> >
>>> > any reason why the API KEY was removed? looks like it is
>> standard to deliver them (albeit obfuscated) with a dropbox client.
>>> >
>>> > ..ede
>>> >
>>> > On 02.11.2014 18:41, cp wrote:
>>> > > Question #256351 on Duplicity changed:
>>> > > https://answers.launchpad.net/duplicity/+question/256351
>>> > >
>>> > > cp gave more information on the question:
>>> > > Ok, I installed 0.6.25 and extracted the app key which
>> really got lost in 0.7.0. I put it in dpbxbackend.py and compiled it, and
>> now it seems to be working again.
>>> > > FTP error remains.
>>> > >
>>> >
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~duplicity-team <
>> https://launchpad.net/%7Eduplicity-team>
>>> Post to : duplicity-team@xxxxxxxxxxxxxxxxxxx <mailto:
>> duplicity-team@xxxxxxxxxxxxxxxxxxx>
>>> Unsubscribe : https://launchpad.net/~duplicity-team <
>> https://launchpad.net/%7Eduplicity-team>
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~duplicity-team
>> Post to : duplicity-team@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~duplicity-team
>> More help : https://help.launchpad.net/ListHelp
>>
>
References