#2009 new defect

One Grid to Rule Them All

Reported by: nejucomo Owned by: daira
Priority: normal Milestone: undecided
Component: code-network Version: 1.10.0
Keywords: extensibility servers-of-happiness location newurls security globalcaps Cc:
Launchpad Bug:

Description (last modified by nejucomo)

Introducing a use case and associated ticket keyword: globalcaps

This is an enhancement request to fulfill this use case:

A user knows a $CAP they want to share with the world, so they tweet it, or print it in a book, or otherwise share it across time and space to a potentially boundless audience.

Anyone using the right software setup who sees that $CAP has a reasonable chance to retrieve the contents.

There are many related design issues, as well as existing mailing list posts and tickets:

This ticket has a scoping problem: when do we close it? I recommend closing it when either of these conditions are met:

  • One user emails a $CAP to tahoe-dev and another user successfully retrieves it without us sharing any introducer information with a checkout from the official tahoe-lafs git repository (any branch); or
  • There is a new separate code base established whose purpose is to implement this use case and whose URL is in this ticket.

Change History (7)

comment:1 Changed at 2013-06-28T04:16:11Z by nejucomo

  • Description modified (diff)

comment:2 Changed at 2013-06-28T04:18:38Z by nejucomo

Ticket #1838, Add StorageLocation hint to Storage Server, suggests a feature which may be used to implement universal caps.

comment:3 Changed at 2013-06-28T04:24:04Z by nejucomo

I advocate the following design strategy: https://tahoe-lafs.org/pipermail/tahoe-dev/2013-June/008448.html

One implication of the outlined design strategy is a need for a webapi feature to expose share placement. I'm going to add a separate ticket for that, because it is not logically necessary for this use case, but it is one approach which would also address several other tickets, such as #1838 and #1657.

Last edited at 2013-06-28T04:25:27Z by nejucomo (previous) (diff)

comment:4 Changed at 2013-06-28T04:25:59Z by nejucomo

Exposing share location in the webapi is also quite relevant to this page: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/ServerSelection

comment:5 Changed at 2013-06-28T04:26:51Z by nejucomo

Client-controlled peer selection is already ticketed in #573.

comment:6 Changed at 2013-07-02T22:46:06Z by daira

  • Component changed from unknown to code
  • Keywords extensibility security globalcaps added; extensability extensability removed
  • Version changed from n/a to 1.10.0

comment:7 Changed at 2014-09-22T20:05:08Z by warner

  • Component changed from code to code-network
Note: See TracTickets for help on using tickets.