Peter Uithoven

Superlogin's example contians a change name example: https://github.com/colinskow/superlogin-demo/blob/master/server/profile.js#L41-L47

I feel like the following question of mine asks the same question or maybe is related? https://github.com/colinskow/superlogin/issues/116

Superlogin [uses](https://github.com/colinskow/superlogin/blob/master/lib/dbauth/index.js#L79) [pouch-seed-design](https://github.com/colinskow/pouchdb-seed-design). I don't see any mention of support for the query language. I think we might need to start an issue and/or pull request there. For examples of...

Could it be that you need to add a permission / scope in the Instagram API? For Facebook this is also a additional permission.

Any reason this isn't merged?

Because it would expose used usernames/emails? I understand that it would make it easier, but shouldn't the `maxFailedLogins` and `lockoutTime` measures basically make that infeasible?

You can use the `superlogin.requireAuth` middleware for example. More on securing routes: https://github.com/colinskow/superlogin#securing-your-routes This is all server side only, you'll need to use a superlogin client to make sure it's...

I don't believe Superlogin supports cookies. But otherwise, with Authorization Bearer tokens it can do what you want.

But if you properly catch the errors, why would they end up in logs?

We also have the need for this, if only to more easily develop a `validate_doc_update` function. So I've started on a script we can run as util. A pitty is...