There are many books available for students who looks for free textbooks. Ask your public or academic library for advice on their databases and which books or article could be relevant to your research. In Norway there is an excellent service with volunteering librarians who answer your questions via phone, email or chat - and most recently also facebook and twitter. It is called Biblioteksvar.

The synchronizing of content that doesn't come from the store your device is locked to, can, however, be a pain. Calibre is a tool that can help you there. The software collects all your ebooks in a library, you can convert them to other formats and push them to your reader when it's connected via USB. Calibre has also predefined tasks of collecting news from feeds, converting them to easily readable ebooks, and pushing the daily news to your device. This works for Google Reader and ReadItLater, too.

The nook is root- and hackable. It runs Android, and if you follow the instructions of the nookdevs, some neighborly concerned Android hackers, you can get around some of the nasty restrictions when you have bought a nook and want to use it outside of the U.S. It voids your warranty, though. You get a web and file browser, a feed reader and lots of other functionality. Someone has even started developing a twitter client, Twook. You will also get the chance to get familiar and comfortable with the Android SDK, and you should be comfortable about using the command line to do all this.

I like paper. I really do. I am a big fan of paper hacks, book binding and paper as a note taking tool. But my fandom only bears so far. I do not wish to carry a big stack of heavy paper books with me when I am traveling, which I do. Or when moving. I do not wish to break my back, or the backs of my helpers. Not every book is worth reading twice, and when it comes to design and typesetting only very few books are that beautiful that you want to collect them because typesetter, printers and book binders have done such a good work. So the ever so often sigh of librarians ("but, what happens to the books!"), well... Let's just say, I am not very worried.

So, why the nook. Right now there are only two devices to my knowledge that feature what is important for me in an ebook reader on the market. (Like, really on the market, not long waiting lists for especially interested people.) Both the Amazon Kindle, and the Barnes & Noble nook have wifi and 3G capability. Both of them have a long battery life when reading, and both seems to be somewhat longlasting. Also, both of them have e-ink screens. (I consider the iPad to be crippleware and not an ebook due to little battery capacity and backlighting. I like shiny devices. But not this one so far.)

I like the nook better, simply because he has a touch screen instead of a keyboard. And because he runs with Android as OS, which also runs on my phone. Although I do not wholeheartedly agree with Google on development decisions and privacy issues, Android is pretty great when it comes to smart phones. Its somewhat open character makes problems set by Google and carriers circumventable.

What made me hesitate to buy either of the two devices, was the decision of the two book stores (and others along with them) and the book publishers to lock down the reading material as much as possible. Every ebook you can buy on Amazon are only readable on the Kindle reader. And you can only buy ebooks from Barnes & Noble if you have a US IP adress and a US billing adress.

Of course, there are other book stores. But a lot of pubishers have said no to selling their material outside the US. I fail to find the appropriate words for this stupidity. I am still looking for ways to buy books. Not to talk about checking out ebooks in a library. Apparently inhabitants of Denmark and Sweden can already do that. But in Norway, librarians and politicians are still busy with letting themselves get scared off by the lobbyists of publishing houses.

I don't want to be locked to Amazon. I buy the occasional book there,
because they have almost everything. I knew before about how tightly the Kindle is linked to Amazon. But experiencing how you really can't use any book that they offer in their store on your *reader, whatever reader that might be, made me really angry. And sure, there are ways of circumventing the lockdown of the Barnes & Noble store. But I ask: why should they be able to do that? Why should publishers and book stores be allowed to be so strict? Why would anyone want to prevent someone from reading a book. Let alone a book he or she wants to purchase?

Ebooks can be a great device for students, people with problems in reading can increase the font size to their liking. If people have their books with them, they will have so many good reading experiences, it could actually make reading popular. Or at least better apprehensible for those with attention deficits. You have a full-fledged full text search at your finger tip with every book that you read. What kind of information society locks down reading of books?

People, some of them librarians or teachers, are worried that people read less books now that there is the internet. Well, do you have to kill trees and emit lots of chlorine in the water, not to speak about the resources used for Transportation of physical books? Only to read a texts longer then 20 pages in a proper more or less linear manner?

Even if you are not against DRM in general. Trust me: You don't want DRM on ebooks.

PIXELS by PATRICK JEAN.
Uploaded by divisionparis. - Explore more music videos.

I have tried it, and I must say that my expectations were not met. Without all the bots now flooding Google Wave, wave is somehow a very slow realtime web-based Multi-User-Chat. My first thought was: This looks a little bit like the realtime chat-feature in that dinosaur ICQ version from almost ten years ago. Only in colour, and with maps, and...Well, probably not bad after all.

