The simple API calls produced very clean data, but the Email and SMS data isįilled with duplications and gotchas. level 20%,75% -sharpen 0x1 *.jpg to normalize them. 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". The scripts included things like imagemagick calls to clean up the scans of my 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. This thing is still a sprawling, very customized script, but there is some 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. attachments - end known_images << attch end end end return email_collection sort! # unique all the attachments by date email_collection. # email_collection is all the emails and all their attachments email_collection. Method and pry) I wound up with this monstrosity. 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. Understandable API that I could query, organize, and import.Įmails… emails were hard. Simple to import and include in the story. Instagram, Spotify, lolcommits, and scans from my journal were relatively Require 'redcloth' require 'htmlentities' require_relative 'media' class Instapost I wrote a simple class that all my different media classes could inheritįrom… it just implemented Comparable so that all different objects could and eventually made it into the final book. So I turned on lolcommits so I'd have a record What if I couldĬonnect all these different pieces of story and read our relationship right Messages… songs added to our shared Spotify list, posts on our instagramĪccounts… even my journal entries that Sarah hadn't read yet. I could read our story!Įxcept… there were so many other artifacts that were mentioned in the I could read an email, and read the texts that were a Xml file and email files, built some ruby objects, sorted by date, and printed Pretty quickly… I had a really basic ruby script that crawled the SMS-oriented Therefore downloaded all my email to my computer.Īt first I was running this manually… eventually it became part of a makefile:Ĭd ~/Library/Mail/V3/ / & ag -l ' ' | xargs -I ~/src//evantravers/sarahsbook/src/story/email I used OSX's Mail.app to connect to my gmail via IMAP, and I had to do some finagling… eventually found a roundabout way of downloading The seed was planted, and scope grew… exponentially. If I could get the emails inĪ readable format, I could sort them by their date stamp and be able to read our PhoneView can export conversations in xml format. It was all there, but it didn't read like a This worked… but it doesn't read chronologically… first you get all the emailsĪnd then you see all the texts. Our texts, and then just use Preview.app to smush the two together. My first thought was simply to use gmail to print all our emails, and to use Provided me the most joy and satisfaction of anything I've ever made. Surprise her and make an archival PDF of all our emails and texts.Īnd then some scope creep occurred… and I wound up writing the program that Preserve our texts and had print-outs of all our emails… I thought I could When I realized my then-girlfriend was saving all her old cellphones to
0 Comments
Leave a Reply. |