15Five | Remote: US, Poland, & Ukraine | Full-time | https://15five.com Multiple engineering and design roles, all fully remote: - Remote: Poland or Ukraine - Backend Engineer: https://jobs.lever.co/15five/bf43681a-74b7-493e-a8c8-9b568af10c04 - Remote: Poland or Ukraine - Android Mobile Engineer: https://jobs.lever.co/15five/9d42917c-c5ed-483e-b807-3243a3617377 - US-based only, remote - Senior Quality Assurance... - Source: Hacker News / about 3 years ago

At 15Five we migrated to Terraform in 8 months with a 3-person team. It went smoothly and gave us more confidence in our AWS infrastructure. When it came to setup a new VPC for a customer, the hours we invested returned to us in a speedy and simple setup, a process that would have been a massive pain if we had done it manually. - Source: dev.to / about 4 years ago

If you want to run Spotify on a Raspberry (or PinePhone or some other device), there’s Spot, which is great, but kinda heavy and slow. There’s Spotify-qt which is faster, requires messing with Spotify developer dashboard, and UI doesn’t fit on small screens. Spotify-qt is itself based on Spotify-tui which runs in the terminal (pretty cool IMO). And a bare client/daemon is spotifyd. So you have quite a few choices... Source: over 1 year ago

Would like to add that you can also use clients such as spotify-qt and Spotify TUI to control said "device". There's also Spot and psst that are standalone (librespot not required but no Connect functionality). Source: over 1 year ago

I have been using spotify-qt[1] lately. It's quite close to the original client from more than 10 years ago. 1. https://github.com/kraxarn/spotify-qt. - Source: Hacker News / about 2 years ago

You could use an an unofficial client, for example: - Spot (GTK, can stream directly) - spotify-qt (QT, just a Spotify connect frontend, so you need something like spotifyd running) - spotify-tui (terminal, again just a Spotify connect frontend) - spotifyd (daemon that is controlled via Spotify connect). Source: over 2 years ago