Arch Linux User Repository

@xyzzy, I think you should update the version number in the PKGBUILD so that everyone's AUR helpers can automatically rebuild the package. There was an update 11 hours ago to spotify-adblock that fixes an issue with all songs becoming greyed out and unplayable. Rebuilding the package is necessary to make Spotify work properly again.

Found this useful in combination with this package, thought I would share - The BlockTheSpot project (Basically spotify-adblock-linux but for Windows), provides a way to patch out not just the ad banner, but also the upgrade button. They are both xpui.js modifications. BTS updates their script with each Spotify update, so you can use it as a reference to manually apply their patches on your own Spotify install. You can take a look at their pacthes by going through their PowerShell install script located here - https://raw.githubusercontent.com/mrpond/BlockTheSpot/master/install.ps1

Scroll to "Remove ad placeholder and upgrade button. (Y/N)" section of the script.

If I try to update I get this error:

==> ERROR: /home/myuser/.cache/yay/spotify-adblock-git/spotify-adblock is not a clone of https://github.com/abba23/spotify-adblock.git The operation is about to be aborted... error downloading sources: spotify-adblock-git

I fixed removing /home/myuser/.cache/yay/spotify-adblock-git

@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.

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'

@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.

@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.

@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.

@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...