[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3457: The separate introducer servers represent unnecessary complexity in an overall Tahoe-LAFS deployment

[Tahoe-LAFS]

#3457: The separate introducer servers represent unnecessary complexity in an
overall Tahoe-LAFS deployment
------------------------------+-----------------------
     Reporter:  exarkun       |      Owner:
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-network  |    Version:  n/a
   Resolution:                |   Keywords:
Launchpad Bug:                |
------------------------------+-----------------------

Comment (by exarkun):

 I think the core of the latter idea above is that using Tahoe-LAFS storage
 itself to propagate this information represents the minimum complexity for
 solving the problem that the introducer servers currently solve.  A
 solution which is simpler in isolation may exist but since the purpose is
 to let clients use the storage servers, total system complexity cannot
 fall below that required to make use of those storage servers.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3457#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage