Simple-peer Alternatives
Similar projects and alternatives to simple-peer
-
-
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
-
-
chaskiq
A full featured Live Chat, Support & Marketing platform, alternative to Intercom, Drift, Crisp, etc ...
-
-
-
WebRTC-Scalable-Broadcast
This module simply initializes socket.io and configures it in a way that single broadcast can be relayed over unlimited users without any bandwidth/CPU usage issues. Everything happens peer-to-peer!
-
-
webrtc-sdk
WebRTC Simple Calling API + Mobile SDK - A simplified approach to RTCPeerConnection for mobile and web video calling apps.
-
-
-
-
-
Reviews and mentions
-
I wrote a peer to peer file sharing site
It is using the simple-peer library to manage the peer connections. You can open the share url in a separate tab if you want to try it locally. If you know how to use the developer tools you can see it is not uploading to a server. The only thing my server is doing is creating a websocket connection initiating the peer connection then it closes the socket. Everything else is done on the browser without the need of a server.
-
Building a customer support solution focused on video calls
Custom peer-to-peer video call implementation can also be done using vanilla webrtc or https://github.com/feross/simple-peer but using an SFU such as Janus can help
-
Show HN: Jam, an Open Source Clubhouse
Not an expert here but have some experience with it:
Assuming that each peer is connected to every other peer via a mesh network [see this image for reference: https://github.com/feross/simple-peer/blob/master/img/full-m...], each outgoing stream (esp. audio / video) is likely going to be duplicated, per recipient.
Scalability over a mesh network is fully dependent on CPU and network performance of all of the connected devices, and I'd doubt it could handle 12 participants if there is video involved, unless all participants are running relatively high-end and modern devices, with optimal network conditions.
You'll need a SFU or an MFU running on the server to handle larger rooms, while enabling all connected devices to only have to send one output stream per media type, regardless of how many connected participants there are.
-
Any example of streaming non "user media" media?
It isn't really documented anywhere, but here is a thread confirming the behavior
-
A local file storage for the web and interopearability layer for web-based apps (submission)
For the tmp-webrtc extension, at first I wanted to create a backend service to implement peer discovery. That would also give me an opportunity to try out DigitalOcean’s paid services (like running backend apps and using a managed database). Unfortunately due to time constraints I didn’t get around to doing that and used the P2PT library for peer discovery instead. P2PT uses public WebTorrent trackers as a WebRTC signaling server, and so no backend services have to be deployed. So it ended up being another static app. This is my first time using P2PT and WebRTC for file transfers though, so I still think I learned a lot.
-
tmp.spacet.me devlog part 4
Sending and receiving files via WebRTC. I used P2PT for peer discovery and simple-peer-files for file transfer. They are based on the simple-peer library. I’ve never used them, and a hackathon is a great time to try out things I’ve never tried before.
-
Is there a Video chat script with WebRTC that I can add to a web page
simple-peer.git
- Simple-peer – Simple WebRTC video, voice, and data channels
Stats
feross/simple-peer is an open source project licensed under MIT License which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.