Blazechan 0.12.0: Road to Decentralization

Also,
Filters exist, you can put the post content in it for the timebeing
Do you wanna know how I know you're Sergio? You suck badly at naming shit. For example, the above statement makes no sense.

working on the logo as we speak

Oh seems like you want to go then.

gitgud.io/LynxChan/LynxChan/blob/master/src/be/engine/postingOps/common.js#L404-407 here, you can see that he's replacing [code] and [ /code] with and . Notice how he doesn't check at all whether two [code] [ /code] tags match. Of course this creates a problem: if you only post [code], then the rest of the page will be monospace.
And here's our golden boy Stephen's fix:
gitgud.io/LynxChan/LynxChan/commit/b955483cf80b79ff245d1d77b5f9c17962375a96
Not only does this reduce one's understanding of code, it also makes it harder to fix things down the line. This is the same engine which is supposed to be "an example to future imageboard developers" (his words, not mine).

And here you go sperging out about shit you don't even understand. I told you before, you don't even know why it doesn't matter if the tags are checked when posting. But I know you are physically unable to listen anyway, so keep on spergin'.

wow. that is cs grad meme tier

Please do enlighten us, o great Sergio, because as far I can see, it does matter apparently, since it needs a fix.

When you render a page, you might render it in a way that will take only PART of the post, because on board pages you cut the text. So only after you do that you can check what is matched or not.

lmao

That's a shitty justification. This would happen with any tag, and in fact it happens here (not sure if it's fixed) when a greentext is cut off. Why not check for all opening tags and close then recursively then? Why monkeypatch?

Because no other tag will cause issues if unmatched.