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
Create a simple API #18
Comments
Does it need any authentication? If not, a simple way of doing this would be to use The rate limiting middleware should be implemented to prevent abuse to begin with, reCaptcha or similar could be a future addition if needed. |
@edcs I think that reCaptcha would be hard if you write plugins for IDE's and editors. A simple JSON api where you post and receive a link would be perfect. If you really want to prevent the spam though, I don't mind registering an "application" to retrieve some tokens to use in the headers. I made plugins for PhpStorm & Sublime & VSCode in the past, so I do want to help create plugins for those! |
@edcs A simple POST & GET endpoint can be added to begin with. It should definitely be rate limited. It should always return JSON. @RobinMalfait I'm not sure if we should start with whitelisting apps. Do you think that's necessary? |
@driesvints whitelisting apps is not necessary. I was just thinking about preventing spam to use something like oauth. How would the rate limit work, do we need to register to get a token or do we need an /auth route first. Or do we just use public POST & GET routes, and implement more security when needed? |
@RobinMalfait: Rate limiting is already built into Laravel with the |
@edcs perfect! We use an older version of Laravel, so I don't know much about all the latest and greatest goodies. Good to know though! |
@RobinMalfait yeah let's just go with the POST and GET route for now and see how it goes. |
I'm going to close this as I don't think this will ever land. |
@RobinMalfait commented on Wed Sep 10 2014
That way we can create plugins for Sublime Text, Phpstorm, ... :)
@driesvints commented on Wed Sep 10 2014
Thanks for the suggestion :)
Also not a priority but feel free to offer some input on how you'd like to see the api implemented.
The text was updated successfully, but these errors were encountered: