ImmortalDB – A resilient key-value store for the browser

Re:ImmortalDB – A resilient key-value store for the browser by applecrazy on Monday January 28, 2019 @03:45PM (#19020909)

Then that’s inconsistent with the beginning of their readme:

> For example, clearing cookies is a common user action, even for non-technical users. And browsers will unceremoniously delete IndexedDB, LocalStorage, and/or SessionStorage without warning under storage pressure.

> ImmortalDB is resilient in the face of such events.

I guess that’s a good thing. I was worried about the next browser supercookie being made with a library like this.

[ Parent | on HN ]

Re:ImmortalDB – A resilient key-value store for the browser by penagwin on Monday January 28, 2019 @03:53PM (#19020976)

It's based on Evercookie https://github.com/samyk/evercookie which is a little less... friendly.

[ Parent | on HN ]

Re:ImmortalDB – A resilient key-value store for the browser by vokep on Monday January 28, 2019 @06:12PM (#19022020)

>Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.

AKA

>Its goal is to identify users after they've taken actions to not be identified

sigh

[ Parent | on HN ]

Re:ImmortalDB – A resilient key-value store for the browser by taco_emoji on Monday January 28, 2019 @06:37PM (#19022234)

I don't think they're being inconsistent - intentionally clearing cookies is common, but clearing app storage less so. And the browser may purge app storage to reclaim space, but that leaves cookies. It's unlikely that both things will overlap unless the user deliberately clears both cookies and storage.

[ Parent | on HN ]