P. S.: Post Scriptum

We seem to have made it.
The website is now hosted on different servers, at dreamhost.com.
Of course what could not be done was to resurrect the wiki, which now should instead be recreated from scratch. And, much worse, the mindmapping tool. The page from which it was possible to make a mind map of a delicious account. Right now I have unfortunately no time for much, as I am in the last months of my Ph.D., yet I hope to find at least the time to put back the program to make the mindmaps. So at least people will be able to make the mindmaps themselves. Apologise to all the spammers that sent me spam in the last 2 weeks. Knowing that all the latest comments were going to be lost anyway I avoided to mark them (about a thousand messages) as spam. Please don’t feel ignored, just sent your message again and I shall trash it asap.

I just came back from the vacations to discover that my website is now a mess.

All the delicious mindmap data have been deleted, and so did the MySQL data of the wiki.

I am not really sure how it could happen, but I am just not going to investigate.
I am, more pragmatically, moving my website to another host. It will take some days, and a lot of the data will in any case be lost.

Please if you came to my page looking for any of the previous services: the delicious mindmap, the wiki aggregator, have patience.

As soon as the transfer have been made, I shall post a new message.
So if this current message is the last one, you know that we are still using the old host.

Pietro

Finally the time has come. Although I wanted to do this from a long time, only now did I found the time and the technical knowledge to do it:
I divided the blog.
I divided all the Italian posts from the English ones. I created a new blog at http://it.pietrosperoni.it, and my italian posts will, from now on, be posted over there. And only over there. Most of the people (3) who read me (5) either read Italian or English posts. And I am sure it must have been very confusing to scroll through a page and find some posts in English and some in Italian. Plus I always had the sensation that I could not write too much in one language, or possible readers of the other language will just assume the blog contains no information at all for them, and dismiss it. This in time made me slow down posting, as I could not always follow particular threads, that would have involved to post many times, in one language.
But now all this has come to an end.

Of course if you want to read entries from both blogs you should add the rss from the italian blog too. Some topic will remain confined to this blog (like tags, for example), others will remain there (like italian politics), while other will span through both medium (like diet, which already is present in both). The wiki in this case should act like a glue, creating a space where entries from both are aggregated. Plus, being a wiki, I (and whoever wants to come and play) will use it to keep notes, aggregate extra content, and generally make some pages stand out while others will only show the blogs entries, the bookmarks, and the context (i.e. the links from delicious popular page, and from technorati).

Generally it is not a smart idea to to come here every time to see if I have written something. I tend to write when I have something to say, so many days might pass before I say something, then for some days I might make one or more post a day. The solution is to add my rss feeds to your feed reader. Bloglines is a good one. I am sure there are better ones. Feel free to suggest them (as I am always looking for ways to improve).

Now let’s get a bit more technical: making this change also meant getting my hands dirty with MySql Continue reading The Italian blog is born: reasons and technicalities

I think it’s the time to present what have I been doing in the last days. A number of improvement have beed added to this web site. In short I have upgraded to wordpress 2.0. I also moved to the next version of wikka. Some of you might remember that I offered some money to whoever could write some code to get the tag plugin to generate an rss list. I didn’t, at the time, explained why. I will now.

Wordpress 2.0 gives the possibility to start categories on the fly. Just adding them, by listing them. Essentially this makes the category in wordpress work like tags (or keywords, for academics). But categories in wordpress also have an rss feed connected to them. Albeit with some bugs, like linking to the whole blog and not to the particular category. So I passed most of the first of January adding to the entries the relative tags as categories. So now I have no need of an rss feed for the tag page, as the tag page has been substituted with the category pages.

You also will rememer that I installed Wikka. The wiki engine. Now wikka is not only open source but also easy source. It is so simple that even I could hack the code. That is very simple! So I changed the code and inserted the possibility to have default pages. In short if before if you were to look for the url http://wiki.pietrosperoni.it/someunexistingpage and there is no page in the wiki called “someunexistingpage” the result would be that the wiki would ask you to edit the page, and you would be redirected to http://wiki.pietrosperoni.it/someunexistingpage/edit.
Now he would create on the fly the page someunexistingpage with the default content. And the default content I chose was the 4 rss feeds:

• the feed from my blog from the category: someunexistingpage
• the feed from my technorati from the tag: someunexistingpage
• the feed from my delicious bookmarks from the tag…
• and the feed from the popular pages in delicious, always from that tag

