A bad but authorized peer could try to create lots and lots of data inside of _local. This will be tracked by the quota manager but I'm not even sure at this point if we have a good way of figuring out what is in _local since it doesn't officially support an enumeration API. We would need to introduce one to PouchDB and then we would need to also associated with each _local entry what authenticated identity created the entry. That way we could clear out entries belonging to peers we no longer want to support. We can also detect peers who have an excessive number of entries.
The text was updated successfully, but these errors were encountered: