dmotz
Joined 16 years ago
Karma
985
Submissions
80
Member since
Oct 20
Recent submissions
Comment · 3 months ago
Trying to make it effortless to build p2p apps without any setup:
Comment · 1 year ago
https://github.com/dmotz/trystero
Direct link to the underlying source code.
Comment · 1 year ago
I'm the Trystero author and I'd say both libs attempt to accomplish the same goal but with very different APIs. One key difference is PeerJS uses a single centralized server by default for matchmaking, whereas Trystero offers lots of flexibility and redundancy, using various signaling connections in parallel.
Comment · 2 years ago
You might be interested in my side project Trystero https://github.com/dmotz/trystero
It abstracts away the work of signaling and connects peers via open decentralized networks like BitTorrent, Nostr, MQTT, IPFS, etc.
Comment · 2 years ago
I have a side project that aims to organize your ebook highlight collections with on-device semantic search. [1] Right now it only indexes your own content but I'd like to add a mode that allows you to share your collection and let others find relevant ideas via semantic search -- a discovery platform for ideas found in books. It's open source if you want a sense of how it works now. [2]
Comment · 2 years ago
This looks exciting and I'm pleased to see more and more frictionless ways of making p2p apps. I've been building a somewhat similar hobby project [1] that aims to connect peers in the browser by piggybacking on open protocols out on the net (BitTorrent, MQTT, Nostr, IPFS, etc).
This project seems to be using Hyperswarm which I've looked at for use as a peering medium but it seems like it's not supported in the browser. I'd love to implement it if that story changes since it's so easy to distribute apps on the web.
Comment · 2 years ago
This is a really nice overview of the nuances of WebRTC.
If you want to try this tech at a higher level, I maintain an experimental hobby project that attempts to abstract all the complicated parts of WebRTC into a simple API. Most importantly, it obviates the need to run your own signaling server by piggybacking on various public protocols like torrent trackers or IPFS to match peers. It's well-suited for quick projects/prototypes.
Comment · 3 years ago
Two personal projects I'd like to get fully-baked eventually:
My attempt to get more out of all my ebook highlights using on-device AI.
https://github.com/dmotz/trystero
My attempt at making it as easy as possible to add p2p to a web app (no server required). A "jQuery for WebRTC" of sorts.
Comment · 3 years ago
A decade ago I built a silly JS library for folding up DOM elements like paper [1] and I eagerly anticipated using element() instead of tediously cloning nodes for every fold. Here we are ten years later and this niche CSS feature has yet to be adopted by the other browsers. Similarly, I thought I'd soon be using the CSS custom filter spec from the same era (which allows custom GLSL shaders to be applied to elements), but it also has yet to pick up traction.
Comment · 3 years ago
Thanks for sharing, I like the name and I'll try it out. Yes, I'd like to add opt-in sharing features in the future -- seeing others' notes can be very insightful as you said.
https://github.com/dmotz