So for each tag I now have a wiki page with the most relevant rss appearing there. But being a wiki page I also can add other rss feeds, write definitions, comments, todo lists. In short modify it as I see fit.

Still it is not perfect. As it writes the page the first time, from that moment the page is set. I can delete it, but I cannot, for example, change the default content for all the pages that only contain the default content. I tried to write a plugin to do that, but I failed when I confronted the fact that I needed to write a plugin {{defaultpage}} who should have activated other plugins:{{rrs}}, for example. Something that I ignored how to do.
Also having the same string to work for delicious (as tag), wordpress (as category name) and wikka (as pagename) puts some heavy constraints on what the string might contain. For example I am already running ashore for all the tags that contain a dot inside (aaargh, del.icio.us!) or an accented letter (aargh, dear italian).

If you want to see how the pages look like just see the idea page. But any link from the right column (provided they have no dots inside or accents) will work fine.

I have to say that I amvery impressed with Wikka. Wikka is a wiki software that I just installed on my web page. It is simple, yet full of plugins. Open source (or I would not consider it). It also permits to integrate freemind mind map inside it. More than this: for each page the administrator, (ehm, that is me!) can decide who is allowed to read, write and comment. I installed it about one week ago, and I avoided to make it public until I would found a way to deal with wiki spam. I already have too much spam on this blog. Finally I found what I think is the perfect solution:

1. only registered user can comment and modify the wiki. It might not make it very fast, but at least I know who said what.
2. I inserted a plugin such that to register people must write a password in the ‘registration code’. But the password is written on the same log in page.
3. To write spam in the wiki they have to manually register. Which I feel is fair. I have no anger toward those that manually spam. Are the mechanical ones that ought to be stopped.
4. If the spammers write something that automatically register, I will change the registration code.
5. And if they write something that automatically grabs from the page the registration code I change the context (the phrase in which the code appears), making their software useless. I will move from:
   • registration code:”pippo pluto” to
   • registrati0n code:”pippo pluto”

As you cannot code for something that blocks all permutation of the word “Viagra”, so you cannot code for something that codes for all the permutation of the phrase: “Registration Code”. Ah! And this is the revenge of the mass!

I think the idea is so brilliant that I will look if I can find a similar plugin for wordpress.

The next think that impressed me in Wikka was the use of rss. It is actually very easy to integrate an rss in a page. Maybe it is the same in other wiki engines, I don’t know. But on wikka it is absolutely trivial. You just need to write {{rss url=”http://the.rss.net/address.rss” cachetime=”30″}} and the rss gets taken shown, and cached for 30 minutes. Now 30 minutes cache is what del.icio.us requires from you if you are going to connect an rss to your homepage. So now I have started to integrate all sort of rss from delicious to my web page. Check for example my Tag Cloud page. With the rss from my personal bookmarks tagged with tagcloud, rss from the popular page in delicious delicious/popular/tagcloud, and the rss from technorati (i.e. people who have blogged on Tag Clouds).

And all this is in the floating right bar. So I still can use the rest of the page as place for me to write content, and notes…

And as notes taker this wiki is slowly becoming. I started moving my Reading List to the wiki. And I added to the reading list, the rss of popular reading lists. You see, how it all comes together.

But this is not all! Wikka (and they should pay me after a post like this!) gives the possibility to set the privacy for each page. That is for each page you can chose who can read it, who can comment on it and who can change it. In this way I can use this not only as my personal notes but as the notes for project that I might be sharing with other people.

Come and say hello: http://wiki.pietrosperoni.it

Wikisource is a repository of open source materials. Various texts are present, all totally open source. This resources repository is necessary, as the commons are getting daily smaller. Well, browsing among the present texts I spotted: The declaration of war on Germany dated 1917.

We keep the document in this repository to give to all the nations the possibility to wage war. Imagine if now someone were to declare a war… copying some of the concepts from this historical declaration on war, and the US were to require a percentage.

Too bad we didn’t patent war when we were in time.

I am at the Semantic Web Applications and Perspectives. Is the first Italian Semantic Web Workshop. It took some time, but finally Italy is moving along too. The talks are mostly in English, and more and more people here speak English really good, which use to be rare in Italy.

My first impression is that there is a big gap between the applications that try to enforce a unified onthology from above and the one (very rare) that have an open mind and gap different onthologies, or even work with open onthologies. I am still half way, but so far I feel I found really interesting:
Peer-to-Peer Semantic Coordination and Platypus Wiki: a Semantic Wiki Wiki Web.
On the second:
Google Search, c2 page and the sourceforge project page.

More to come