4

Especially in light of the Flatiron School using the Stack Exchange API* as a part of a student-created program, it'd be useful if you could use write methods without the required Stack Apps post so long as the authentication token passed corresponded to the user who owns the API key registration.

This would let people use their own accounts to develop an application using write privileges without having to throw up an "(Placeholder)" post, only requiring them to create a listing once the application was ready for other people to use.

*I don't know the full scope of this, but based on the several placeholder posts so far it seems to require write access

Improve this question
4
  • Related: (1) Original feature request (now edited), and (2) Error message and placeholder workaround, and (3) Ancient sandbox request/workaround (but still needs a placeholder post with API 2.2).
    – Brock Adams
    Commented Mar 18, 2014 at 21:43
  • Only justification I can see is possible (future) auditing? IE, I see/install Super_Evil_App and can then trace it by ID (somehow? some day?) to a Stack Apps post and Stack Apps user?
    – Brock Adams
    Commented Jun 23, 2015 at 20:04
  • The association is already tracked internally, so that's mostly only a concern for users of the application to have a place to complain. Assuming we still require a post for anyone who is not the API key owner to use the key, I think we'd end up with the best of both worlds (i.e. no app posts until the app is ready for others to use)
    – Tim Stone ♦
    Commented Jun 23, 2015 at 20:06
  • The only possible downside would be making sure this requirement was made clear, otherwise people might publish an app without creating the post and then no one could use it.
    – Tim Stone ♦
    Commented Jun 23, 2015 at 20:07

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .