I would recommend that the developers of Kokonotsuba edit its readme and advertise its features a little better. This board software seems to be fast, featureful, and up to date. Yet to my knowledge, Heyuri is the only website that uses it? Let's change that and promote Kokonotsuba.

Aside from making the github repo more appealing, let's make embassy threads on other western boards, encouraging them to migrate, and let's make it easy to convert vichan boards to kokonotsuba.

One way to start would be making a comparison chart of all of Vichan and Kokonotsubas features and seeing what each software has that the other doesn't.

After we prim up the repo and make this comparison chart, I can help make introductory threads on several western boards. ヽ(´ー｀)ノ

Let's brainstorm some features to consider. We'll try to leave out obvious ones like "ban feature" as that's expected.

Open to critique, this is just off the top of my head.

I'm not super familiar with vichan so I don't know the full extent of its features but I think the only things we're missing as of writing that are worth mentioning are: reply-moving/thread-merging, a web ui for editing configs (basically complete but not live on heyuri yet), and a report system (half complete on a different branch).

the readme and other documentation could definitely use some updating...

>After we prim up the repo and make this comparison chart, I can help make introductory threads on several western boards. ヽ(´ー｀)ノ
sounds liek a plan! I'll finish up the config editor and reports, plus some other stuff I've been sitting on.

Can't give an ETA right at this moment but it's definitely on The List. The current goal would be a stable release we don't have to refactor, the config editor is the last 'big' refactor I can think of, past that point I think it'll be ready for a stable release

>>188469
Its a good list, u've got most of them.

some others worth mentioning -

