124 karma · joined February 7, 2024
For me it is: Nike Run Club, Firefox, Omnivore, YouTube, Spotify and Apple Health.
For example, Nike Run Club offers some stats on the app but I’d like to be able to do more. Spotify shows me I follow this artist but I’d like to know since when have I followed them. YouTube has my watch history but I’d like to be able to process what kind of content I was consuming during a certain time period.
Would you consider it a risk even if the app was open source?
You are right about switching to an open service! I am prioritising such services. Like Omnivore[1] is for bookmarking.
[1]: https://omnivore.app
So far I have worked out the connectors for a handful of services (prioritising those with local data and public APIs) and a general-purpose database schema to store and query the data.
I have an existing app (made using the Tauri framework in Rust + Svelte) that acts as a local file search engine that I hope to use as a starting point.
However, this isn’t intended to be the “ultimate” app with your entire digital footprint logged to a database. It’s supposed to have a few meaningful connectors to services that people would actually be interested in. And a lot of these services offer public APIs as well (Spotify, Omnivore, Strava). Plus, browser history and local files (like markdown notes) are easy to access.
Do you think this reduced scope would be of any interest to you?
Although the benefit of using a static site generator like Hugo is the ability to short codes to reuse code snippets (like embedding videos or images). But that can wait - getting five posts out first is important!
For working with embeddings on desktop, would you recommend using a vector DB? Or can we get away with SQLite (or Isar)?