You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am an imageboard engines developer (http://tinyboard.org and https://int.vichan.net/devel/). Both engines already implement a 4chan compatible api and I, for one, would like to standarize our efforts with you, and another developers.
config.json
Many imageboards have custom URLs for images etc. IMO, the config.json file would be a nice fit, so that some application can actually work with every imageboard, of course if it's actually conforming to the new API, without any changes. The file would have to eg. describe the urls (especially, that you recently changed your URLs).
Multiple file upload
We are currently just responding to the client like if the thread had only one file. We can do some extension sending an array of additional files.
tim field
tim field is specified to be integer. Many imageboards, tho, have another characters in the filename.
The text was updated successfully, but these errors were encountered:
Hello, I am an imageboard engines developer (http://tinyboard.org and https://int.vichan.net/devel/). Both engines already implement a 4chan compatible api and I, for one, would like to standarize our efforts with you, and another developers.
config.json
Many imageboards have custom URLs for images etc. IMO, the config.json file would be a nice fit, so that some application can actually work with every imageboard, of course if it's actually conforming to the new API, without any changes. The file would have to eg. describe the urls (especially, that you recently changed your URLs).
Multiple file upload
We are currently just responding to the client like if the thread had only one file. We can do some extension sending an array of additional files.
tim field
tim field is specified to be integer. Many imageboards, tho, have another characters in the filename.
The text was updated successfully, but these errors were encountered: