>Download Chan.
>Host JSON of posts.
>Build simple interface.
>Use nginx as reverse proxy.
>??????????
Profit
Why the fuck do you want a DB when it's already JSON. FFS.
>Download Chan.
>Host JSON of posts.
>Build simple interface.
>Use nginx as reverse proxy.
>??????????
Profit
Why the fuck do you want a DB when it's already JSON. FFS.
A better way to do this is to probably put everything client side. Make a cross platform application that just fetches new posts every so often. The browser is pretty perfect for this is we can set up a cross platform local server to host a local copy of qcodefag and this board.
Search
https:// github.com/bvaughn/js-search
Pros: Fast enough once index is built.
Cons: Have to build index, or send it from a server, ipfs, blockchain, whatever.
UI
rip it from qcodefag for q posts
Add 8ch layout to some button on qcodefag or some tab
Display the posts as normal, but add search bar for board side of new client for qcodefag and this board.
Pic related, it's easy to get .json formatted threads.
inb4 we all pwn ourselves.
Conveniently this also alleviates the clown issue should that garbage bill pass. I mean not really since we'll still own ourselves but fuck, we can try.
I don't know why nobody cares but it's trivial do download threads, posts, and boards through the 8ch api in the form of JSON. There is no reason to not have the local client make the get request every so often.
I meant the hypothetical client with which people are searching this board and staying updated. That client should search for posts all on it's own instead of relying on a single source of truth. (saves infrastructure money too)
Literally just build an index of tags and use fucking client side javascript. Muh databases. Jesus Christ people. You could even let users share tags.
First one with a completed project wins. Peace.