Jannis Mattheis

I mean it more like a general matching configuration. ``` // goverter:converter // goverter:matchIgnoreCase // goverter:matchNames tag:json fieldName type Converter interface { Convert(source []Input) []Output } ``` this would mean...

Yes, the user that shares their screen will encode, encrypt and upload the video stream for each connected user. The CPU usage can be optimized by reducing the frame rate...

I cannot say for sure, because this is done in the browser implementation of WebRTC, but I'd expect it is encoded for every viewer. Basically, screego obtains a [MediaStream](https://developer.mozilla.org/en-US/docs/Web/API/MediaStream) via...

Currenty not, you can use Jitsi or another sharing tool, they proxy the traffic through the server, so the one that shares the screen doesn't have to encode the video...

Hmm, maybe this is only a documentation issue. Screego doesn't necessary need users, because you can disable the login: https://github.com/screego/server/blob/c652513ccdb6341e6a1409119bceb6c3a849c204/screego.config.example#L66-L71 When setting the value of the auth mode to `none`,...

What do you mean with authenticated turn? Prometheus is unaffected by the SCREEGO_AUTH_MODE setting, you'd have to create a user like you'd do with SCREEGO_AUTH_MODE=turn.

It basically just works out of the box and should be secure. The TURN credentials are separate from the user credentials and will be generated on demand for new connections,...

@nogweii Yes, thanks for summarizing. Point 5 is optional and only needed if you have prometheus metrics enabled.

Yeah, sounds like a useful addition.

I think something like "archiving tags" would be easier understand for users but yeah this sounds useful.