So many Open Source repos assume that you already know what the proprietary version is and don't bother to explain what they are, just how they relate to $other_thing. I got through the whole introduction without any sense for what this was and was hopeful when I saw a Features section that it'd finally explain itself... but no, all I know now is it can download apps (what kind of apps, and to what?), modify buttons to do "any function" (out of what set?), and integrate with discord and weather but not some other things (what does 'to be migrated' mean?).
If you're writing a README like this, it's a good idea to remember that there are a bunch of people who may be interested in your tools because they're FOSS but would never have interacted with whatever proprietary thing you're comparing them to. Do us all a favor and give a two-sentence explanation for what you're building on its own terms.
Can't help but feel that you're barking up a somewhat nonexistent tree here. This project is for interfacing with the deprecated Spotify CarThing. If you don't know about it, you're very likely not their target audience, so I think it's pretty fine if you don't get it. If you do know what the CarThing is, the readme intro covers what this project does pretty well.
In similar vein, you wouldn't expect a Javascript library readme to start by explaining what Javascript is or what a software library is, but if you didn't know those things, you would feel equally lost.
I'mma be completely honest, I had no intentions of this blowing up like it did. The Readme has been in desperate need of a revision and documentation is all but nonexistent. Why? Because I'm just a college student who likes coding and figured I'd take on a fun little project. I'm not a company, an organization, and i have no idea what the crap I'm doing half the time! A formal wiki is in the works and will eventually be implemented and linked to across the ReadMes and websites.
No worries at all! I'm more commenting on this as a trend even from people who post Show HNs of their own than asking for specific changes to this project!
Do what's fun for you, no more, but definitely polish it up if you're looking for broader uptake.
Seems kinda like it does about 10% of what a Streamdeck does, minus the physical hardware. Of course, for most of those users having the hardware (16 or 32 key macro board with user-controllable displays behind the (clear) buttons. Basically it looks like a keyboard with LCD keys.
A mini description of this since the page doesn't explain it very well: The CarThing is basically a mini Linux device that runs a web app that lets you control your phone's Spotify from the hardware itself. It was designed to be attached to old cars that don't have dedicated media centers.
Spotify discontinued it a while ago and subsequently open-sourced some of the bootloader and kernel code. Researchers then were able to tear it apart, and as a result you can now do whatever you want with it. DeskThing is a project that makes it easier for you to do so; it's basically an app store of custom web apps made by the community that you can upload back into the CarThing.
Thank you! I don't know how many projects I've seen on github which sound like they might be interesting, but where there's no way to really understand what it does without installing it. If people want their widget to be used, they ought to provide a video or at least some screenshots that show it in action.
The instructions are also completely messed up, if you're using macOS you need to go into a Discord server to get the real instructions. If the owner is reading this, I suggest focusing on one thing at a time instead of trying to finish everything / all platforms at once :)
Looks like a project to open up Spotify’s discontinued Car Thing to homebrew apps.
If the devs are reading this: the GitHub README and homepage both don’t have a description of what the project is. I had to click around for a while until I found the about page.
This is like the 20th Cool Thing that I’ve seen posted on HN that could be explained by a photo and yet the creators seemingly didn’t even think to take one (despite building out a whole website and everything). How does this keep happening?
I also just posted a few images - the GUI has changed so much over the last couple months that any photo I would've taken would be outdated as of now. There's a lot of content on the subreddit though!
I was thinking the same thing! I was looking all through the repo and site to see if they had any pictures of the apps running, or a setup using the device. To me, this is the easiest way to sell your project and show how cool it is!
Even knowing what it is, and having a Car Thing somewhere in a box in a closet, I still don't have any idea what this DeskThing thing is.
Some Chromium shell with yet-another-appstore that can somehow show (or maybe control) Spotify, Discord and weather, with Trello and Audible planned is my best guess. I guess, a couple screenshots or photos would've done wonders in this regard.
Either way, I fail to understand why I might prefer a separate low-power device to do something with the apps I can already see and control from desktop. But I'm glad someone found a use case for their Car Thing.
I have a CarThing and managed to get this working on it after several attempts and it is actually pretty good. If they revamp the website and README it really has the potential to take off.
If the dev came here and posted this themselves, maybe. My public repos are all nonsense but anyone could post them here, and now I’m suddenly on the hook to a bunch of miserable nerds for not explaining myself well enough? Please
From the FAQ page of the Car Thing (the spotify device)
"What should I do with the device?
We recommend resetting your Car Thing to factory settings and safely disposing of your device following local electronic waste guidelines. Contact your state or local waste disposal department to determine how to dispose of or recycle Car Thing in accordance with applicable laws and regulations."
That's sad. They should link to this project, or officially release kernel/drivers.
They can't. They're legally washing their hands of the product. If they recommended anything else, they could be liable for defective products or for supporting a general purpose computing device, which comes with a plethora of other legal potholes (including export restrictions).
That sounds like one of those things rich people say when they don’t want to do something and want people to be mad at “lawyers” or “government regulations” instead of them.
Readit News
If you're writing a README like this, it's a good idea to remember that there are a bunch of people who may be interested in your tools because they're FOSS but would never have interacted with whatever proprietary thing you're comparing them to. Do us all a favor and give a two-sentence explanation for what you're building on its own terms.
In similar vein, you wouldn't expect a Javascript library readme to start by explaining what Javascript is or what a software library is, but if you didn't know those things, you would feel equally lost.
Idk. Even in Jira tickets, I write a short background section to bring everyone up to speed.
I like when everyone gets a chance to be on the same page.
I'mma be completely honest, I had no intentions of this blowing up like it did. The Readme has been in desperate need of a revision and documentation is all but nonexistent. Why? Because I'm just a college student who likes coding and figured I'd take on a fun little project. I'm not a company, an organization, and i have no idea what the crap I'm doing half the time! A formal wiki is in the works and will eventually be implemented and linked to across the ReadMes and websites.
Thanks for understanding! Cheers
Don’t worry. Neither does anyone else. Everyone just gets better at faking it with time.
Do what's fun for you, no more, but definitely polish it up if you're looking for broader uptake.
https://deskthing.app/about
which I think is completely fine, wouldn't want to have that in a repo README personally
Spotify discontinued it a while ago and subsequently open-sourced some of the bootloader and kernel code. Researchers then were able to tear it apart, and as a result you can now do whatever you want with it. DeskThing is a project that makes it easier for you to do so; it's basically an app store of custom web apps made by the community that you can upload back into the CarThing.
Looks like a project to open up Spotify’s discontinued Car Thing to homebrew apps.
If the devs are reading this: the GitHub README and homepage both don’t have a description of what the project is. I had to click around for a while until I found the about page.
I also just posted a few images - the GUI has changed so much over the last couple months that any photo I would've taken would be outdated as of now. There's a lot of content on the subreddit though!
Some Chromium shell with yet-another-appstore that can somehow show (or maybe control) Spotify, Discord and weather, with Trello and Audible planned is my best guess. I guess, a couple screenshots or photos would've done wonders in this regard.
Either way, I fail to understand why I might prefer a separate low-power device to do something with the apps I can already see and control from desktop. But I'm glad someone found a use case for their Car Thing.
This repo is software for a device called Car Thing, which was made by spotify.
It’s a tablet-like device to put in your car. This repo loads it with software useful to be used at your desk instead.
It seems like at the end of this year Car Thing will no longer work.
https://en.m.wikipedia.org/wiki/Car_Thing
Here’s a picture of car thing
https://cdn.mos.cms.futurecdn.net/Qj4rWZisMXRjY4vmn2BsFS.jpg
"What should I do with the device? We recommend resetting your Car Thing to factory settings and safely disposing of your device following local electronic waste guidelines. Contact your state or local waste disposal department to determine how to dispose of or recycle Car Thing in accordance with applicable laws and regulations."
That's sad. They should link to this project, or officially release kernel/drivers.