-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[Meta] Suggest issues deserving bounties #2199
Comments
And maybe we should also bump the existing bounties since no one is tackling them. |
Bounty added on #1979. Thank you :) About lsquic I really don't know what has to be done, so I will let you guys handle it to be sure it's "complete".
Waiting for @Perflyst Since we started adding bounties Perflyst wanted us to only add them on bugs (and not enhancements/feature requests). Back then it was mainly because there was so much problems with Invidious, but now I guess it's time to add some bounties to enhancements/feature requests. |
We have to discuss if we really want Google SSO on Invidious, in my opinion it's a pretty bad thing to have on a service mainly made to avoid Google. If it's only an issue when I know what PubSub is however I'm wondering... is it really useful to have? I think we had this discussion before and if I remember correctly the answer was yes, but I would just like to be sure. |
If someone can define what needs to be done I guess we can add a bounty. I can't estimate how much work this will be.
Even though it is my own feature request I still think this feature is not very important compared to other bugs / improvements left
Sounds good to me, go for it
This looks more like a discussion to me than some feature request |
Some people want to use their G-account to continue to interact with the content creators/community (comments/likes) without being too much tracked and annoyed by Youtube itself. And if we work better on accessibly, it could be another reason (than privacy) why people choose us.
Some videos, mostly music, contain a form of DRM that requires a small algorithm to run on the client side to "verify" that they can play the video. decrypt_polling is a "job" (a function ran periodically by crystal) that extracts this algorithm. Because this function is currently broken, issues like #1947 happen.
I honnestly have no clue about what PubSub is, lol. But from what I remember from "hovering the code", it's required for subscriptions or something? |
Yes it is very important, for big instances it allows to instantly get notified once a new video comes out instead of waiting 5 days that Invidious refresh all the 100 000 channels in the database. |
If the budget is not all booked, allocating it to items in to-dos might be of interest. Though, where is the limit — 2$ bounties for minor bugs, paper cuts, feels wrong. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I think #2236 deserves a bounty. Using invidious on iOS has become tedious. |
@SapeurPonpier Thank you for the suggestion, bounty added! |
This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked. |
I think the automatic db migration could be a good candidate for a bounty. It's blocking a few PRs #2254 (comment) |
I think we should consider putting up bounties for whoever can discover the source(s) of the memory leaks in Invidious |
Sure, we should discuss it |
This is a meta issue where organizations members, and users in general can suggest issues that deserve to have bounties added to them.
The text was updated successfully, but these errors were encountered: