tytan652

The plugin `obs-services` will mainly register services which uses stream key. `obs-services2` is meant to be used to implement services with specific behavior, right now there is Dacast, and many...

> They can't offer extra features such as the RPC of rtmp. In fact, rtmp doesn't even have a formal password/key system! Each service _should_ be able to do its...

They are already usename and password in the [service API](https://obsproject.com/docs/reference-services.html#c.obs_service_info.get_username), I think they are just not used except for Dacast and Custom services. But I don't know if RPC is...

> It'd be very nice if obs could do stuff like subscriber alerts without the aid of 3rd party websites. Not implemented imperatively in OBS, but in a plugin meant...

Update: This RFC draft is split into two RFCs. I put them in the same PR because they are dependent of each other. If you want me to separate them...

The RFC 38 is quite well proven with a try of implementation of the API and not the UI logic for now [here](https://github.com/tytan652/obs-studio/tree/protocol_api). Right now the only visible benefit is...

Since https://github.com/obsproject/obs-studio/pull/5047 is merged I can really begin the phase 4 after making some rebase.

Update about phases: - Phase 1 has now his PR even if was not a good idea, next time I will talk about it to @jp9000 beforehand - https://github.com/obsproject/obs-studio/pull/5104 -...

Thank you for your reviews > I'll start off by saying that eve though there is some interdependency between these two RFCs they should be two separate PRs. Like I...

PR split, commit will be squash later and phases are moved elsewhere.