dend/decksurf

🌊 Lightweight and open way to manage your Stream Deck device.

Hi, I'm Den 👋

I am an engineer + product manager combo.

Things I do:

• 🔒 Build software that makes other software more secure.
• 🎙️ Record a podcast where I interview notable folks about their career lessons.
• ☕️ Build a utility to keep your Windows machine awake.
• 📕 Maintain a list of resources to help product managers grow.
• 💻 Tinker with USB data from a popular button box.

In the past I've reverse engineered and documented the Halo Infinite REST API, Zune REST API, and the Xbox media API, among others.

On the rare occassions I have time to play video games, I play Halo.

You can find me on GitHub, LinkedIn, YouTube, Stack Overflow, and Hacker News.

decksurf's Issues

Set up SDK publishing to NuGet

Should be done through GitHub Actions from this repository.

Set up project documentation

Use DocFX to generate Markdown + managed docs for the SDK, and publish on https://docs.deck.surf. Documentation generation can happen through GitHub Actions after every repo commit. Baseline documentation is likely going to live in its own separate documentation repo.

Set up release pipeline for the CLI and the default plugin

Currently there is no way for someone to just download the project and run it - they need to compile it, which is not user-friendly.

Configure the tooling to work with devices other than Stream Deck XL

The design of this project has revolved around Stream Deck XL, but not other device form factors. This needs to be improved.

Add media controls for the default plugin (Barn)

Add the ability to manage media playback on the current machine.

Add support for managing OBS content through the default plugin (Barn)

Need to figure out what the best way it is to support integration with OBS. My initial investigations in using the frontend API failed (the API hooks to the window, and it manages all processing within the UI - see feature request), so I need to look for alternatives. Currently that is:

1. Implementing a custom plugin with a communication protocol.
2. Using obs-websocket.

I am leaning towards the latter, since it does the bulk of the important management tasks without having to re-invent the wheel and add another dependency.