BelisarithOriginal post
@everyone
I am developing a fun little side-project using this great Baas.
I am using react and wrote a hook to get a session (currently with a fake user/password hard coded for development, will incorporate correct login later on). However, during development I am refreshing the app pretty often and I always get a new session. After a few times, the rate limit kicks in. Am I doing something wrong. Can I somehow disable the rate limit - btw. I am hosting appwrite in my homelab and I see no problem currently with unlimited requests, because this application is not open to public.
Summary
To avoid hitting the rate limit, instead of creating a new session each time, use the `account.get()` method to check if the user has logged in previously and if a session already exists. This way, you can save the session in local storage and retrieve it when needed. However, note that if you're using Appwrite cloud for the Hackathon, you cannot disable the rate limit. If you're self-hosting Appwrite, you can disable it.