Getting rid of Wordpress...

Aha, at last I finally decided to get rid of Wordpress: sql injections were really a plague and I didn't have time to stay up to date (nor it is easy to update automatic installs on servage)

Here it is what I did:

1) I exported my wordpress blog. You have only to login to your WordPress account, navigate to the Dashboard, look for the Export link. Wordpress will produce a WXR file (Wordpress eXtended Rss) which you will be able to save to your local machine.

2) Go to Wordpress2Blogger, browse the saved WXR document and click Convert and save that file to your local machine. This second XML file is a blogspot specific file.

3) Create your blog on and choose the XML export file you just produced in the Import Blog Tool. Alternatively if you already own a blogspot blog, go to the panel, choose the "Settings -> General". On the first row, immediately before the "Title" filed (yes, it's just a little hidden) there are import and export links. Just click on import and you will see immediately all your old posts and comments

4) After creating my blogspot blog, I wanted to integrate in my site, using my domain name and my look and feel: to do that I just configured the great Rapidblog plugin from Loghound software in my Rapidweaver project. You basically only need to give the blogspot username/password to the plugin.

Et voilà, a complete blog migration in less than one pomodoro! Bye bye wordpress.


Ahhh, virus in blogs...

I have been hit by an infection. The old Wordpress I was using was apparently vulnerable to a sql injection, and I only found out thanks to google, which showed in the search that the site can harm you. Well, thanks, google. I hadn't time to investigate how exactly the injected javascript could harm, because I had my problems to reinstall wordpress and migrate the content, and that's enough.

Javaday è qui!

Il secondo Javaday è qui. Non mancate, io sarò presente con un talk sul clustering di Terracotta. Anche se non vi frega nulla del transparent clustering, sarà comunque un'occasione per conoscersi più da vicino!

Leopard: things I like and things I dislike, a developer perspective

It's more than a full day working on Leopard right now. So, here are my first impressions on what I like and what I don't like from a developer perspective.What I like:
  1. Time Machine. Easy, almost everyone paid lip service to TM. But it's still impressive when you look at it
  2. Dtrace and Instruments. This is a joy for developers. More on this in next posts, in the meanwhile have a look at Bryan Cantrill blog,  dtrace creator 
  3. Spaces. Another easy one. Bye bye buggy Virtue Desktop, welcome pre-organized spaces (yes, you can assign applications to predefined spaces)
  4. Terminal. You won't need anymore iTerm to tail logs in tabbed windows.
  5. Calendar icon now shows the real date and not 17 of July!
  6. Ruby/Rails out of the box. Very nice to have ruby/rails integrated. Well, I would have preferred a java 6 virtual machine, but it's nonetheless a nice feature. Not as much as the Calendar icon, but a good one :). Jokes aside, is nice that ruby apps on apple are also Dtraceable
What I don't like:
  1. No Java 6. No workarounds: but java 5 looks very fast, and rumors are that we will see java 6 very soon. (hopefully with fast opengl rendered Swing, working Java Sound and a lot of dtrace probes)
  2. PostgreSql from MacPorts failed to compile, and I still hadn't had time to see why
  3. The 3D Dock looks ugly. Easy workaround:  simply type "defaults write no-glass -boolean YES" and then a "killall Dock" in the command line
  4. The tranlucent menu looks ugly too. This isn't easily and completely solved right now
  5. Skype works only the first time! This happens because Skype self-modifies itself after the first launch, and the app signing mechanism break. Either wait for Skype folks to solve it or reinstall with the firewall disabled. More info here
  6. Intellij Idea 7.0.1 can't be assigned to a space :(
Comments (1) Show Comments

Migration Assistant, thank you very much!

Yesterday I received a shiny new MBP. Being my 5th Mac with OSX, I thought I almost knew all of the basics. Well, I was wrong.

I was almost ready with my rsync scripts and a great dose of patience to migrate all my stuff to the new beast when one of my colleagues pointed me to Migration Assistant. For me, that was one of those misterious icons you never use, probably being there for obscure reasons I certainly don't need to cope with, like Grapher (/Application/Utilities/, or ODBC Administrator (/Application/Utilities/ODBC, or [Put your favourite example here]. You know, that kind of stuff even Steve Jobs doesn't know exactly why is there or what is for.

Well, it turns out that Migration Assistant is really really useful and it does really really work. All you need is a firewire cable, then:

  • you connect the old mac with the new one

  • you start the Migration Assistant (/Application/Utilities/Migration, or, even better, you choose to "migrate data from another mac" during the setup procedure wizard

  • you (re)start the old mac keeping the T button pressed: that makes your mac go in "firewire disk" mode. You will see a fancy firewire logo moving on your screen when it's ready

  • you choose from a wizard what you want to migrate (Users, Applications, and so on). I selected all the checkboxes

  • you wait :)

