Platform Specific Issues

FAQ

Project Information and Support Links

web service URL: https://OBS.Ninja project development URL: https://github.com/steveseguin/obsninja developer/maintainer: [email protected] donations: via GitHub Sponsors

Community Support

Discord: discord.gg/EksyhGA Reddit: reddit.com/r/obsninja

Where can I get support?

The preferred support mechanism is via Reddit or Discord, which offer community-assisted support. Development issues, feature requests, and bugs are tracked on Github. For mission critical support issues, or business-related inquiries, you can contact Steve directly.

Where can I report a bug?

It is most helpful to report bugs via the official Github. We also monitor the Reddit and Discord channels, though it is easier to miss reports that occur there.

Group Chat (aka, a room)

The group chat feature creates a virtual room where multiple devices can connect to share audio and video. It offers echo-cancellation and text-chat support as well. A room's ‘director’ can manage the guests from the control room, easily accessing individual sources for integration into OBS.

How does Group Chat work?

  • Guests have their own link to join the chat room. They will be able to see all of those in the chatroom, including themselves. Settings to restrict what sources each group member can see or hear are also available.

  • The "director" will be able to view the chat room, without joining it themselves, and they will have controls provided that will let them modify aspects of how the room shows up in their OBS. For example, they will be able to mute certain people so they can't be heard or seen in OBS.

  • The director will be provided isolated direct links to each of those video streams in the group room, allowing for fine-grain mixing control in OBS.

  • Text-chat is available to those in the group chat

  • Passwords are available to keep rooms secure, but are optional. Passwords are not stored on any server; they are used for client-side end-to-end encryption.

  • Guests present in the Group Chat room will see and hear all other present guests video/audio streams; by default anyways.

  • The video quality of those in a group room will appear low to guests, but this is to ensure more bandwidth and CPU resources are made available for the OBS's access to the stream. You can increase the quality, but with potentially detrimental results.

  • Group rooms are not restricted in size, although more than 10 guests can start to be challenging.

Using OBS Virtualcam (or the Mac equivalent), you can let your guests view the OBS live stream itself with sub-100ms of latency. In this case, each guest only needs to view one video stream, the main mixed OBS stream, freeing up group resources to allow for even larger group rooms. This is usually called &broadcast mode.

Privacy, Policies, and Data-collection

OBS.Ninja is a peer-to-peer network, which implies it naturally will share your IP address with the remote guests you are connecting with. There are ways to prevent this, such as using VPNs, TURN-servers, and/or enabling IP-leak protection in your browser, but this is not the default behavior. In no way does OBS.Ninja accept responsibility if your IP address is leaked. Connecting only with trusted peers, such as people you know and trust, is recommended for most use cases.

OBS.Ninja does not store IP addresses or other personal information for longer than is needed to provide the service. This might include for purposes of TURN relay server, error reporting, or for Denial of Service abuse prevention (anti-flooding). There are no user-accounts, although you may use third-party services such as Discord, Reddit, Email, or Youtube to communicate with the OBS.Ninja developers, support, and community.

OBS.Ninja uses Cloudflare as a webserver caching and DNS service, and for site security. Cloudflare may use technical cookies and data-collection to provide reliable service and very basic analytics for OBS.Ninja. These general usage analytics may be shared with the community, such as when the service sees a large spike in usage, and Cloudflare claims this data is all GDPR-compliant.

Video data may at times be transferred via a hosted TURN video relay server, but this is done only to ensure service. This media data is not stored and is only accessible to the intended remote peer. In most cases though, the video data is directly transferred between two peers, without the use of such servers. Any data that passes through the TURN server remains encrypted per the WebRTC standard, and some TURN servers provided offer further TLS encryption on top of it.

OBS.Ninja on its own does not use tracking cookies, though it may use the occasional cookie for storing preferences, settings or history for the purpose of improved user experience. These are not used for tracking, nor are they transferred anywhere. Cloudflare may use technical cookies, as mentioned previously.

Deploying the OBS.Ninja code yourself will still reveal your IP address to some servers, such as STUN/TURN/WSS servers, which are needed for WebRTC to function. The OBS.Ninja hosted and operated servers do not collect personal data, although it may be possible that error or system logs will occasionally capture an IP address. These logs are generally cleared and are not stored longer than needed to ensure reliable and bug-free service.

When using the service, Stream ID values and Room names should be kept secure and treated like passwords when possible. Actual passwords are available additionally though, which are used to enable a client-side encryption mechanism that ensure two peers are unable to connect if passwords do not match. Passwords are not shared with any server and remain client-side. Passwords also are used to encrypt room names and confidential connection data. To further protect the user, any deployment of OBS.Ninja to a private domain name will be further secured, as the domain name will be used as a salting mechanism for both room names, stream IDs, and encryption. As a result, a stream or room on one domain will not be accessible from another hosted deployment on another domain.

While nearly all data transfer is peer to peer based, the initial handshake between two peers is still handled by a server. Once the peer connection is established though, the two peers use that to negotiate transfer of personal data, media streams, chat messages, and other aspects. Backup handshake servers are hosted to ensure reliability, such as with https://backup.obs.ninja. There are several hosted handshake, website, and TURN servers across the globe, with the primary servers hosted in the USA. Details for hosting a personal-sized handshake-server is here, https://github.com/steveseguin/websocket_server/.

OBS.Ninja cannot guarantee privacy, service, or security, despite its efforts to protect you. You use the site, code, or service at your own risk and acceptance. Questions or requests related to privacy can be made out to [email protected]