Why I’m sticking with the old Flickr Uploadr

Software

I’ve been on Flickr since October 2005, and I’ve typically used my Flickr account as a way to showcase: a) what I consider some of my best efforts, b) specific photography projects — like Little Light Left, Inception: architectural visions, and 1:60 — and c) geeky photo albums to document something in particular, like IBM WorkPad, The return of the 5.25″, Carry on or Cameras. Over the course of these past ten years (!) I’ve used Flickr constantly but I’ve never ‘mass-uploaded’ entire batches of photos and I tend to not follow other Flickr members who do so. I prefer selection. Since the start, I’ve also tried to be meticulous, and that’s why for me uploading two or three photos isn’t a casual or a quick 1‑click task. It takes some time, as I want to enter tags, a proper title (and sometimes description), and the photos have to be filed in one of more albums and uploaded to the relevant groups I’m subscribed to.

I’ve always found the uploading experience to be lacking, no matter the tool, whether it was the Flickr’s Web interface or third-party applications. One exception was possibly 1001, a nice application by Adriaan Tijsseling, but development has ceased a while ago. In recent years I’ve come to rely on the first-party client Flickr Uploadr, which, while not having a particularly attractive UI, has been doing the job.

Old Flickr Uploadr

As you can see, it’s easy to add one or more photos, enter the necessary information, and upload. A couple of things I would have added, functionally, were auto-completing tags based on the tags you had already entered in the past, and the possibility to upload the photos to the Flickr groups you’re subscribed to.

As I said, not a fancy application, but useful and quite compatible with my kind of workflow.

Meanwhile, the Upload page of Flickr’s Web interface has got better since the latest site redesign has sedimented. I’ve been using it more frequently in the past months — it’s reliable, it offers tag auto-completion, it lets me upload to groups, and it’s generally what the Flickr Uploadr app should be.

The new beta Uploadr

A few days ago, exactly by visiting the Flickr Upload page on the Web, I noticed the suggestion to download the new Flickr Uploadr app. Since the previous version (judging by the file info pane in the Finder) was last updated in 2009, I downloaded the new one eagerly, expecting the kind of improvements displayed on the Web interface. I installed the app in the Applications folder (as the disk image itself suggests when you open it) and that meant of course overwriting the old version. And when I launched the new Uploadr, I almost immediately regretted installing it.

New Uploadr 1

First bad sign: “Upload automatically”. I said to myself, Of course I imagine I’ll still be able to select the photos I want to upload, and do whatever the old version let me do.

New Uploadr 2

…And this second screen gave me hope: “On the next screens, you can choose what to upload.”

But apparently, my choices are limited to folders of photos:

New Uploadr 3

No, I don’t want the Uploadr to automatically upload photos I may add to these places. I usually save screenshots on the Desktop, and I take a lot of screenshots, so no, unchecked. Same for the other folders: I can’t have this app upload whatever I put there. I still hope that the next screen…

New Uploadr 4

Upload my iPhoto library,” really? Everything? No fine-grained options? But I don’t use iPhoto anyway, so I uncheck the option and still hope that the next screen will take me to an interface where I can select the photos I want to upload.

New Uploadr 5

Tough luck. There’s nothing here. Everything is supposed to be automatic. The new Flickr Uploadr has become a mass uploader. But I decide to play along, for the sake of experimentation, and create a Flickr Up test folder. I want to see if everything is really automatic, or if I still have the possibility to perform edits and add information to the photos I place in the folder.

New Uploadr 6

 

New Uploadr 7

But no, the photo is uploaded right away. No information is added to the photo, and once I visit my Flickr page, the Photo Title field is auto-filled like this (surely a bug):

Thanks Flickr Uploadr!

Even worse, the Uploadr has automatically created a Flickr Up test album with the title of the folder I created for this test.

Sticking with the old version

Perhaps I’m not a typical Flickr user or I don’t belong to the current target audience, but my first impression of this experience is, How can people be okay with this type of automation? Uploading from the iOS app isn’t the greatest experience either, but at least it’s more thoughtful — you have the opportunity to give a title to your photo, do some basic editing, share it, geotag it and file it into one or more albums. In the new Flickr Uploadr the only level of control you have is selecting source folders of photos, and that’s it. This new version of the Mac client is significantly dumbed down, in my opinion, and it seems to be aimed at people who either love to flood their photostreams with dozens of photos at once or use their Flickr account essentially as a backup and don’t really care about showing their photos in a meaningful way. 

I have recovered the old Flickr Uploadr from a previous Time Machine backup and will keep using it until it works. If you’ve been using it the way that I do and have a similar upload workflow as mine, I suggest you avoid ‘upgrading’ to the new Uploadr and wait — maybe new features and more fine-grained options will be added in the future. I believe you can even keep the two versions together in the Applications folder — to write this article and take screenshots I kept the two apps by renaming the older version Flickr Uploadr 2009.app — so you can experiment and maybe have the best of both worlds, so to speak. As for me, I have already deleted the new version.

iPad, text editors, workflows, and a frustrated digression on simplicity

Tech Life

I have greatly enjoyed Federico Viticci’s iPad Air 2 Review: Why the iPad Became My Main Computer and I really think it’s required reading for those who still doubt the power of the iPad as a portable computer.

As I was reading his article, I stopped and thought: what Federico and I do is not that different. I’m a writer (and I’m not into podcasting, so I don’t even share that kind of workflow and don’t need podcasting hardware and software), I do a decent amount of photo-editing, I read a lot, I manage email, I take a lot of notes, I’m on Twitter and App.net, I have my selection of RSS feeds to follow… you get the picture. I stopped and thought: then why isn’t the iPad my main computer as well? Why can’t I go iPad-only, too?

I ‘get’ the iPad, I love using my good old third-generation model, and I really agree with Viticci’s conclusions — the iPad can be an empowering and liberating device. So what’s wrong in my case? What is it that doesn’t work?

A certain workflow fragmentation perhaps (and my workflows are nowhere as complex as Federico’s!), and the need to have an eye on multiple open windows and files, especially when I’m writing fiction. 

Speaking of writing, here’s a recent anecdote. I’m in my home office, sitting at my MacBook Pro in desktop configuration, writing an episode of my novel, Low Fidelity (more information: here and here). When I’m writing fiction, my preferred tool is TextEdit, I write in rich text format, all my files are RTF. Nothing fancy, but I need to see the formatting. I need to see the parts in italics, bold, in smaller font size, that sort of thing. I can’t write fiction in Markdown or HTML like I do when I’m writing articles to be published online or on my Vantage Point magazine.

My upstairs neighbours have been doing renovations for a while now, and in the late morning they start making noises that prevent me from concentrating, so these days I’m practically forced to continue my work somewhere else. I don’t feel like disconnecting everything to bring the MacBook Pro with me. Nor do I feel like taking one of my PowerBooks. I want to travel light, so I take a small backpack, put the iPad 3 and the Incase Origami Workstation inside, then a few pens and notebooks, and I’m off to the library. Of course, I’ve saved my work in a dedicated Dropbox folder, so I’ll be able to easily resume writing from the iPad.

Once arrived, I set up the Origami Workstation, wake the iPad, and from there — at least theoretically — it’s just a matter of picking a text editor among the few I’ve purchased and— oh wait… None of them will handle my RTF files saved with TextEdit. Not Phraseology, not iA Writer, not Daedalus Touch (my favourite of the bunch), not WriteRight… Then there are apps like UX Write and GoodReader which at least let me read the RTF files I need, but to actually continue my work right where I left it, I have to copy what I wrote, paste it into a new text document (say, in Daedalus Touch) in the same Dropbox folder, and take it from there. And write in plain text, or Markdown, which may be fine with you, but it’s hugely annoying for me.

Sure, if I had to work on the iPad only, or if my setup were iPad-first, Mac as a secondary device, instead of the other way round, my approach would probably be different, and I would perhaps choose my tools more carefully. Still, I would need to use a pleasant application that lets me write in rich text format directly (no, I don’t want to write in Markdown and check the preview all the time). When I publicly expressed my frustration, some suggested I use Microsoft Word for the iPad, or Apple’s Pages both on the Mac and the iPad. These solutions, however, strike me as a bit overkill for my needs, and frankly it’s also a bit silly that I have to compromise and resort to tools I don’t like using just because they do the job (I also don’t want to use iCloud for syncing — it’s a long story that I’ll leave for another article, maybe). I did that back in the 1990s and I hated it.

It looks like I’m whining, but bear with me. I’m not saying that the iPad is at fault here, because it’s not. I’m not saying there’s a shortage of iOS text editors, because there is not. The iPad and my frustration in having to change my workflow on the fly because of an unexpected snag are just triggers that have led me to another, deeper frustration — that despite all the talking about simplifying things, about solutions to eliminate friction, technology is still a complicated affair. And in a few places, unnecessarily so.

One of the problems is that apparently we can’t agree on what simplicity is or should be. Let’s stick to iOS text editors. My idea of simplicity, as one who has used computers for writing for about thirty years, is that today we should be able to write using a completely WYSIWYG (What You See Is What You Get) interface. Rich text format shouldn’t be a problem given the hardware capabilities of today’s machines. Instead we have to deal with ‘code’ and plain text as if we were still using WordStar under DOS. I have nothing against Markdown per se, but I’m starting to get tired of this minimalist trend in writing tools, sadly endorsed by more than a few tech-savvy writers. Simplicity here, for me, is clicking/tapping a button and seeing the text in bold right away, or in italics, or neatly organised in a bulleted/numbered list. Not using asterisks *for emphasis* or hash signs for #different ##headings ###etcetera. My point is, it’s 2015, and we shouldn’t be resorting to solutions like Markdown to maintain formatting across tools and platforms — we should be using formatted text everywhere effortlessly, in a WYSIWYG way.

If you take a look at the afore-linked list of iOS text editors, carefully compiled by Brett Terpstra, you’ll see that of all those apps (107 at the time of writing, the list was last updated on December 12, 2014), only one can both create/edit and export RTF documents — Textilus. Then there are Daedalus Touch and Wisdom Writer, which can only export to RTF, and Knowtes which can open RTF files in external apps. That’s it.

Yes, dear pedant nerd reader, I know that RTF is a proprietary format developed by Microsoft, and that I’m throwing ‘RTF’, ‘Rich text’ and ‘formatted text’ in the same cauldron. What I’m saying is that today, with text, the idea of simplicity is that we use markup languages for formatting — while my idea of simplicity is that, by now, we should have all the necessary technology (and plenty more) to just be free to use formatted text directly, everywhere. We should not approach writing as if we are inputting code or instructions. This idea of simplicity is for engineers and programmers.

I’m reminded of what Donald Norman says in The Design of Everyday Things:

Designers often think of themselves as typical users. After all, they are people too, and they are often users of their own designs. Why don’t they have the same problems as the rest of us? The designers I have spoken with are thoughtful, concerned people. They do want to do things properly. Why, then, are so many failing? […]

There is a big difference between the expertise required to be a designer and that required to be a user. In their work, designers often become expert with the device they are designing. Users are often expert at the task they are trying to perform with the device. […]

Designers have become so proficient with the product that they can no longer perceive or understand the areas that are apt to cause difficulties.

With simplicity in technology, we’re following similar lines. The simplicity users need or expect in their interaction with today’s devices is often different from the simplicity offered by hardware and software makers. When the two coincide, the result is a great user experience. But when that doesn’t happen, then we have frustration, workflows broken by the stupidest details or quirks, difficulty in using potentially flexible and empowering devices — such as the iPad — with maximum efficacy.

To conclude, and to return back to the beginning of this piece, what Federico Viticci has achieved — using the iPad as his sole computing device — today should be a simple process, and more people should be able to do the same. But it’s still a road uphill. It takes time and determination. It takes patience. Federico is a power user, and has got to where he is with his iPad by constantly refining his workflows and methods, by constantly researching apps and solutions, by trying different approaches to optimise the process. A lot of regular users I know (and I bet you know your share too) aren’t willing to go down that road. They perhaps want a certain simplicity and a certain fluidity and integration in carrying out tasks with their iPads that gets complicated or thwarted by the fragmentation of the There’s an app for every little thing model. 

For people like Federico, having all these little blocks at one’s disposal is the opportunity to create rich and efficient constructions (workflows). Other people, instead, get confused and bewildered by all the little blocks and stick to a few of them that are immediately useful and familiar, keeping tasks and activities separated, and generally ending up using an iPad at half of its potential. I have a friend who realised exactly that problem in how he uses his iPad, and told me what he thought was the cause: “I mistook the device’s intuitiveness for simplicity” and added, “Simplicity should scale better.” 

And thus ends this rather meandering piece.

Phone Expander

Software

Phone Expander

Yesterday I noticed a link-post on The Loop: This Mac app makes saving space on your iOS device a snap, and since lately on my aging 16 GB iPhone 4 space is running low, I immediately checked the app out. It’s called Phone Expander and it’s very simple to use. The original review by Christina Warren at Mashable explains very clearly what to do. 

I already did a photo spring cleaning, and removed unnecessary apps and all the apps I realised I don’t really use anymore, so the only option left was Clear Temporary Files. The app loaded all the apps in my iPhone and sorted them by cache size, putting the apps with more ‘temp files luggage’ on top (I wasn’t surprised to see the usual suspects: Spotify, with 320 MB’s worth of temporary files, then Flickr, Yahoo Digest, Hipstamatic, VSCO Cam, etc.). As Phone Expander was loading the apps, it calculated the total amount of space all those temporary files were taking up in my iPhone. I was astounded to find that it was 2.37 GB.

I could have just clicked the button to clear all, but I de-selected a few photo apps and Newsstand magazines just in case. Still, I ended up clearing out more than 1.5 GB. Phone Expander is currently in beta and can be used for free. It doesn’t feel like a beta, though, as it appears to do its job quite well (of course, the more apps you have, the more Phone Expander will take to clear their temporary files). If you don’t want an app in beta to handle your iOS device, back it up before using Phone Expander.

By the way, one neat feature of the Clear Photos option, as Christina Warren notes in her review, is that “before it deletes a photo or large number of images, it backs them up to your desktop.”

When I downloaded the app, I was afraid it was Yosemite-only (I couldn’t find the minimum requirements on the app’s website), but it works under Mavericks as well. 

If you need to free up some space on your iOS devices and are looking for a simple way to do it, you may want to give Phone Expander a try.

The perfect laptop and the race to the thinnest

Tech Life

Three things have inspired me to write this. 

Thinsistence

I know the pictures at 9to5Mac are not of a real MacBook Air, that they are a rendition based on information purportedly received from Apple. But let’s play along and pretend that this is a faithful rendition of the future 12-inch MacBook Air. Am I alone in thinking that it’s overall quite ugly?

Some selected quotes from the article to emphasise what’s driving me nuts lately about laptops, and Apple laptops in particular: 

Apple is preparing an all-new MacBook Air for 2015 with a radically new design that jettisons standards such as full-sized USB ports, MagSafe connectors, and SD card slots in favor of a markedly thinner and lighter body with a higher-resolution display. 

The 12-inch MacBook Air will be considerably smaller than the current 13-inch version, yet also slightly narrower than the 11-inch model.

Apple has squeezed the keys closer in order for the computer to be as narrow as possible …

Apple has also relocated some of the function keys across the top and simplified the arrow key array in order to keep the keyboard as narrow as possible without taking away from overall usability.

The elimination of physical feedback in the click is part of Apple’s plan to reduce the thickness of the MacBook to a bare minimum.

As can be seen in 9to5Mac artist Michael Steeber‘s rendition above, the new 12-inch Air (on the left) is far thinner than the current 11-inch model (on the right). Taking cues from the current Air, the future model has a teardrop-like, tapered design that gets thinner from top to bottom.

The upcoming laptop is so thin that Apple employees are said to refer to the device as the “MacBook Stealth” internally. In order to reach that new level of portability, Apple not only slimmed down the trackpad and tweaked the speakers but the ports as well … 

Thin, thinner, narrow, narrower, as narrow as possible, reducing the thickness, far thinner, slimming down…

Let me get this out of my system: I am sick and tired of this obsession to make laptops as thin as possible. It’s becoming an exercise in design, a race to the thinnest machine. And yes, I believe that usability suffers in the process. What sells thinness to the customer is, I think, the lightness that goes with it. And yes, of course your laptop has to be lightweight and the least bulky there is. But when such thinness and lightness are achieved at the expense of usability (a more cramped keyboard, a bigger trackpad further reducing the palm rest area, a trackpad without physical feedback) and even ports and connections, I simply don’t understand and begin wondering how much sense it all makes.

Yes, as I’ve said I’m assuming that the information revealed in the 9to5Mac article is good, and for the sake of argument I’m taking it at face value. I tend to believe the bit about Apple “planning to ditch standard USB ports, the SD Card slot, and even its Thunderbolt and MagSafe charging standards on this new notebook” and leaving the 12-inch MacBook Air with just one USB Type‑C port. Perhaps it won’t remove the MagSafe connector just yet, but Apple is always looking for new solutions and is obsessed with this kind of optimisation. It’s a move that can be expected from Apple. Just look back at the first MacBook Air — it only had one USB port, a Micro-DVI video port, an audio jack and the MagSafe connector, where a regular MacBook of the time had Ethernet, two USB ports, a FireWire port, audio in and out, and a Mini-DVI video port.

In early 2008, I loved the idea of the MacBook Air. It certainly was more compact and lighter than a regular MacBook, weighing only 1.36 kg against the 2.27 kg of the MacBook and the 2.45 kg of the 15-inch MacBook Pro of the time. I’ve had a Mac laptop as primary machine since 2003, when my beloved blueberry iMac G3 broke for the second time. When the first MacBook Air was introduced, my main machine was still a 12-inch PowerBook G4 — believe it or not — and was starting to feel limited for my needs. The future was with the Intel architecture, and for a moment I considered purchasing the MacBook Air as my first entry to Mac Intel machines. 

But the MacBook Air wasn’t the ideal laptop for me. I wasn’t really concerned with pure processor performance: lots of reviews said the first-generation MacBook Air was underpowered and slow, due to its small 4,200 rpm hard drive and a lackluster 1.6 GHz Core 2 Duo chip. But hey, I was still using a 1 GHz PowerPC G4 machine. The Air was lightning fast in comparison. What felt limiting to me was the Air’s lack of ports. And not just because I would have also used the Air as a desktop machine. Even when used as a laptop, only one USB port and the lack of Ethernet and FireWire was a deal breaker for me.

I’m digressing. In 2008 I thought that, while the MacBook Air was not the laptop for me, its thinness and lightness were truly revolutionary, and I was sure that the MacBook Air would be the perfect laptop for many other users. And that was an easy prediction. The original 13-inch MacBook Air was light, thin, and quite usable, as usable as a regular 13-inch MacBook (the keyboard was the same size and so was the palm rest area). 

When the 11-inch MacBook Air was introduced in late 2010, I was a bit perplexed at first, but again, an even smaller Air made sense for those wanting a truly ultra-portable machine that was also rather powerful. And it was nice to have more choices for the MacBook Air line of products. All the people I know who do a lot of work while flying were quite happy to have such a tiny machine with them in their trips. In late 2010 I was one year into my new Intel laptop, a 15-inch MacBook Pro, so I wasn’t thinking about a new laptop. That 11-inch Air was surely appealing: it had more connections than the original MacBook Air (well, one USB port more, but still), a solid state drive, the maximum RAM was 4 GB instead of 2… And above all, it had a very nice battery performance. But again it wasn’t the ideal laptop for me because I did not find it very usable for long writing sessions.

Indeed, at a later date, I had the opportunity of testing an 11-inch MacBook Air thoroughly. While I’m sure that owners of such a machine will disagree with me on this, I have to say that I didn’t find its size and form factor very usable after spending one day writing on it. And I don’t mean writing the occasional email and doing light typing stuff. I mean writing long-form pieces for hours. I found the 11-inch Air too cramped for my tastes, and I ended up with aching wrists because I couldn’t rest them comfortably in the limited area around the trackpad. I had to take more pauses, frequently readjusting my posture, etc. I remember thinking: I hope it doesn’t get any smaller or more cramped than this.

Where am I going with this? I’m simply saying that while in 2008 a laptop such as the first MacBook Air made sense compared to the other laptops produced by Apple and by Apple’s competitors (the Air was really the thinnest, lightest notebook of the time, there was only one Sony Vaio model, I think, with a similar form factor); and while in late 2010 a smaller, thinner MacBook Air still made sense — what sense does it make to build an even thinner 12-inch MacBook Air now? In 2008, getting a MacBook Air meant saving a lot of bulk and getting a laptop that weighed almost one kilogram less than the lightest Apple laptop of the time. In late 2010, getting an 11-inch MacBook Air meant saving a decent amount of bulk and almost 300 grams compared to the 13-inch model — enough to be worth considering the smaller Air. But I don’t think that a thinner 12-inch Air now is going to offer a comparable weight and bulk loss to justify this obsessive trimming. (Again, assuming Apple is really building such a laptop.)

The purported killing of most ports, and the purported aim to produce an even thinner MacBook Air just seems arbitrary at this point; a mere design exercise, as I already said. You sacrifice connections, keyboard space, trackpad feedback, and usability to have what, a laptop that may weigh 50 grams less than a 13-inch Air and be a couple of millimetres thinner? Can we stop for a second and ask, What’s the point? To beat a record? To claim to have the thinnest computer with a high-resolution screen? At that point, let’s just make an iPad Air with a keyboard attached (hint: still not great ergonomically.)

The perfect laptop

As Ben Brooks said:

The first thing we have to realize is that there is no perfect laptop. What is perfect for one person won’t be for another. It all depends on your values (speed, size, battery, screen, etc).

Having said that, I won’t be stopped from thinking about this a little more. The way I look at a perfect laptop is in the bigger picture of my entire setup. To that end there are two possible setups:

  • Desktop based: either an iMac, or larger 15” laptop at home.
  • Highly portable: MacBook Air as a main machine.

I won’t get into which is better, both have their merits, but to determine what a perfect laptop is I like to think about it in the vein of the above two setup scenarios.

Since 2004, my home office setup has always consisted of a Mac laptop in desktop configuration — attached to a bigger external display, to an extended keyboard and mouse, and attached to any external drives I’ve had on my desk. When I needed the Mac with me, I just disconnected everything and put the laptop in my backpack. The size of the laptop only mattered in one regard: how often I would use the laptop while out and about. Since in 2004 I was often off-site, a compact laptop was in order, so instead of buying a 15-inch PowerBook G4, at the time I opted for the 12-inch model, and it ended up being a very wise move. The 12-inch PowerBook G4 is probably the laptop that’s achieved almost-perfect status in my extended experience. Compact and lightweight enough, a decent battery life for the time, and with enough connections and enough power to be used as a desktop machine, connected to a 20-inch 1680×1050 external display.

By the time I had to upgrade my setup in 2009, I wasn’t commuting or moving around as I used to do five years before, so the need of having a small, highly portable machine with me wasn’t as strong. Also, my sessions at the computer while out and about were getting longer, so it made sense to consider a bigger laptop, and that’s why I got a 15-inch MacBook Pro instead of a 13-inch model (or an Air). The bigger display and trackpad, and the ample space in the palm rest area are great for long writing sessions.

Matt Gemmell, in his piece, emphasises what he looks most in a laptop:

What I do need, though, is true portability: small size, light weight, and the robustness to carry off the first two qualities without compromise. And I certainly need the reassurance that this tool will be ready for use whenever and wherever I might want to work.

Matt is very satisfied with his 2013 11-inch MacBook Air: This laptop already does all those things. It’s tiny, very light, and very solid. Those problems are solved.

He adds:

Portability isn’t a special requirement for a laptop. It’s not a premium feature. It’s the essential promise of the device’s whole concept. And until recently, they came with compromises that were technological, eating away at the ideology of the category. But that problem has pretty much gone away. Now, subnotebooks can find their natural home: the casual user. Me.

To conclude with a thought that ties to the observations I was making earlier, and to follow Matt’s drift, what I’d like to point out is this. Now that we have (Apple) laptops which are sufficiently thin, sufficiently lightweight, extremely portable and with batteries that last a day and let us be highly productive overall, perhaps it’s time to focus on other things that aren’t “how to make this laptop even thinner.” People still use bags and backpacks and briefcases and, as I observe every day in the city, they typically carry around a lot of stuff. I doubt that shaving off two millimetres or 50 grams from an already incredibly thin and light machine is going to make all that difference for the regular user. How about working on comfort? How about making a laptop slightly wider to accommodate a regular keyboard, with enough space to comfortably place your hands when you need to write or navigate the interface with the trackpad? If I buy a laptop with great portability, that allows me to work for hours and hours without needing to charge it, I’d like to have a laptop that’s also comfortable to use it for hours on end.

People and resources added to my reading list in 2014

Tech Life

At the beginning of 2013 I decided to start a series of ‘annual reports’ where I listed the people and resources discovered during the previous year worth adding to my reading list. I also took the chance to talk about how my ever-flowing RSS feeds’ organisation was going. I believe it’s important to do this, to share these findings, because there are a lot of interesting and writers and websites out there deserving of a wider audience. 

Last year I wrote:

With regard to reading — both online and offline — I feel my 2013 has been a denser, richer year than 2012. I know for sure I’ve read more books in 2013 than the year before, and as for reading stuff online I’m left with the impression that I’ve found more quality writing overall. Maybe I’m just getting better at instinctively avoiding the bad writing and at filtering out the noise while tuning to the signal.

Well, I have to say that 2014 hasn’t felt as rich. (To me, obviously.) Many times I stumbled on insightful posts and contributions, but didn’t add those authors to my feeds mainly because of the intermittent quality of their production, or because I wasn’t interested in the main topics they usually talk about in their websites and blogs.

Anyway, here are the ‘new entries’ in my RSS feeds, in truly no particular order:

  • getwired.com by Wes Miller. — I love Wes’s style. He’s another tech-oriented author who writes only when he really has something to say, and when he does, he writes thoughtful long-form contributions.
  • Avery Pennarun, discovered thanks to John Gruber when he linked this post by Pennarun on Daring Fireball. Apenwarr, his blog, is updated infrequently, but when he updates, it’s really worth your time. His most recent articles on Wi-Fi technology are rather technical but extremely informative if you want to have a deeper understanding of it.
  • Brent SimmonsInessential — I follow Brent since I first discovered NetNewsWire years ago. I decided to add his site to my feeds when he started updating it more frequently.
  • Michael Tsai is the developer of SpamSieve, among other things, and SpamSieve is the best email spam filter application for the Mac. Like with Brent Simmons, I have been reading Michael for a long time (since I discovered the About This Particular Macintosh e‑zine back then) and I used to visit his blog on a fairly regular basis, then last year, after considerably pruning my feeds, and seeing that he too, like Simmons, had started updating more frequently, I decided it was time to finally add his blog to my feeds. 
  • Le Journal du Lapin by Pierre Dandumont (in French, for the most part; he sometimes publishes articles in English). — Pierre is another vintage Mac enthusiast and updates his blog frequently. He always finds something interesting to talk about or link to. I was looking for someone who wanted to attempt a project I thought about carrying out — putting a higher-resolution display in my clamshell iBook — and Pierre has done that and thoroughly documented it, too!
  • The Pickle Theory (née The Typist) by Shibel Mansour — Shibel is a great guy and I always enjoy his insightful posts. He’s one of those you wish they updated their blog more often.
  • Aral Balkan and Ind.ie — Aral was a great 2014 find for me: he’s intelligent, articulate, and passionate about what he does and what he wants to build with the Ind.ie project. And we share the same views about privacy, surveillance, and what he calls Spyware 2.0.
  • The Robservatory by Rob Griffiths, and Kirkville by Kirk McElhearn. — I’ve been reading Rob and Kirk for a long time, and even translated some of their Macworld articles into Italian back when I was a collaborator of Macworld Italia Magazine. Like with other old-timers in the Mac community mentioned above, I’ve been checking their websites often over the years, and finally decided to use my RSS reader to consistently keep track of what they write.
  • Alex Roddie — Alex is a writer and a vintage Mac enthusiast like me. If you want to know more about where he comes from and what he writes, here’s a link to his main website. But, he also writes an excellent blog at the website where he offers his professional editing and proofreading services — Pinnacle Editorial. The Pinnacle blog is a great resource, with articles written by Alex himself and by guest authors, featuring contributions on writing, reviews, and commentary related to the book publishing world. Then he also maintains a great blog on vintage Macs called Macintosh HD; he writes less frequently there, but the blog really deserves to be in your bookmarks if you, too, are a vintage Mac enthusiast.
  • Big Mess o’ Wires by Steve Chamberlin. — Steve is one of the good tinkerers. He’s the maker of the Macintosh Floppy Emu (From the Floppy Emu page: “[It’s] a prototype floppy and hard disk drive emulator for vintage Macs. It uses an SD memory card and custom hardware to mimic a 400K, 800K, or 1.4MB floppy disk and drive, or an HD20 hard drive. It plugs into the Mac’s external or internal floppy port, and behaves exactly like a real disk drive, requiring no special software on the Mac”), and it’s a really ingenious device. I discovered Steve exactly by following a link to his emulator, but as you’ll see, his website is full of interesting projects and technical investigations.

Of course, I’m still reading and following the people I discovered in 2012 and 2013 (see links to my old articles at the beginning). 

Briefly, on podcasts

I rarely have time to listen to podcasts on a regular basis. There are only three exceptions. The first two are podcasts I subscribed to a long time ago, so I managed to always find the time and the attention for them; the third is the 2014 new entry:

  1. John Gruber’s The Talk Show because, well, John Gruber. Episodes are long and the conversations rambling, but always in an interesting, unpredictable way. That’s what makes me return for the next episode.
  2. The RetroMacCast with James and John, obviously dedicated to the world of vintage Macs. James and John are great guys, long-time Mac fans who know their stuff.
  3. Release Notes, with Joe Cieplinski and Charles Perry. Episodes are generally short compared to many other tech podcasts, about half an hour each, and that’s good. The two hosts have a great pace, and a to-the-point, no-nonsense approach which is quite enjoyable. Well worth my time (and yours).

That’s it.

RSS management and reading software

Considering the subject, I think it’s relevant to mention how my RSS management has changed, and which applications I’m using now to read my RSS feeds. 

On the Mac

On my main MacBook Pro, I use Reeder 2, connected to my Feedly account. There I keep basically all the feeds I follow on a daily basis. In the period before Reeder 2 was released, I used ReadKit and has been quite a decent alternative. I still use it every now and then because I love how it manages my Pinboard bookmarks and displays them as feeds.

On my most-used PowerPC Macs — the Power Mac G4 Cube, and the 12-inch and 17-inch PowerBook G4 — I use NetNewsWire (the older version 3.x, of course), and I keep only a subset of feeds, usually those that are considered ‘slow feeds,’ i.e. sources updating less frequently. 

On iOS

Both on the iPhone and the iPad I now use Unread, which for me is the best RSS reader, period. If you still use an older device — like the original iPad, stuck at iOS 5.1.1, or the iPhone 3GS on iOS 6.1.6 — I strongly recommend Byline by Phantom Fish. It’s a solid RSS reader which provides a great integration with iOS 5 and 6’s UI.

What I use to ‘read later’

For the most part, I still don’t read later, and I’m still applying more or less the same techniques described in the afore-linked article. In Safari, though, I started doing things a bit differently in 2014. Instead of keeping a lot (and I mean a lot) of tabs open on articles and stuff I want to read/act upon within the day or the day after at the latest, now there are three layers of bookmarking:

  • Open browser tabs, only for articles I want to read straight away once I finished whatever ‘foreground task’ is getting my attention, and articles I want to write about on my blog.
  • Safari’s Reading List, for articles I want to go back to as soon as I can, but that lack the priority of those articles and sources I keep in open tabs. The Reading List feature is also useful because it’s a synchronised bucket — I can save there something I notice while using my iPhone or iPad and then read it later on the Mac’s big screen at my desk.
  • Pinboard, for long-term storage of resources I want to keep for future reference.

That’s all. In the next days I may update this article if I realise I made grave errors of omission.