ether/ep_webrtc là dự án JavaScript với 74 sao. Audio & Video chat for Etherpad - Video Conferencing with a focus on collaboration
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
WebRTC-based audio/video chat and screen sharing with other users visiting the
same pad.
The audio and video streams are peer-to-peer: every user sends a copy of their
audio/video streams directly to every other user visiting the same pad. Because
of this, it works well for small groups (2 to 4 users, more if video is disabled
or everyone has fast Internet connections) but not for large groups.
Installation
Option 1: Use the /admin interface, search for ep_webrtc, and click
Install.
Option 2:
cd /path/to/etherpad
pnpm run plugins install ep_webrtc
Option 3:
cd /path/to/etherpad/node_modules
git clone https://github.com/ether/ep_webrtc
Settings
Plugin On/Off
In the settings menu there is a toggle to turn the plugin on and off for the
user. When toggled, its state is saved in a cookie and applied when any pad is
visited. The value can also be changed by adding av=true or av=false to the
URL query parameters.
The default value for this setting can be controlled in the server's
settings.json file (it defaults to true):
"ep_webrtc": {
"enabled": true
}
Video/Audio On/Off
The settings menu also contains separate toggles for starting video and audio
sharing when the plugin is enabled. When toggled, their state is saved in a
cookie and applied when any pad is visited. They can also be changed by adding
the following to the URL query parameters:
webrtcaudioenabled=true
webrtcaudioenabled=false
webrtcvideoenabled=true
webrtcvideoenabled=false
The default value can be controlled in the server's settings.json file:
"none" (the default): Initially enabled by default.
"soft": Initially disabled by default.
"hard": Unavailable (it cannot be enabled).
Custom Activate Button
The misnamed listenClass setting allows you to specify a CSS selector for an
element (or elements) that will activate the plugin when clicked. This is
usually combined with "enabled": false. Example:
By default, this plugin uses Google's STUN servers. To use custom STUN/TURN
servers, set ep_webrtc.iceServers in your settings.json to a list of
RTCIceServer
objects:
To limit abuse, the coturn TURN server
supports ephemeral (temporary) usernames and
passwords.
To take advantage of this feature, configure your TURN entry as follows:
credentialType: Must be set to the exact string "coturn ephemeral password".
username: Ignored. (The username that will be sent to the TURN server is
dynamically generated and based on the user's Etherpad-generated author ID.)
credential: Must be set to coturn's static-auth-secret
setting.
lifetime: How long (in seconds) the password will remain valid after the
user visits a pad. After this amount of time, new TURN connections will fail
until the user reloads the page (which will generate a new password). Defaults
to 43200 (12 hours).
There is also support for ephemeral credentials from the
Xirsys API:
credentialType (required): Must be set to the exact string "xirsys ephemeral credentials".
url (required): The desired Xirsys TURN API endpoint.
username (required): Your Xirsys username.
credential (required): Your Xirsys API secret.
lifetime (optional; defaults to 43200 = 12 hours): How long (in seconds)
the ephemeral credentials will remain valid after the user visits a pad.
After this amount of time, new TURN connections will fail until the user
reloads the page (which will generate a new password).
When shardIceServers is false (the default), all clients receive all
RTCIceServer objects in the iceServers list and it's up to the browser to
figure out how to use them to connect with peers. When true, this plugin
assigns a single entry from iceServers to each pad and gives out only that
assigned entry to users that connect to the pad. The intention is to provide a
better guarantee of load distribution across a set of TURN servers, and to avoid
an unnecessary network hop when both peers are configured to force the use of
TURN.
Microphone Settings
The microphone can be configured by setting audio.constraints to any audio
constraints
value acceptable to client browsers. It has the following default value:
For a full list of available constraints, see the
standard.
Video Sizes
The camera's record resolution can be configured by setting video.constraints
to any video
constraints
value acceptable to client browsers. It has the following default value:
For a full list of available constraints, see the
standard.
Changing the record resolution does not change the size of the displayed video
widgets. To change the video widget size, set video.sizes.small and/or
video.sizes.large:
You can see metrics for various errors that users have when attempting to
connect their camera/microphone:
ep_webrtc_err_Hardware: Some sort of hardware-related connection problem on
the users' computer.
ep_webrtc_err_NotFound: Could not find user's camera/microphone.
ep_webrtc_err_Abort: Some sort of other, non-hardware related connection
problem on the user's computer.
ep_webrtc_err_Permission: User did not grant permission to their
camera/microphone.
ep_webrtc_err_SecureConnection: Etherpad is not set up on a secure
connection, which is requried for WebRTC.
ep_webrtc_err_Unknown: Some other unspecified error. Perhaps a bug in this
plugin.
Developing and contributing
Basic
If you're just working on the interface and don't need to test connections to
other computers, you can point your browser to localhost instead of 0.0.0.0.
WebRTC generally requires a secure connection (https), but an exception is
made specifically
for localhost and domains that end in .localhost.
Developing / Testing Communications
If you need to test communication, you may get away with opening two browser
windows to the same URL on localhost. However this may be of limited utility,
especially if you're confirming that sound works appropriately. In order to test
on two computers, you'll need your dev computer to serve on an IP address
accessible from the other computer, at which point you will no longer get away
with using localhost. You will need SSL certs, though for dev purposes they
can be self-signed.
Generate your certificate, which will give
you your cert and key files. In settings.js, set the full path to them on your
file system:
"ssl": {
"key": "/path-to-your/epl-server.key",
"cert": "/path-to-your/epl-server.crt"
// "ca" - not needed for dev purposes
}
Point your browser to your outward facing IP address, preceeded by https://,
and accept the security warning (since this is a self-signed cert).
Bug Reports
Please submit bug reports or patches at
https://github.com/ether/ep_webrtc/issues
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/ether/ep_webrtc là nguồn chính thức.
ether/ep_webrtc có bao nhiêu sao?
ether/ep_webrtc có 74 sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/ether/ep_webrtc. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
ether/ep_webrtc có phải mã nguồn mở không?
Có — ether/ep_webrtc phát hành theo license Apache-2.0, nghĩa là mã nguồn mở để đọc, fork và (tùy license) tái sử dụng. Mã: github.com/ether/ep_webrtc.
ether/ep_webrtc có website riêng không?
TopGit chưa ghi nhận URL trang chủ cho ether/ep_webrtc. Phần README ở tab phía trên thường có link demo, hoặc xem mô tả GitHub của repo.
ether/ep_webrtc là gì?
ether/ep_webrtc (ether/ep_webrtc) là dự án JavaScript trên GitHub. Theo mô tả gốc: Audio & Video chat for Etherpad - Video Conferencing with a focus on collaboration
Đọc đầy đủ README ở tab phía trên.
ep_webrtc có đáng để bạn bỏ thời gian?
ChatGPT, Claude và Perplexity đều đọc được trang này. Hỏi thử xem họ nghĩ gì về ep_webrtc.