The DeskThing: the perfect desk assistant
github.com
github.com
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.
[0] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
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.
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.
I appreciate the concern though
- Solo DeskThing Developer
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.
I'm just a guy who hasn't even graduated college yet ¯\_(ツ)_/¯
Cheers
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.
The hard part (at a DIY level) is, honestly, the physical buttons and knob — wired as an input device to the compute without hogging the device's (likely only) port — and with good industrial design (no gross 3D-printed textures that easily get dirty from being touched a lot; no deep wraparound plastic bezel that prevents you from touching the corners of the display; dynamic-function side buttons thin enough to allow the screen to show the labels for them; etc.)