Interesting. But this seems to be limited to the supported data-sources? No generic format to build your own sources? Also, why the focus on a timeline? Not all personal data or tasks are time-related. So is this more about personal data, or a timeview on personal data? If you want to have collaboration on this, maybe think about splitting it into backend and frontends. With the backend being the storage, and it's im…
Data sources are extensible, they basically just need to implement 2 methods: https://pkg.go.dev/github.com/timelinize/timelinize@v0.0.24/...
> No generic format to build your own sources?
I'm designing an import API that will let any script or program push data to the timeline.
> Also, why the focus on a timeline?
Seemed to make the most sense.
> Not all personal data or tasks are time-related.
Probably true. Do you have examples of what you're thinking of?
> If you want to have collaboration on this, maybe think about splitting it into backend and frontends. With the backend being the storage, and it's import-mechanism, and the frontend being open for anyone to put their own view onto the data, and maybe work with them.
That's how it is right now; it's a client-server architecture. It has a CLI and a JSON API so you can build your own front-ends.
> Maintaining personal data has demand here, but so far there is no real unified project catering to a broad range of services and different types of data. So there is a space to fill and a community to build IMHO.
I agree, this is a huge void that needs to be filled!