Spectralis devlog #39
—Hello again proggers—
All-nighter, running on 3 Monsters and a Coke Zero. Reverse engineering APIs is hard as hell, and untitled.stream in particular fought back the whole way. Also snuck in a fix for a Spotify library issue on the side.
3 Monsters and a Coke Zero is not a nutrition plan, it’s a battle strategy
Cat or dog? 429 Too Many Requests
Okay let’s get into it~
—Yap—
Following up on devlog #38’s untitled.stream compat work — turns out “working on it” undersold how hard it actually was. Genuinely brutal reverse engineering session, plus a smaller fix that came out of the same stretch of work.
—The Great Suffering—
1 — untitled.stream Was Particularly Hard To Crack
Chasing this compatibility since devlog #38, and it turned out to be one of the harder reverse-engineering targets yet. No public API to lean on, so it was the usual slow grind of observing behavior and piecing together how it actually works under the hood.
some APIs give up easy, this was not one of them
2 — Reverse Engineering APIs In General: Still Hard
Not a new lesson given devlog #17’s whole saga, but worth restating: this category of work is consistently the hardest and slowest kind on the whole project. Going in with better patience and verification habits this time though, which helped.
3 — Spotify Library Polling, Increased
Bumped how often libraries get polled to account for some Spotify-side issues that were surfacing. Smaller fix, but a real one, found and shipped in the same session.
—FAQ (no one asked these but they are here)—
Q: What is a “progger”?
A: A human programmer. You. The one who ran on three energy drinks to crack one integration.
Q: Is untitled.stream compat actually working now?
A: Meaningfully further along after this session, following up from devlog #38’s start on it.
Q: Did this go better than devlog #17’s reverse-engineering disaster?
A: Yes — hard and slow, but productive this time rather than a total dead end.
Q: What was the Spotify polling issue specifically?
A: Library state getting out of sync too easily — more frequent polling keeps it closer to accurate.
Q: Sleep status?
A: Same as every other all-nighter devlog. Not great. Worth it this time though.
—This is the end*—
*end for now, rate limits permitting
PIPSQUEAK!!!