Any interest in rolling any of this into the hex library?

[trestrantham]

Hey there. Just found this fork and poked through all the changes you all have been incorporating. Would you be at all interested in rolling any of these changes back into https://github.com/trestrantham/hedwig_mopidy so we could have them in the hex versions of mopidy and hedwig_mopidy? There's obviously some org-specific changes you've made, but I could see a lot being teased out and driven by configuration (default user/playlist, etc.) if you're interested.

[bucchere]

Hi! We've been talking amongst ourselves about this a bit and I wanted to share a few thoughts. Our goal was to build a social DJ bot that could shuffle a given Spotify playlist running on a Raspberry π on our office sound system. People in the office slack could interact with the music by voting up/down, changing the volume, etc. We use it every (week)day and your code was awesome as it got us 80% of the way there. But we also went in some directions that I don't think you want to go, especially with the Spotify-specific stuff and the voting. I think a good way forward would be for us to create another fork with only the features that make sense, e.g. what's next and the volume controls. The "brain" that keeps track of the current playlist is also nifty, but it requires a third party dependency you probably don't want (redis). So with all those caveats, I'm interested to hear your thoughts!

[trestrantham]

Hi there. Thanks for the reply! To start, I think we are pretty well aligned with the intent of both mopidy and hedwig_mopidy. I started down this path for the same reason (shared, chat-driven, office music player) as a replacement for my old, homegrown version that used rdio and ruby (https://github.com/trestrantham/walkman). I wrote a blog post that stitches everything together including Spotify on Medium. The mopidy library should have basic support for playlist and leveraging a brain could easily be coerced into using a specific Spotify playlist. I was originally thinking about using an elixir Agent to serve as a brain (in lieu of a 3rd party dependency) and use configuration to seed it on app restart. I'll think through this some more, but I don't think we're too far off in the first place! 😄