Recently created ideas in Wuala tagged with upload

When I'm uploading pictures, I usually upload hundreds at a time. It would be beneficial if I could see the overall upload progress so I can get some sort of idea as to when it'll be done.

Suggestion:

Overall Progress: 24% (uploaded 56 MB of 233 MB, 32 files of 114 completed)
Estimated time left: 5 Hours, 24 minutes

I think it would great if wuala had an option to verify the uploaded contents with the source file maybe with an md5sum or something. And also an option to force the upload for files that don't have the same checksum.
Thanks,
Ron

Hi,
ich hätte da eine idee bzw einen Vorschläg. Wäre es nicht möglich ein Programm für Linux zu schreiben mit welchem man Resourcen auf einem Rechner freigeben kann.
Die einstellungsmöglichkeiten sollten für Dateigröße, Uploadgeschwinddigkeit sowie ordnerfreigabe, Portwahl und eine Begrenzung für die Verbindungen wären sehr schön und würden reichen (bei der Ordnerfreigabe müsste es auch möglich sein verschiedene Ordner freizugeben (falls man beispielsweise mehrere Festplatten hat).

Falls es so ein Programm berreits geben sollte sorry ich hab ́s nicht gefunden ;)

gruß

Request Feature

Hi

it would be awesome if wuala let the admin or/and mods know who uploaded something to the group... ok, you can see it on every single file who uploaded it, but thats very time intensive if there are much files :)
some groups dont like leecher, and this would help i guess....
maybe also a new role (automatic) for uploaders...

thx

It would be nice if there were more statistics in the program. Ones that I personally would like are:

Estimated time to complete upload of a file(I know upload speeds jump around a lot but maybe if you use the average for the past 10 seconds or something)
Estimated time to complete upload of all files pending
Under file uploads and downloads a time stamp with a date (for maintenance uploads too)
Total amount (MB/GB) people have downloaded from files I share (Separating Global and friends would be nice)
Total amount (MB/GB) people have downloaded from me if I share my hard drive (So if people are accessing my computer for fragments of other people's files I am curious to know total amount of information I have uploaded that is composed of other people's fragments)

feel free to add your own suggestions

I think it would be a great idea that everybody could share more files with his friends than his space would allow.
This could work this way: Every user could have an "offers"-folder in wich he stuffs all the files he wants to share with certain persons or groups.
Then only the filenames and hashes are saved, not the files themselves.
If files the user offers already exist in the wuala network, they could be "linked" to the file without being substracted from the users space contingent.
The more important idea is that people could "download" the file offers this way:
A friend clicks on the offered file, then the file is automatically uploaded by the user who offers the file and stored in the wuala network as soon as he or she signs on in the wuala network.

What do you think about this idea? Please share your thoughts by commenting this entry.

Ich bin 24/7 online mit meinem Rechner und Wuala läuft ständig und lädt mit 10 bis 400kbs permanent hoch.

Dadurch bekommen die Leute ihre Daten, die auf meinem geteilten Speicher liegen.
Da das eines der Grundprinzipien von Wuala ist, sollte man dafür auch mehr Speicher bekommen.

Dadurch würde es vielleicht noch mehr "Power User" geben.

I need a button and visual feedback to verify that all the uploads are done.

I often work in a laptop and when I am finished, I copy the current work to Wuala and shut down the computer. When I go to the another computer next morning, I get a message that the file is not uploaded.

I even once got a crash during the upload and the file was not uploaded in any of my computers!

So I want some transaction kind of thinking here. When I copy a file to wuala, I wont it certainly be in the local cache when the operation is finished. I want to be able to delete the file at this point and be sure that Wuala takes the responsibility of the file - even thought it is still in the local cache.

In the transaction two I want to be sure that the file is available from other computers. I want a visual feedback when this has happened and I want to be 100% sure that it has actually happened. Even if a lightning hits to my computer at the same second.

And I certainly don't want that the system updates the metadata before the actual data. If the upload fails, I want to find the current version. Currently I get a message that the file is not uploaded and the old version is not available.

I don't think that Wuala makes a good job with these transactions currently. At least I have LOST some important data already.

It would be nice if in the status area (Where it shows transactions, Encrypting status, etc.) it would show what the application is doing. Like "Uploading mycooltestfile.txt (48%)" and "Maintaining mycoolmusic.mp3 (99%) - 239 Files Remaining"

hi there,

from time to time i need to startup a wuala client at some remote destination (clients, friends, whatever...) and just log into my wuala useraccount and just dump some files/data into my wuala-space. what i am wondering about how quickly i can logout/close this temporary wuala client so that my uploaded/added data stays alive in my wuala dumpspace.

it would be best if a running client when doing uploads, would first look for other clients running with the same credentials and then trying to dump the data first to these same-account nodes, or maybe after a while there could be also nodes of friends (wuala friends), or the nodes that a wuala node is closest to (network-wise) and so on....

sometimes i have only little time to let this temporary wuala node running, and i dont know when i am on the safe side so that my uploaded file(s) have safely arrived inside the wuala storage space.

maybe you are even already doing this on your clients/nodes, but it hasnt been clear, thats why i have posted this.

i have also read about your plans, there there will be a standalone wuala java-only (non-install) client, which could (probably) run from websites (applet) and so on, without real installation on any operatingsystem that comes with java support.

this would also make sense, to have these java (most likely) temporary clients to first try to communicate to other running clients of the same user, so that they spread modified/new data to the more stable and persistent clients of the same user first, and that those clients then take over the spreading and distribution of the data fragments/parts.

thanks and cheers.