
Release History
2018/01/18 Hide Search Results - Keep embarrassing data from being seen over your shoulder
2018/01/15 People - Aggregate your Contacts into a single Person
2018/11/28 LifeScope now an OAuth2 Provider - Build apps that can work with your LifeScope data
2018/10/29 New Providers
Financial files (manual upload)
Slack
2018/10/08 Upload Locations - Accurately estimate your Events from Google Location files
2018/09/24 New Providers and Sources
Microsoft (Calendar, Outlook, OneDrive)
Uber
Lyft
Google (Photos, Calendars)
2018/08/21 Map View - Explore your history in space as well as time
2018/07/09 Public Sharing of Tagged Results - Curate your stories and share them with others
2018/07/06 Browser Extensions - Make Events, Content, and more from your approved browsing history
2018/06/12 Location Tracking - Get better location estimates for locationless data
2018/06/05 XR View Beta - XR view available in explorer
2018/06/02 New facets - Search through Content and Contacts
2018/05/21 Rebuilt Re-Release - Launch of rebuilt application
GraphQL API
Vue.js-based frontent
Nuxt.js framework for app server
10 providers - Facebook, Google, Instagram, Twitter, Dropbox, Steam, Spotify, Pinterest, reddit, Github
2017/11/15 Beta - First Public Release
Renamed to LifeScope
Tagging system added
New authentication system
Favorited Searches system added
8 initial Providers supported
Major bug fixes
Roadmap
Improve the Connection update process for greater reliability.
Resolve issues with certain endpoints.
Add Where filters and Map View for geolocation searching.
Add more Providers such as Fitbit and Slice.
Limitations
LifeScope indexes plain text data from Providers. Certain rich text data, such as in emails, are currently not indexed.
Images included in emails often require authentication that we just can't get. You'll probably notice a lot of images in emails that don't load right, or at all.
Some Providers only return recent results, such as GitHub only providing data from the last month. If you delete a Connection to one of these Providers and create it again, LifeScope may not be ablt ot restore everything that had previously been collected.
Known Issues
Provider Issues - Some data from certain providers are currently causing issues with our indexing system. If you are having trouble with a Connection updating, please try the fixes below.
Steam
Games Owned - During times of high traffic for Steam, such as weekends, Steam will timeout when LifeScope tries to index Games Owned. This issue usually resolves itself after a day or two.
Spotify
Albums & Tracks - Certain saved Albums and Tracks are causing errors in our indexing system. Please try unselecting Albums or Tracks and then Disable your Spotify Connection. Wait a few seconds and Enable your Spotify Connection. This will usually resolve your issue in less than a day. This will be resolved in future versions.
Reddit
All Permissions - During times of high traffic for reddit, such as weekends, reddit will time out when LifeScope tries to index reddit data. This issue usually resolves itself after a day or two. This will be resolved in future versions.
Comments - Certain Comments are causing errors in our indexing system. Please try unselecting Comments and then Disable your reddit Connection. Wait a few seconds and Enable your reddit Connection. This will usually resolve your issue in less than a day. This will be resolved in future versions.
Dropbox
Files - Certain Files are causing errors in our indexing system. Please try unselecting Files and then Disable your Dropbox Connection. Wait a few seconds and Enable your Dropbox Connection. This will usually resolve your issue in less than a day. This will be resolved in future versions.
Github
GitHub Events - During times of high traffic, such as weekends, GitHub will timeout when LifeScope tries to index GitHub Events. This issue usually resolves itself after a day or two. This will be resolved in future versions.
Other Issues
Initial Connections - On occasion, when adding Providers the initial data collection can be delayed. This will be resolved in future versions.
Connection Names - When creating a Google and Spotify Connection, the generated name is currently not your username but your ID. Please name these accounts yourself. This will be resolved in future versions.