New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In-built news feed/button #911
Comments
This is a feature request, tag it as one, please. Thank you. |
Sorry but this screams bloat. non-Windows/MAC users couldn't do anything even if they wanted. They can't directly download a binary from us. They have to wait for their distro's packagers to make the new version available. Windows users already get a popup window when a new version is available. If they care for the changes, they can get them in the But there are 2 things we can do/improve on the site:
|
You misunderstood me I guess (or maybe not). The main point is that people will read news. If they read them, we can make announcements, which we think are important. Like "Ubuntu PPA users: Please adjust your repositories." I don't want direct downloads or a different update mechanism, just a way to communicate with people. (I understand that many people don't fit into the Ubuntu PPA user crowd for example. But it's just an example. Btw we could make an Ubuntu bugreport, ask the community so affected people can sign it. You can ask the devs to upgrade given packages if the users benefit from that.) |
I don't think coding such a feature in qbt is a good idea. The PPA change was in the |
Yeah but that's just an example. But oh well, I don't want to bloat the software either. |
It could parse the changelog at https://www.qbittorrent.org/news Edit: it could also encourage on-boarding devs |
Not sure if this is easy or hard in Qt. But maybe worth a try.
People (and so do I) miss important announcements like the PPA change.
And we could use this to tell people to upgrade (for the BTGuard fix.)
Original idea (from me): http://qbforums.shiki.hu/index.php/topic,2166.0.html
Feature:
The function behind:
The text was updated successfully, but these errors were encountered: