Last modified: 2011-01-25 00:32:09 UTC
Uploading a video file (see URL) to Wikimedia causes my otherwise stable connection to drop. It's your site and not my connection as I can upload the same file to my own web site without incident. I used to have similar problems with YouTube until I used MS "Gears" (which YouTube provide as an option. Might I suggest you do likewise.
Note that source file is 52mb, well below the 100mb upload limit. Nigel, can you describe what you mean by the 'connection dropping' in more detail? Do you get an error message, blank screen, etc? You might be running into bug 19476 which is in the post-upload processing, not related to the actual upload transfer process (but still damned annoying!)
There are post-upload drop outs too and these might be due to processing. However, there is a connection loss during uploading too. I don't happen to know the right technical term for it - but you would get a similar result if you presseed the reset button on the WiFi hub. No on-screen messages - just a change in the status icons on the windows taskbar. Please stop trying to shift the blame somewhere else. Since I wrote to you, YouTube have changed their upload in some way that makes it more stable ...ask them how they did it (they might even tell you).
(In reply to comment #2) > Please stop trying to shift > the blame somewhere else. Assume good faith. Brion wasn't trying to shift blame away from MediaWiki, just to a different process *inside* MediaWiki. However, your experiences seem to indicate he's not (completely) right, as you have connection loss during uploading as well. > Since I wrote to you, YouTube have changed their > upload in some way that makes it more stable ...ask them how they did it (they > might even tell you). If I had to guess I'd say they probably use chucked uploading (dividing the file into smaller pieces (chunks) and uploading them individually), which is also in the works for Wikipedia. The fact that the icons in your status bar change indicates your entire internet connection is dropping, not just the connection between you and Wikipedia. For this reason, I think the problem is most likely with your ISP or somewhere else between you and Wikipedia, and may be triggered by the size of the file you're uploading (this would also explain YouTube uploads now working right, assuming they did indeed switch to chunked uploading). I'll ask a more qualified person to comment as well, though.
Could you elabourate as to what your network setup is (ie internet connection type, network type - wifi/wired) Which status icons? What do they change from/to? If you're using a router, is the firmware on it upto date? Can you check what MTU size your pc is using, and also what the router/modem is using? I'm not saying Wikipedia isn't to blame, but it would seem more to be more a configuration at your end
There is one significant hole in the argument that my system is to blame and blame that must attach itself to respondents for not reading what I wrote (originally) with more care. To repeat. I can upload significantly bigger files to my own website without connection loss and thus the problem lies between my ISP and Wikipedia. I don't need a lot of opaque technological terminology here - just good old-fashioned logical deduction
(In reply to comment #5) > There is one significant hole in the argument that my system is to blame and > blame that must attach itself to respondents for not reading what I wrote > (originally) with more care. To repeat. I can upload significantly bigger files > to my own website without connection loss and thus the problem lies between my > ISP and Wikipedia. I don't need a lot of opaque technological terminology here > - just good old-fashioned logical deduction I guess we missed that, and it reduces the likelihood of your setup being to blame. Still, could you at least answer the non-opaque questions in comment #4? Also, did you upload the file to your own website using HTTP or FTP?
Friefogg chunk uploading may help out in cases like these, but we will leave the bug classified as invalid since nothing specific to this bug can easily be directly addressed.
