Works with GitHub gists, public GitHub URLs, some dropbox public URLs, public files on Google Drive, and (after authentication) private files on Google Drive.
You can also drag and drop a Profile-*.json file onto the webapp.
Once authorized, you'll see Timeline Viewer as a registered Google Drive viewer when opening .json files. Once you select the Timeline Viewer, it will open in a new tab and load the timeline asset from your Drive.
You can share this URL with any users who have both:
- authorized Timeline Viewer to Drive via the typical Google OAuth flow and..
- have
Editpermission to the Google Drive file
To revoke authorization, visit your Google security permissions.
Run:
yarnornpm iyarn run devornpm run dev- it will open site in browser and run server for you.
Master branch's docs folder is what's published to gh-pages, to simplify deployment.
Auth keys have localhost:8833 whitelisted, so you can hack there.
- Remote debug Chrome on Android (Dev channel or Canary).
- (Verify it works as expected)
- Open devtools on devtools
- Look at
location.hrefand grab the hash out of itcopy(new URL(location.href).pathname.match(/@(\w+)/)[1])
- Pop that into the hash in
docs/index.html
- chrome 79/80/+ (a9b97dff480d5c50843b5190c4d02373a0fc6d84) breaks in our setup. appears to be a decent amount of work to fix.
- chrome 78 (675968a8c657a3bd9c1c2c20c5d2935577bbc5e6 was base commit) is fine
- chrome 70 (81bf34f6bd3784247d7787d879821061c1b7484b) was fine until the removal of custom elements shipped and broke clientside in chrome 80
I sometimes use the archive of https://chromereleases.googleblog.com/ to find a target chrome version.
Cypress is used for integration testing.
To run test just invoke yarn test
- https://www.speedscope.app/ is quite good