Moderation category: Anti-Spam System as something like "Spam rule webpanel", Thread CSS editor AKA CSSHax (via the cssHax module), post editing, post note system (highly useful!!! and i don't think any other board software has this feature AFAIK)

Admin category: ad management webpanel, capcode management ui, performance graphs (requires excimer to be installed)

Misc: Full banner submission system along with mod tools to manage them

I see search down the bottom, I think vichan's search system has more-or-less the same capabilities as koko's, but vichan's search UI sucks. i designed ours to be like the search systems that some 4chan archives have

as for a migration system there is some retired code from when gurochan/kereste were getting converted, which can be resurrected when we're ready.

If there's anything else you wanna mention let me know and i'll get around to it

Hello

I'm a biased source, but I've worked as mod/admin with those softwares in the past and I genuinely think kokonotsuba is better than all those listed (especially for bigger boards like GUROchan, in terms of speed), at least from the administration standpoint.

Kokonotsuba's home page is https://kokonotsuba.github.io/ which is meant to serve the full purpose of readme, including listing features and a better set up guide (and a devchat that can act as a support channel).

>>188469
it's not enabled on heyuri, but we have youtube embedding for a past board that migrated from vichan, here is demonstration:
https://kere.st/dev/koko.php?res=831
kokonotsuba has been in works since 2020, but it wasn't publicly used until 2021 outside testing instances

...
now, small caveats of kokonotsuba may include:
- Upgrading sometimes involves running SQL commands. It's very simple, just requires checking the "upgrade" page in koko's homepage before pulling changes.
- there isn't a captcha system. I believe it's a pain in the butt for the user for such a small benefit to administration, and starting to make gradually less sense with AI.
- likewise we don't yet have a report feature. It's not really needed for boards that don't receive thousands of posts, but it's planned to be implemented soon for the sake of koko not lacking the feature.

...for small boards, we have anti flood settings and a way to have staff on PC immediately be aware of new threads (pictured - it's a thread watcher feature that any user can enable from [settings] too, and allow the website to send notifications if they desire)

Thanks for being willing to spread the word of Kokonotsuba. I'm willing to help where I can

Kuso, I accidentally went back in my browser and lost my long reply... add this to the list!!1

Anyway, the (abbreviated) reasons I think kokonotsuba hasn't seen wider adoption are:

1. Hardly anyone knows about it
2. Not n00b-friendly to install and configure (compared to others)
3. Not 4chan/8chan-in-a-box - it misses many features, bells, and whistles that are expected on those types of systems, and that's what most new imageboard admins want
4. No proper release structure or easy upgrade method

That's not to say it necessarily should do all these things, just that this is why it's not the go-to imageboard software despite all it's pros

>>188475
>3. Not 4chan/8chan-in-a-box - it misses many features, bells, and whistles that are expected on those types of systems, and that's what most new imageboard admins want
it does

I'm trying to list features objectively. I guess I'll add "user created boards" to the list although thats a "no" in both fields

>>188477
(meant to have a question mark on "it does")

(also allow users to edit posts..)

>I'm trying to list features objectively. I guess I'll add "user created boards" to the list although thats a "no" in both fields
I listed moar in my original reply b4 I lost it...

- User board creation/management/moderation
- Built-in dynamic front page (with recently active threads across multiple boards)
- GUI for creating rules page (global & per-board), FAQ, etc.
- Dynamic board listing with PPH/PPD, active IPs, board tags, etc.
- Dynamic board navbar (showing all listed boards, showing most active boards, etc.)
- Report system

and so on

i'd like to add a field for measuring speed and responsiveness, but not sure how to measure that objectively. Maybe setting up each software and just taking measurements on the same server

>1. Hardly anyone knows about it
to my understanding, that's the reason list is being made ^^;

>2. Not n00b-friendly to install and configure (compared to others)
I disagree, it only requires surface level familiarity with cli to install. PHP itself is easy to install (compared to nodejs). It loses installment easiness to vichan because requires a non-web accessible backend... but this is intended for certain flexibility (eg having boards on img.heyuri and dis.heyuri being connected to same "main part").
I'd say configuring is the same level of hardness, though kokonotsuba requires careful updating that admins would want to check https://github.com/Heyuri/kokonotsuba/commits/main/global themselves to see changes made to "global/" folder. The way configurations work is being modified right now, so this may be immediate subject to change though

>3. Not 4chan/8chan-in-a-box - it misses many features, bells, and whistles that are expected on those types of systems, and that's what most new imageboard admins want
it doesn't have features of 8chan (user curated boards), maybe that's something to note.. I eventually want koko to have OPs being able to moderate their threads, for similar effect of smaller scale

>4. No proper release structure or easy upgrade method
It's currently a rolling release software to save us from additional work of documenting releases.
I'll admit upgrading it isn't very easy (aforementioned cli/reading code requirement), but I'd debate if other alternatives are very easy either

>I'd say configuring is the same level of hardness
I don't think it's even close to certain others, where it can all be done from the browser with a proper UI instead farting around with multiple plaintext config files that are hard to make any sense of. I know hachi is working on this area, but I'm talking about the present

Install is not easier than certain others either, since u have to do a lot of it manually rather than "run this one script and everything magically installs and launches itself"

Current Status of the spreadsheet

I left out a handful of the features the anonymous mod mentioned because they aren't present on base vichan either. Added headnotes for clarity

Also, an idea I had:

Have 2 repositories, stable and unstable. The unstable repo would be used the same way the current singular one is. Constantly updated without attention paid to changelogging or version compatibility.

A second, stable repo where releases are numbered, update instructions are laid out clearly, and changelogs list additions and deletions.

The stable repo could also consider removing some of Heyuri's cultural footprint on the software to make it more generalized for a wider audience. Many board admins could view the default inclusion of heyuri fortunes, emotes, etc as them using HEYURI's software rather than using kokonotsuba. This is disadvantageous. I do not support removing credits to heyuri however

>>188481
here's some performance graphs I took just now for kokonotsuba

this one is for rebuilding 10 static pages on a massive board

replying to a thread on a massive board

deleting a reply

deleting a thread (slower since it rebuilds all static pages)

>Have 2 repositories, stable and unstable. The unstable repo would be used the same way the current singular one is. Constantly updated without attention paid to changelogging or version compatibility.
We are currently in middle of some things in development so immediately creating a stable version doesn't make sense at the moment - but eventually, we can maybe distribute kokonotsuba in a zip file on github.io homepage.
Those who benefit from the repo being on github are those who are familiar with using git, who are already likely advanced enough to deal with a rolling release software.

>The stable repo could also consider removing some of Heyuri's cultural footprint on the software to make it more generalized for a wider audience. Many board admins could view the default inclusion of heyuri fortunes, emotes, etc as them using HEYURI's software rather than using kokonotsuba. This is disadvantageous
That's fair. Currently it's just a few things in static/ that has Heyuri print and could be changed. We mostly didn't have alternatives for certain stuff, but if Kokonotsuba itself had some personality (like a mascot or icon), it could have Kokonotsuba-default fullbanners. I think 300x100 banners already have a boring placeholder, we can just go with stuff like that too.

>I do not support removing credits to heyuri however
There already isn't a lot of credit to heyuri besides hijacks in source codes of js files
The credit goes to kokonotsuba's home page, and Heyuri is mentioned there.

>I left out a handful of the features the anonymous mod mentioned because they aren't present on base vichan either.
Some n00bmins do still adopt base vichan, but I also commonly see:

- modified vichan forks (such as 8chan's infinity)
- jschan (8chan-like)
- Lynxchan and derivatives (8chan-like)
- TinyIB
- futaba/futallaby/wakaba/kareha on sites that last about 5 minutes

I think a feature comparison chart should include these as well

>here's some performance graphs I took just now for kokonotsuba
It'd be interesting to see the same graphs for other imageboard software, just for comparison

for context the performance graphs are taken from an instance running an old version of gurochan's db.

so any tests on other software will need to be on something similarly sized, my one is 344MB (231599 posts) but the size will vary depending on the software

i can tell everyone right now though that without taking graphs and stuff from vichan, gurochan when it was using vichan would freeze and throw server errors just trying to delete posts - clearing cp spam took like 5 minutes XD