webrtc

最近我发现有个趋势哈，就是ARM server越来越多，但是ARM好像不像x64平台那么好识别，总是有各种各样的arm识别不了。

如果SRS能出ARM的docker镜像，那会比较容易跑起来。

我们目前docker只支持x86体系，其实镜像是可以支持多个架构的。

Summa

Hello!

When text line in list is too long and part of it is moved on the next line, list number is placed on the last line. When I use <br>, list number is placed on the first line of multiline text.

Demo is below:

Demo text:

1. [ ] task 1
2. [ ] task 2 task 2 task 2

Is your feature request related to a problem? Please describe.

Fonoster Voice could benefit from re-using the files generated by a TTS Engine. It will make things faster and reduce costs for the users.

Describe the solution you'd like

The Voice server could maintain a list (perhaps in memory). The list should be a hash of the parameters used to create the transcriptions.

Also,

It would be nice to use shortcuts for common functions, like:

• s to trigger screen sharing (start/stop)
• someKey to switch between available streams
• f to trigger full screen
• c to copy the room url

Currently node selectors follow a strict inheritance. For example, RegionAwareSelector is built on top of SystemLoadSelector. This provides limited flexibility if a user wanted to use CPU load or bandwidth as a metric.

I think it would be good to restructure this to be more flexible, where the selection could happen on multiple metrics (even with region as another dimension). For example, y

Since the URLs are just a gate pass for the video call, there might be a chance of getting intruders into the call with a simple brute force.

Users feel more secure if we have some passcode or approval from the creator to join into call.