Beautiful Lyrics Versions Save

Adds a Dynamic Color Background based on the Covert-Art and Uplifts the Spotify Lyrics

2.5.6

11 months ago

In this release these are the Changes;

Made it so Analytics is checked every minute to determine whether or not to trigger (starts immediately, then checks every minutes)
- Basically, I noticed that when I made the update 2.5.5 I got a ton of traffic. This shouldn't happen because of the cached date value. What I realized though is that if you keep Spotify open (putting your computer to sleep, closing the laptop lid, etc.) and you never restart Spotify it will never trigger Analytics again. I need to have accurate daily-user counts so I can predict how much usage my API endpoints will get. So this is why this change was made so that we don't have to worry.

Full Changelog: https://github.com/surfbryce/beautiful-lyrics/compare/2.5.5...2.5.6

2.5.5

11 months ago

Not going to write a lot - just updated relative-paths for my end and the cache version for lyrics to accept the new server-side lyrics (updated feature recognition)

Full Changelog: https://github.com/surfbryce/beautiful-lyrics/compare/2.5.4...2.5.5

2.5.4

11 months ago

In this release these are the Bug Fixes:

Fixed Tracking creating an img element instead of iframe element (No idea how I messed this up)

Full Changelog: https://github.com/surfbryce/beautiful-lyrics/compare/2.5.3...2.5.4

2.5.3

11 months ago

In this release these are the Changes:

Added versioning to Cache so that older versions can be removed and "cache" refreshed
Updated local types to match new backend returns

In this release these are the Bug Fixes:

Fixed ExpireCache using General store-type instead of ExpireCache

Full Changelog: https://github.com/surfbryce/beautiful-lyrics/compare/2.5.2...2.5.3

2.5.2

11 months ago

Changed the way the Caching System worked so things could be in their own stored values to reduce running into the 10MB limit in the future. Additionally added a uniqueness-check to the client-side analytics loading so that in the case someone restarts spotify or refreshes it that it doesn't trigger more than once per day.

In this release these are the Changes:

Improved Caching System to Segment Stored Values
Improved Uniqueness and Frequency of Visitor Reports

Full Changelog: https://github.com/surfbryce/beautiful-lyrics/compare/2.5.1...2.5.2

2.5.1

11 months ago

This is a small release mainly moving the backend URLs to a dedicated domain (beautiful-lyrics.socalifornian.live and track.beautiful-lyrics.socalifornian.live respectively)

I know it can be seen as a little invasive or scary that any form of analytics is being added into a Spotify Extension - seems kind of weird! But I want to make it perfectly clear that I am using CloudFlares analytics - which does not fingerprint, store cookies, or anything like that - it purely is based off smart-ip tagging to determine a visit and whatnot. There isn't anything it tracks other than visits/page views as well.

So this is the least intrusive analytics you can get on the market today that provides me with exactly what I need; how many people are using my extension. I have put extensive reasonings and notes on the track html page, in the code and here as to why I need it. The short story is that when I first put out the update for the backend lyrics url - to start caching lyrics early before they are used in the extension - I saw I was getting 2-3 requests a second. Given that this extension has 45 stars (as of writing) I figured maybe I have double the users in user-count; however, this was very wrong as I was assuming from the actual amount of requests being made that I had thousands!

This non-intrusive and consumer facing analytics solution from CloudFlare will help me understand how many people are using my extension and how many people my updates will affect - I hope you understand! If you have an issue with it please contact me in the Spicetify discord - my username is @socalifornian

In this release these are the Changes:

Added non-intrusive CloudFlare analytics to gauge user-count
Switched backend url for lyrics to specific domain

Full Changelog: https://github.com/surfbryce/beautiful-lyrics/compare/2.5.0...2.5.1

2.5.0

11 months ago

This is a stepping-stone release to 3.0.0 which will bring huge changes visually to Lyrics and major performance optimizations.

In this release there is a new Service that is responsible for communicating with a backend-server to retrieve the best lyrics possible (syllable synced, line synced, or just unsynced - most of the time syllable or line).

This was originally intended to be released in 3.0.0 but I figured it would be better to start handling Lyrics internally for the Extension now than to do it on 3.0.0 release. On the backend-server - lyrics are cached for a month - so it's important that this is pushed out live so that lyrics can start being grabbed and then stored for the best user-experience on launch.

Although - even when the lyrics are being grabbed for the first time - it is still extremely fast. When the lyrics have already been grabbed and stored the time to get the lyrics will be almost.

This is because the backend runs on the edge. What that means is that when you make a request to the backend it will be to a server very close to you; which means super fast response times. The database server and backend-server are both in the same building - so on the backend there is no delay in getting already stored lyrics - and on your end there won't be either.

So, In this release these are the Changes:

New lyrics-retrieval internals in the Extension
Created Service-Starter methods for when Spicetify methods fully load-in
New Types Folder Structure
New Songs Service to handle changing songs, current songs, loading song details (from Spotify), and lyrics for the Song (Backend)

Full Changelog: https://github.com/surfbryce/beautiful-lyrics/compare/2.4.5...2.5.0