[GH-ISSUE #43] Add support for https://cdn.jsdelivr.net #306

Closed
opened 2026-03-14 08:15:55 +03:00 by kerem · 2 comments
Owner

Originally created by @CharlieS1103 on GitHub (Oct 1, 2021).
Original GitHub issue: https://github.com/AnanthVivekanand/spotify-adblock/issues/43

Why we need it:

Currently working on a custom app the be implemented by default with spicetify-cli, this custom app will pose as a marketplace for all extensions and themes. The repository is currently private and will be finished in like a month or two. It requires all requests from https://cdn.jsdelivr.net to pass through in order to function at all

Thanks, if you have any more questions just mention me.

Originally created by @CharlieS1103 on GitHub (Oct 1, 2021). Original GitHub issue: https://github.com/AnanthVivekanand/spotify-adblock/issues/43 ## Why we need it: Currently working on a custom app the be implemented by default with spicetify-cli, this custom app will pose as a marketplace for all extensions and themes. The repository is currently private and will be finished in like a month or two. It requires all requests from https://cdn.jsdelivr.net to pass through in order to function at all #### Thanks, if you have any more questions just mention me.
kerem closed this issue 2026-03-14 08:16:18 +03:00
Author
Owner

@CharlieS1103 commented on GitHub (Oct 1, 2021):

I would appreciate it if you would just add these to the whitelists.

"jsdelivr.com", //Remote extension loading on spicetify
  "cdn.jsdelivr.com", //Remote extension loading on spicetify
  "api.github.com",//Github api calls 
  "raw.githubusercontent.com",  //Github content fetching
<!-- gh-comment-id:931864350 --> @CharlieS1103 commented on GitHub (Oct 1, 2021): I would appreciate it if you would just add these to the whitelists. ``` "jsdelivr.com", //Remote extension loading on spicetify "cdn.jsdelivr.com", //Remote extension loading on spicetify "api.github.com",//Github api calls "raw.githubusercontent.com", //Github content fetching ```
Author
Owner

@AnanthVivekanand commented on GitHub (Oct 1, 2021):

Thanks for your contribution, but this almost seems out of the scope for the project. I'd encourage you to fork and add these changes to a downstream fork you could use with your project. From there, you could continue to merge any upstream changes.

This project is mainly intended to be used stand-alone with vanilla Spotify, and although I commend your efforts on your project, I'd rather keep this repo's functionality focused on regular Spotify. But once again, you're welcome to fork, add your own changes, and continue using upstream changes from here. And keep me updated on your project, I'd love to check it out if you make it public when it's finished. @CharlieS1103

<!-- gh-comment-id:932534037 --> @AnanthVivekanand commented on GitHub (Oct 1, 2021): Thanks for your contribution, but this almost seems out of the scope for the project. I'd encourage you to fork and add these changes to a downstream fork you could use with your project. From there, you could continue to merge any upstream changes. This project is mainly intended to be used stand-alone with vanilla Spotify, and although I commend your efforts on your project, I'd rather keep this repo's functionality focused on regular Spotify. But once again, you're welcome to fork, add your own changes, and continue using upstream changes from here. And keep me updated on your project, I'd love to check it out if you make it public when it's finished. @CharlieS1103
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-adblock#306
No description provided.