#tanteknot just risk, likely outcome - given past experience with others who have done so
#aaronpkbut it was more important for me to have my content on my site and be comfortable sharing my site than it was to set it up right the first time
#tantekproblem is that by copying from Twitter, it stops being *your content* and starts being *their content*
#tantekso you didn't really achieve that, unfortunately
#tantekit's why pushed so hard to get the tantek.com -> twitter connection working as part of the first version of Falcon that I installed/ran.
#tantekand now I have a local archive of my old tweets that I can batch import whenever I get around to writing a batch import script
#tantekall of which were published and downloaded *before* their TOS changes, so screw those changes, they don't apply retroactively (good luck if they try to make them do so)
#aaronpkmy next task is to get aaronparecki.com -> twitter working properly, with good auto-shortening rules and auto-linking, etc. I didn't have a place to work on that before, and now with my new site I do.
#tantekanyway - because of the looming TOS changes (are they effectively immediately? or do they take effect very soon?), probably best to make POSSE a priority
#tantekand we can also tell people to CC license their tweets
#aaronpkwhat's the best license for that? cc-by-sa?
#tantekwhich will also trump Twitter's API TOS, since the owner of the content is creating a license for their content that goes beyond what Twitter allows