And then you will have a new mac, virtually identical to the old one. Same desktop, same apps, same stuff in the trash bin, same history in the browser, same network options, same items at startup, etc. I had only 3 minor issues, and here are the workarounds:

  • Some icons on the Dock was broken, showing a question mark. I just clicked on them to solve this :)

  • Alfresco didn't work anymore. Looking at the logs, it was really a postgres problem: the postgres user didn't migrate (in fact, it wasn't even selectable in the Migration Assistant wizard, probably because the UID was to low or too high to be in the normal user range, who knows?). This is really a piece of cake, just recreate the postgres user and group with the same UID/GID with Netinfo Manager (/Applications/Utilities/NetInfo or using the shell.

  • The admin user wasn't anymore an admin! The user data correctly migrated, but OSX was confused and, although it had the Admin checkbox correctly set, couldn't act as an administrator (sudo for example didn't work). Being the only Admin user, OSX don't let you unset/reset the checkbox. The workaround here is simply to create another Foo admin user, then unset and reset your real Admin user Administration checkbox, and then delete the Foo admin user.

This time, the god of system administrators smiled at me and I had an up and running laptop in a few hours (just about 2 hours for 50Gb on the 400Mb firewire) and a few minutes to fix minor issues. Well done!
Comments (5) Show Comments

Odio più i “piuttosto che” o i “quant’altro”?

Beh, prima o poi dovevo cominciare a scrivere delle cose che odio, visto che il blog si chiama "Legendary Diplomacy" :)

Non so se ci avete fatto caso, ma l'informatico in prevendita, o più in generale nelle riunioni (più spesso in quelle in giacca e cravatta), adotta un linguaggio un po' diverso dal suo solito, un linguaggio con cui cerca di darsi un tono. Non solo l'informatico, certamente: ma purtroppo frequento quasi esclusivamente questa bistrattata categoria...

Tipicamente nei discorsi del prevenditore in azione troverete avverbi inutili, oscure espressioni pseudo-anglosassoneggianti che pretende tutti capiscano, snobismi vari e più in generale parole artificialmente forbite che hanno sinonimi molto più semplici ed immediati. Penso la cosa sia in fondo piuttosto normale, poichè nelle riunioni spesso si cerca di apparire più fighi ed intelligenti di quello che si è veramente. E nelle riunioni in cui si cerca di vendere qualcosa ovviamente molto di più.

Ma in tutto questo [normale] fastidio ci sono però alcune espressioni veramente antipatiche, parole che mi danno letteralmente il voltastomaco e che passano il confine del semplice irritamento cerebrale:

  • Piuttosto che

  • Quant'altro

Frase tipica: "Beh, qui il prodotto usa hibernate, e come ben sapete con hibernate potete usare MySql [pausa artificiale] piuttosto che Postgres [pausa artificiale un po più lunga] piuttosto che Oracle, [qui fa la faccia navigata, del tipo che ha la tecnologia in mano, li sa tutti ma non serve dirli] o quant'altro"

A questo punto di solito mi voglio alzare ed urlare, ed ultimamente mi trattengo sempre più a fatica. "Piuttosto che" in italiano non ha valore disgiuntivo, non è sinonimo di "oppure". Manco per sogno. Si usa per dire "Piuttosto che comprare il tuo prodotto, mi faccio frate", ossia esprime come minimo una forte preferenza, se non addirittura una scelta già fatta od obbligata. Usarlo come disgiuntivo è un vezzo snob, ed è pure sbajato. Secondo Beppe Severgnini il mostriciattolo "piuttosto che" è di provenienza "agiato settentrionale", ma credo che ormai abbia invaso tutta l'Italia.

"Quant'altro" invece non so proprio da dove venga e perchè. Forse il neosnob, memore dell'avvertimento della maestra delle elementari di non concludere mai le frasi con eccetera, pensa di trovare salvezza in questa schifezza? Suvvia, diciamo eccetera, o meglio ancora non diciamo niente. Oppure concludiamo con una bella ricorsione infinita così il cervello va in tilt e il problema è risolto alla radice.

Ora mi sento molto meglio: ho messo giù i miei pensieri sconnessi e mi rendo conto chiaramente che odio molto di più i "piuttosto che" che i "quant'altro". E' già un bel risultato, no?
Comments (3) Show Comments