Hey @User

What brings u to our server?

Found out about the Golang library via Angel list, saw the words "Open source" and "Mumbai" together and it piqued my interest haha!

Awesome!

Did u check out SuperTokens?

Doing it right now, got 10 tabs open already 😛

Haha! If u have any questions, feel free to ask! 🙂

And if u want to contribute to our Golang library, then u can join supertokens.io/slack

Already joined the slack channel (But I see you're more active here). Sure I'll study a bit about Supertokens and get back to you in an hour or so.

Sure!

Hey @User Glad to see you've finished postgres, what is actually the issue with RN and cookies? cant you just use local storage?

also what is reason we have to sign up to supertokens.io in order to use the open source software?

So we prefer to keep using cookies even for RN since that allows you to use the same auth system for a website (if you choose to build that in the future). If we use a non-cookie based method for RN, then you will have to build another set of APIs just for a website (in which you should use cookies). The issue with RN (which they claim to have fixed in the latest unreleased version), is that it doesn't handle cookies properly by default. To fix this, we are using our iOS / Android native library and building a RN wrapper around that. You should have no issue with using that in your project. The reason we have a sign up for an open source project is so that we can quickly make the product better by talking to people, like yourself, who use our solution. Sign ups help us get in touch easily, and also help us to give you an amazing implementation experience. Over time though, we want to remove the sign up for our open source version and just keep it for the paid version.

@User ^

Does this mean that you will be able to see our session DB if we sign up because it says sign up and super tokens will store the db for you

Apart from this that sounds fantastic

oh no. We will not be able to see anything from your end. Your sessions will be only stored in your Postgresql db.

Ahhhhh

it's a complete on premise solution. You have complete control over it all. haha

Hahah Oh, And so this cookie thing, does it allow black listing via redis?

you mean JWT blacklisting?

via redis

Is it like this: -> Cookie contains JWT -> Redis Holds Cookie -> Refresh token from token in cookie

Cookie contains access token (JWT) and refresh token (non-JWT). Right now, we store the refresh token in postgres. We are building out caching functionality using redis and memcached that will then store session data to improve read speeds. But with JWTs, most session verification calls will not need any network operation anyways. So it's super fast!

Also, what on our site lead you to think "sign up and super tokens will store the db for you" - if you could please send a screenshot, then we can make the messaging there clearer 🙂

@User I think the wording here could be changed

ah i see. Fair enough! Will make the change 🙂

Hahah phew, thought it was one of those cough cough Firebase

hahaha!

Let me know if you have any more issues or questions please 🙂