Option to disable confirmation prompts on remote editing save/upload

[Andrew]

Please read the whole thing before you disregard it yet again. I am posting this as a new issue, even though it is a very old issue, because the alternative would be to reopen one or all of these issues:

​http://trac.filezilla-project.org/ticket/4694
​http://trac.filezilla-project.org/ticket/2914
​http://trac.filezilla-project.org/ticket/2992
​http://trac.filezilla-project.org/ticket/2341
​http://trac.filezilla-project.org/ticket/5295
​http://trac.filezilla-project.org/ticket/1670
​http://trac.filezilla-project.org/ticket/5582
​http://trac.filezilla-project.org/ticket/5005
​http://trac.filezilla-project.org/ticket/5303
​http://trac.filezilla-project.org/ticket/5157
And on the forums:
​http://forum.filezilla-project.org/viewtopic.php?t=14672
​http://forum.filezilla-project.org/viewtopic.php?f=2&t=5416
​http://forum.filezilla-project.org/viewtopic.php?f=2&t=20445
​http://forum.filezilla-project.org/viewtopic.php?f=2&t=20554
​http://forum.filezilla-project.org/viewtopic.php?f=2&t=20081

I have read every single post of every thread listed above, and I fully understand the technical issues raised -- really, I do. Codesquid/botg, you seem to regard this as a foolish request for a minor feature that would cause major problems. But the risk is on the extreme fringe -- a vanishingly small percentage of the FileZilla userbase whose presumed stupidity somehow outweighs the NEEDS of the vast majority who only edit small text files.

The confirmation prompt is not a minor annoyance, it's a major and unnecessary BOTTLENECK IN OUR WORKFLOW. I sometimes save/upload/refresh SEVERAL TIMES PER MINUTE, often with several files at once. That prompt absolutely kills my productivity, but the only way I can get rid of it is with a hackish AutoHotkey workaround or to patch the source and recompile??? That's just ridiculous, and here's a list of other FileZilla users who have already taken the time to post on this ticketing system to express interest in this simple but crucial capability:

sparkey0
miked
mslade
jonathanbruder
Redsandro
viniciusandre
triple5
mike810
martinsustek
frogworth
rufwork
jdoree
roti
thlayli_x
ultrasick
s0l1dsnak3123
Troop116rules
alisalaah
mildavw
baz4096
ciantic
daemon72
Justy
suamisoleh
Pinchiukas
Grzegorz
whymydigg
pontiac76/pontiac_76
kotecky
buddhaflow
bl4nk
terasek
galundin

And on the FileZilla forums:

doublethink
jesus2099
jumpfroggy
ElPazzo
Ray Yates
George-FZ
kadarx
abdullah512
masterdam79
pants
pawz
ryan4021
asmodeus
qidizi
azoundria

Please consider that list a petition.

Among all these tickets and forum threads, I found only ONE user who expressed full agreement with the current policy of requiring a prompt on every save/upload with no available option to bypass it:

charlieangel784
(...boco? He hasn't publicly disagreed with your stated position, but he has reluctantly admitted that the current situation is a real problem.)

The rest of us are not simply a vocal minority, we're the vast majority of your users, and we're a lot smarter than you give us credit for. We're not asking you to endanger the integrity of those fringe users' data, we're only asking you to give us the opportunity to gain an ENORMOUS improvement in the efficiency of our workflow through a simple NON-DEFAULT option with a very clear warning/disclaimer right in the GUI. There's NOTHING UNSAFE about that!!! It's not the developer's fault if grandma formats the root partition, and it's no reason to take away the format command just because somebody might accidentally destroy their data. Some amount of hand-holding safeguards are appropriate, but ultimately, you just can't save stupid users from themselves -- certainly not at the expense of the great majority who are unaffected by the risk in the first place.

So here's an original suggestion to legitimize this post as a new issue: whitelist and/or blacklist by filetype and/or external editor program. That's clear enough, right? Whitelisting would only allow bypassing the prompt on filetypes or editors known to be safe. Blacklisting would only forbid bypassing the prompt on filetypes or editors known to be at risk. The community could maintain the list(s) so you don't have to deal with the tedious details. Of course, it's easier to just have a bit more faith in the intelligence of your users -- or a healthy disregard for their self-caused problems -- but if you're adamant on protecting them from their own persistent ignorance, this is a solid solution. And please don't tell me it's a "technical impossibility." ;)

Seriously, though, thanks for all your hard work over the years. FileZilla is truly wonderful and very appreciated.

• Andrew Lundin