Cyberduck Mountain Duck CLI

#3937 closed enhancement (fixed)

Fix annoying donation panel

Reported by: abhibeckert Owned by: dkocher
Priority: normal Milestone: 3.3.1
Component: interface Version: 3.3
Severity: normal Keywords:
Cc: Architecture:


The periodic "please donate" panel in Cyberduck is extremely annoying.

I love open source software, and am involved in more than one project myself (one of which has received thousands of dollars in donations), but I would never harass people the way Cyberduck does.

I'd like to see requests for donations become a lot more subtle (maybe a menu item, a prominent button on the website, and a prominent button in "new version available, install now?" messages.

I realise it costs money to create/distribute quality software, but if your project is good enough (and Cyberduck certainly is), then there's no need to nag people. The donations will come regardless, and plenty of them (I know this from first hand experience).

I'm almost annoyed enough to create a fork of the project without any such harassment.

Change History (4)

comment:1 Changed on Nov 20, 2009 at 1:15:57 PM by dkocher

  • Component changed from core to interface

We display the donation prompt when no donation key is found and

  • When launching a newer version than previously opened.
  • When you click Don't show again for this version it is displayed again nevertheless after 30 days.

There are no other limitations when using Cyberduck without any donation key or other visual reminders whatsoever.

comment:2 Changed on Dec 14, 2009 at 3:07:15 AM by

I checked the "Don't show again for this version" and clicked later, however it still asks me to donate every single time I quit the program. In the past it would only ask once per version. The window now prevents my Mac from shutting down until I handle it each time. Tried deleting the two config files and it didn't help.

comment:3 Changed on Dec 14, 2009 at 6:38:52 AM by

Like Tom, I get the nag screen even if I ask for it not to be shown again for this version.

comment:4 Changed on Dec 14, 2009 at 8:24:50 AM by dkocher

  • Milestone set to 3.4
  • Resolution set to fixed
  • Status changed from new to closed

This is a bug in 3.3 (refer to #3994) fixed in in r5610. Thanks for reporting this issue!

Note: See TracTickets for help on using tickets.