Another expectation is also not yet met: Wave being an open protocol, based on XMPP, which enables everyone to set up their own wave service. Similar to email, for instance. Imagine email not being implementable by each and everyone with a webserver. That would, obviously, be very bad. Or would it? So if Wave claims to be the new black email+, it can not only depend on Google as an organization, can it? As cloudy as it may be. As I hear, the open part of the waveprotocol is not yet very wave-ey. Which is sad. I hope, that point, too, improves.

Since I lowered my expectations, though, from a very high level, I find it a quite useful tool. I hope, the Google Wave developers will manage to make it a bit faster, though. The user experience is definitely lacking there.

Another reason for my disappointment probably was, that my experience is based on having only a few people to communicate with. At first, there where my friends. Most of them are quite savvy with communication, so we fiddled a bit, but we did not have much to collaborate on, since we live so far apart and don't really have projects we are working together on right now. But more and more people got on Wave, and in the last week I made contact with librarians in Norway, and not least (most of the) co-organizers of and speakers at the "Free and Open Libraries" conference about F(L)OSS software in libraries next week in Bergen, Norway. So we started collaborating, and suddenly the whole map inclusion in wave made a whole lot more sense.

The second  most interesting thing are public waves. I have searched for waves matching my temporary, or overall professional or private interest. I found interesting waves:

Open wave for librarians using Wave

Female Geeks

NaNoWriMo

Hackerspaces FAQ

And many more public waves. Something that I did not find, though, was a public wave for knitters, and it took off very fast from zero to 101 wavers contributing as of today.

Knitters on Waves

Although in the more tech-savvy wave topics people try to figure out things before they participate, many of they waves with specific topics end up becoming undertaken by people take about the Google Wave sandbox and about figuring things while they are at it. This is tiring, and I find myself not participating anymore where Waves become so bloated and cluttered with dozens or even sometimes hundreds of such messages.

What has not happened yet is the development of a certain code of behaviour, what people called "netiquette" (or something) before for this service. Some places people are concerned about it. Most places they are not. Gina Trapani and Adam Pash from Lifehacker have written the Complete Guide to Google Wave. And there is probably more to come. Not only explanations, but also features.

I am still waiting for things to get more exciting. I didn't use twitter much the first six months I had my account, and now I twitter a lot. With all the tummy-ache that follows, relying on a centralized server. So I really hope it grows on me, because XMPP is great, and I think it could become very useful.

The problem is that there are so many different cell phone models out there, with different screen sizes, colour capabilities, browsers. The networks differ from being very slow to very fast. Which leads to 35% less likeliness of completing a task with mobile browsing than otherwise.

• So it is important to deliver relevant content adapted to these situations automatically. Mobile tools need to be able to:
• Detect the device
• Switch to the adaption for this model
• Aggregate functionality and content to this situation, and
• theme it accordingly

Then the presentation went on to demo open.siruna.org and OSMOBI (which is in alpha) and to show how it is possible to make mobile websites automatically using Siruna's service, supporting the Garland theme and colour picking module.

It was interesting to see some of the paper modules, one of them made into a "screen"cast of how the site would act if the user started clicking on buttons.

The biggest hold-up for me is that you need full root access to the webserver, which I don't have. But it would certainly make things a lot easier. If we could develop and package a good solution for libraries in Norway, we could make it easily reproducable and accessible to other norwegian libraries.

• OAuth
• OpenID
• The Hire
• XRDS/simple
• Activity Streams
• OpenSocial

The talk was not so much about Drupal. But the point was that all those connecting methods were either very useful or very appliable. Tim argued that it was the main interest of nowadays social networks to have a centralized and locked-down user base and to own their data, and that therefore the interest of social networks weren't that big to build good open connecting methods or protocols.

One directory per site in /sites/*

Hosting: 2 apache servers and 1 MySQL

page views per day in the 100.000s
stable & dev/maintenace cost effective
code for all sites go in /sites/all/

different mysql-tables, admin-account is replicated through all tables (how?)

Boost module?

OpenAtrium is supposed to be an Intranet-like collaborative platform to share Documents, calendars and project/task-data. It is supposed to connect members of a group or a team at work. It looks appealing and it seems to serve its purpose from the beginning. It is one of the few approaches to package Drupal into a product, to download and serve from the beginning.

The talk showed its features, and also adressed the problem in Drupal development/site/feature building, where you have the very centralized repository of core at drupal.org, and the contributed modules, too. But when you want to make packages and built more features around them, there is no existing infrastructure to do so.

What was now implemented by pingvision, who took OpenAtrium by developmentseed in use, was a feature server, that is supposed to provide this function. It didn't get very clear, is this actually solves the problem, or if it is just a temporary workaround. It seems to me, that if OpenAtrium already steps out of the cvs/drupal.org way of working - using git and github - why not make the full step and host everything in open git repositories?