Replies: 10 comments 13 replies
-
Recently, I have repeatedly expressed my negative opinion about Bountysource and recommended that users not use it (at least to involve me). Personally, I don't deal with Bountysource anymore since I can't withdraw any money. |
Beta Was this translation helpful? Give feedback.
-
|
I didn't know who was going to fill the request at the time. I used Bountysource only because it was listed as a method here, and I don't have a bitcoin wallet or want to spend time figuring it out. Too old. |
Beta Was this translation helpful? Give feedback.
-
|
I can't find BountySource on our repo's authorized apps/integrations. I think I may have removed it a couple of years back. And with qbittorrent/qBittorrent-website@7e3601b I removed our recommendation from the donate page. I wish I had done it sooner but I didn't know the info you have provided here. The last issue which is difficult to fix: In the past, when I had enabled their integration in the repo, their tool edited every open issue and put a note at the end of the first post encouraging people to use BountySource. See for example #13868. There isn't an easy way to remove that note. One could write a tool/script, leverage the github API, fetch all issues, scan first post for that string in the end and edit the post. But I am not gonna do it atm. |
Beta Was this translation helpful? Give feedback.
-
|
Lol, there's a lot of old issues in here with the bounty source stuff. I wrote a quick python script to edit all the bountysource comments from a repo. You need to pip install PyGithub first. I was able to read all the issues and remove the bountysource tags and their contents (I tested it with print statements) but I didn't test if editing actually works (because I don't have a repo with bountysource issues like this to edit and I don't want to set one up). It uses some regex magic too. Here is the code below: #To run this script you need to:
#pip install PyGithub
'''
Reference code:
https://pygithub.readthedocs.io/en/stable/introduction.html (for set up and auth)
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens (to generate a token)
https://pygithub.readthedocs.io/en/stable/examples/Repository.html#get-list-of-open-issues (to get list of open issues)
https://github.com/PyGithub/PyGithub/blob/main/github/Issue.py (to see how Issues in this library are structured)
https://github.com/PyGithub/PyGithub/blob/main/github/Repository.py (reference to get_issue(number))
'''
from github import Github
from github import Auth
from github import Issue
import re
auth = Auth.Token("YOUR-AUTH-TOKEN-HERE")
g = Github(auth=auth)
repo = g.get_repo("qbittorrent/qBittorrent")
issues = repo.get_issues()
#issues = [repo.get_issue(13868)] # Test with specific issue number
# Get all issues containing any reference to bounties
for issue in issues:
body = issue._body.value
if (re.search("(?s)(?<=<bountysource-plugin>).*?(?=</bountysource-plugin>)",body)):
print("BOUNTY ISSUE: "+str(issue.number))
#print(body) # Body before editing
# Remove the inside contents of the bountysource-plugin
body = re.sub("(?s)(?<=<bountysource-plugin>).*?(?=</bountysource-plugin>)", "", body)
#print(body) # Check to see what the removed inner body of the bountysource-plugin tag looks like
body = body.replace("<bountysource-plugin></bountysource-plugin>","")
#print(body) # See what the issue looks like without the bountysource-plugin tag and its contents at all
# --------------- UNTESTED AT ALL ---------------
# I only did the reading all the issues part of this, someone will need to actually test if editing the body will actually work
# Refer to https://github.com/PyGithub/PyGithub/blob/34c4642eb1fae2d754cfeb30874515cb1a19f5e1/github/Issue.py#L312
# to see how to edit issues
#issue.edit(body=body)
# --------------- UNTESTED AT ALL ---------------
else:
print(issue.number)
g.close() |
Beta Was this translation helpful? Give feedback.
-
This sucks: bountysource/core#1586 (comment)
I am sorry that you and others have lost money. |
Beta Was this translation helpful? Give feedback.
-
|
I appreciate your comments. Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Thank you sledgehammer for bringing up the bankruptcy in your reply. I can confirm that I also had issues trying to access the app.bountysource.com site within the past month (I don't remember the exact day). I tried contacting them to bring this up with the form at the bottom of the main bountysource website but it also couldn't go through. I thought it was a temporary problem that would be addressed within a week so I didn't think about it too much and just moved on when I saw the site didn't work. I am sad to see the bankruptcy issue. I hope the person who put up $500 for #14160 isn't out $500. Funnily enough I am in the middle of making a desktop app to manage qBittorrent using electron.js and the qBittorrent Web API (thank you so much for everyone who contributed to the existence of the web API) that tracks statistics similar to what that poster wanted with the addition of other "hacky solutions" that are easier to make in JavaScript such as torrent migration to a different OS, fair seeding, client blacklists, speed preferences for private trackers over public tracks, speed preferences for categories and tags, etc. I am going to make a separate GitHub account for it (this is a throwaway account) and have an alpha version up within a month. I would prefer if that poster for the $500 bounty source ticket kept that money and gave it to a food bank or homeless shelter instead. As for bounties in the future: I did a quick search and found something called Gib Work for bounties. I only spent 5 minutes looking at it but this might be an alternative to bountysource if you want in the future. |
Beta Was this translation helpful? Give feedback.
-
|
@sledgehammer999 I'd remove mentioning bountysource from donation page completely.
|
Beta Was this translation helpful? Give feedback.
-
|
I missed that reference. Removed with qbittorrent/qBittorrent-website@513a3d6 |
Beta Was this translation helpful? Give feedback.
-
|
I just did a https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aissue+is%3Aopen+in%3Abody+bountysource Some issues with |
Beta Was this translation helpful? Give feedback.
-
|
All the automatically appended bountysource tags seem to follow the same format. I mention a possible solution to remove all mentions of bountysource here: #20260 (reply in thread). Unfortunately, I tried forking and duplicating the qBittorrent repo but neither results in the issues being carried over to my repo so I can't test if the editing actually works. |
Beta Was this translation helpful? Give feedback.
-
|
@sledgehammer999 @glassez I'm willing to go through all open/closed issues via the search string I provided above & manually edit/remove "bountysource" info from them. See #15 as an example, would this suffice? Remove mention of bountysource from it's initial introduction via https://www.qbittorrent.org/news#monday-november-16th-2020---donation-info-updates???? |
Beta Was this translation helpful? Give feedback.
-
|
There's 1236 issues with the bounty source footers.. |
Beta Was this translation helpful? Give feedback.
-
Correct for "open" & "1200" for closed. Unless there are any objections - I'm going to make a start on this today! |
Beta Was this translation helpful? Give feedback.
-
I am not going to stop you. But are you're sure you wanna do that manually for so many issues?
IMO, there's no point to retroactively remove stuff from an old news entry. |
Beta Was this translation helpful? Give feedback.
-
Ya, that's no problem for me.
No problem. I'll come back to you when it's just the ones with actual bounties on them to see if you want to leave any other comment.....only about 6 of them. |
Beta Was this translation helpful? Give feedback.
-
|
I suggest you do the edits in reverse order. Aka from the oldest issue towards the newest. Otherwise the sorting order of "recently updated" will be borked. Just a suggestion though. |
Beta Was this translation helpful? Give feedback.
-
I did start with oldest to newest, however - I focused primarily on "feature request" & then moved on to "issues" - it seems @thalieht has helped out too. All open issues have been taken care of now except for those labelled "bounty" & the closed are down from 1200 to 895, some of these are unable to be edited as they were converted to discussions -> https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aissue+in%3Abody+bountysource+is%3Aclosed+label%3ADiscussion |
Beta Was this translation helpful? Give feedback.
-
|
@sledgehammer999 33 with "bounty" & "discussion" labels left over to be handled ref. https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aissue+is%3Aopen+in%3Abody+bountysource |
Beta Was this translation helpful? Give feedback.
-
|
The bounty links are essentially dead.
example markdown: ---
There is a [$15 open bounty](https://www.bountysource.com/issues/45215267-continue-to-seed-lonely-torrents?utm_campaign=plugin&utm_content=tracker%2F298524&utm_medium=issues&utm_source=github) on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F298524&utm_medium=issues&utm_source=github).
**DISCLAIMER:** There are [trustworthiness and solvency issues](https://github.com/qbittorrent/qBittorrent/discussions/20260) with BountySource. qBittorrent is not affiliated with them. Use them at your own risk. |
Beta Was this translation helpful? Give feedback.
-
To clarify: I mean put the disclaimer to issues which have a bounty already posted. |
Beta Was this translation helpful? Give feedback.
-
|
I've added the disclaimer....unsure of how to handle the "discussion" labelled issues..... |
Beta Was this translation helpful? Give feedback.
-
|
@sledgehammer999 Have a look at #12842 (comment) as perhaps an alternative?? |
Beta Was this translation helpful? Give feedback.
-
I created a bounty for a request and funded it. I can't access their backend. I had asked for my money back at one point months ago and received no reply (I had planned to send it to the developer who had completed my request using a different method)
I am reading some stories where people have lost all of their bounties that were waiting in bountysource.
If this is the case I think that platform should be removed as a payment method. I am out $100 and so is @glassez
https://www.isitdownrightnow.com/app.bountysource.com.html
Beta Was this translation helpful? Give feedback.
All reactions