Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 21 2019 23:17
  • Nov 21 2019 01:26
  • Oct 29 2019 13:44
    dependabot[bot] labeled #32
  • Oct 29 2019 13:44
    dependabot[bot] opened #32
  • Oct 29 2019 13:44

    dependabot[bot] on npm_and_yarn

    Bump ws from 1.1.5 to 7.2.0 Bu… (compare)

  • Oct 29 2019 13:43
    dependabot[bot] labeled #105
  • Oct 29 2019 13:43
    dependabot[bot] opened #105
  • Oct 29 2019 13:43

    dependabot[bot] on npm_and_yarn

    Bump mixin-deep from 1.3.1 to 1… (compare)

  • Oct 29 2019 05:43

    nathanoehlman on master

    2.3.0 (compare)

  • Oct 29 2019 05:42

    nathanoehlman on master

    Improve handling of stuck buffe… (compare)

  • Oct 29 2019 05:42
    nathanoehlman closed #10
  • Oct 29 2019 05:38
    nathanoehlman synchronize #10
  • Oct 29 2019 05:22

    nathanoehlman on buffer-write-debugging

    Improve reporting of buffer wri… Update travis configuration Update travis-multirunner and 2 more (compare)

  • Oct 29 2019 04:55
    nathanoehlman synchronize #10
  • Oct 29 2019 04:33
    nathanoehlman synchronize #10
  • Oct 29 2019 04:27
    nathanoehlman synchronize #10
  • Oct 29 2019 02:45
    nathanoehlman opened #10
  • Oct 25 2019 08:37
  • Sep 30 2019 14:48
  • Sep 23 2019 06:10
    betimer opened #104
Damon Oehlman
@DamonOehlman
If you have any questions about rtc.io feel free to ask them here!
@silviapfeiffer Welcome :)
mimicgdl
@mimicgdl
Hi
Mauro Pompilio
@malditogeek
just found out about RTC.io, great stuff @DamonOehlman :+1:
Damon Oehlman
@DamonOehlman
Thanks @malditogeek - let me know if you have any questions.
Damon Oehlman
@DamonOehlman
Just a quick heads up - I'm probably going to move the primary rtc.io discussion channel to the organisation channel now that gitter supports such things: https://gitter.im/rtc-io
Damon Oehlman
@DamonOehlman
Hmmm - looks like that might actually not be a good idea as organisation repositories are locked down to only organisation members so rtc-io/discuss it remains
Mauro Pompilio
@malditogeek
:+1:
Damon Oehlman
@DamonOehlman
Hey folks - if people could vote this firefox issue up that would be great. It's pretty bad that they don't support the behaviour outlined in the issue report: https://bugzilla.mozilla.org/show_bug.cgi?id=852665
Flávio Ribeiro
@flavioribeiro
:+1:
Damon Oehlman
@DamonOehlman
@kumavis just posted this over on the rtc repository - definitely a worthwhile read: https://www.pkcsecurity.com/blog#webrtc-flow
Damon Oehlman
@DamonOehlman
For anyone trying to use WebRTC where you are trying to maintain a sizeable mesh of connections, it's probably worth starring this Chrome issue: https://code.google.com/p/chromium/issues/detail?id=421253
Silvia Pfeiffer
@silviapfeiffer
/rfw
oops
Damon Oehlman
@DamonOehlman
ANNOUNCE: Thanks to the efforts of @Neograph734 we now have support for signalling over socket.io: https://github.com/rtc-io/rtc-signaller-socket.io
Damon Oehlman
@DamonOehlman
ANNOUNCE: New high level package for doing screensharing in a way that works consistently across webapps, atom-apps, etc: https://github.com/rtc-io/rtc-screen (thanks to @maxogden) for the push
Firefox screensharing support is still to be done but I should be able to tackle that early next week
Shannon Code
@genecyber
I'm confused , rtc-mesh is written in node, but running via node disconnects all peers.
Here a suggestion is made : rtc-io/rtc-mesh#8 but I'm not sure how to use the library
Is there an implication to browserify
I must have missed
Shannon Code
@genecyber
Damon Oehlman
@DamonOehlman
@genecyber I'll see if I can make some improvements to the documentation to ensure this is made more clear (especially given you are at least the second person to hit a problem with it)
Damon Oehlman
@DamonOehlman
@genecyber Logged as rtc-io/rtc-mesh#9
Hamzeh Alsalhi
@hamsal
I'm trying to code a prototype of a mobile device streaming live video to a server and the server echoing back a processed version of the stream to the mobile client. We see how to handle WebRTC on the mobile device, but have not been able to find any examples of server-side code that handles WebRTC and let's me access the frames for processing (without running a browser). Could someone please point me in the right direction or give any suggestions?
Damon Oehlman
@DamonOehlman
@hamsal apologies for not getting back to you on this - I think what you are talking about would be probably within the domain of janus (https://github.com/meetecho/janus-gateway)
I think they've already implemented an echo functionality, and may have processing capabilities also
you won't be in the realm of JS though
this might be worth a look to: https://github.com/js-platform/node-webrtc (a great project, but AFAIK still doesn't have support for streams)
kumavis
@kumavis
@DamonOehlman hello/ playing around with rtc-io stuff again recently
how are things going?
kumavis
@kumavis
i have a question im sure you’ve encountered before
im looking to setup a hub-spoke connection graph
i want to use webrtc b/c it exposes reliable + unreliable data channels
how can i most elegantly setup a connection with only the hub and not the other spokes?
kumavis
@kumavis
im using quickconnect
Damon Oehlman
@DamonOehlman
@kumavis hey mate - sorry I only just saw this message last night...
let me have a think about it - primarily I would think the way to do it would be to include a qualifier in the announce message of the hub which the spokes would look for before attempting to set up a new peer connection
you have the ability to filter out announce messages based on criteria by overriding the allow attribute of the peer:filter event (documented here: https://github.com/rtc-io/rtc-signaller#events-regarding-peer-state)
I think that should work...
Vinay
@vhmth
Hey guys do y'all know if I'd be able to create a client on a node server
and then save the stream that gets sent to it to a file?
Basically the flow would be:
  1. Get a MediaStream object from the browser.
  2. Create a client and add that object.
  3. Create a client on the server that the client from the browser connects to.