From 7950b14d4d9be5bf96cc41e344457b45fb06554b Mon Sep 17 00:00:00 2001 From: caraitto Date: Tue, 11 Oct 2022 18:07:39 -0400 Subject: [PATCH] Lower the bfcache limit to 10 min. Also, add the privacy rationale for needing a low limit. See also #3. --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0e7942d..f0b3224 100644 --- a/README.md +++ b/README.md @@ -315,9 +315,13 @@ Specifically, beacons will have the following privacy requirements: * Delete pending beacons for a site if a user clears site data. * Beacons registered in an incognito session do not persist to disk. * [#3] If a page is suspended (for instance, as part of a [bfcache]), - beacons should be sent within 30 minutes or less of suspension, + beacons should be sent within 10 minutes or less of suspension, to keep the beacon send temporally close to the user's page visit. - Note that beacons lifetime is also capped by the browser's bfcache implementation. + Network requests can reaveal information about users, like coarse + IP location as networks change. Users can reasonably expect that + this information isn't sent to sites after leaving a page, hence + a low limit. Note that beacons lifetime is also capped by the + browser's bfcache implementation. [#3]: https://github.com/WICG/unload-beacon/issues/3 [#27]: https://github.com/WICG/unload-beacon/issues/27