If you're patching client IDs into a program from the debian/ directory, surely it would be just as easy to patch them into the service file as into the source code though, right?
As for Ubuntu One OAuth code, I agree that it's OAuth code is weirdly non-standard (I filed bug 978719 about it way back). However, I'm not sure how your proposed API changes would help with U1: while it isn't using a fixed consumer key and secret, those values are assigned as part of the authorisation process rather than being passed in by the application. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554040 Title: Allow hiding authentication data in scope binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1554040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
