I have a website that acts as a database for Magic: The Gathering rules questions. I've been working on an API to serve those questions. It's my first time designing an API, and it has some rather atypical requirements, so it's kind of a mess.
If, within a week of me announcing the API publically, I find out about a serious bug, this resolves to YES. Otherwise it resolves to NO after a week has elapsed later.
Serious is subjective. Roughly it means "something bad enough it may significantly interfere with other people's usage of the API, and/or I feel the need to fix it right away".
If you want to manipulate this market towards NO, you can try to find bugs and tell me about them so that I can fix them before releasing the API. If you want to manipulate this towards YES, you can instead wait to notify me about any bugs you find until after I release it. (I'll probably be releasing it in 5-10 days, but no guarantees.)
Related questions
@IsaacKing it's up to you of course, and it depends on what your client will look like and how you will implement it, but it does not have to be that way.
see these docs for a very popular paradigm that mostly uses POST for everything:
@IsaacKing it depends on what you want to use it for. I'd say it's bad design, and you should have used post but if you're sure you'll only need small payloads I guess it ok.
I feel like @IsaacKing's propensity to think of things as serious problems is probably somewhere around the 10th percentile.
@IsaacKing How is this "no confidence"? If it were a website I'd made myself, I'd confidently bet it up to 90% or 95%. Here I'm scared to push it even to 75%. That's an awful lot of confidence.
@Boklam The most likely way this resolves NO is if I release it, there's very little interest, and nobody finds any of the bugs within a week, even though they exist.
The only reason I'm not betting the market lower is because at some point someone here will go find a bug just to make it resolve YES.