lofi

As always, these kinds of things are good for "simple" stuff (e.g. stuff you don't really need AI for) but totally suck for "complicated" or "weird" things. For example, I curiously ran it on one of my OSS projects: https://github.com/dvx/lofi It's a cute little Electron-based mini Spotify player that gets maybe like 200 users a day and has 1.3k stars on GitHub. Code quality is pretty high and it's more or less "feature-complete." There's a lot of simple/typical React stuff in there, but there's also some weird stuff I had to do. For example, native volume capture is weird. But even weirder is having to mess with the Electron internal window boundaries (so people can move their Lofi window where-ever they want to). We're essentially suppressing window rect constraints using some funky ObjectiveC black magic[1]. The code isn't complicated[

Ran it on a "real" OSS project of mine (https://github.com/dvx/lofi/), and it was stuck at 99% loading for about 30 minutes. Then, when it finally parsed the codebase, when asked anything it always returns "Error: Internal error while locating sources." Specifically, I wanted to see if it can context switch between TypeScript (used for the front-end), ObjectiveC (used for a few Mac features), C++ (used for Windows volume features), and GLSL (used for visualizations). But alas. At one point, this random prompt popped up: https://imgur.com/a/mYeluaU —what's "Onboard?" Is this some kind of weird LLM leakage/hallucination? With all respect, this is like a pre-MVP quality product. The codebase isn't even particularly large and the experience is extremely sub-par. Charging for something like this is honestly highway robbery.

In readme[0] small footprint named as an advantage instead: > Design goals > ≤ 100MB memory footprint [0] https://github.com/dvx/lofi#design-goals

> a Tiny Spotify Player Grab 80 Mbytes binary.[0] [0] https://github.com/dvx/lofi/releases/tag/v1.6.1

Maybe because the initial commit was in January 2019: https://github.com/dvx/lofi/commit/caf81d949d4c7d5177507139f...

I do think that podcasting is ripe for disruption and a great candidate for a "super app" that can end up being people's go-to to listen to podcasts and be exposed to new ones. Spotify did literally nothing to actually support podcasting as another vertical--which it 100% is. Podcasting isn't just "music" and it's a profound misunderstanding to believe that it is. It's honestly embarrassing that their biz dev people were like: "just buy out Joe Rogan, that should do the trick." To this day, I mostly listen to podcasts on YouTube. Spotify doesn't have transcripts, scrubbing, chapters, discoverability, "shorts," etc., etc. I run an open source Spotify player[1] and their API doesn't even have a podcast type/category (lol, they are actually "music videos" in the JSON payload). It's like podcasts don't even exist. [1] https://github.com/dvx/l

Don't mean to hijack this thread, but I built out a mini Spotify player with visualization support: https://github.com/dvx/lofi Even had a few folks contribute a couple of neat visualizations[1] :) PS: Visualizations were unfortunately deprecated on Macs since like 1.5.0 because of the incredible difficulty of getting the audio stream data. Pretty sure there's no way of doing it these days outside of a kext. [1] https://github.com/dvx/lofi/tree/master/src/visualizations

This is awesome! Will try to add it to the next release of https://github.com/dvx/lofi

Anecdotal, but I maintain a mildly popular Spotify player (https://github.com/dvx/lofi) which needs a similar flow for OAuth authentication. I've never had an issue created or complaint about the Windows Firewall popup.

This is way cool! Mad respect to you audio engineers out there. I tried implementing FFT last year in one of my open-source projects[1] (key word: tried). [1] https://github.com/dvx/lofi/commit/285bf80ff6d7f0784c14270de...

Switch is used pretty often when UI needs to look different based on certain application states (consider any 3+ state button). I was curious if I used it recently, and, in fact, here it is in some code I wrote a few months ago[1]. It's also used all the time (also happens to be fairly idiomatic) when dealing with Redux, MobX, etc. [1] https://github.com/dvx/lofi/blob/master/src/renderer/compone...

I love this idea so much, I made it an issue on a the Lofi repo -- a somewhat popular Spotify player I built: https://github.com/dvx/lofi/issues/37 I'll work on it when I can get a bit of free time.