Timeline for Sharing link to software installer
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2017 at 17:33 | comment | added | Michael Schumacher | I am aware that GIMP is used mostly as an arbitrary example here, but let me add the following: we prefer links to our downloads page, because we can always link to the most current stable version from there. Deep links to specific files can trap users with old versions - please do not do this if you won't have control over the location where you've published at a later time. | |
| May 26, 2016 at 13:48 | comment | added | Michael Hogan | The examples you've given for how to present the links are the primary kind of guidance I'm looking for... How to create a sense of trust so the end user feels safe to click the link and isn't surprised. | |
| May 26, 2016 at 13:17 | comment | added | Brian | To point out the obvious: Before asking the author for guidance, check if the author has already provided guidance. Such guidance comes in two forms: 1) The author asks you to do something. 2) The author's license requires you to do something. For example, some freeware software explicitly forbids hosting the download yourself, whereas GPL software always allows you to do so. After all this, you'll know, "I'm allowed to do X,Y, and Z. The author's preference is for Y and Z." Mind you, none of what I said is UX-related. | |
| May 26, 2016 at 9:51 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
added 327 characters in body
|
| May 26, 2016 at 9:45 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |