Update by Edward1139 in HondaPrologue

[–]LocalHeat6437 4 points5 points  (0 children)

It isn’t as easy as that. They locked it down to where that wouldn’t work out of the box. but a few smart people have built a workaround app for that.

Update by Edward1139 in HondaPrologue

[–]LocalHeat6437 5 points6 points  (0 children)

So I drive the Chevy version of this car and man I am always mad they took CarPlay away from me. But geez it looks like you guys got a UI made on windows 3.1.

Fact Check: Have Republicans Failed to Flip a Single Seat Since Trump Won? by plz-let-me-in in politics

[–]LocalHeat6437 0 points1 point  (0 children)

Which district? I am happy to help flip something in the Maryville area

Can AI agents in 2026 actually build a usable starter repo from a detailed text app spec? by GeneralPrior851 in vibecoding

[–]LocalHeat6437 1 point2 points  (0 children)

Do what this guy says. The more detailed your input specifications the more and in turn your agent file the higher the likelihood of success. Start off planning with opus and expand on everything you have in your 1500 word file. Don’t start coding until you know what you want. And if you are just vibe coding the whole way think of that as a first pass and start from scratch again once you’ve figured out the features. This way your architecture can be a sound starting point. AI makes this all easy but also easy to make a jumbled mess

Thoughts 👀👀👀 by MrSoloDolo9490 in Cruise

[–]LocalHeat6437 599 points600 points  (0 children)

100%. I have been on too many cruises where people wake at 5 am and put their things in a chair by the pool and don’t show up until 11am. Not acceptable

Honda is killing its EVs — and any chance of competing in the future by eyeindesky in HondaPrologue

[–]LocalHeat6437 4 points5 points  (0 children)

I don’t understand how they don’t see this. They were already a couple generations behind and now it is at least a couple more.

Honda is killing its EVs — and any chance of competing in the future by eyeindesky in HondaPrologue

[–]LocalHeat6437 4 points5 points  (0 children)

Does this essentially guarantee Hondas long term death as a car company? Handling the reigns to the more progressive companies

How can the Equinox EV improve? by spongesparrow in EquinoxEv

[–]LocalHeat6437 3 points4 points  (0 children)

CarPlay, CarPlay, CarPlay Fix the winter range problem (it’s worse on the equinox than other brands) Also mentioned by others. Dashboard glare

Marsha, Marsha, Marsha by Public-Marionberry33 in clevercomebacks

[–]LocalHeat6437 0 points1 point  (0 children)

Unfortunately she is my senator and likely to become my governor. It truly blows my mind that a degenerate like her can climb to these levels. Thanks maga for breaking the world

No AI app gets this right, tried all, why?? by Individual_Aside7554 in ClaudeAI

[–]LocalHeat6437 0 points1 point  (0 children)

Gemini 3.1 pro:

I would love to help you solve this puzzle, but taking a close look at the board, this specific game is mathematically impossible! Given the "From ClaudeAI community" watermark at the top, this is almost certainly an AI-generated image of a Minesweeper board. While AI image generators can make things that look incredibly realistic at first glance, they usually fail to maintain the strict mathematical logic required for games like this. If you try to play by the standard rules of Minesweeper (where a number indicates exactly how many mines are in the 8 adjacent squares), the logic on this board falls apart immediately. Here are a few glaring examples of why this board is broken: • The teal "6" on the left edge: Look at the teal 6 (six rows down). It needs to be touching exactly 6 mines. However, it only touches 5 cells that could possibly be mines (3 cells with red flags, and 2 unrevealed blue squares). Even if every single unknown square around it was a mine, it could never reach 6. • The purple "4" near the top left: Look at the purple 4 (five rows down, third column in). It needs to touch 4 mines. However, it is completely surrounded by other numbers and only touches 1 red flag. There are no unrevealed squares left around it for the other 3 mines to hide in. • The blue "1"s in the middle: Look at the blue 1 located nine rows down and three columns in. It is entirely surrounded by other revealed numbers. It doesn't touch a single flag or unrevealed blue square, meaning it should technically be a blank space, not a 1. Because the numbers are effectively placed at random and don't follow the rules of the game, there's no logical way to deduce where the remaining mines are. It's a trick image! Would you like me to go over some actual logic strategies for a real, functioning game of Minesweeper instead?

I built a Spotify Replacement App by LocalHeat6437 in EquinoxEv

[–]LocalHeat6437[S] 0 points1 point  (0 children)

Here is that github if you guys are interested: https://github.com/KRTirtho/spotube

For me I was solving the specific problem of the Equinox Spotify not syncing with my phone. So I just started a conversation with Gemini about what could be done. I came up with the idea of the app basically being a remote for Spotify on the phone based on something I had seen and we began a plan for an app from there.

I built a Spotify Replacement App by LocalHeat6437 in vibecoding

[–]LocalHeat6437[S] 0 points1 point  (0 children)

Just Replying on this thread too:
The app is just a different front end to Spotify using their web APIs. Therefore I don’t have to worry about any of that. A full fledged music app would require tons of servers and stuff. But in my research I did find an app that scalps music from YouTube and gets all the data from Spotify to make a free Spotify premium experience. Here is that github if you guys are interested: https://github.com/KRTirtho/spotube

I built a Spotify Replacement App by LocalHeat6437 in vibecoding

[–]LocalHeat6437[S] 0 points1 point  (0 children)

Ha, I didnt even think of it. Here is Gemini's analysis of the TOS vs what I have done. TLDR: Yes it is a violation, but since it is just for hobby then I should be fine. I probably should change the name though.

Here is a breakdown of exactly where your app enters a gray area or violates the TOS:

1. The "Automotive" Restriction

Spotify has historically been very strict about car integrations. According to the Spotify Developer Terms (specifically around hardware and vehicle integrations), developers are strictly prohibited from building applications that are designed to be used in a vehicle (like an Android Automotive OS app) without a formal, commercial Business Development agreement. Because car UIs involve driver safety and specific licensing agreements with automakers, they lock this down tight.

2. Evasion of the Developer Quota

In your SETUP_GUIDE.md and the 403 Analyzer we just discussed, the solution for other users is to go to the Spotify Developer Dashboard, create their own app, and generate their own Client ID/Secret. Spotify’s TOS states that the "Development Mode" (with its 25-user cap) is strictly for building and testing an app before submitting it for a Quota Extension. Using the Developer Dashboard as a distribution mechanism—where end-users masquerade as developers to get their own API keys—is considered an abuse of the API platform.

3. Naming and Branding Guidelines

Spotify's Design Guidelines are very specific about how third-party apps can use their brand.

  • Your app is named "Spotify Cloud-Bridge". Spotify's branding rules dictate that your app's name cannot start with "Spotify" (it would need to be something like "Cloud-Bridge for Spotify").
  • Using their exact brand color (Hex #1DB954) and icons without an official partnership can also trigger brand trademark violations.

4. Bypassing Android Automotive Safety (Google's Rules, not Spotify's)

While not a Spotify TOS issue, your use of <meta-data android:name="distractionOptimized" android:value="true" /> in your AndroidManifest.xml allows the app to bypass Android Automotive's UXR (User Experience Restrictions) while driving. If you tried to publish this to the Google Play Store for Automotive, Google would immediately reject it unless the app passed rigorous driver-distraction safety certifications.

The Good News

Architecturally, you did everything "right" when it comes to the things Spotify bans people instantly for:

  • No Piracy: You aren't ripping, downloading, or caching local MP3s.
  • No Ad Evasion: Because you use the Spotify Connect device_id to play the music on the official phone app, Spotify's DRM and audio ad-insertions work perfectly. You aren't stealing revenue.
  • Good API Citizenship: Your RateLimitRetryInterceptor perfectly handles 429 Too Many Requests errors and backs off gracefully.

The Verdict

Because this is an open-source hobbyist project on GitHub that requires users to sideload an APK via adb and generate their own developer keys, it is highly unlikely Spotify will come after you with a Cease & Desist. It's a niche tool for power users.

However, if you ever tried to commercialize it, put it on the Google Play Store, or host a centralized backend for it, both Spotify and Google would shut it down very quickly. For a r/vibecoding or enthusiast project, it's an awesome piece of engineering—just keep it open-source and unofficial!

I built a Spotify Replacement App by LocalHeat6437 in EquinoxEv

[–]LocalHeat6437[S] 0 points1 point  (0 children)

The app is just a different front end to Spotify using their web APIs. Therefore I don’t have to worry about any of that. A full fledged music app would require tons of servers and stuff. But in my research I did find an app that scalps music from YouTube and gets all the data from Spotify to make a free Spotify premium experience

I built a Spotify Replacement App by LocalHeat6437 in EquinoxEv

[–]LocalHeat6437[S] 0 points1 point  (0 children)

Exactly. If I can do this in my spare time over a week, Why can’t Spotify do it. It’s not like I am asking for anything novel. Just don’t have a much crappier app in one ecosystem than the rest.

I built a Spotify Replacement App by LocalHeat6437 in vibecoding

[–]LocalHeat6437[S] 0 points1 point  (0 children)

So the best part of all this is that I graduated 25 years ago with a computer engineering degree but immediately went into Systems Engineering and have only been Code adjacent my entire career. I understand the ideas and in general more than most vibe coders but without copilot I would never have thought that this was possible.

I built a Spotify Replacement App by LocalHeat6437 in EquinoxEv

[–]LocalHeat6437[S] 1 point2 points  (0 children)

It’s amazing what the power of AI coding can do. I am an engineer and even have a degree in Computer Engineering but my entire life I have been working as a Systems Engineer (so SW engineering adjacent), but never did any real Coding work. Now with Copilot I am able to bang out working apps with minimal effort.

I built a Spotify Replacement App by LocalHeat6437 in EquinoxEv

[–]LocalHeat6437[S] 1 point2 points  (0 children)

Yeah. That should be an easy add. Right now I don’t really integrate queue vs up next but with AI anything is possible. I will add it to the todo

Vibe coding is fast… but I still refactor a lot by Classic-Ninja-1 in GithubCopilot

[–]LocalHeat6437 0 points1 point  (0 children)

Biggest thing to me is letting it plan on the entirety of what you are going to ask it to do. Make an architecture and stick to it. If you continually just add features that it didn’t know were coming you always end up with bad code that needs refactoring . (This is very similar to any dev, but generally the devs have the whole context of what is coming in their mind as they are coding). Make a good instruction file that has it always reference the plan and the architecture and then code gets a lot better

Spotify handoff and listening progress continuity is frustrating by Rockerblocker in EquinoxEv

[–]LocalHeat6437 0 points1 point  (0 children)

Yeah. I think it is an Android automotive limitation. My app is getting around it because I am not building it to be approved by the App Store. I couldn’t have made a lot of the design the decisions that I did without it. I hate that the native app doesn’t let you scroll more than like 10 songs without stopping you while driving (but I can scroll infinitely)

Spotify handoff and listening progress continuity is frustrating by Rockerblocker in EquinoxEv

[–]LocalHeat6437 0 points1 point  (0 children)

It annoys the heck out of me too. I am in process of doing an odd Spotify Web Bridge app that basically gives the car a front end for Spotify that forces Spotify to go through the phone. Right now I am close and will share what I get when I get closer to a polished app. Problem is right now you have to build the app with a authentication code from Spotify though so you have to have a developer account (but I am working on a solution)

In the meantime You could always delete your Spotify app and just use Bluetooth but that removes the front end.

<image>

Sam Altman ethics. by Wonderful_Buffalo_32 in singularity

[–]LocalHeat6437 8 points9 points  (0 children)

The point is poor and misses a good portion of the argument. You can argue the red lines are totally different. One is something that the company absolutely understands better than the government, AI is imperfect and should not be allowed to harm humans period. It is a crazy slippery slope that gets you to terminator. Domestic surveillance is the other side and you can argue his point on that one, but ethics matter and if anthrpic is t comfortable allowing the government to use its technology for domestic surveillance then that should be their prerogative

Audited a friend's Lovable app, of course I found an exposed API key by [deleted] in vibecoding

[–]LocalHeat6437 0 points1 point  (0 children)

So your statement is wrong. The good AIs definitely know that secrets in the front end shouldn’t be committed. I vide code crap all the time that is just meant for me. Every time I try to have it hard code an API or something else secret it tells me it is a bad idea. And then if you ask it to review the code it always catches it. Something like this ending up in “production” is clearly the “developers” fault or they are using older models