Open edqx opened 1 month ago
Unless there's strong demands, I don't think an API makes sense.
If people want the data Ziglist has, they can:
I think these three solutions work fine for most cases without the overhead of designing+maintaining API endpoints.
It would be quite helpful to many people to make use of a public REST API for Ziglist, so that people can make their own applications that make use of the knowledge available. For example, someone's package manager CLI could make use of the directory, or someone could make a CLI for Ziglist, or a discord bot, etc.
Here's some example endpoints I had in mind: