Actually, the chrome 'sync services' aren't available because the Pkgfile in opt/chromium doesn't build with api keys. You can generate/build with these keys using the following instructions[1]. I believe there's also an option to provide the keys at runtime. That should fix your problems with syncing. Here's my Pkgfile[2] for chromium. It's heavily based on the arch PKGBUILD, but uses my own api keys and enables some other things widevine and flash. BTW, the readme of opt/chromium also has warnings about the lack of features due to Google API access in the NOTES section. 1 http://www.chromium.org/developers/how-tos/api-keys 2 https://github.com/maraku/crux-ports/tree/master/chromium On Wed, Jul 20, 2016 at 05:47:18AM +0000, Alex Matviychuk wrote:
So the implication then is that this was broken on Google's end rather than some issue with the crux build?
Not sure why they wouldn't just harvest my info on crux just as easily as on other platforms. Is anyone running into this on non-crux builds of chromium?
On Tue, Jul 19, 2016, 10:31 PM Thomas Penteker <tek@serverop.de> wrote:
Hello,
maybe this is related to Them changing the Terms of use wrt privacy and surfing behavior.
https://mobile.twitter.com/phlsa/status/754337623964053504
Best regards, Thomas
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux