![]() Simple to import and include in the story. Understandable API that I could query, organize, and import.Įmails… emails were hard. I guess we didn't want to let the email conversation die? Whatever.Īfter much travail and experimentation, (made easier thanks to the to_s The first big problem is that every most email replies include the fullĬontent of every email and attachment before it… and Sarah and I hit reply a She replied from different phones and different operating Sarah used multiple email accounts in ourĬonversations. Method and pry) I wound up with this monstrosity. ![]() # email_collection is all the emails and all their attachments email_collection. attachments - end known_images << attch end end end return email_collection sort! # unique all the attachments by date email_collection. Several hundred pages worth of space!!!) Intermission: Architecture I probably could have used some smarter code, but this made sure that only theįirst occurrence of an attachment made it to the final HTML. This thing is still a sprawling, very customized script, but there is some Store, and some simple ruby API calls to get data from Spotify and Makefile and ruby scripts for getting all the emails out of Mail.app's file This is a combination of PhoneView's SMS export, my There is basically a three step process… mostly driven by the makefile. The scripts included things like imagemagick calls to clean up the scans of my Sections about our relationship, and used mogrify -colorspace Gray I used scanbot to grab jpgs of my journals, then cropped manually to the Journals and notebooks that I was photographing with my phone.Īs you can see, it became an obsessive quest to capture the "whole story". level 20%,75% -sharpen 0x1 *.jpg to normalize them. The simple API calls produced very clean data, but the Email and SMS data isįilled with duplications and gotchas.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |