Jiten's dashboard

Yes, I agree, we don't need another IM network. How about implementing a Jabber server in wuala client? that way you can use external programs for the actual communication and would allow for same IM names as Wuala names. That way you can leave chat and VOIP functionality for whatever programs the users choose to use.

Devices that are wuala clients but that aren't actually interactively used could identify themselves as such. In addition there could be an idle timer that gets reset when the user does something. The situation isn't really different than with the IM clients.

FUSE has been around for quite a while and I'd expect any distro release during the last two years to have it. There is also FUSE implementation available for Mac OS X and it looks like a windows version exists too.

NFS-server approach has some problems if you were already running nfs-server. Luckily I no longer needed it so I could turn it off. I didn't manage to get wuala's NFS share mounted without shutting down the original.

1. I've toyed with 2 ideas concerning used storage sharing.

First option would be to simply just share used storage evenly. However this has the potential to be rather jumpy for some files and keeping it synchronized might use quite a bit of resources. From users' point of view, though, this one is the least effort and simple to understand.

Another option would be to not share used storage but allow users to specify how much of their space they wish to reserve for catching copied files that get deleted from the original owner's files.

2. I'd suggest 2 kinds of copies. Private copy, meaning that as far as commenting is concerned, it's a different file and Linked copy that keeps the comments but somehow indicates which comments are from which copy. Maybe even have 2 kinds of comments? public comments that show on all linked files and private comments only on the specifc copy.

3. I think groups should have storage allocation too. Users could give a part of their own to the group and perhaps automatically on copy if there is not enough available. The group system does need some more polishing, it's rather limiting that only founder can create directories or invite members for example.

4. I think it's unlikely to be a big problem. When there are copy owners left but their combined available storage isn't enough to keep the file, I'd suggest emailing the owners. There could be a list that has files in danger of deletion unless enough available storage allocation is found, of course only of files the user has access rights to. In any case, a notification for people who have favourited (or copied) the file in question is probably a good idea.

I don't know what happened but I no longer have this problem.

Right, I probably should've mentioned this seems to happen only with images from world tab. One of my friends, who I invited, also has the same problem. However, it looks like shared (not public) images work just fine. At least ones we have very recently uploaded. I'll do some testing on whether making them public changes things.

Update: I don't know if this is related but some image files I tried to upload don't seem to be uploading. They show up but can't be opened.