NEW: Frontend and backend have been separated from Blazechan and are not replacable. The documentation for the interfaces will come before the 0.13.0 release. We are getting closer and closer to a 1.0 release. CHANGE: The folder layout has been modified a bit. Shell scripts are now in bin/ and config examples are in etc/. NEW: The config file is now in JSON format and resides in config.json in the root directory. The names are pretty much analogous from the .env file, so migration will be easy. The new configuration file also gives you the option to change your database backend. CHANGE: install.sh should now be fully working, and as more operating systems are tested with Blazechan, more systems will be supported. If your system is not supported, you can skip the check with --disable-packages at the moment. CHANGE: Blazechan now doesn't directly depend on Node.js to work, but the default frontend does. If you install a frontend without it, you should not need node.js at all. CHANGE: The API for Blazechan has been tidied up a bit. A major API refactor is also coming soon, which will make the API reflect more of the functionality of the main site. BROKEN: Moderation is currently broken. It will be fixed before the final release. BROKEN: Likewise, extensions are broken. This is because the frontend/backend separation changed both the APIs and the paths of a lot of functionality. BROKEN: Some of the panel still doesn't work. See above.
It is finally here. After long last, the engine is fractured but whole. In the coming weeks, I will be slowly fixing the remaining issues, adding in the missing features, and make this imageboard software the greatest among all. I was burnt out for a while in general, couldn't work on any code (went to work like a zombie), now I got out of my burn-out and am back to making imageboards great again. And yes, the frontend got a rework.
Do you still host a beta instance for the newer releases?
Ryan Jackson
dev was shut down but will be brought back up. I'll be moving Nextchan to a new server once 0.13.0 releases.
Thomas Jones
Lynxchan is better
Blake Smith
...
Jeremiah Harris
Fuck off fag.
You won't believe how things will look
Logan Mitchell
can you explain the reason the internet page collection you manage has a sort of vacuum force to it?
Joshua Harris
Only you seem to be experiencing it. Maybe the issue is on your end?
Logan Hill
Network latency will render moot any performance gains from using C.
Cooper Murphy
i too experience a degree of suckage, can you please fix this in the next release
Bentley Sullivan
LMAO.
Ryder Green
Servers interact with thousands of people at the same time, and spend a lot of effort compiling html documents and accessing databases.
Austin Morales
Blazechan has a hybrid document/application cache which relies on Redis to store documents based on the user. It's not as fast as a dedicated document cache like Varnish, but it still will not generate a page per request.
Nathan Lee
Take two: It stores documents and serves you a static page with some non-static elements based on your login status via ESI.
Carson Rodriguez
Wouldn't meguca make for a good base?
Matthew Sanchez
The owner is a google loving chrome using cuckchanning hipster faggot.
Ethan Phillips
so i installed this blazechan on my home server and man, does it suck
a haiku by me
Nathan Morris
stay mad metafag~
Nathaniel Young
Because Meguca does not have good features
Ryder Hernandez
What is the problem? Did the installer fail or something? I can help you if you're having trouble.
First of all, Second, the liveposting kills any involved discussion and devolves it into IRC tier one-line replies.
It is only used for transpiling assets from ES6 into ES5 and from SCSS into CSS. It also bundles the dependencies in a pain-free way.
Connor Gonzalez
Also note, only the default frontend requires Node.js. If a frontend that doesn't need it is written, then you won't need Node.js at all.
John Brooks
Updates today:
Blazechan Core frontend-default backend-postgresql >Added hash and eq for using in sets and for checking equality
We're getting closer and closer to a -b2 release. Only the global moderation actions do not work at the moment. I will be fixing them (hopefully today) and releasing v0.13.0-b2. The roadmap is as follows: I am also planning to completely revamp the Javascript of frontend-default to make it more stable and add features a lot of people wanted. I will be creating dev.nextchan.org/ again today to test the beta. I'll post here when it's online. It will be on NeXTCHAN's future server (when 0.13.0 is done) which is a higher-end server hosted on DigitalOcean.
I'm not having an issue. When a crash occurs please click "switch to copy-paste mode" (located in mid-to-bottom of page) and copy the contents into a post in the thread.
I started rewriting the frontend JS to make it more robust and add long-yearned-for features. It should be done tomorrow or in the weekend, I'll leverage a lot of code from the current JS.
Already known, fix soon. It seems like not all images are allowed to be used as transparency masks, such as GIF. I use the image's alpha channel as a transparency mask when JPEG thumbnailing is enabled before overlaying it to the post background color canvas. I'll try to find a solution to this.
Carter Edwards
Searching around for this tells me that all images used for the mask need to be RGBA, even though PIL's documentation says it's converted. Perhaps it only automatically converts the pasted image itself and croaks with mask images of different type?
Brayden Nguyen
...
Xavier Long
I actually wrote an HTTP server in C because I was bored (HTTP/1.1 parser and everything).
Luis Garcia
A http server is very far from an actual website with dynamic content, let alone a social media one
Then you write a fastcgi module, not really hard either.
Kayden Martinez
I will integrate StopForumSpam.
Jacob Kelly
Over the weekend I had some stuff I had to tend to, but I still tried to refactor the frontend JS for Blazechan as much as I can. Thread updates are now working. AJAX posting will be done soon, but probably not tomorrow as I will be very busy. I will be pushing the current changes over to the repo, but it doesn't work fully yet. I'll squash the commits once it's fully done.
Daniel Brown
Forgot to attach. A new module system has been established. The JS settings modal is now auto-generated on the fly meaning NoJS users won't have it in the page html anymore. I'm working towards cleaning up old cruft and bringing in features that people have requested.>>989668
write the imageboard in VHDL or verilog and maybe this thread will become more interesting and less trash. I want real speed. not your scripting language trash speed
Hudson Hernandez
For what purpose? Things would get complicated really quickly. You basically have to create your own NIC, your own IP stack, your own SATA controller, web server, image manipulating tools to generate thumbnails, which means implementing PNG, JPEG, GIF and other decoders/encoders... Sure you can use IP cores but in the end you're still designing hardware not software. It's like creating imageboard with 74xx series ICs only instead of schematic you're using a circuit description language.
Charles Cruz
Will posting work in w3m?
Charles Carter
It had better.
John Jenkins
bump where are you m712
Tyler Gonzalez
How do you want me to take you serious when the first thing you tell me about your software is a straight up lie?
