Comment by slightwinder
5 days ago
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 import-mechanism, and the frontend being open for anyone to put their own view onto the data, and maybe work with them.
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.
> Interesting. But this seems to be limited to the supported data-sources?
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!
> Probably true. Do you have examples of what you're thinking of?
Bookmarks, contacts, notes for example, they are usually not time-based but by context, category or whichever organization their usage demands at the moment. They can be time-based in a journal, but usually I do not remember websites or people by the time I encountered them, so I would not search them this way.
The other question is how personal is personal in this project? Are my IMDB-ratings valid data for this? My Ebook-collection? My Steam-account? Those are usually things I would not manage in a timeline or a map, but with different interfaces and features.
Bookmarks are bookmarked at a specific time.
Contacts are already handled as first-class concepts in Timelinize, known as "entities". Entities don't have timestamps, but they have a name and attributes that can be anything, and the relationship between the entity and its attributes can be bounded by time.
Notes are also created and updated/changed at specific times.
> Are my IMDB-ratings valid data for this? My Ebook-collection? My Steam-account? Those are usually things I would not manage in a timeline or a map, but with different interfaces and features.
Could be, if you wanted to timeline those! (Like, when you rated a certain movie. Or when you got or read a certain book. Or when you got a new Steam game.)