Usually where rate limit info is returned it's done in the response headers to avoid having to make a request against your limit to find your limit. It would also display for a failed (limit breached) request if done that way.
I had a mission involving sending a present to Duke.
On mobile the selection for users is small, the first time I hit the second user down instead of Duke. I deleted the filled out user id, put 4 in again and selected Duke correctly. The send box confirmed it was going to duke. However the mission has not recorded it and cannot be completed.
I had a mission involving sending a present to Duke.
On mobile the selection for users is small, the first time I hit the second user down instead of Duke. I deleted the filled out user id, put 4 in again and selected Duke correctly. The send box confirmed it was going to duke. However the mission has not recorded it and cannot be completed.
500s are a general status code for a server side issue. It's not going to be one specific bug that every post in this thread relates to. It's pretty much a dumping ground to report them as we mere mortals do not have any further info to specify the errors.
Frankly they should be logged, categorised, graphed and alerted against depending on what degree of monitoring setup Torn has.
Thread title implies there was no middle ground and there was. He could've held his hands up before the competition actually started and said, "Yeah, alright, you've found a workaround and I wanted the teams to be random. We'll do a reset on the memberships and remove the gender restrictions." Pretty straightforward.
Adding all that whitespace would increase the size of every API response. For that reason it'll likely never be made the default - unnecessary overhead. Bear in mind that APIs are for machines first and foremost! It it what it is - an Application Programming Interface.
Usually where rate limit info is returned it's done in the response headers to avoid having to make a request against your limit to find your limit. It would also display for a failed (limit breached) request if done that way.