hackkitten

Yeah, there does have to be something in for them, even if it's just positive PR which they can cash in for more subscriptions or such.

The plan is to get NymphCast into a 'good enough' state, before sending an inquiry off to various services to see whether they're interested in getting their service on NymphCast.

As they say, you already got the 'no', so why not try to get the 'yes' or 'maybe'? :)

Maybe you misunderstood me. I have made available a client SDK that will allow anyone to create a NymphCast client with accompanying app on the server.

I have intentionally made this the same as things work with ChromeCast.

Thank you for the feedback :)

I have no plans to stop working on this project any time soon. Having it work as a ChromeCast Audio replacement was one of my initial thoughts back in 2019, and while the scope has slightly increased, that initial goal hasn't been altered.

After some feedback, I am prioritising the implementing of multi-target streaming (multiple speakers/TVs) so that this will exist (in some form) in the first release.

Another of the goals is for the whole system to be dead-simple to setup and use. Heavens know I have wasted enough of my life trying to make half-broken projects somewhat do what they were supposed to do. I'd rather my own projects are not among those :)

(I'm the NymphCast author)

My apologies, I thought you were talking about the server-side.

On the client side having it integrated into the 1st-party client apps would be great, yes. Right now in the SoundCloud app I implemented a basic track/album/author search function that uses the server-side app to search through the SoundCloud database.

Though barebones right now, it provides essentially the same functionality as using the SoundCloud website directly. I can imagine this approach working in a generic fashion, assuming some network-accessible API is available that provides this information.

I do not feel that I dismissed support for 1st party apps in the article. In fact, I have considered doing so for Netflix and Spotify, among others. Some have a control API for the 1st party app, such as what is used on Android, for example.

It's however a lot of work, with spotty documentation and questionable support. That's why for the first release I haven't really bothered with it too much and instead focused on the core functionality of streaming audio and video, and controlling the NymphCast server from the client.

(I'm the NymphCast author)

I will not disagree with you on AngelScript's documentation being rather lacking. While implementing the runtime support is doable for an experienced developer like myself, I would not want to inflict it on a junior dev. Ditto for learning to use AngelScript from just the official documentation.

I'm currently working on a dedicated website for NymphCast (to be launched over the coming weeks/months), that will contain development guides for NymphCast apps and kin, as well as some AngelScript tutorials and references.

Since it's a hobby project at this point, any timescale I can give is relative of course :)

(I'm the NymphCast author)

One idea I have to perhaps get around this issue is to fudge in an external/new audio/video output that can be targeted instead of the standard outputs. This of course gets into some heavily platform-specific nonsense, which is why I haven't pursued it further yet. Maybe after the first release of NymphCast it's something to look at in more depth :)

(I'm the NymphCast author)

I blame the education system for not teaching kids more about insects and their life cycles :)

No, 'nymph' as in 'dragonfly nymph', as in the part of an insect's life cycle, which is also the reason why I called it 'NymphRPC'. The idea being that these are frameworks that allow the grown-up application to emerge after development.

(I'm the author of NymphCast/NymphRPC, etc.)