From 678a17d1fcd84d5b3d42fde7b494fcce22f04440 Mon Sep 17 00:00:00 2001 From: Yao Xiao Date: Mon, 16 Sep 2024 18:07:52 -0400 Subject: [PATCH] Remove text after the second sentence --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index be39e44..fee1d1a 100644 --- a/README.md +++ b/README.md @@ -90,7 +90,7 @@ The topics will be inferred by the browser. The browser will leverage a classifi * e.g., site A might see topic ‘cats’ for the user, but site B might see topic ‘automobiles’. It’s difficult for the two to determine that they’re looking at the same user. * The beginning of a week is per-user, per-site, and per-epoch. That is, for the same user, site A may see the new week's topics introduced at a different time than site B, and for the same user and site, the duration of a topic may not be exactly one week. This is to make it harder to correlate the same user across sites via the time that they change topics, or via the time interval between two changes. * Not every API caller will receive a topic. Only callers that observed the user visit a site about the topic in question within the past three weeks can receive the topic. If the caller (specifically the site of the calling context) did not call the API in the past for that user on a site about that topic, then the topic will not be included in the array returned by the API. The exception to this filtering is the 5% random topic, that topic will not be filtered. - * Each epoch is automatically deleted within four weeks. The exact deletion time is per-user, per-site, and per-epoch. Active users won't notice this deletion because only the most recent three epochs are exposed, covering just three weeks of data. But for inactive user, this ensures that the specific time an epoch is deleted can't be used to track or identify them across different websites. + * Each epoch is automatically deleted within four weeks. The exact deletion time is per-user, per-site, and per-epoch. * Note that observing a topic also includes observing the topic's entire ancestry tree. For instance, observing `/Arts & Entertainment/Humor/Live Comedy` also counts as having observed `/Arts & Entertainment/Humor/` and `/Arts & Entertainment`. * This is to prevent the direct dissemination of user information to more parties than the technology that the API is replacing (third-party cookies). * Example: