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
The way Puter.js currently works is very good (open authentication windows, etc...), but it only works if the user's browser can open popups. If Puter.js is used in a browser which don't support popups (such as browser on consoles), or simply if puter.js is used in something which won't run in a browser (example : a game).
So i thinked it would be useful if a new menu was added to Puter's settings for creating API keys, managing their permissions (use AI, read FS, write FS, etc...), and delete them, and add a Puter.js function that could be something like puter.auth.signInKey(api key) to auth with an API key instead of using an account.
Other ideas for API keys :
Allow users to set an expiration date to API keys
Allow users to set a limit to API keys (example : let API have 50 AI uses per month, or revoke API key when limit is reached)
The text was updated successfully, but these errors were encountered:
The way Puter.js currently works is very good (open authentication windows, etc...), but it only works if the user's browser can open popups. If Puter.js is used in a browser which don't support popups (such as browser on consoles), or simply if puter.js is used in something which won't run in a browser (example : a game).
So i thinked it would be useful if a new menu was added to Puter's settings for creating API keys, managing their permissions (use AI, read FS, write FS, etc...), and delete them, and add a Puter.js function that could be something like
puter.auth.signInKey(api key)
to auth with an API key instead of using an account.Other ideas for API keys :
The text was updated successfully, but these errors were encountered: