It's a nice solution to a problem that the author found. I am afraid that knowing Google's walled garden around Chromecast, the `castnow` and `catt` utilities might have trouble staying afloat.
This lets you create programs that run on the Chromecast, and programs that can send data to the Chromecast. Programs that run on the Chromecast must be "registered" on Google's cloud platform, and "published" on Google's Chromecast platform. https://developers.google.com/cast/docs/registration
The only way to run code on the device is to either serve your code through Google's platform, or root the device and own it like the Linux box it is.
None of Google's documentation speaks about the Cast protocol itself. It's against the Chromecast TOS to create a custom receiver device. You must buy the Chromecast hardware. There have been several attempts to reverse-engineer the receiver protocol and create custom receiver devices, but none of them work with the current protocol.
