fs
libdatachannel
fs | libdatachannel | |
---|---|---|
7 | 27 | |
208 | 1,543 | |
3.4% | - | |
6.8 | 9.3 | |
3 months ago | 6 days ago | |
HTML | C++ | |
GNU General Public License v3.0 or later | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fs
-
persistent storage API on Firefox temporary extension
You can use File System Standard https://fs.spec.whatwg.org/ to write data for that origin (Firefox doesn't implement File System Access API, nonetheless a File object can still be written to local disk using File API).
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
Both Firefox and Chromium (Chrome) have implemented WHATWG File System Standard.
-
SQLite WASM in the Browser Backed by the Origin Private File System
Can you just slow down for a moment and focus on what you said?
> We're literally in the discussion about File System API that is:
> - not on any standards track
As others have pointed out the standard is here:
https://fs.spec.whatwg.org/
> - considered harmful by other browser vendors
It is literally being drafted in conjunction by all the major browsers.
> - shipped by default in Chrome
So what? I for one am thankful that Chromium enables features earlier than other browsers. If you don't want the Chromium implementation then don't use it.
-
Show HN: I built a WASI playground for running CLI binaries in the browser
Score another point for memfs, the in-memory node.js fe impl.
WHATWG recently took up File System Access spec as their FS spec. It both looks semi promising, but they seem to only care about & are only building specs for specifically emscripten wasm users. Only sync apis, only usable from dedicated workers... there's some hopes for more latter but feels super weird to see the web finally get fs access & have it be fast... but for it to be extremely odd shaped hand tailored to a very narrow class of use.
https://fs.spec.whatwg.org/
- Learn Postgres at the Playground
libdatachannel
- VoRS: Vo(IP) Simple Alternative to Mumble
-
Simplicity of IRC
You can use https://github.com/paullouisageneau/libdatachannel for your C/C++ integration needs. It's 10k lines. So the answer is 0. Its required dependencies (I assume this as they are git submodules in deps) are more than 100k lines, though, srtp support making the bulk of it. On my machine it took 11 seconds to compile it.
Irssi is 64k lines (plus its dependencies), so I guess that makes WebRTC complicated.
Can't argue that DCC isn't simple, but perhaps the protocol deviced decades ago is a bit too simple.
-
OBS merges AV1 support for WebRTC
Most of the work happened in the libdatachannel! You can check out my PR here[0]
[0] https://github.com/paullouisageneau/libdatachannel/commit/a6...
-
Pure C WebRTC
I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....
When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!
Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)
-----
I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!
* https://github.com/shinyoshiaki/werift-webrtc (Typescript)
* https://github.com/pion/webrtc (Golang)
* https://github.com/webrtc-rs/webrtc (Rust)
* https://github.com/algesten/str0m (Rust)
* hhttps://github.com/sepfy/libpeer (C/Embedded)
* https://webrtc.googlesource.com/src/ (C++)
* https://github.com/sipsorcery-org/sipsorcery (C#)
* https://github.com/paullouisageneau/libdatachannel (C++)
* https://github.com/elixir-webrtc (Elixir)
* https://github.com/aiortc/aiortc (Python)
* GStreamer’s webrtcbin (C)
See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.
- WebRTC for the Curious
-
Building WebRTC server implementation for Erlang
This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
Use any means necessary to transfer your data across devices. Could be IPFS, could be FTP, could be EventSource, WebSocket, WebTransport, Fetch, whatever. See https://github.com/guest271314/secure-file-transfer; offscreen-webrtc, https://github.com/paullouisageneau/libdatachannel.
-
Client side Rest server?
I've successfully used libdatachannel to Web pages to connect native applications and stream data to the browser.
-
Security Framework
Alternatively you can use your server as a signaling server for WebRTC (Insertable Streams ("Breakout Box"), or data channels https://github.com/paullouisageneau/libdatachannel), then users (peers) can exchange data themselves and you don't need to store anything, see True End-to-End Encryption with WebRTC Insertable Streams, A complete example for a WebRTC datachannel with manual signaling.
-
Datachannel video streaming?
there is also a c++ library that can be used to open a data channel connection, I think a number of SFU “servers?” use this library (I wish I had) https://libdatachannel.org/
What are some alternatives?
node-postgres - PostgreSQL client for node.js.
libjuice - JUICE is a UDP Interactive Connectivity Establishment library
file-system-access - Expose the file system on the user’s device, so Web apps can interoperate with the user’s native applications.
Pion WebRTC - Pure Go implementation of the WebRTC API
goyo.vim - :tulip: Distraction-free writing in Vim
aiortc - WebRTC and ORTC implementation for Python using asyncio
v86 - x86 PC emulator and x86-to-wasm JIT, running in the browser
sora-unity-sdk - WebRTC SFU Sora Unity SDK
runno - Browser-based runtime for programming languages and WASI binaries.
janus-gateway - Janus WebRTC Server
datasette-lite - Datasette running in your browser using WebAssembly and Pyodide
µWebSockets - Simple, secure & standards compliant web server for the most demanding of applications