Re: [Duplicity-talk] Deprecation of pydrivebackend

[Jakob Bohm]

Dear Edgar,

See comments inline below


On 2023-06-21 16:52, edgar.soldin--- via Duplicity-talk wrote:
> On 21.06.2023 15:50, Jakob Bohm via Duplicity-talk wrote:
> > Dear Duplicity team,
>
> hey Jakob
>
> > For everyone except the few insiders participating in today's
> > discussion, it is important to ensure that all explanation
> > texts in manpage etc. do not assume facts not provided where
> > that text is.
> >
> > In particular:
> >
> > A. The manpage snippet below refers to "the downloaded JSON", but
> >    not when and where that download would come from.  If this is
> >    part of unchanged text above that sentence then fine.
>
> feel free to contribute a better documentation. nobody here is getting 
> paid and everything is done on a voluntary basis.
That is the standard asshole answer when someone comments on a
proposed change.  In this case I was pointing out that the text
(as quoted)contains a dangling pointer to text not in the quote
and possibly not in the full manpage either.

> > B. Discussions elsewhere seem to assume that everyone using GDrive
> >    does so via a developer account.  Please update text (without
> >    unstated assumptions) for ordinary users, including warning if
> >    this is somehow against Google Policy.
>
> which discussions? i don't see Google policy violations, what do you 
> mean exactly?
Elsewhere in this thread, look around.
> > C. Elsewhere William asks for migration instructions and got a
> >    reply about "If he already did X", which is clearly specific to
> >    William and not a part of any migration recipe that could be
> >    used by others once the old URL Scheme is deprecated as indicated
> >    by the thread subject.
>
> obviously the "migration instructions" as such do not exist. that is 
> why he was referred to what little as documentation is available.
However, William was clearly asking for such migration instruction to be
written cooperatively in the mail thread, but was sidetracked by a reply
entirely specific to William and not to anyone else.  This same thing often
happens in other public fora, where a prototypical sufferer of a common
problem is given a reply that only applies to their particular case, 
then the
useless reply is marked as a solution for all other sufferers.

> > P.S.
> >
> > I happen to be currently using AWS S3 glacier via the boto3 code,
> > and find similar readability problems in that documentation,
>
> same principle applies. if you are dissatisfied you are welcome to be 
> part of a solution. general complaints will improve nothing.
I am stating that I am using the S3 situation as inspiration for
my criticism of theGDrive situation, bug reports and potential
patches for that may or may not come later.

> > hence this mail about general principles seemingly about to get
> > similarly mishandled for Google users.
>
> and again, please handle it better, if you feel inclined to. we are 
> lacking human power all over and it unfortunately shows.
Again I was stating that the AWS S3 situation (which may or may
not have its own forthcomming discussions) is merely inspiration
for why I comment on how GDrive users are being treated. It's
called empathy.

> sunny regards.. ede
>
> > On 2023-06-20 14:36, Chris McGinley via Duplicity-talk wrote:
> > > Thanks Edgar.
> > >
> > > Here are some thoughts on the GDRIVE man page notes (I used the 
> > > Google My Drive approach with a regular user account) -
> > >
> > >     1. The target URL can be found in the downloaded JSON (i.e., 
> > > *GOOGLE_CLIENT_SECRET_JSON_FILE*) as the client_id property.
> > >
> > >     2. *MyDriveFolderID* can be found by observing the URL when 
> > > accessing your destination folder
> > >
> > >
> > >     For example: 
> > > /gdrive://11111111-ab123cd456ef789.apps.googleusercontent.com/mylaptop?myDriveFolderID=xyz987uvw654/
> > >
> > >      * where /11111111-ab123cd456ef789.apps.googleusercontent.com/ 
> > > was found in the downloaded JSON file, /xyz987uvw654/ is the parent 
> > > folder ID found from browsing to Google Drive /backups/ folder, and 
> > > /mylaptop/ is a subfolder of /backups/
> > >
> > >     Also note, if migrating from pydrive, do not point 
> > > *GOOGLE_CREDENTIALS_FILE* at the pydrive credential file; it should 
> > > point to a new (and non-existing) file destination.
> > >
> > >
> > > Best.
> > > Chris
> > > On Tuesday, June 20, 2023 at 07:56:28 AM EDT, <edgar.soldin@web.de> 
> > > wrote:
> > >
> > >
> > > we welcome suggestions to improve documentation. if you provide some 
> > > textual changes based on your experience we will happily include 
> > > them in the man page.
> > >
> > > ..ede
> > >
> > > On 20.06.2023 13:54, Chris McGinley wrote:
> > > > I was able to make the move over to gdrive after sending over my 
> > > response. The DriveID, MyDriveFolderID, and the destination URL were 
> > > not entirely obvious to me from the man page notes; however, with 
> > > some trial and error, I was able to get it all working.
> > > >
> > > > -Chris
> > > >
> > > >
> > > > On Tuesday, June 20, 2023 at 06:41:00 AM EDT, edgar.soldin--- via 
> > > Duplicity-talk <duplicity-talk@nongnu.org 
> > > <mailto:duplicity-talk@nongnu.org>> wrote:
> > > >
> > > >
> > > > hey WIlliam,
> > > >
> > > > how about following the instructions in the man page? :)
> > > > 
> > > https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend 
> > > <https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend> 
> > > <https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend 
> > > <https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend>> 
> > >
> > > >
> > > > good luck ..ede/duply.net
> > > >
> > > > On 19.06.2023 18:53, William via Duplicity-talk wrote:
> > > >  > I have been using pydrive for 6+ years, as documented in the V8 
> > > manual page (https://duplicity.nongnu.org/vers8/duplicity.1.html).
> > > >  >
> > > >  > No mention there that pydrive is not to be used.
> > > >  >
> > > >  > Is there a cookbook instructions on how to convert the pydrive 
> > > commands/setup to gdrive.
> > > >  >
> > > >  > I use DUPLY to drive the backups, so the necessary EXPORT and 
> > > file specs are in the DUPLY conf file.
> > > >  >
> > > >  >
> > > >  > On 6/19/23 11:59, Kenneth Loafman via Duplicity-talk wrote:
> > > >  >> Hi all,
> > > >  >>
> > > >  >> Does anyone use the pydrive backend anymore? This would be a 
> > > URL schema of "pydrive://", "pydrive+gdocs://" or "gdocs://"
> > > >  >>
> > > >  >> It was replaced with the gdrive backend a couple of years 
> > > ago.  Before we deprecate it I was just trying to find out if there 
> > > was anyone still using it. And how?
> > > >  >>
> > > >  >> ...Thanks,
> > > >  >> ...Ken
> > > >  >>
Enjoy

Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded