Twitterrific 4.3

Software

When yesterday I launched Twitterrific on my Mac, the application greeted me with an update notification. I updated right away because in the list of new features my eye immediately caught this:

• Improved t.co and Twitter picture handling

And as soon as I relaunched Twitterrific, I found out that this improvement does exactly what expected.

As you know, if someone you follow posts an image in a tweet using the canonical Twitter app for Mac, the image link will be wrapped and obscured in a t.co link. As I complained a while ago, with Twitter’s own t.co service all links are created equal, and you can’t know at a glance if they’ll point to an image or an article on another site. It’s unnerving because most Twitter clients can display images inline, and I hate when clicking a t.co link forces me to open a new tab in the browser only to discover that it was a twitpic or yfrog link that the client could have handled internally. With the 4.3 update, Twitterrific recognises whether a t.co links hides an image and if it’s the case, it will display said image inline. I am deeply grateful to the Iconfactory guys for this.

Which isn’t even the best feature of this update! From the Iconfactory blog:

Version 4.3’s best feature is the ability to sync your reading position across all versions of Twitterrific by using the Tweet Marker API. Twitterrific keeps track of where you are in the timeline and displays that position as a bookmark on the tweet’s timestamp. Twitterrific can also automatically scroll to this position – no more searching for where you last left off. This makes reading your timeline a breeze when moving between Mac and iOS during the course of a day. Turn on timeline syncing via Twitterrific’s settings.

Some of the notable highlights in Twitterrific 4.3 include:

  • - Syncing of timeline positions across all versions via Tweet Marker
  • - Improved t.co and Twitter picture handling
  • - Support for displaying Camera+ images inline
  • - Support for normal tweet notifications with Growl (Mac)
  • - Refinements to full screen mode & scrolling in Lion (Mac)
  • - Improved handling of errors associated with incorrect time & time zones
  • - Plus more – iOS / Mac

Most of the kids are alright

Handpicked

Source: Rosamicula — most of the kids are alright:

What these riots — which aren’t demonstrations, but parties got out of hand, with fires and prizes — is the degree of alienation from their own communities, their inability to acknowledge that they are part of any community. They also don’t see themselves as angry or even oppressed, because they cannot look beyond the circumstances they are in and the peer pressures around them. And it is about bad parenting, to the extent that when the 13 to 20% become parents they have no aspirations or responsibilities for their children to inherit. That won’t change if you treat merely them as victims, and enhance their sense of entitlement to trainers and TVs, nor if you treat them merely as criminals and process them through a judicial system that encourages recidivism.

Si è davvero di parte?

Mele e appunti

Oggi più che mai è difficile entrare nel dibattito tecnologico e gestire la variabile Apple senza sembrare di parte. Che si sia a favore o contro, appena si parla di Apple si finisce inevitabilmente etichettati. Lasciatevi sfuggire una frase come “Secondo me l’esperienza utente è superiore e più piacevole sull’iPad”, ed ecco che sarete subito chiamati fanboy. Chi è utente Mac di lungo corso come il sottoscritto, è abituato a certe dicotomie. Negli anni Novanta e Duemila furoreggiavano simili discussioni fra utenti Pc Windows e utenti Mac. La Apple di vent’anni fa però non aveva la prominenza di oggi, era l’outsider dalle idee brillanti ma incompreso, il suo era un mercato di nicchia, così di nicchia che non passavano due settimane senza che giungesse la solita voce di corridoio secondo cui Apple era ‘sull’orlo del baratro’ e avrebbe chiuso bottega da un momento all’altro.

La Apple di oggi scoppia di salute e a ogni suo minimo movimento, sul Web e nelle reti sociali si scatena il dibattito, quel dibattito sempre polarizzato a cui accennavo poco sopra. Sin da quando mi sono accorto che la tecnologia non era un interesse passeggero, ho cercato di affrontare qualunque dibattito portando una posizione il più possibile bilanciata. Se c’è da mettere a confronto dei prodotti e delle soluzioni, cerco sempre di provarli tutti personalmente prima di esprimere un giudizio.

Le cose si complicano nel mondo mobile, di smartphone e tablet, in questi ultimi anni esponenzialmente cresciuto, inevitabilmente preponderante e continuamente davanti ai nostri nasi. In questo mondo il dibattito è molto più scomodo in quanto Apple gioca un ruolo così importante che non è possibile ignorarla, e risultare obiettivi è un lavoraccio. Dire che iPhone e iPad sono, nel complesso di hardware e software, i prodotti migliori delle loro rispettive categorie può a tutta prima sembrare una posizione di parte, ma è davvero così?

Dalla presentazione di iPhone all’inizio del 2007, Apple ha indubbiamente rivoluzionato il mercato dei telefoni cellulari: questo non lo si nota tanto nelle vendite di iPhone, pur straordinarie, ma dal fatto che prima di iPhone l’usabilità di un cellulare era sostanzialmente un misto fra una calcolatrice e un cercapersone, e l’idea più vicina a un’interfaccia touch era quella di usare uno stilo grande come uno stuzzicadenti su schermetti piccoli e poco luminosi. Uscito l’iPhone, tutta la concorrenza è saltata sul carrozzone e guarda caso in tempo record ogni costruttore di smartphone aveva in catalogo la sua personale imitazione di iPhone. A cinque anni di distanza, nessuno ha ancora sfornato un prodotto con la medesima reattività, con la medesima integrazione hardware/software, con un’interfaccia altrettanto ben congegnata. HP/Palm è molto vicina, a mio avviso. webOS è un sistema operativo elegante e con tantissimo potenziale. Merita menzione anche Microsoft, che per una volta ha portato freschezza e originalità in Windows Phone 7. Android non ha ancora raggiunto l’usabilità di iOS. Sono tutti ottimi tentativi, il problema è che iPhone era già più che utilizzabile sin dal primo giorno, 5 anni fa.

Con iPad il discorso è analogo, se non ancora più marcato. Prima di iPad il mercato dei tablet era pressoché inesistente, e quel poco hardware che veniva prodotto aveva tutta l’aria di essere una prova concettuale più che dispositivi fatti e finiti. E ovviamente non c’era traccia di interfaccia multi-touch. L’anno scorso Apple presentava iPad e, dopo il classico giro di interventi da parte di sapientoni che ne pre-determinavano l’insuccesso e l’inevitabile flop, quando il dispositivo ha cominciato a vendersi come il pane, la concorrenza si è impegnata a far uscire la propria idea di iPad. A qualunque costo e a prescindere dal livello di rifinitura. Al punto che, come ha scritto Harry McCracken parlando del Playbook di RIM, stiamo entrando nell’era dell’hardware beta. L’importante, per la concorrenza, è sfornare un tablet che possa competere con iPad, e poi promettere ai clienti che certe funzionalità saranno introdotte in seguito. Alle persone normali, però, interessa che un prodotto che costa qualche centinaio di Euro funzioni bene sin da subito.

A fare l’osservazione giusta è ancora una volta John Gruber:

Questi non sono tablet ‘beta’, sono pessimi tablet, punto e basta. È vero che il loro hardware sembra più vicino alla qualità dell’iPad rispetto al loro software, ma migliorare il software è la parte più difficile in prodotti come questi. Quando RIM avrà rilasciato quel paio di aggiornamenti software cruciali, l’intero mercato sarà cambiato. La verità è che Motorola, Samsung e adesso RIM hanno prodotto degli aspiranti concorrenti di iPad che impallidiscono a fianco di iPad. È così difficile ammetterlo?

Come per iPhone, con iPad siamo già alla seconda generazione del prodotto, e la concorrenza non è ancora riuscita a produrre un dispositivo che offra la medesima esperienza d’uso da subito, fuori dalla scatola. A me, che ho provato di persona questi altri dispositivi, non sembra affatto un’osservazione di parte.

-§-

(Nota: Questo articolo è originariamente apparso sul numero 85 di iCreate magazine nella mia rubrica ‘Appunti’. Se lo ripubblico qui non è per mancanza di idee o di materiale; semplicemente, ho pensato che valesse la pena pubblicare le mie osservazioni in rete così da raggiungere un pubblico più ampio).

One month with Google+

Handpicked

After all the chatter and blabbing about Google+, I was interested in hearing some impressions by someone who was actually using it, and I was secretly hoping that that someone would be a competent, tech-savvy journalist. That’s why I enjoyed One month with Google+: why this social network has legs by Jacqui Cheng at Ars Technica. 

She writes:

After one month with Google+, it’s clear to me that this—sending updates to certain groups of people and not to others—is the main appeal of the service. I was one of the first people to loudly declare that you can do the same thing on Facebook, but so few people know this that it’s basically a nonexistent feature; that’s the problem with Facebook. With Google+, sending out certain updates to some people and other updates to other people is right at the forefront of the experience. You are always asked to make a conscious decision about your social circles and about which circles get to see which posts.

And here’s a feature I didn’t know about:

There’s also the (wondrous) ability to “mute” posts on Google+. You know how you “Like” a friend’s photo on Facebook, only to get alerts for every single one of that person’s 300 family members when they end up commenting on the picture and arguing over whose body part is in the corner? Imagine if you could simply hit a button to ensure that you never have to hear about that post ever again—even if it’s your own post. We’re not talking about blocking certain users—sometimes you want to keep a person around, but you just don’t want to hear about a topic anymore. That’s a huge bonus to Google+, and those I’ve spoken to agree that it’s one of the better unsung features of the service.

