libdweb
ws-tcp-proxy
libdweb | ws-tcp-proxy | |
---|---|---|
4 | 1 | |
442 | 30 | |
-0.2% | - | |
0.0 | 2.9 | |
11 months ago | about 1 month ago | |
JavaScript | Go | |
MIT License | MIT License |
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.
libdweb
-
WICG/direct-sockets: Direct Sockets API for the web platform
I appreciate the effort, but I'd rather want libdweb to be resurrected. It's a shame that Mozilla killed it
I want to be able to write extensions that can do whatever the hell I want. It's my computer and it's my Browser. If necessary, I would enable it in the about:config. But there should be an option to allow me to do that.
https://github.com/mozilla/libdweb/issues/109#issuecomment-5...
-
Is there any way to get Mozillas attention back on libdweb?
I do demand the ability to reasonably extend my browser though. There used to be some effort in this direction: https://github.com/mozilla/libdweb https://bugzilla.mozilla.org/show_bug.cgi?id=libdweb
- A guide to IPFS connectivity in web browsers
-
Support for the IPFS Protocol – Firefox Bugzilla
Mozilla gave up on distributed web a long time ago, Just look at the libdweb[0] project. No update in years, nobody even to get almost complete patchset to firefox reviewed and merged.
[0]: https://github.com/mozilla/libdweb
ws-tcp-proxy
-
WICG/direct-sockets: Direct Sockets API for the web platform
This would be so amazing. In order to access most vanilla services like redis, postgres etc. you need to deploy a bridge https://github.com/zquestz/ws-tcp-proxy
CloudFlare/Deno etc. all have these workarounds around tunnelling but all that would disappear with this protocol. I made a service for writing servers on the web (https://webcode.run -- somewhat abandoned at this point but it is still running), and a big problem with the approach was the web's inability to make TCP connections.
What are some alternatives?
ipfs-companion - Browser extension that simplifies access to IPFS resources on the web
webrtc-for-the-curious - WebRTC for the Curious: Go beyond the APIs
au-revoir-utm - Removes crappy utm_ tracking stuff