TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: Share the DOM of any webpage in real-time

6 pointsby drag0sabout 4 years ago

2 comments

drag0sabout 4 years ago
Hey folks!<p>We built this Chrome Extension as an alternative to screensharing. The big difference vs &quot;video screen-sharing&quot; besides bandwith and latency is the interactivity. Duckly recreates and keeps in sync the DOM from the shared site to an iframe on the other peers so it feels like you&#x27;re browsing the remote site from your own browser. We use it a lot for sharing pages hosted on localhost and writing emails or browsing kanban boards together.<p>This extension has been built by mainly leveraging MutationObserver APIs [1], Chrome Extension APIs, a lot of browser events, and WebRTC! All the data is always sent with P2P and E2E encrypted with WebRTC, so it never touches any kind of server. You can read more details of how it works internally on the &quot;How does it work?&quot; section here [2].<p>Btw, we launched here 8 months ago as GitDuck [3], we decided to change the name to Duckly because other profiles than developers started using it (or could be using but the tool was marketed for developers only) [4]. As a nice side-effect, we get rid of the possible conflict with Git&#x27;s trademark [5].<p>Let us know us know what you think!<p>[1] <a href="https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;API&#x2F;MutationObserver" rel="nofollow">https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;API&#x2F;MutationObs...</a><p>[2] <a href="https:&#x2F;&#x2F;duckly.com&#x2F;blog&#x2F;cobrowsing-interactive-screen-sharing&#x2F;" rel="nofollow">https:&#x2F;&#x2F;duckly.com&#x2F;blog&#x2F;cobrowsing-interactive-screen-sharin...</a><p>[3] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=24228826" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=24228826</a><p>[4] <a href="https:&#x2F;&#x2F;duckly.com&#x2F;blog&#x2F;gitduck-is-now-duckly&#x2F;" rel="nofollow">https:&#x2F;&#x2F;duckly.com&#x2F;blog&#x2F;gitduck-is-now-duckly&#x2F;</a><p>[5] <a href="https:&#x2F;&#x2F;public-inbox.org&#x2F;git&#x2F;20170202022655.2jwvudhvo4hmueaw@sigill.intra.peff.net&#x2F;" rel="nofollow">https:&#x2F;&#x2F;public-inbox.org&#x2F;git&#x2F;20170202022655.2jwvudhvo4hmueaw...</a>
amaxabout 4 years ago
Cool idea using an iframe for interactivity, will for sure try it out!<p>I read the part about p2p and quality in your description &quot;<i>If you are on a call with up to 4 participants, your voice and video are also only shared P2P. For calls with more than 4 participants, we use a cloud infrastructure in order to maintain the call quality</i>&quot;<p>Just curious what&#x27;s the limiting factor of p2p here. I always read comments like <i>Signal has better voice quality than WhatsApp due to p2p</i> etc, and I&#x27;m not very well versed on the subject.
评论 #27122836 未加载