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
Would it make sense to include an optional client name in api calls? It's only useful for the backend to see what apps are using the service. It makes no difference to the client.
It would be two optional fields,
client app name (whatever the client app desires, ie: "ChromePlugin", "ReVanced", etc)
client app version (chrome plugin version, ReVanced patches version, etc).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Would it make sense to include an optional client name in api calls? It's only useful for the backend to see what apps are using the service. It makes no difference to the client.
It would be two optional fields,
Beta Was this translation helpful? Give feedback.
All reactions