Skip to content

TURN in scope? #1

@max-mapper

Description

@max-mapper

Hey, awesome project :) @mafintosh and I have been talking a while about the need for a TURN style proxy... use case is basically:

  • A and B can't connect directly due to firewall issues
  • C runs a service on a publicly accessible port that donates bandwidth for anyone to use
  • A and B connect via C, but C cannot read their encrypted dat streams. Only the IP addresses/ports of A and B are exposed to C
  • Because its Dat, there can be many A's, B's and C's in a swarm

I was wondering if this use case is close enough to the bridging protocols use case to put into this module. What do you think? (also what do you think @mafintosh?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions