alternate method of adding image hosting services by users #74
Description
currently the services NativeShot uses are hard-coded apparently and this creates two issues: 1), someone will always want a service that isn't included and 2), if the dev wants to add that service, they have to write the code and pump out a new release which then has to be reviewed (by Moz), etc.
what i would propose is that the image hosting part of the code be rewritten to become more like a framework and that the 'code' for each image hosting service be written to simple text files, by users, which can then be added as a sort of plug-in to NativeShot - users could then write the necessary scripts to support whatever service they want and then these could then be shared with others through GitHub
i don't know anything regarding the different API's that the image hosts offer so i don't even know if this is doable, but here is what one of these scripts might look like if it is - perhaps it could be as simple as a standard INI file...
friendly_name=imgoat
url=https://imgoat.com/
connection_protocol=https
account_name=me
account_password=notmypetsname
upload_folder=
that would be uploaded as a text file on GitHub (maybe by pull request?) and usable by anyone that wanted to add the imgoat hosting service - all they would have to do is download the file and stick it in some dedicated directory for the NativeShot extension
after doing so, and restarting the browser i assume, an "imgoat" item (from "friendly_name") would be added to the browser context menu to support this service
NativeShot would take it from there, having the necessary generic code to make an https connection and whatever else is needed