You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2020. It is now read-only.
Currently, the teller has support for API routes but the live teller used for the demo in PR does not expose the endpoint via https so others can connect to it. The teller does not have support for tokens which it should have in order to prevent dos attacks potentially impacting energy accumulation. For this, a few factors need to be considered:
Is the teller API open to everyone or just the platform
Will exposing the API negatively affect the performance of the teller in terms of heat and other dynamics which we may not be aware of
These need to be clarified upon before we can expose the live teller.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, the teller has support for API routes but the live teller used for the demo in PR does not expose the endpoint via https so others can connect to it. The teller does not have support for tokens which it should have in order to prevent dos attacks potentially impacting energy accumulation. For this, a few factors need to be considered:
These need to be clarified upon before we can expose the live teller.
The text was updated successfully, but these errors were encountered: