Catalog of /lynxchan/
New Thread:

Max Message Length: 4096
Spoiler Max File Size: 1.00 MB
File Limit Per Post: 3
Remember to follow the rules .
R: 0 / I: 0 / P: 1
Locked Pinned
List of chans using LynxChan Leftist theme. User owned boards. Shitposting theme. User owned boards. User owned boards.
Let me know if there is any site I forgot to include.

R: 0 / I: 0 / P: 1
Locked Pinned Bumplocked

R: 0 / I: 0 / P: 1

LynxChan 1.9 is about to enter beta and introduces a very important feature: JIT caching.

JIT caching is caching pages once they are requested, instead of caching when their content is changed.

This feature should allow for not only a significant reduced CPU usage but also for a more responsive experience for users.

Other from that, this version will also add a few features:
File search on media management
Maintenance images
Ability to restart the unix socket from a GUI
Subject editing
Board locking
Better global board moderation
SSL can be made mandatory
Mass bans directly from ips
R: 0 / I: 0 / P: 1

No, the software known as "LynxChan" does not work.

It is objectively bad not because it was made by a Brazilian, but because it was written in Node.js

I have been the Administrator and Owner of "32Chan" for a year now, and I have only used "LynxChan" as the main software. I can guarantee you that it does not work.

It is garbage to be quite honest with you. The file names are an eyesore and you cant forget that it's written in Node.js, one of the worst languages to use when writing image board software unlike PHP.
R: 0 / I: 0 / P: 1

Since I can't reply to the locked pinned thread about chans whom use lynxchan, I'll create this thread to inform you that ( uses lynxchan.

R: 3 / I: 0 / P: 1

Just dropping some front-end / back-end feature suggestions I'd love to see.

Reports should be easily accessible by janitors, moderators, and administrators. Why not have a JavaScript widget similar to 4chan's thread watcher? It allows for janitors, moderators, etc to quickly and easily address reports inline.

Ban requests: On large-scale imageboards, where we can hope LynxChan to be eventually destroyed, you'll eventually need to hire janitors that you can't really trust. For this, I propose a ban requesting system that janitors can use to request for a user to be banned based on a post that they made. This BR would be sent over to the moderators and displayed in-line in the widget.

Viewing reports: Allocate reports to a catalog
Reports could be displayed in a catalog. Many imageboard users are used to using a catalog interface to view posts, so putting reports in a catalog would make the moderation experience more comfortable for new moderators.

Archive: In-line archive that expires after a set period of time. Like 4chan's internal archives.

Restorable deletes: Don't trust janitors to permanently delete content; hide it from the users and only allow the moderators to permanently delete them. Prevents abuse by untrusted rogue janitors. Perhaps make this a configurable option, so for example a role of root could only permanently delete content.

Live-posting: Like meguca, odilitime has already started working on this with his project called megud.

I took these ideas out of multiple imageboard softwares that exist, hopefully they will all eventually exist in a single imageboard software.

Do you plan to eventually write a featurefull, stable, good-for-public-use frontend? I like a lot of the front-ends out there, but none of them are comparable to 4chan's, vichan's (and forks), Infinity Next's etc. I love the engine, and I've been keeping a close eye on it!

R: 1 / I: 0 / P: 1

I'm currently using lainchan but was wondering if lynx is worth using it. Would It be an easy migration if I choose to? Have you ever used a tinyboard fork before and switch to lynx? Is it worth it?
R: 3 / I: 0 / P: 1

Feature Suggestion: Something similar to vichan's filtering system
In vichan, you could do something like this to globally block a known spammer.
// $config['filters'][] = array(
// 'condition' => array(
// 'name' => '/^surgeon$/',
// 'body' => '/regards,\s+(the )?surgeon$/i',
// 'OP' => false
// ),
// 'action' => 'ban',
// 'add_note' => true,
// 'expires' => 60 * 60 * 3, // 3 hours
// 'reason' => 'Go away, spammer.'
// );

Having a feature like this for lynxchan would be extremely helpful for banning/blocking spambots. Do you think you could implement something like this for lynxchan?
R: 0 / I: 0 / P: 1

There's a problem with your CSS making the border around a posts, that is shown by hovering over any linked post, uneditable.
R: 1 / I: 0 / P: 1

what file would i need to edit so that IPs are deleted after a post or a few moments after a post?

R: 2 / I: 0 / P: 2

Any reason for banning >>>/pol/264? That was a very /pol/ related thread and Zionist memes are a real thing. I say the ban was uncalled for and the topic should be allowed. Endchan got over 200 posts on the topic, all with fruitful discussion about memes, their purposes, and agents used to create them or spam them (like outing Ben Garrison as a Zionist shill).
R: 1 / I: 0 / P: 2

Anonymous:~/Lynxchan/src/be$ ./boot.js --debug-fe
throw error;

SyntaxError: Unexpected string in JSON at position 43
at Object.parse (native)
at loadGeneralSettings (/home/anonymous/Lynxchan/src/be/settingsHandler.js:418:28)
at Object.exports.loadSettings (/home/anonymous/Lynxchan/src/be/settingsHandler.js:465:3)
at Object.<anonymous> (/home/anonymous/Lynxchan/src/be/kernel.js:553:17)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)

I get this error when I try editing src/be/general.json. Happens anytime I try to configure anything from the readme. What am I doing wrong?

R: 2 / I: 0 / P: 2

Bumplocking NOW
Hey Lynx. When the fuck you gonna add bumplocking? Srsly. Thx

R: 20 / I: 8 / P: 2

LynxChan 1.7
For a while, the mod tools have been rightfully criticized on LynxChan. I have always put mods behind users and admins and it showed.

But now with 1.7 I looked into changing that. This version brings several improvements to moderation:

Better report queue
Now reports display the reported content, removing the need for mods to open the page to see what has been reported. But in some cases they won't even have to open the page, because now you have the option to automatically delete the reported content when you close it's report.
Along with that, two other lesser changes were made to the report queue; the link to visualize the post takes you to the moderation page and you can close multiple reports at once.
Reports are deleted when their reported content is deleted, removing cluster.

More moderation tools
Deletion by IP have been implement for board staff too, so they are able to deal with spam better without relying on the global staff.
Narrow range ips have been implemented, allowing for range bans to use 3/4 of the ip instead of 1/2, giving moderation more control over range bans.

Moderation quality of life
To make bans easier, now ban duration defaults to 5 years and global staff are not required to use the captcha for applying bans anymore.
Integration with the database filters a good portion of spam before it is even posted.
Bans no longer require an explicit expiration date, now you indicate a duration in days, months, days, hours and minutes, using any combination of units.

But not only moderation tools have been improved. A number of details have been changed for users too:
Links to download files with their original name now use the "download" property of the link tag, allowing them to just click on the link to download it and save bandwidth if they had already opened the file.
Extensions have been re-introduced to files.
Deletion now tells the user how many threads and posts have been deleted instead of just giving back a success message.
Ids have their background colored.
New threads only give a response after their page have been created, eliminating the 404 after creating a thread.
Added a thread creation form to the catalog.
TOR posting settings have been changed, allowing site admins to require only TOR users to use the block bypass while allowing them to post files.

And some general improvements were made to site administration features:
Added a setting that control the maximum length of posted messages.
Board owners can turn their boards into textboards.
Now its possible to tell the engine to use ffmpeg to generate gif thumbnails for improved performance at the cost of quality.
Flags now have a class added to it when they are location flags, allowing custom board css to make specific changes to specific location flags.
Added a feature that allows to configure how long ips are stored on the posts.
HTML generation optimized with individual HTML caches.
Captchas no longer require a temporary file written to disk.
Temporary directory is now created automatically if possible.

This update will enter beta on October first and will be released 45 days later.

R: 3 / I: 0 / P: 2

Stephan can you add my site :)

R: 16 / I: 10 / P: 2

More testing
Same captcha countdown timer mismatch here?

R: 1 / I: 0 / P: 2

Hey Lynx man, Is there anyway to transfer a vichan/tinyboard imageboard over to your Lynxchan engine?
R: 0 / I: 0 / P: 2


R: 0 / I: 0 / P: 2

No cookie captcha
no cookie captcha

R: 13 / I: 18 / P: 2

message is mandatory
R: 7 / I: 0 / P: 3

Where can I submit feature requests?

R: 8 / I: 3 / P: 3

LynxChan 1.8
LynxChan 1.8 main addition is multi-lingual support.
This feature allows site owners to specify alternative language packs and front-ends and associate languages to them.
When an user visits the site, the engine seamlessly picks an available language from the user and serves content in that language.

This version brings some other minor features so far:
-More granular and specific verbose modes.
-A terminal command to perform a clean shutdown of the engine.
-A board setting that allows for a maximum age that threads are allowed to be bumped.
-Improved spammer and TOR ips storage.

This version will be released 03/17.

R: 2 / I: 0 / P: 3

LynxChan Installation Tutorial
This is for debian.

Pre-install: Make sure you've created a user account with sudo rights, and use it for the rest of the tutorial. Do not run lynxchan on the root account.

1. Install nodejs

curl -sL | sudo -E bash -
sudo apt-get install -y nodejs
sudo apt-get install -y build-essential

2. Install Mongodb
sudo apt-key adv --keyserver hkp:// --recv EA312927
echo "deb wheezy/mongodb-org/3.2 main" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.2.list
sudo apt-get update
sudo apt-get install -y mongodb-org

3. Install imagemagick
sudo apt-get install imagemagick

4. Install ffmpeg
sudo echo deb testing main non-free \
sudo apt-get update
sudo apt-get install deb-multimedia-keyring
sudo apt-get update
sudo apt-get install ffmpeg

5. Clone lynxchan into your home folder
sudo apt-get install git
git clone

6. set up lynxchan
cd LynxChan/aux
Continue through it, I recommend installing the default front-end at first.

7. run the root setup so 'lynxchan' becomes a command
sudo ./

8. run lynxchan for the first time


ctrl c to close it

Part 2: Setting up a different front-end
You can either edit the current fe or get another one. Check out the list here.

1. Find the fe that you want
cd LynxChan/src
git clone 'the one you want'

2. Create the root account
lynxchan -ca -l login -p pass -gr 0
where login and pass are the login and password of your choice

3. run lynxchan

4. Head into your account. The default port is 8080
so localhost:8080 or ipaddress:8080 in your web browser

login with your newly created root account

5. head into localhost:8080/globalSettings.html
change a bunch of settings, but mostly change the fe to the folder of the desired fe.
example, if you cloned freechMinimalism, change the 'fe' part to 'freechMinimalism'

6. Save, the stop the engine and rebuild
lynxchan -r

Running lynxchan through nginx reverse web proxy

1. install nginx
sudo apt-get install nginx

2. remove apache2/stop apache2
to remove:
sudo service apache2 stop
sudo apt-get remove apache2
sudo apt-get autoremove

to stop:
sudo service apache2 stop

3. change the conf files for nginx
cd /etc/nginx/sites-a*

paste this
server {
listen 80;
server_name localhost;

location / {
proxy_pass http://localhost:8080;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-For $remote_addr;

link it

ln -s /etc/nginx/sites-available/ /etc/nginx/sites-available/

delet the old config
cd /etc/nginx/sites-e*
rm -Rf default

start lynxchan as a service, then start nginx
sudo service nginx start
sudo service lynxchan start

access it from your web browser


Tell me if you want a tutorial for nginx, it's simple though just google it

R: 4 / I: 1 / P: 3

So I know nothing about CSS, where can I find a board template? I have something in mind for my board on 32chan but I have no idea how to do it and no idea how to learn

R: 2 / I: 0 / P: 3

>Lynxchan only being used on a bunch of ghost town chans.
>Next not even used on a site that's up.

Both you and Josh failed lmao, go join Parley in dead corner.

R: 9 / I: 8 / P: 3

filename thread

R: 0 / I: 0 / P: 3

Heads up: 1.7.1 released.
It fixes a bug where when using board ip deletion it wouldn't pick the post ip, but the thread containing the post every single time.

So I decided to make it public here, since it could be a little destructive.
R: 1 / I: 0 / P: 3

hey Lynx how do I get LynxChan to run on port 80 instead of 8080?
R: 1 / I: 1 / P: 3

R: 2 / I: 0 / P: 3

Does LynxChan support Youtube embeding?
>> Sérgio


Vichan has this feature, and I'm planning to install LynxChan soon.

R: 24 / I: 7 / P: 4

A couple years ago, I used to use a certain chan. It was the single biggest western chan at the time. And while I knew it wasn't perfect, I thought it was a place outside the corporate control of narrative. A place where bullshit was exposed, not propagated. Then one day, I found an article with some credibility about corruption on the media. I looked at the board's catalog, found nothing about said subject and created a thread linking the article. This board had a history of deep mistrust on the media and the people that usually reported on said media, so I thought other people would appreciate this piece of information. Instead I was immediately banned for 3 months.
At that point, I realized the tentacles of the people controlling narrative on the media could reach way, way further than I thought. I realized that when it comes to information exchange, society as a whole cannot afford to put all of it's eggs on a single basket. Because no matter what kind of basket it is, the people out there to control what people talk and think will always be able to find some way to control which eggs stay on the basket and which ones are buried and forgotten as if they never existed.
I stopped using that chan completely and started to diversify the chans I used. One of them managed to take many of other people moving away from the chan that banned me and at some point, the software it used could not cope with the stress it was being put under. That caused the owner of this new chan to look for alternatives and after looking at the existing software, I thought to myself "I can do better". I knew I could do something faster, easier to manage, more secure, more flexible. Something that would make everything else obsolete and take away this technical hurdle from people willing to run chans.
And so, LynxChan was born. And in just one year, with the help of talented and dedicated people on all areas, it managed to rise higher than I could ever ask for. Now people willing to run chans are not tied to archaic, crippled and unmaintained technology. Now they have something that can serve for any style of chan they want to have, that will handle any amount of work and that can be deployed without issues on a matter of minutes and can be customized in any way. All without sacrificing features.
This represents a huge addition to the chan ecosystem, one of the last shelters of free speech on an increasingly controlled and censored internet. If this ecosystem is to survive, its crucial it evolves and adapts to new scenarios and standards. There is a long road ahead but I am certain this project will become more successful as time goes on. I'd like to thank everyone that not only put their time and energy into helping development, but also people that trusted the software into their servers.

On a different topic, I am dropping support for versions 1.1 through 1.4. I know this is not the ideal way to do it, without a reasonable time window, but I feel 1.5 is the oldest relevant version by now and I really don't feel like maintaining the older ones. They will be moved to a legacy repository.
About future plans, I am thinking of focusing on usability for a while. I know that moderation tools are sub-par on this area. 1.6 implemented probably the last big feature overhaul, so there isn't much left to be done besides this kind of polish.
R: 1 / I: 0 / P: 4


why don't you take over freech?

R: 1 / I: 0 / P: 4

This anon gets it.
R: 0 / I: 0 / P: 4

Feature requests
Stephen, please add a news page. They're very useful.

R: 6 / I: 1 / P: 4

1.6 is pretty much feature complete, so I figured I would go and make the usual thread with the new version highlights:

File deduplication and upload skipping
Now captcha can be required for only new threads but not replies
Implemented SFW boards and SFW overboard
Board staff can't see ip ranges as clear text anymore
Inactive accounts can have their boards marked as inactive
Maximum amount of allowed files is displayed on pages
Improved front-end development tools

It shouldn't take too long until the next beta, so stay tuned.

R: 40 / I: 5 / P: 4

1.5 beta has started.

Main changes:
Custom CSS applies to catalogs
Sharding allows to several servers to coordinate to run a single site
Rebuild messages not only have different priorities, but some block the queue until completed
Addons can specify broad versions to be compatible with
No more sub-domains for the api and static files
Now volunteers for boards have shortcut for them on the account page
Message limit increased to 4096 characters
Errors when processing files don't keep other files from not being processed
Location flags integrated and can be activated by board owners
Board volunteers are allowed to change board settings
Alternative spoiler markdown using asterisks
Auto-saged(bumplocked) threads now have an indicator
Board owners can set lower limits for some global settings to their boards
Multiple board sorting options
Added a terminal command to reload front-end files without restarting the server
Some global stats can be displayed on the front-page
Added daily graphs with global PPH
RSS feed of boards have all the threads now

At 30/1 I will release the first RC, 2 weeks later I will release it as a stable version.

R: 1 / I: 1 / P: 4

Test post
Can this run on an iis server?
R: 5 / I: 0 / P: 4

If anyone had issues posting in the past couple hours, it was because I got a front-end file with the wrong domain after I deployed the fix to the catalogs css.

R: 6 / I: 0 / P: 4

bug report
i dont know if this is proper place for it but i want to report a bug:

Im on normie phone with android and longer replies are not wrapping properly.

R: 2 / I: 2 / P: 4

I wish you success.
R: 0 / I: 0 / P: 5

Just a heads up, my datacenter is shitting itself, so any connectivity issue, its because of that.

You can follow the issue here:
I use the dallas one.

R: 0 / I: 0 / P: 5

8chan-like front end
The demo is usually up at

R: 14 / I: 2 / P: 5

Daily reminder that LynxChan will never power 8chan

02:10:17 -!- StephenLynx [] has quit [Quit: Leaving]
04:06:35 < copypaste> JEWS: just give up on Lynx
04:06:40 < copypaste> he's autistic to a fault
04:06:51 < copypaste> can't even keep his IRC client connected so I can talk about him behind his back
04:06:53 < copypaste> lmao

R: 10 / I: 1 / P: 5

I have scheduled both the beta and release of 1.4.0, as you can see on trello.

1.4.0 main changes:
Multi-board optimization
RSS feeds
Case-insensitive filters
Removed account locking feature
Upgraded password hashing to pbkdf2
Upgraded authentication token security
Added latest images to front-page
Post previews hold images and are updated

R: 1 / I: 2 / P: 5
Locked Bumplocked
>no multi image upload


R: 6 / I: 1 / P: 5

Repositories migration
I have moved all repositories to because gitlab became too fucking slow.
The old ones won't be deleted, but they won't receive updates either.
So remember to point any repository you have to the respective one at

To update it, just go to the repository, enter the .git directory and edit the file config, replacing the URL to gitlab to the one to gitgud.

R: 1 / I: 0 / P: 5

If anyone noticed some instability, I was testing some shit, turning the server on and off.
Now it should be normalized.

R: 4 / I: 2 / P: 5

>Id: 565f7041dcdba3747566ef85
>Reason: Auto ban
>Expiration: 12/02/2020 (Wed) 22:27:13
>Applied by: Auto ban add-on

How do you like them apples?
R: 5 / I: 0 / P: 5

>no https
do i just let windows 10 h4x0r5 steal my rarest pepes in transit?

R: 1 / I: 0 / P: 5

>LynxChan uses Node.js as a runtime environment
So what are your views on the recent eggplant crisis?