[tahoe-dev] Read only (client/gateway only) Introducer furls?

[Zooko O'Whielacronx]

Dear Garonda Rodian:

It sounds like you're confusing the authority to access certain
files-and-directories (which ultimately boils down to some
cryptographic keys and/or cryptographic identifiers) with the
authority to upload data. The former is currently controlled by those
caps that you named, the latter is currently controlled in a very
limited, brittle way, which is that if you give someone the FURL to
your introducer then they gain the authority to upload as much as they
want to any storage server that connects to that introducer.

Fixing the problem from the server's perspective — that servers can't
control which clients can take up how much storage space — is the
topic of ticket #666. Fixing the problem from the client's
perspective, that you also mentioned in your email — that clients
can't control which servers they are relying on for the longevity of
their ciphertext — is the topic of #467.

Although actually I think the plan that Brian made (with the help of
some other people) for #666 will partially address the latter problem,
too.

https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467# allow the user to
specify which servers a given gateway will use for uploads
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/666# Accounting: limit
storage space used by different parties

Regards,

Zooko