Rémy HUBSCHER

> Using the remote user ID means having to ask the user "who am I?" at the beginning of every sync. It can also be done only the first time...

It is true that Kinto gives a toolkit to be able to create Resources on other endpoints. I don't think today kinto-http.js is able to configure totally custom urls. but...

> I really like the idea of having this defined like that. :+1:

Shall we implement a kinto.js backend based on http://leveldb.org/ ? Refs https://github.com/Level/level ([browser support](https://github.com/Level/level-js#browser-support))

> Will it give what Roman expects? I am not quite sure to be honest.

We should provide a share this record and share this collection feature. I think.

I think we should stay closer to what the Kinto API provide in order to keep the same scope of functionality: ``` js const db = new Kinto(); const tasks...

There are three levels of permissions to handle here plus groups management. We need Buckets permissions management: ``` const db = new Kinto("bills"); db.permissions({"read": [Authenticated]}); ``` We need Collections permissions...

About group management, I have in mind something like: ``` const db = new Kinto("bills"); db.addGroup("readers", [""]); db.addToGroup("readers", [""]); db.removeFromGroup("readers", [""]); db.deleteGroup("readers"); ```

I think there are two different things: - Live server update for Bucket and Collections permissions (when creating/updating a collection or bucket) - Per records sharing which will use the...