8 comments

[ 0.17 ms ] story [ 75.1 ms ] thread
I was confused because I thought I'd seen this before. But then it turns out I saw Fastpotify (https://github.com/shardqa/fastpotify/tree/main) last week.

But then the domain fastpotify.rocks redirects to spotifast.rocks - so I guess this is a rebrand of the one I saw last week?

that's right, and it went viral on HN in the last few weeks as well.

I've been using it for a few weeks now though without issue! One thing I ran into up front though is that you have to make your own Spotify App (in the developer dashboard) and set the client ID in the Spotifast's settings otherwise it's rate-limited to the point of being unusable.

https://spotifast.rocks/make-it-even-faster/#make-a-spotify-...

i love the idea, but it takes lit 30 seconds to load the home page :(
I really like this. I'll definitely continue using it.

There is just one thing that bugs me - during every cold start my playlists take like half a minute to load, and that's even with my personal API key. Surely these could be cached?

Ah do you have to use an API key? I assumed it would pretend to be the real Spotify client?
You don't _have_ to but without one it uses a shared rate limit pool
I don't know how these things work, so my question might sound stupid: if this app can connect to spotify to play songs, that means it has the sound data of a song in a byte array, then it can write the byte array to a file and use a bunch of available tools to convert that file to mp3?