Consider moving off Sourceforge
Given the issues some projects have seen with hosting through Sourceforge (GIMP, more recently Nmap), and unetbootin already using Github's releases page ( https:/
I have two specific reasons for this request:
1: unetbootin, as reported on the Sourceforge page right now, sees over 115k downloads per week from Sourceforge. If Sourceforge were to do a similar GIMP-style stunt with bundling adware for even just the Windows downloads, that's almost 89,000 affected users each week!
2: Sourceforge redirects users *to* insecure downloads over http, even if a user specifically uses an https URL. Github serves content over https, and redirects users from http to https in the case that they manage to get an http URL.
I'm not sure if releases on Github can be retroactively edited to include binary releases as well, perhaps it could just be a change for the next release onward? Of course, traffic wouldn't necessarily move over quickly, and Github may end up in the same situation some years from now just the same. Googling "unetbootin download" shows Sourceforge for the first three results, and inertia will likely keep it there for a while as well.
Even considering the above, I think it's worth at least dual-hosting on Sourceforge and some other alternative. I only mention Github in particular because it is also free, and already in use for unetbootin source.
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- UNetbootin Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply: