Package Details: spotify-adblock-git 1:1.0.0.r2.g990c0f2-1

Git Clone URL: (read-only, click to copy)
Package Base: spotify-adblock-git
Description: Adblocker for Spotify
Upstream URL:
Licenses: GPL3
Conflicts: spotify-adblock
Provides: spotify-adblock
Submitter: xyzzy
Maintainer: xyzzy
Last Packager: xyzzy
Votes: 30
Popularity: 2.83
First Submitted: 2018-12-14 14:05
Last Updated: 2021-05-06 07:48

Latest Comments

1 2 3 4 Next › Last »

xyzzy commented on 2021-05-06 07:11

@polyzen: Thanks for the hint! I've changed the pkgver and also removed the epoch, since the new versioning scheme already preserves monotonicity.

Edit: Removing the epoch wasn't a good idea apparently. It breaks version monotonicity for people who had already updated while it was added, so I restored it.

polyzen commented on 2021-05-06 02:13

With projects that tag releases, you should use a pkgver that includes the version and numbers of commits since that release.

For this project you could get that with: git describe --long --tags | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'

coxackie commented on 2021-05-05 21:45

@xyzzy I do apologise; while I was following the thread, I can also see that it is off (package-)topic. I can rescind the previous comments, if you wish, for integrity's sake.

xyzzy commented on 2021-05-05 19:53

@coxackie: Enabling higher bitrates isn't possible. Requesting the decryption keys with a free account just results in errors.

That said, please try to keep comments here about this AUR package.

Sanras commented on 2021-05-05 19:47

@coxackie I don't think we can enable higher bitrates, as that seems to be tied to the account. I have a modded Android Spotify app as well, and it has unlocked skips, no ads, etc. They also enabled the quality changer, but noted that it doesn't actually do anything, as that setting is controlled server-side. I guess you are simply not given access to the higher quality files with a free account, which makes sense. So unfortunately, you do still need to pay for premium to get that. However, I honestly don't care too much, I was never able to tell the difference between 128kbps and 320 anyway.

coxackie commented on 2021-05-05 19:25

@Sanras this is awesome - can confirm. many thanks. It should not be too difficult to make a script that does this automatically, using sed. however, this makes one wonder... are there other properties that we can play with that allow, for example, to enable 320 bitrate, like in premium...

Sanras commented on 2021-05-05 18:19

@coxackie, with huge thanks to @xyzzy for pointing me in the right direction, I found the line that controls the UI ads.

Unzip, and open xpui.js with a text editor. Search for the following line - a=()=>({type:r.ADS_ENABLED}), and replace it - a=()=>({type:r.ADS_DISABLED}).

Save file, rezip it (Seems compression level doesn't matter too much, I used Ark, and left it at default). Then rename the in /opt/spotify/Apps to, and paste in the modified version.

coxackie commented on 2021-05-05 15:56

@Sanras could you please report back on what you did for this? I think one can make a separate aur package that provides a hook to potentially replace xpui.js in every occasion (reverting the change upon uninstall). Hopefully it does not change too much between versions.

Sanras commented on 2021-05-05 15:33

@xyzzy, thanks for that info. I will look into it myself and see if I can remove the placeholder.

You say that it's a zip file, does it need a specific compression level when zipping it back up? I remember back when I was swapping my phone's boot animation, it wouldnt work unless the compression was set to "store" (no compression) level.

Another idea - since this would need to be done with every update, could I make a shell script to automate this? Of course, this depends on how much the xpui.js file changes each time.

xyzzy commented on 2021-05-05 15:27

@Sanras @matt17br: I removed the ad placeholder by modifying xpui.js in /opt/spotify/Apps/ (zip file). Can't remember what exactly I changed, but there are some rather convenient properties you can look for (e.g. "ADS_ENABLED"). Getting rid of all the ads like that should be possible in principle, but would likely be a lot of work and the changes would also have to be reapplied after every update.