3 ms·

Oh wow that's awesome. This sounds a lot like my project, in philosophy and practice: https://github.com/NickSto/life-browser https://github.com/NickSto/life-br

Oh wow that's awesome. This sounds a lot like my project, in philosophy and practice: https://github.com/NickSto/life-browser https://github.com/NickSto/life-browser I've focused on Google Takeout exports so far. Only gotten Hangouts and Voice working at this point. I feel like all of us need to be working on a common codebase for all these parsers. I just found out a week ago that the Hangouts format changed significantly and totally broke my parser (which I actually adapted from https://bitbucket.org/dotcs/hangouts-log-reader/ https://bitbucket.org/dotcs/hangouts-log-reader/)

karlicoss 6y ago
Thanks, I'll check it out! Yep, agree about the common codebase, that's why I'm trying to keep everything modular and thinking a lot about it. I describe this bit of my philosophy/design here [0]. I've only written parsers/exporters if I haven't found any (or any that wouldn't be a complete pain to adapt) so far. Google Takeout processing is a part of HPI, but I was going to extract it in a separate repository, so perhaps we both could benefit from it. [0] https://beepb00p.xyz/exports.html#bindings https://beepb00p.xyz/exports.html#bindings
- anantse 6y ago
  Hmm it's interesting how diverse the data sources people are actually using, but there's definitely overlap. I also have tried searching before I write anything myself, and often I find something (both Hangouts and Voice were like that). But it's funny how my use case is always significantly different, so I end up having to put in plenty of work on top of what they've already done. I suppose one thing that could be universally useful is common documentation about what we've discovered in reverse-engineering the formats. I often have extensive notes like this: https://github.com/NickSto/life-browser/blob/master/drivers/hangouts/hangouts.txt https://github.com/NickSto/life-browser/blob/master/drivers/... I remember finding a wiki about this a while back but I can't find it right now..

karlicoss 6y ago

Thanks, I'll check it out! Yep, agree about the common codebase, that's why I'm trying to keep everything modular and thinking a lot about it. I describe this bit of my philosophy/design here [0]. I've only written parsers/exporters if I haven't found any (or any that wouldn't be a complete pain to adapt) so far. Google Takeout processing is a part of HPI, but I was going to extract it in a separate repository, so perhaps we both could benefit from it. [0] https://beepb00p.xyz/exports.html#bindings https://beepb00p.xyz/exports.html#bindings

anantse 6y ago
Hmm it's interesting how diverse the data sources people are actually using, but there's definitely overlap. I also have tried searching before I write anything myself, and often I find something (both Hangouts and Voice were like that). But it's funny how my use case is always significantly different, so I end up having to put in plenty of work on top of what they've already done. I suppose one thing that could be universally useful is common documentation about what we've discovered in reverse-engineering the formats. I often have extensive notes like this: https://github.com/NickSto/life-browser/blob/master/drivers/hangouts/hangouts.txt https://github.com/NickSto/life-browser/blob/master/drivers/... I remember finding a wiki about this a while back but I can't find it right now..