Steps to reproduce:
- pull spicetify locally
- search replace all https for github / api.github to http instead of http
- recompile the binary
go build -ldflags "-X main.version=$(git describe --tags)" -o ./spicetify
Move that binary to your primary spicetify folder (on macos probably this:)
which spicetify
/Users/yourusername/.spicetify/spicetify
Now you have a spicetify client that is very unsafe because it does http requests. but that means we can intercept them :P
- modify the intercept-http-request.js file to add your GITHUB PERSONAL ACCES TOKEN
create a new token here
https://github.com/settings/tokens/new
You need the following rights:
- public_repo
- read:packages
No other rights are needed
- run the following command in your terminal
npm install
chmod +x ./run-proxy.sh
./run-proxy.sh- run the following command in another terminal window
spicetify update-
Profit. It turns the spicetify http update requests into a https command on our end, and adds the auth header.
-
Profit deleted, because once you update spicetify, you would need to recompile the binary again to use HTTP so this entire project is completely useless! :D