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
This is somewhat a duplicate of one of the points in #17.
Currently, there is no way for a program to deal with a change in endpoints, for example when the image URL changed from http(s)://i.4cdn.org/'board'/src/'tim'.'ext' to http(s)://i.4cdn.org/'board'/'tim'.'ext'. Active developers could change these URLs, but programs that weren't updated were left in the dust.
I propose a new file called options.json (or similar), sitting at the root of http(s)://a.4cdn.org/.
This file would define all the routes to allow for programs to dynamically resolve any and all URLs needed for operation.
It's format could perhaps be like follows:
{
"version": 1,
"json": {
"thread": "a.4cdn.org/`board`/thread/`no`.json",
"page": "a.4cdn.org/`board`/`page`.json",
"catalog": "a.4cdn.org/`board`/catalog.json",
"threads": "a.4cdn.org/`board`/threads.json",
"boards": "a.4cdn.org/boards.json"
},
"images": "i.4cdn.org/`board`/`tim`.`ext`",
"thumbnails": "t.4cdn.org/`board`/`tim`s.jpg",
"spoiler": "s.4cdn.org/image/spoiler.png",
"custom-spoiler": "s.4cdn.org/image/spoiler-`board``custom_spoiler`.png"
"icons": {
...list of all the other icon resources go here
...again using the backtick if there is to be replacing (only country for now)
}
}
The version would be incremented for any change to the API, allowing programs to output a warning if the API is a newer version than what has been programmed.
The text was updated successfully, but these errors were encountered:
Good proposal. How about a custom config for some boards? Some of them may have custom icons, etc. I'd propose also doing board/options.json. Also, including there links to the HTML versions of the threads may also be helpful.
This is somewhat a duplicate of one of the points in #17.
Currently, there is no way for a program to deal with a change in endpoints, for example when the image URL changed from
http(s)://i.4cdn.org/'board'/src/'tim'.'ext'
tohttp(s)://i.4cdn.org/'board'/'tim'.'ext'
. Active developers could change these URLs, but programs that weren't updated were left in the dust.I propose a new file called
options.json
(or similar), sitting at the root ofhttp(s)://a.4cdn.org/
.This file would define all the routes to allow for programs to dynamically resolve any and all URLs needed for operation.
It's format could perhaps be like follows:
The version would be incremented for any change to the API, allowing programs to output a warning if the API is a newer version than what has been programmed.
The text was updated successfully, but these errors were encountered: