Top all-time · #19277
TensorWorks
Company blog · tensorworks.com.au/blogprogrammingsystems
TensorWorks is the company blog at tensorworks.com.au, writing about programming and systems. Since 2021, 4 different Hacker News readers have linked it 4 times, most often “WebRTC Stream Limits Investigation”. No feed was found, so read it on the site itself.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN commenters cite this TensorWorks post on WebRTC stream limits, which tests browser-to-browser streaming, when estimating how many viewers a given uplink can serve and whether a WebRTC bug applies.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- WebRTC Stream Limits Investigation2 people · 2 mentions · first linked 2021-02-08
What Hacker News says?
Practically: however many your computer and uplink can serve. OBS needs to be tested, but this browser to browser test may give some indication: https://tensorworks.com.au/blog/webrtc-stream-limits-investi... . If you've got 100 viewers and can manage to saturate a gigabit uplink (which can be difficult because of routing and other upstream crap) you should be able to send about 9mbps video + overhead, which is pret…
Comment linking /blog/webrtc-stream-limits-investigation/
on “OBS Merges WebRTC Support”Submitted Unreal Engine C++ compilation for Windows under Linux with Wine as a story · 2 points
HN discussionAlso, can't tell, but does the webrtc client overcome this bug? https://tensorworks.com.au/blog/webrtc-stream-limits-investi... . Probably not. I have a theory that webrtc hasn't found it's footing because the native client doesn't appear to appropriately error out large messages.
Comment linking /blog/webrtc-stream-limits-investigation/
on “Show HN: A example of running P2P network in browser (WASM+WebRTC+Chord DHT)”Submitted WebRTC Stream Limits Investigation as a story · 1 points
HN discussion