Well, in our case it seems to be pretty unreliable so I am thinking what if we made a mistake in the bloom filter itself. Alternatively, maybe iOS persists the filter result somehow?
Here's how it looks like: we load a new bloom filter, reset PIR cache, try to open some example domain, but it does not trigger any PIR query (while it should and it actually did trigger it before).
@KayleeSC hey, glad to see it helped! Just in case, I recently added an option to test via Oblivious HTTP so that you could test full stack and not just only the PIR part.
Well, in our case it seems to be pretty unreliable so I am thinking what if we made a mistake in the bloom filter itself. Alternatively, maybe iOS persists the filter result somehow?
Here's how it looks like: we load a new bloom filter, reset PIR cache, try to open some example domain, but it does not trigger any PIR query (while it should and it actually did trigger it before).
@KayleeSC hey, glad to see it helped! Just in case, I recently added an option to test via Oblivious HTTP so that you could test full stack and not just only the PIR part.