Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed updates to availability values #29

Open
domenic opened this issue Jan 21, 2025 · 0 comments
Open

Proposed updates to availability values #29

domenic opened this issue Jan 21, 2025 · 0 comments

Comments

@domenic
Copy link
Collaborator

domenic commented Jan 21, 2025

We've received feedback in webmachinelearning/translation-api#12 and webmachinelearning/prompt-api#18 that the values "no", "readily", and "after-download" for the availability() functions might be unclear to non-native speakers.

At some point these were answers to the question canCreateXYZ(), at which point I think those names were pretty good. But now that the function is named availability() they are not as good.

We propose the new names "unavailable", "available", and "downloadable".

In addition, we propose adding a fourth state, "downloading". In the current proposal, if a model is currently downloading we'll return "after-download". But the desired user experience for if the download is not yet started, vs. if the download is already started, could be pretty different. A site might want to go ahead and create a summarizer/etc. if the download is already started, whereas they might want to prompt the user to check if the download has not yet started.

Feedback on this is welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant