Re: [whatwg/storage] Meta: export keys, sheds, and bottles (PR #179)

domenic left a comment (whatwg/storage#179)

I'm glad to have started this discussion, as I suspected these might be intentionally internal.

I'll note that my case is pretty different from the more complicated ones suggested above: I'm just referencing these concepts in semi-normative "privacy consideration" sections. Here's a representative sample:

> The simplest [privacy mitigation] is to treat model downloads like all other stored resources, including them in a **[=storage bottle=]** which is partitioned by **[=storage key=]**. This lets the origin model's existing privacy protections operate and obviates the need for anything more complicated. The downside is that this spends more of the user's time, bandwidth, and disk space redundantly downloading the same model across multiple sites.
>
> A slight variant of this is to re-download the model every time it is requested by a new **[=storage key=]**, while re-using the on-disk storage. This still uses the uesr's time and bandwidth, but at least saves on disk space.
>
> Going further, a user agent could attempt to fake the download for new **[=storage keys=]** by just waiting for a similar amount of time as the real download originally took.

I'd be curious if you have advice for this sort of text. Should we just say these concepts without linking to them? Should we try to use more vague language so as not to depend on these concepts existing, if they're actually considered internal implementation details?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/storage/pull/179#issuecomment-2742176439
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/storage/pull/179/c2742176439@github.com>