Felix - doesn't set the to read flag and populates the title with the url being saved.Twitterrific - sets the to read flag, but populates the title with the text of the tweet 6.Alien Blue - gets the title right, but for some reason sets the private flag.I need to copy the link and add it via Pinbook 5. Zite - has no send to Pinboard functionality built in.Oddly, the iPhone version gives you the option to set the flag yourself, but the iPad version doesn't. Reeder - gets the title right, but doesn't set the to read flag.And they all do it wrong in different ways: Or give me a dialog box so I can do it myself. The correct way to send something to Pinboard is to fetch the url and populate the title field appropriately and set the to read flag. The only problem I have with this "workflow" is with the apps I use. It seems like a waste not too see them in their natural habitat. Getting rid of the clutter that junks up a lot of the web pages on the Internet is useful, but most of the sites I read are actually well designed. Besides, I'm lazy and forgetful so in most cases it just wouldn't get done.Īs a side benefit I can also view the articles as the authors intended them. I don't have to worry about pulling the page into Evernote or something similar for long term storage. And since I pay for the archiving service, the full content of the pages is automatically saved for me. I'm not reading articles with one service and "bookmarking" them with another. The single biggest advantage to this new "workflow" is that everything is in one place. Now that there's finally a good Pinboard app, I have. But in the back of my mind I knew it was there, waiting for me to find a good use for it. Even when I wrote my Pinboard reading list script for Pythonista, I wasn't seriously using it in any meaningful way 4. Like a lot of tech nerds I jumped on Pinboard in the early days. So what, then, is the fourth option? The FreeBSD of read later services, if you will. After all, that wouldn't fit my absurd analogy comparing the three aforementioned services to the three aforementioned operating systems. But not because I've seen the light and embraced Readability 2. And now, for various reasons that I won't bore you with, I've ditched both of them. Each one has its strengths and weaknesses and I've gone back and forth more often than I care to count. Update: Poche linked back from their blog.Since temporally delayed reading became a thing, I've invested a considerable amount of time and effort in both Instapaper and Pocket. My only complaint so far? A lot of the user community only seems to discuss Poche in French (“poche” means “pocket” in French) – certainly something I’m not accustomed to in a largely Anglophone open source community. I haven’t gotten an offline version working (there’s an Android app though, and an export to ePub feature seems likely). It’s nice and lightweight, with a responsive design that works on phones, tablets, and desktops. I even deleted my Instapaper account and switched to using Poche instead. Looking for a self-hosted alternative to other “read later” apps? I’ve been pretty happy with Poche (PHP, demo) so far. ![]() Over time, I started using Instapaper less and less… Pocket seemed like a nice alternative, but I couldn’t really bring myself to switch. Their web app isn’t very mobile friendly either. I used to use Instapaper often, but was turned off by the price for mobile apps and (former?) incompatibility with Android.
0 Comments
Leave a Reply. |