New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

figure out an elegant way to integrate / work with WebRTC #63

Open
silverbucket opened this Issue Mar 31, 2013 · 3 comments

Comments

Projects
3 participants
@silverbucket
Member

silverbucket commented Mar 31, 2013

See conversation in issue #60 for the initial discussion.

@silverbucket silverbucket added this to the tracker-ongoing milestone Aug 31, 2014

@michielbdejong

This comment has been minimized.

Show comment
Hide comment
@michielbdejong

michielbdejong Sep 9, 2014

Member

Mentioning this in https://unhosted.org/adventures/14/Peer-to-peer-communication.html:

So this simple demo app uses webfinger and sockethub to implement a simple text chat. It's still not very usable, since sockethub was not really designed to listen on ports; this means you can have only one chat conversation at a time. But we'll work on that and will eventually get it working as a proper chat app, with an addressbook and everything.

Member

michielbdejong commented Sep 9, 2014

Mentioning this in https://unhosted.org/adventures/14/Peer-to-peer-communication.html:

So this simple demo app uses webfinger and sockethub to implement a simple text chat. It's still not very usable, since sockethub was not really designed to listen on ports; this means you can have only one chat conversation at a time. But we'll work on that and will eventually get it working as a proper chat app, with an addressbook and everything.

@silverbucket

This comment has been minimized.

Show comment
Hide comment
@silverbucket

silverbucket Sep 9, 2014

Member

OK that's fine. I wouldn't say it's not designed to listen on ports. It's perfectly capable of it. Maybe saying: since the functionality for opening up new ports on the fly is a feature not yet implemented in sockethub.. ?

Member

silverbucket commented Sep 9, 2014

OK that's fine. I wouldn't say it's not designed to listen on ports. It's perfectly capable of it. Maybe saying: since the functionality for opening up new ports on the fly is a feature not yet implemented in sockethub.. ?

@silverbucket

This comment has been minimized.

Show comment
Hide comment
@silverbucket

silverbucket Sep 9, 2014

Member

Also putting this text here for reference:

Incoming Requests

The goals of Sockethub are to provide a generic API to messaging from unhosted web apps, that includes posting to someone elses instance. Consider for example, a webfinger record that has a sockethub entry along with it's remotestorage one:

    {
      "href": "https://storage.5apps.com/silverbucket",
      "rel": "remotestorage",
      "type": "https://www.w3.org/community/rww/wiki/read-write-web-00#simple",
      "properties": {
        "http://tools.ietf.org/html/rfc6749#section-4.2": "https://5apps.com/rs/oauth/silverbucket"
      }
    },

    {
      "href": "https://sockethub.5apps.com/",
      "rel": "sockethub",
      "type": "http://sockethub.org/rel/sockethub",
      "properties": {
        "http://sockethub.org/rel/useraddress": "nick@silverbucket.net"
      }
    }

Now, consider another users wants to get a hold of you. They have your sockethub endpoint, and the user address you register as when you connect to it.

With that information they could make an HTTP POST to sockethub, something like:

HTTP POST https://sockethub.5apps.com/
{
  "actor": {
    "address": "michiel@michielbdejong.com",
    "name": "Michiel B. de Jong"
  },
  "target": [
    {
      "address": "nick@silverbucket.net"
    }
  ],
  "platform": "webrtc",
  "verb": "invite",
  "object": {
    // .... webrtc connect information ...
  }
}

This is all hypothetical for now, but the idea is that if I'm online, with a WebRTC enabled app, I'd get your invitation for a WebRTC chat.

Member

silverbucket commented Sep 9, 2014

Also putting this text here for reference:

Incoming Requests

The goals of Sockethub are to provide a generic API to messaging from unhosted web apps, that includes posting to someone elses instance. Consider for example, a webfinger record that has a sockethub entry along with it's remotestorage one:

    {
      "href": "https://storage.5apps.com/silverbucket",
      "rel": "remotestorage",
      "type": "https://www.w3.org/community/rww/wiki/read-write-web-00#simple",
      "properties": {
        "http://tools.ietf.org/html/rfc6749#section-4.2": "https://5apps.com/rs/oauth/silverbucket"
      }
    },

    {
      "href": "https://sockethub.5apps.com/",
      "rel": "sockethub",
      "type": "http://sockethub.org/rel/sockethub",
      "properties": {
        "http://sockethub.org/rel/useraddress": "nick@silverbucket.net"
      }
    }

Now, consider another users wants to get a hold of you. They have your sockethub endpoint, and the user address you register as when you connect to it.

With that information they could make an HTTP POST to sockethub, something like:

HTTP POST https://sockethub.5apps.com/
{
  "actor": {
    "address": "michiel@michielbdejong.com",
    "name": "Michiel B. de Jong"
  },
  "target": [
    {
      "address": "nick@silverbucket.net"
    }
  ],
  "platform": "webrtc",
  "verb": "invite",
  "object": {
    // .... webrtc connect information ...
  }
}

This is all hypothetical for now, but the idea is that if I'm online, with a WebRTC enabled app, I'd get your invitation for a WebRTC chat.

@skddc skddc modified the milestone: tracker-ongoing May 4, 2017

@silverbucket silverbucket added this to Backlog in Overview Sep 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment