Skip to content
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

Switch to Community Maintained fork of bump-lavaplayer #1429

Closed
wants to merge 1 commit into from

Conversation

dmizelle
Copy link

This pull request...

  • Fixes a bug
  • Introduces a new feature
  • Improves an existing feature
  • Boosts code quality or performance

Description

I tried setting this up as an alternative to using red-discordbot and ended up immediately running into #885.

There is also #1375 which advocates for moving to youtube-dl+ffmpeg as a replacement for lavaplayer, but that would take quite a bit of work as it is called out in the issue.

After the OG lavaplayer repo was abandoned, the community forked it and has been maintaining it since:

https://github.com/lavalink-devs/lavaplayer

This commit moves us from using this project's forked version to the community's fork.

I tested this with some tracks that were returning HTTP 403s and it is now resolved (at least in my testing...)

Purpose

Bumping this to a more recent version allows us to pull in a fix from lavalink-devs/lavaplayer/pull/16

Relevant Issue(s)

This PR closes issue #885

I tried setting this up as an alternative to using red-discordbot and
ended up immediately running into jagrosh#885.

There is also jagrosh#1375 which advocates for moving to youtube-dl+ffmpeg as a
replacement for lavaplayer, but that would take quite a bit of work as
it is called out in the issue.

After the OG lavaplayer repo was abandoned, the community forked it and
has been maintaining it since:

https://github.com/lavalink-devs/lavaplayer

This commit moves us from using this project's forked version to the
community's fork.

I tested this with some tracks that were returning HTTP 403s and it is
now resolved (at least in my testing...)
@MichailiK
Copy link
Collaborator

Hi, thank you for this PR! I've seen & been pointed out to several lavaplayer forks, though I haven't spent much time looking into any of them. Would you happen to be familiar with the situation of lavaplayer forks & can elaborate on it? If not, that's perfectly fine.

@MasqueOu
Copy link

Hi! I've been using the same library for a few weeks on my bot, and there's literally no way out of any 403 error (I've checked the issues relating to this kind of problem, and all the videos mentioned go through without a hitch).

You're free to go, it works more than fine.

Thank you very much for the work you do to maintain this bot!

@jagrosh
Copy link
Owner

jagrosh commented Mar 3, 2024

Superseded by #1490

@jagrosh jagrosh closed this Mar 3, 2024
@CNote325

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants