/tech/ - Technology★

Do you still host a beta instance for the newer releases?

>>986484

dev was shut down but will be brought back up. I'll be moving Nextchan to a new server once 0.13.0 releases.

Lynxchan is better

>blazing fast

<python

pick one

next time do it right and write it in C

>>986488

Fuck off fag.

>>986489

You won't believe how things will look

can you explain the reason the internet page collection you manage has a sort of vacuum force to it?

>>986500

Only you seem to be experiencing it. Maybe the issue is on your end?

>>986489

Network latency will render moot any performance gains from using C.

>>986500

>>986502

i too experience a degree of suckage, can you please fix this in the next release

>>986480 (OP)

>Blazing fast imageboard software

>written in Django.

LMAO.

>>986509

Servers interact with thousands of people at the same time, and spend a lot of effort compiling html documents and accessing databases.

>>986536

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.

>>986544

>store documents based on the user.

Take two:

It stores documents and serves you a static page with some non-static elements based on your login status via ESI.

Wouldn't meguca make for a good base?

>>986583

The owner is a google loving chrome using cuckchanning hipster faggot.

so i installed this

blazechan on my home server

and man, does it suck

a haiku by me

>>986585

stay mad metafag~

>>986583

Because Meguca does not have good features

>>986602

What is the problem? Did the installer fail or something? I can help you if you're having trouble.

>>986583

First of all,

>go

Second, the liveposting kills any involved discussion and devolves it into IRC tier one-line replies.

>>986496

Should have coded it in Rust.

>>986754

I'm not a homo.

>everyone ITT complaining about python

>not complaining about nodejs in the frontend

I see /tech/ has been overrun by nodevs

Updates today:

Blazechan Core

>Frontends now have a custom/ folder to override static assets

>Documentation for installation was updated, and should be correct now

>Documentation stubs for the frontend and backend interfaces have been added

>The nodejs dependency has been removed from install.sh. Also it sets a default (nano) for $EDITOR now.

>Removed unnecessary requirements.unstable and renamed requirements.stable to requirements.txt. Also removed a lot of unneeded dependencies.

frontend-default:

>Added the custom/ folder for asset override

>Finally reverted to the original Blazechan logo (consequence of previous change)

backend-postgresql:

>The README now warns you to use PostgreSQL as the Django backend if you choose to use it.

>>987162

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.

>>987162

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.

Updates today:

Blazechan Core

>Brought icons up to date with FontAwesome 5

>Fixed an issue where tripcode could be set to null while editing causing the database to complain

>Added a function to the Post interface to set editor name

>Fix editing and fix import names

>Check moderation permissions before doing anything else in views, because otherwise database hits from unauthorized users can occur

>Added initial permissions data file to seed global and board permissions from that (engine/data/permissions.json)

>Explicitly specified board logs template name. Board logs template must now reside in templates/board/logs.html

>Exposed a cache clear method for board index only

>Fixed expired bans showing in banned view, and bans running 1 minute early

>Delete (Boardwide), Ban, and Ban&Delete (Boardwide) now all work

frontend-default

>Fixed some action links pointing to "feature post"

>Moved actions.html up one dir and deleted redundant templates/board/post/single/

>Updated all icons to FontAwesome 5

>Fixed the board logs template location

>Fixed a bug where the username in board logs wasn't showing

backend-postgresql

>Added hash and eq for using in sets and for checking equality

>Post.is_thread() now uses a more efficient method to check whether the post is a thread

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:

>v0.13.0-b2: moderation

>v0.13.0-b3: panel

>v0.13.0-b4: extensions

>v0.13.0-b5: permissions and role editing

>v0.13.0 final: documentation for the backend and frontend interfaces, a lot of stability testing, unit tests

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 https://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.

Insta-crash on https://dev.nextchan.org/*/

>>987162

Why would they complain about node?

>>987945

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 seem to encounter this issue trying to open it, plz help

https://youtu.be/Ttc5AXUOcFQ?t=2

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.

>>987470

>>987979

> Nodejs in the frontend

> Javascript for the backend, in the frontend

> Blazechan!

Is op a masochist? Does he know where he is?

BRB, writing an imageboard in C.

>>988430

>javascript for the backend

Wut?

>>988442

That would be awesome.

>>988444 (nice numbers)

From trying to goto catalog https://0x0.st/sEv2.txt

From trying to post image https://0x0.st/sEvL.txt

>>988446

>catalog

Already known, fix soon.

>img posting

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.

>>988544

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?

>>988430

>writing an imageboard in C

>calls other people masochists

>>988548

I actually wrote an HTTP server in C because I was bored (HTTP/1.1 parser and everything).

>>988549

A http server is very far from an actual website with dynamic content, let alone a social media one

https://learnbchs.org/

why does your website suck

create an anti-spam extension

please

i beg you

>>988550

Then you write a fastcgi module, not really hard either.

>>988632

I will integrate StopForumSpam.

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.

>>988634

Why don't you do it then?

>>989675

It's fixed in upstream but not yet uploaded to dev.nextchan, let me do that right now.

>>989712

Huh, I thought it was fixed but git says all is up to date. Let me see.

Latest updates:

>Added a new Post class allowing easy manipulation of posts on the page. Also added back a basic Post module back for the frontend JS with post hiding.

>The bug where non-PNGs were broken is fixed.

>ThreadUpdates now uses the new Post class. Also, the model of handling newly arrived posts has changed. Now on a new post, a new-post event is sent which can be listened to with:

document.addEventListener("new-post", e => {
  const post = e.post;
  post.name = "Something";
  // ...
}, false);

I'm currently bringing back image expansion.

Updates today:

Blazechan Core

>Simplified video thumbnailing (moved around regexes so they don't re-compile for every video thumbnail generation, removed useless hour:min:sec computation as ffmpeg accepts just seconds too), and fixed a division by zero error for no-video streams.

>Added the mimetype of the attachment in `AttachmentSerializer`.

>Added 2 new methods to the IPost interface: `get_cites` and `get_citings`, to get a list of cites from and to a certain post respectively.

frontend-default

>Image hover has been added for video and images.

>Video file expansion added.

>Basic cite hovering added (only for posts on page, no reverse cite hover yet), will be extended tomorrow

backend-postgresql

>Implemented `get_cites` and `get_citings` required by IPost

>>991322

Bumparooooo!

>developing imageboard software in 2011+7

ISHYGDDT

>>998998

Shad yes

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

>>999412

>write the imageboard in VHDL or verilog

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.

Will posting work in w3m?

>>999729

It had better.

bump

where are you m712

>>986480 (OP)

>blazing fast

>python

How do you want me to take you serious when the first thing you tell me about your software is a straight up lie?

>>1005158

Remember that lynxfags will always btfo

Rewrite it in erlang