I agree, this is something I’m sure I would resort to if I started using Google+ (unlikely).

Finally, this is another point I agree with:

However, the most important thing for Google to do right now is to retain its current audience and keep the momentum going. Enough people use Google+ and say enough good new things about it that it could establish itself as a legitimate alternative to Facebook, but fickle users can easily be driven away by boredom at this early stage. So long as Google+ keeps improving, it should be okay; if it implements some of the suggestions thrown out by its users, it could be more than okay.

Lion Is a Quitter

Handpicked

For the first time since I’m on Mac OS X, I’m not getting particularly thrilled about the latest version of the operating system. I remember embracing the transition to Mac OS X from Mac OS 9 with enthusiasm, and every time a new version of Mac OS X was out, I immediately upgraded, certain that the benefits always outweighed the compromises. I always trusted Mac OS X to the point that — apart from a manual backup of my most important data — with every upgrade, I just inserted the system discs and updated, without too many paranoid precautions. 

You’ll probably think it’s silly, but for me Lion is becoming a really controversial upgrade. It’s the first time a new version of Mac OS X has made me really consider not only a simple backup, but a complete cloning of the contents of my main hard drive and a Snow Leopard/Lion dual-boot configuration. It’s the first time I’ve waited so long before actually upgrading. It’s the first time I’m really giving a lot of thought to that benefits/compromises balance, because for the first time I’ve the feeling that what Lion is giving me barely compensates what it’s making me leave behind. Mind you, these are strictly personal reasons & observations. They’re related to how I’ve been using my main Mac, how I’ve been perfecting my workflow, the applications I’ve come to rely upon, etc. In this regard, as I’ve already said, Lion feels rather disruptive to me. I find many of its new features appealing, but at the same time perhaps I’m just not ready to adjust my habits. In a nutshell: I will upgrade to Lion, but for the first time with a strong safety net and less enthusiasm than before.

I’ve written this long introduction to this great article by Matt Neuburg — Lion Is a Quitter — to make you understand where I’m coming from and why I agree with Matt’s position. His piece is about a so-called feature in Lion, Auto Termination. What does it do? Neuburg quotes the amazing review of Lion by John Siracusa:

Lion will quit your running applications behind your back if it decides it needs the resources, and if you don’t appear to be using them. The heuristic for determining whether an application is “in use” is very conservative: it must not be the active application, it must have no visible, non-minimized windows — and, of course, it must explicitly support Automatic Termination. 

This ‘feature’, though, seems to be messing with Neuburg’s workflow:

Yesterday, the same thing happened to me with Preview. I launched Preview because I wanted to open a certain PDF document. So I chose File > Open to summon the Open dialog. At that point, however, I realized that I wanted to make some changes to the folder containing the PDF document I intended to open. So I closed Preview’s Open dialog (and I may also have told Preview to hide) and switched to the Finder. When I was done messing about in the Finder, I tried to use Command-Tab to switch back to Preview to bring up the Open dialog again — but I couldn’t, because in the meantime, Preview had quietly been told to quit, by the system, behind my back, without notifying me.

[…]

As Siracusa goes on to point out, when Automatic Termination occurs, the terminated application may in fact not really be terminated. For example, right now on my machine, TextEdit is listed in Activity Monitor as one of my running processes. It’s using some memory; it has open files. Nevertheless, TextEdit doesn’t appear in the Command-Tab switcher or the Dock. Lion has faked me out twice: it has caused TextEdit to vanish from the GUI’s display of running applications even though I didn’t quit TextEdit, and at the same time, it has kept TextEdit running in the background.

Matt then questions the usefulness of Auto Termination, and in my opinion he makes some good points against it, both from a technical and a user experience standpoint. 

I know that this, like the change from Exposé + Spaces to Mission Control, is bound to give me headaches because part of my workflow is having two or three applications in the background and having to move back and forth from one to another to compare, make changes, open files, copy-paste contents, close files, and so on, and it would be hugely annoying for me if the system decided to quit one of these applications behind my back just because I don’t have open documents or windows at a particular moment. That’s why I really sympathise with this bit:

[T]he fact is that when Lion caused Preview to quit automatically yesterday on my machine, I was using Preview. I wasn’t using it actively at that moment in a way that Lion knew about — there were no open Preview windows, and Preview wasn’t frontmost — but I was engaged in some activity involving Preview. I had switched away from Preview only in order to prepare things in the Finder so that the document I intended to open in Preview would be ready. But when I switched back to Preview with Command-Tab, Preview was gone. That’s not helpful or useful; it’s annoying, confusing, and a hindrance. I had to launch Preview explicitly again in order to continue with my task.