Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi David,

On Sun, Jan 25, 2015 at 04:27:12PM +0000, David Gerard <dgerard@gmail.com> wrote:
I want to write a blog post saying how I did
this - before I do so, will there be a problem putting it up with that
secret (which is presumably the one in every TDF build)? Should I use
another one? If so, how do I obtain another one?

Even if it's not hard to get the TDF secret from the binaries, it's not
fair to advertise them. The more widely it's known, the more probable
that someone will reuse it in some nasty application, then the
TDF-registered app ID will get shut down, making LibreOffice users sad.

See here on how to obtain your own ID:

https://developers.google.com/drive/web/about-auth

If you write a blog post about this topic, that's great, but I guess
best to not mention any ID explicitly, they are kind of a secret anyway.

Regards,

Miklos

Attachment: signature.asc
Description: Digital signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.