> The bottom line is that I am strongly recommending that 1Password users not be early adopters of this.
Some good points that I did not consider before I enabled 2-factor authentication for [Dropbox](http://db.tt/bl7yQBc)[^aff]. I hope I do not regret my decision.
[^aff]: Affiliate link where I get slightly more Dropbox space if you sign up.
Last night, [Drafts for iPhone](http://click.linksynergy.com/fs-bin/stat?id=r*bqlTuiXSo&offerid=146261&type=3&subid=0&tmpid=1826&RD_PARM1=http%253A%252F%252Fitunes.apple.com%252Fus%252Fapp%252Fdrafts%252Fid502385074%253Fmt%253D8%2526uo%253D4%2526partnerId%253D30)[^aff] got an update to 2.0. It has a [bunch of new features](http://agiletortoise.com/blog/2012/8/20/drafts-20-and-drafts-for-ipad-10.html), including the ability to capture “links” to things like phone numbers and the ability to append to Dropbox files. That, however, was not the only Drafts related news. [Drafts for iPad](http://click.linksynergy.com/fs-bin/stat?id=r*bqlTuiXSo&offerid=146261&type=3&subid=0&tmpid=1826&RD_PARM1=http%253A%252F%252Fitunes.apple.com%252Fus%252Fapp%252Fdrafts-for-ipad%252Fid542797283%253Fmt%253D8%2526uo%253D4%2526partnerId%253D30) was also released and there is [Simperium-based](http://simperium.com/) sync between the two versions[^note]. I am just starting to use the new features, but there have already been write-ups from [Gabe Weatherhead at MacDrifter](http://www.macdrifter.com/2012/08/drafts-app-update.html), [David Sparks at MacSparky](http://macsparky.com/2012/8/drafts-for-iphone-and-ipad), and [iMore](http://feedproxy.google.com/~r/TheIphoneBlog/~3/4MmtqsQwuQw/story01.htm).
[^aff]: Affiliate Link (as are all links to the Drafts apps in this post.)
[^note]: I have only used the sync for a short time, but, so far, I have been impressed. If this is what we can expect from Simperium-based syncing, then I think a number of iOS developers might look into moving to that. I hope [Instacast](https://johnkiv.us/2012/08/06/the-state-of-instacast-syncing/) is next.
MPlayerX is the latest app to leave due to the sandboxing restrictions:
> MPlayerX will lose so many features if it adopted Sandboxing, it could not load the subtitle automatically, it could not play the next episode for you automatically, it could not save the snapshots to the place where you want to, etc. Without those features, MPlayerX were just another lame Quicktime X, which I could not accept.
I initially took a wait and see approach about the sandboxing restrictions, but I am having a hard time not taking a wholly negative view of them the more time goes on.
(via [Michael Tsai](http://mjtsai.com/blog/2012/08/18/mplayerx-leaving-the-mac-app-store/))
What bothers me most about [Twitter’s upcoming API changes](https://dev.twitter.com/blog/changes-coming-to-twitter-api) is Twitter’s apparent claim to our content. Not only is Twitter a service that was built upon the backs of third-party developers and their associated apps, but it is also a service that relies exclusively on content generated by its users[^facebook]. Now, after users have been piping their content into the service for years, Twitter has decided to restrict the way that content can be viewed on the other end.
The argument for why this is problematic is very similar to the argument that has been had over various “read later” applications. Content controllers were upset because these applications stripped out the formatting and marketing associated with their content. Their opposition was countered by saying that, essentially, these read later sites are simply “text-only web browsers” and information on the web has always been viewable via such browsers. Through these read later applications, any content, no matter what platform posted or formatted it, can be viewed in a manner preferred by the end user.
Twitter aims to remove this ability with its “Display Requirements.” It prevents end clients, essentially browsers of Twitter’s user’s content, from displaying content generated by the users in a manner that the users would prefer[^browser]. This does not sit right with me. It is far too much control for a company to try exert over content that it did not create. The blocking of third-party clients is just one symptom of this much larger issue of control.
[^facebook]: One might argue that Facebook is similar in that it is built exclusively on user generated content. I would counter by saying that Facebook at least provides some extra value in its profiles, events, photos, etc… that is not available on Twitter. Stated another way, Facebook is more than simply the content of user’s status updates.
[^browser]: Twitter is technically limiting access to its API, not to various pages on its website that display the information. I feel that this does not change my argument. The exact technical method by which Twitter broadcasts their information does not change that it is essentially a broadcaster of information on the web.
What a strange story. There seemed to be a ton of disinformation about it earlier this afternoon. The current party line is that “both its game and desktop services ‘will continue to operate.’ That includes ‘all of OnLive’s apps and devices.'” Good news, but I am hesitant to re-up my subscription when there is this much turmoil around the future of the service.
I agree with their conclusion. I use [Screens](http://click.linksynergy.com/fs-bin/stat?id=r*bqlTuiXSo&offerid=146261&type=3&subid=0&tmpid=1826&RD_PARM1=http%253A%252F%252Fitunes.apple.com%252Fus%252Fapp%252Fscreens-vnc-control-your-computer%252Fid400012962%253Fmt%253D8%2526uo%253D4%2526partnerId%253D30)[^aff] and love it.
[^aff]: Affiliate Link
Yesterday [Twitter announced upcoming changes to their API](https://dev.twitter.com/blog/changes-coming-to-twitter-api) and there has already been a ton of brilliant writing about the changes. For a breakdown on the changes, I recommend either [Marco Arment’s posting](http://www.marco.org/2012/08/16/twitter-api-changes) or [Dieter Bohn’s writeup on The Verge](http://www.theverge.com/2012/8/16/3248079/twitter-limits-app-developers-control). There is also commentary from [Ben Brooks](http://brooksreview.net/2012/08/twitter-bullshit/), [Matthew Panzarino](http://thenextweb.com/twitter/2012/08/17/twitter-4/), [Dan Frommer](http://www.readwriteweb.com/archives/why-twitter-just-pushed-developers-aside-to-secure-its-future.php), and [MG Siegler](http://parislemon.com/post/29582867630). Over at Daring Fireball, John Gruber has two posts, [one in response to Anil Dash](http://daringfireball.net/linked/2012/08/16/dash)[^dash] and one that summarizes his interpretation of the changes, entitled [Twitter to Client Developers: Drop Dead](http://daringfireball.net/linked/2012/08/16/twitter-drop-dead):
> So Klout, which is utter vainglorious masturbatory nonsense, that’s OK. But services like Storify and Favstar, which are actually useful and/or fun, those are no good. And don’t even get me started on Twitter turning against client apps.
The whole thing makes the development of [App.net](http://app.net) look even more important than it did just 24 hours ago.
[^dash]: [Anil Dash’s original article.](http://dashes.com/anil/2012/08/what-twitters-api-announcement-could-have-said.html)
This week’s episode of This Week in Google starts off with 30 minutes or so of the panel talking with [App.net’s](http://app.net) Dalton Caldwell. The interview is very insightful as to App.net’s future. I was unaware of Mr. Caldwell’s vision that App.net would be infrastructure focused (i.e. they’ll be an “API company.”) In fact, he was torn about even producing the [alpha.app.net](http://alpha.app.net) website because he wanted third-party clients to handle that and he did not want people to think he was simply making a Twitter clone. The whole interview is quite good and definitely worth a listen if you are interested in App.net or the social web.
I kind of want to go to Dunkin Donuts just to try this[^fn1].
[^fn1]: Okay, and to have a few delicious donuts.
I do not see the benefit to using Chrome over Safari on iOS, however, I hope more developers provide this functionality. It is a positive development for the iOS ecosystem when developers can find some way to work around a lack of configurability in a particular area.
[Ben Brooks](http://brooksreview.net) recently linked to a few tips about [how to get iCloud in your Finder sidebar](http://brooksreview.net/2012/08/icloud-tip/). The problem I have with those methods is that they create a link to the iCloud folder directly and that folder contains horrible, ugly-to-look-at directory names[^fn1]. My alternative is to create a folder called “iCloud” somwehere else, fill that folder with nicely named symbolic links[^fn2] to the applications I use, and then add that folder to the sidebar. Here are the current contents of my iCloud folder with the symbolic link command[^code] I used to create each one:
* Byword
ln -s ~/Library/Mobile\ Documents/N39PJFAFEV~com~metaclassy~byword/Documents/ Byword
* iA Writer
ln -s ~/Library/Mobile\ Documents/74ZAFF46HB~jp~informationarchitects~Writer/Documents/ iA\ Writer
* Numbers
ln -s ~/Library/Mobile\ Documents/com~apple~Numbers/Documents/ Numbers
* Pages
ln -s ~/Library/Mobile\ Documents/com~apple~Pages/Documents/ Pages
* PDF Pen
ln -s ~/Library/Mobile\ Documents/7PKJ6G4DXL~com~smileonmymac~PDFpen/Documents/ PDF\ Pen
* Pixelmator
ln -s ~/Library/Mobile\ Documents/4R6749AYRE~com~pixelmatorteam~pixelmator/Documents Pixelmator
[^fn1]: Not to mention that you have to click into the “Documents” sub-folder in each directory to actually get to your documents
[^fn2]: If you need more information on symbolic links, [this tutorial from Mac OS X hints](http://hints.macworld.com/article.php?story=2001110610290643) is a good place to start.
[^code]: Depending on your screen width, the command might be longer than you are actually seeing on the page. Combine that with hidden scroll bars in Mac OS X and you might not realize that the command extends beyond what is plainly visible. Just keep that in mind if you are copying and pasting the various commands from the webpage into a terminal window.
My fiancé downloaded this late last night. Her initial impressions were positive.
> We will be making this course, Brown’s upper-level programming languages offering, available for free on the Web. People anywhere are welcome to view the lectures, read the materials, and do the assignments.
> The on-line version does not offer credit from Brown; but those who successfully complete it can get recognition of this directly from the instructor. In particular, because we anticipate some people following the course will be busy professionals, we will offer three levels of recognition:
I am really tempted to do this. I probably do not have time to pull it off, but I am really tempted.
(via [Michael Tsai](http://mjtsai.com/blog/2012/08/13/brown-csci-1730/))
Command-Shift-I
(via [Ben Brooks](http://hints.macworld.com/article.php?story=20120809074726545))
Really solid episode of The Talk Show this week. 2 hours and 20 minutes of John Siracus and John Gruber talking about all things Mac-y, Geek-y, and Tech-y.
Ben Brooks on TextMate 2 going open source:
> Unlike so many other people, I haven’t switched to Sublime Text 2 or Chocolat 1 — no I decided to jump fully into Coda 2 and Writer. I haven’t missed TextMate since making the change a while back, but I always held out hope to switch back to it.
I’m in his camp. I use [Coda 2](http://itunes.apple.com/us/app/coda-2/id499340368?mt=12&uo=4)[^aff] for web and most programming work and [iA Writer](http://itunes.apple.com/us/app/ia-writer/id439623248?mt=12&uo=4) for almost all of my writing.[^bb] I, however, do not have any desire to switch back to using just a text editor.
[^bb]: I don’t always use a text editor, but when I do, I use [BBEdit](http://itunes.apple.com/us/app/bbedit/id404009241?mt=12&uo=4).
[^aff]: Normally I use affiliate links, but that does not feel right when I link to someone else’s content, especially when Ben Brooks [has things behind a paywall](http://brooksreview.net/2012/07/new-tbr/). Therefore, these links are all direct Mac App Store links.
It looks nicer and seems, during some initial use, to run faster.
[Downcast](http://click.linksynergy.com/fs-bin/stat?id=r*bqlTuiXSo&offerid=146261&type=3&subid=0&tmpid=1826&RD_PARM1=http%253A%252F%252Fitunes.apple.com%252Fus%252Fapp%252Fdowncast%252Fid393858566%253Fmt%253D8%2526uo%253D4%2526partnerId%253D30)[^aff] has been chipping away at the [issuses I had with it](https://johnkiv.us/2012/07/20/making-the-best-of-the-current-ios-podcast-player-options/). This time, they have reduced the amount of time necessary to refresh the feed list by having the feeds auto-update via geo-fencing[^fn1]. Unfortunately, Downcast still appears to suffer from the [battery drain issue](https://johnkiv.us/2012/07/20/making-the-best-of-the-current-ios-podcast-player-options/) that was one of the show-stoppers for me previously.[^downcast] If Downcast were to get this fixed, it would probably be my sole podcast app.
[^aff]: Affiliate Link (as are all app links in this post.)
[^downcast]: Talking with Downcast support, it appears that this battery drain is likely a result of the iCloud syncing. In fact, the support representative encouraged me to try to use the app without syncing turned on to see how it performs. Maybe it is time for Downcast to follow the lead of [Instacast](http://click.linksynergy.com/fs-bin/stat?id=r*bqlTuiXSo&offerid=146261&type=3&subid=0&tmpid=1826&RD_PARM1=httpThursday094094itunes.apple.com094us094app094instacast094id420368235094mt?8?o?4PMartnerId?30) and [explore some other syncing alternatives](http://vemedio.com/blog/posts/state-of-instacast-sync).
[^fn1]: It is very similar to the way [Instapaper does it](http://blog.instapaper.com/post/24293729146)
There’s a [full list of changes on their blog](http://www.pixelmator.com/blog/)[^note], but my favorite is the new alignment guides:
> Building precisely aligned image compositions is now short work in Pixelmator 2.1, with the new smart Alignment Guides. This new feature lets users position objects with pinpoint accuracy and build compositions quickly by using individual objects or image elements. The Alignment Guides gracefully appear and disappear onscreen as they are needed, while Object Spacing automatically shows when objects are equally spaced on the canvas.
[^note]: Post link is an affiliate link.
Finally.