nickname's dashboard

nickname replied to "Blue screen with Kaspersky AV 2009 on Vista x64", but it was removed. see the change log

A comment on the question "http://www.lacie.com/de/products/product.htm?pid=11136" in Wuala:

its not exactly unsolicited, as wuala now belongs to lacie, and lacie has apparently had a similar product even before it bought wuala. whats the big deal? is your problem the lacie takeover or the comments in this "forum" that you dont like. if you cant live with lacie, you better stop using wuala. other than that you better start chilling. – nickname, on March 22, 2009 00:57

nickname replied on March 20, 2009 08:00 to the question "broken menus" in Wuala:

its broken then ;p reinstall your winblows :D

nickname replied on March 20, 2009 00:36 to the question "broken menus" in Wuala:

restart your wuala. it probably didnt update or load all its resource files (jar and so on) properly.

A comment on the idea "wuala gets merged with lacie - oh noes" in Wuala:

why you meeting with them? what you doing with wuala folks xactly? :) greets m8 – nickname, on March 19, 2009 20:42

nickname marked one of Bugreport's replies in Wuala as useful. Bugreport replied to the idea "wuala gets merged with lacie - oh noes".

A comment on the question "Friend can't upload more than 1Gig into my 82Gigs?!" in Wuala:

;) its all on the website. you dont actually share space in a group, but only share control and can arrange and sort stuff, group logically, manage users content and shit like that. sharing space and hosting for others, donating space and stuff was already being proposed. but as a simple workaround (but not very highly controllable) is to let the desired user log in to your machine(s) where you generate high storage quota (uptime availability) once and thus the earned storage space gets divided on that machine every user that once logs into a wuala client profits from it earning storage. so it can be either pretty practical to earn storage for other wuala accounts (friends, family, company, work, collegues,....) but it can also be exploitable. people logging into your wuala clients when you dont have proper control over the machine eat up your earned storage and canibalize on your primary users storage credits :) – nickname, on March 19, 2009 19:15

nickname replied on March 19, 2009 18:59 to the question "Friend can't upload more than 1Gig into my 82Gigs?!" in Wuala:

huh? you can only upload "into" your own earned contigent/credits. he cant use your credits. in groups any everywhere everybody brings their own quota and space.

ever been reading those faqs, howtos and documentation?

nickname shared an idea in Wuala on March 19, 2009 18:34:

wuala gets merged with lacie - oh noes

http://www.wuala.com/blog/2009/03/exc...

wonder what will happen to opensourcing wuala after all. didnt hear any praisals or recommendations ever so far about lacie stuff.

in fact, quite the opposite. you decide.

nickname replied on March 18, 2009 14:31 to the question "today i can t connect,wuala make something on their server?" in Wuala:

ditching doesnt necessarily mean abandoning it alltogether. you can switch datacenters or switch providers, or add different ones for fallback, backup, redundancy

nickname replied to "today i can t connect,wuala make something on their server?", but it was removed. see the change log

A comment on the problem "Filesystem Integration did not work with OpenSuse 11.1" in Wuala:

herm... but according to opensuse and novell pages this looks like an oss successor that is superior to portmap wich is udp/tcp v4 only

http://www.novell.com/products/linuxp...
http://nfsv4.bullopensource.org/doc/t...

well there are some migration infos about how to get from portmapper to rpcbind, maybe will try that stuff some other time, or anybody else willing to check and run some trials. – nickname, on March 17, 2009 16:32

nickname replied on March 17, 2009 13:12 to the problem "Filesystem Integration did not work with OpenSuse 11.1" in Wuala:

i didnt look into this rpcbind and portmap stuff, but will this ever get resolved differently? will wuala also work with rpcbind some day or is it simply incompatible with rpcbind?

is rpcbind supposed to be some successor of portmap or whats the exact deal?
greets.

nickname started following the problem "Linux client is very temperamental" in Wuala.

nickname replied on March 13, 2009 19:52 to the question "work with access back-end on wuala and front-end on my own computer" in Wuala:

basically all you can do is work with you access file (.mdb i suppose or something) locally on your harddisk. and whenever you are finished using access you simply copy/sync that local folder where your .mdb access file is into your wuala storage folders.

you only save/sync the mdb file "once" at the end whenever your work is done with access.

only way to work with big and frequently changing files and apps that dont create tempfiles or diff-files locally and save the actual file only at the end or few times only.

nickname replied on March 13, 2009 14:16 to the question "work with access back-end on wuala and front-end on my own computer" in Wuala:

wuala always stores complete files. that the smallest item it can store. many programs need random access (especially also writing) inside their files. that doesnt work with wuala as long as such apps read and write into big files constantly (within a very short amount of time).

what platform are you using for your frontend and where is the backend (wuala) running on and how do you interconnect these two?

you could copy the file to your local storage first, and then analyze how access exactly works on that file (windows i suppose... filemon and other systools are your friend). if you seed bytewise read/write access from your access.exe ;) to that file it will not work directly from the wuala storage.

the solution would need caching of the whole file and some kind of algorithm that would allow the wuala client to know when it would actually make sense to write back the whole file into the wuala cloud thus updating the file being represented in the wuala storage space.

i doubt that it will be possible to solve this kind of problem in general in the near future.

wuala is simply not made for this problem. its an archive space, and not a live storage space like a real harddisk with bytewise random access.

nickname replied on March 13, 2009 10:04 to the problem "Command line fails to give prompt" in Wuala:

the prompt shell was long gone. many months now if im not mistaken. i liked it better. there is no command completion in this way :(

nickname replied on March 12, 2009 18:05 to the problem "Wuala löscht mp3's beim ändern der ID3-Tags" in Wuala:

huh? chaning id3 tags means editing the file. editing the file creates essentially a new file, and a new (different and distinct) file hash, as its a different file from there on. why would wuala delete your file when you are editing it? its maybe a simple incompatibility with your music player/editor and the way it actually tries to modify and edit the file. send a bugreport

nickname replied on March 12, 2009 00:41 to the question "how much redundancy in traffic does one upload generate?" in Wuala:

cant be true. especially on slow lines or with very big files you are able to observe that wuala shows progress as 100% but the file is still grey and not finished and accessible. only after a while when it appears on the maintenance tab in the client the file is finished.

i know that maintenance is generating multiple chunks and re-uploading the file redundantly. but there is some percentage in difference even on the first upload before it becomes available in my opinion.

only the devs can tell exactly how their algorithm and system works.

nickname asked a question in Wuala on March 11, 2009 20:08:

how much redundancy in traffic does one upload generate?

how much upload is being generated when my filesize is 100%? wuala never stops generating traffic at 100% fileupload, but uploads (to be seen in mantenance) much more. what is the factor for each file? i suppose its my client that is generating the redundancy chunks, or uploading the redundant chunks into the cloud. are there any exact details about total traffic that one file generates? (in %)

my question is strictly for first-time initial uploading of a single file. file is 100kbytes in size, or 100megs. wuala uploads n*filesize (n>1) during initial upload. how big is n?

thanks.