Futaba
http://www.2chan.net/script/
Futallaby (up to 040103)
http://www.1chan.net/futallaby/
Wakaba
http://wakaba.c3.cx/
moeren
http://moepic.dip.jp/gazo/script/index.php
siokara
(seems to be still in heavy development.
couldn't find a link to an available
version of the script)
http://siokara.ath.cx
Swetnote
(couldn't find a link to an available
version to the script, it's probably
only for people who register or
perhaps even a pay-product?)
http://www.sweetnote.com/
I'm now doing a barrel roll, it'll take me up Cudder's butt.
It's like playing a game of "carve your own pathway..."
Some updates.
Most of the untranslated strings have been translated now. Those that haven't were either overlooked or are intentional. There is still some Shift_JIS characters in the script but those in turn were intentional also.
The postbox is now automatically toggled on, you can still unextend/re-extend it, but what counts is that javascript doesn't need to be enabled to post anymore.
I'm currently working on overhauling the style scheme for the usual futaba layout scheme because it looks better (hopefully in other's opinions as well) in comparison. I'll probably still release the other skin, but probably not included within the script compressed archives, maybe as modifications or some crap, I don't know.
I got shafted by another host, for no reason, again.
The webserver redirects to full page ads for shit like golden casino, I'll start looking for hosting later.
Yay, a friend of mine is hosting me for the time being.
I also finished 3.0, the demo board (showcasing only some of the new features) is over here at: http://dataloss.we-is-experts.com/board/
For the changelog/feature list for 3.0, check out the readme at http://dataloss.we-is-experts.com/board/readme.txt, I'd take the time to highlight things here on this board but I'm exhausted and sick, so I would like to get to bed right about now.
Enjoy, pick apart, make suggestions, etc.
Also before you ask, the script is available in two compressed archive formats on the front page (I shamelessly stole the style from desuchan ;)
And yeah, IPM is me. What the acronym actually expands to is beyond retarded, but I use it because others recognize me by it.
Res page caches added, broken admin panel deprecated, bans now managable by external textfiles, noko, secure tripcodes, admin/mod capcodes, reflink parsing, etc.
A bunch of the crap I've added (or in the case of the admin panel taken out).
This means, yes, it installs more like wakaba now, and yes, I got rid of the stupid board creation function.
Your fortune: Reply hazy, try again
>This means, yes, it installs more like wakaba now
Or futaba, whichever comparison you'd like to make.
Yay!
How are you supposed to view people's IP's in order to ban them? The admin panel showed the IP/host so that problem posters could be banned...
I made a script for editing text files, like the ban files, but without a way to view IP's, it's sorta pointless to even have an IP ban file...
Screw it, I'll just add a checkbox and let the admin/mod pass ban people. Liked "your" script better when it didn't just look like Futaba, though.
another imageboard script...more info there, feedback welcome.
...uh....
Do you not see the big "Manage" link on top of every board? That's the management panel, in which there are two radio buttons, "Management Panel" and "Manager Post."
The former radio button takes you to a menu for deleting posts, in that menu the host of each poster is listed. Just grab the host from there and plop it in the external datafile for host/IP bans, it's not exactly that hard.
>The admin panel showed the IP/host so that problem posters could be banned...
Uh...that's the management panel. For a while there was a shii-chan like admin panel in this script that I deprecated with this release because most of the features it included were bloat and half of them were broken.
>Liked "your" script better when it didn't just look like Futaba, though.
I really can't tell what you're trying to get at here, but I'll try.
If you're referring to the past look of the script, than that's just personal preference and really, I'm sure most people liked the original futaba look better,
If it's features you're talking about, and you think I just renamed a translated futaba and released it...um, you obviously haven't looked at it at all, because there's a metric fuckton of crap I hacked in.
Res page caches (static html of individual threads)? Post highlighting/quoting/reflink parsing? Secure tripcodes? Noko? Javascript to remember the name and e-mail fields (surprisingly not ganked from wakaba!)? Admin/moderator capcodes? Bans manageable via external datafiles? Ommited image count along with ommited post count? Not having to tick a checkbox that says "lol omg i'm not posting an image" if you want to post an imageless thread? etc.
tl;dr: SERIOUS BUSINESS
Yeah, I'm not stupid, I was 95% asleep. I figgered it out once I did a test install. Sorry for provoking you to incredulity, but admit it, you've been asleep while looking at scripts before too.
May I suggest one little teeny-tiny feature? And a rather Big one too?
If you could do these two things, you'd rock.
>>134 Case in point in favor of an edit option for a board. I meant to say, "Poti Board is the best Futaba-based PHP board script with an oekaki option", because it's nowhere near as good as Wakaba, though Wakaba requires MySQL.
While looking? Hell, I've been asleep while coding...
It's no problem, I just haven't been having the greatest of days today (cleaning up a flooded basement with a wetvac is not my idea of fun...fuck you Illinois weather).
>Implement Poti Board's edit feature. People can redo their post instead of deleting it if they make a simple mistake in their post. This is something I consider a genuinely useful feature, as it can save a lot of time and messiness on a board.
An edit function, eh? Shouldn't be too hard to implement. It'll most likely resemble potiboard's function rather than desuchan's though, since there is such a thing as too much javascript. ;_;
>Rig up an oekaki module for it. Poti Board is the best Futaba-based board script with an oekaki option, but there's a lot of files, it's all in Japanese, and a lot of the config stuff just plain blows. If you could do this with your current version it'd put it way above the rest of the Futaba-based php scripts out there, and I'd be able to replace my Poti Board with your script, and appreciate your efforts forever.
Hmm, again this shouldn't be too hard to edit in. I'll probably throw it in as a function in suigintou.php by default and let the user decide whether or not to turn it on in the config (0 = no, 1 = yes...).
I'd most likely just use ShiPainter for the applet, is that okay?
With more than one page, suigintou 404's on clicking "next".
>>138
That'd work just fine, I don't like PaintBBS anyway. ShiPainter is the only applet I use for oekaki drawing.
Fixed. Redownload suigintou, and if you have existing boards copy the new suigintou.php and replace the old one with it, then update the board's caches (in the management panel) and the other pages should render.
Now I'll work on your other suggestions.
Smashingly awesome, and I look forward to seeing what else you can do with that old cow. Thanks, Makoto!
That's pretty cool, but it isn't enough to make me want to use Kusaba... XD
>145 Please, please, pleeeeease, keep it a single-board script. I'd hate to see it get as overused as KusaTrevor, those sites are tumors on the ass of the internet.
This is probably the best new image board script since Wakaba, no lie. I love the way Youtube videos are implemented, and a lot of other stuff about it. If you release the code before I die from exposure to the internets, I'm installing Python on my server, just so I can have a copy of this running.
http://404chan.net/test/
Thought you guys might be interested. Nothing special really.
i dunno. if i dont build in multi board support then running more than one board would require one process per board (~30mb mem) or running via plain cgi which would be slow (although possibly fast enough with caching and a slow board).
it is tempting though, for one thing it makes the code much cleaner and it would discourage people from making loads of unused boards.
The post form is kind of a mess. Too many things going on in there. Also, the part with the checkboxes breaks horribly if the browser window is narrow. Typing things into the normal textboxes may be unintuitive to new users, but it also doesn't overwhelm them with mysterious options they don't understand.
Also, forking seems like the kind of thing that just adds complexity and confusion. One of the key features of this kind of board is the simplicity. You don't need to have an automated option for everything, if you can do it by hand just as easily. Like forking, people could just say "Hey I am starting a new thread on the topic brought up in post so-and-so", and that will be much easier to understand for everyone involved.
With a lack of complex features, people use natural language to describe what they are trying to do instead, and that tends to make things easier for everyone involved.
i agree the post form is messy/dont look quite right... its a sort of jumble instead of a neat little stack atm.
not sure what you mean about the browser width thing..
im not likely to do 2ch/futaba style tripcodes or sage/noko in the email field - i can see what you mean about making input simpler for new users but i always found these things to be unintuitive. there is a sort of cuteness appeal there, but it just doesnt that much sense - what if you want to give an email (on a few boards i have actually seen people using the email field for that lol) but also want to sage or noko, or what if you want to sage and noko (i have wanted to before). the whole "sage as an attack against the op" thing is kindoff depressing to.
about forking...well you may be right, but i want to try it out. it is configurable anyway.
thanks for the input, i do appreciate it.
Hmm, on another machine, the "Bump Thread" label wrapped all the way to the left, but it doesn't on this machine. Funny that.
I figured with all the changes I'm making to kusaba I might as well just be the one continuing development on the software.
So without further hesitation I am announcing that I am taking up development of kusaba.
I am working toward a kusaba 2.0 release.
I am also working on getting a sourceforge project for it.
But for now you can keep up to date on my progress and planed features through this thread:
http://www.operatorchan.org/sug/res/379.html
>>154
I'd suggest starting from scratch, you'd have to rewrite the entire thing to make any sort of improvement. The new features look promising though.
I've recently made alibi source code public.
I don't know how familiar any of you are with EleoChan but it's a not-extremely-popular imageboard that uses a tagging system instead of traditional boards. It's different in a lot of ways but the same in others. It was originally written in Ruby on Rails but I've ported it to a similar framework called Merb.
The port was actually more like a complete rewrite. As such it's only 80% complete. However, it runs, you can make posts and such, edit them, delete them, and what not. Some of the features are pretty nice if I do say so myself. There are missing features like an error messages for failed posts. I plan to keep working on it eventually but right now I'm busy a lot with school.
The reason for the release is to get my name out there, see if anyone else can add any features, and lastly because EleoChan is soon closing for a variety of reasons.
I'm going to guess that most of you are completely unfamiliar with Ruby, Rails, Merb, Git, GitHub, or the necessary things to get it running on your host (presumably a VPS) such as Mongrel or Phusion Passenger. In my own head, this is a good thing, to prevent a dozen sites on cheapass Dreamhost accounts popping up everywhere. Anyone smart enough to get it running is free to use it. If I had to give one a quick tutorial on how to get it running locally:
2a. There's probably some gems not listed in that that you'll have to install, you'll find out what they are when you try no. 3 and you get exceptions.
3. run the app locally with "merb" in the alibi directory and fool around with the app at localhost:4000
http://github.com/Eleo/alibi/tree/master HOPE YOU KNOW HOW TO USE GIT
This is the second time I've done this.
>>156
nice job on this, also glad to see someone else using git instead of clunky svn.
Well, problem being all the purists here seem to hate kusaba with a passion. That makes finding support a little harder for those who need it.
How the hell did you get F5 to work properly with kusaba? That's one of the problems everyone seems to have with it.
I made a google code project for kusaba 2.0
So, when are your improvements going to be released? I like what I see so far. I've managed to make the kusaba news script have the same appearance as 4chan's news script, and I've done the same with FAQ and Rules. I'm not much of a programmer but I have been having quite a measure of success with making the software a little more aesthetically pleasing. If I could help, let me know :D
>>162
Well I try to update the current source code at the google project within 2 days of a new feature being coded.
If you guys want I could fix a few thinks up and release a "current version so far" download.
Could I get a link to the imageboard where you have changed the look?
http://www.animeyo.net/kusaba/news.php
Currently scrounging webspace from a friend :P
I've left the top part where the logo should be blank, purely because I haven't had time to make one yet. One function that kusaba's news script needs is a limit to how many news posts are displayed, with the rest in an archive akin to 4chan's.
The rules and news page are actually stored in a text file somewhere on my other computer. FAQ and Rules look a little odd as another admin felt the need to try and mess with the CSS. Sideframe is also undergoing re-design whenever I find the time.
Disregard bottom paragraph, meant to say rules and faq page are stored in text files.
http://code.google.com/p/kusaba-2/downloads/list
current is now up.
I know there us already a thread for this but what the hey, this is for those are interested. the guy who made this has already upped the source code.
one of the mods from 24chan is coding for a new version of kusaba called Kusaba X.
Why the fuck are people trying to continue my script?
Seriously, I abandoned it for a reason. What the shit?
>>169
I'm loving you more and more with each post.
>>171
If you knew anything about his Kusaba script, you'd already know the answer: Just as shitty.
>>172
ÂiÂLÂEÂÃÂE`Âj
>>171
I uploaded the first public release today, http://code.google.com/p/pyib-standalone/ for anyone who is interested. Note that it's just for testing, as I've been busy with other things and haven't had the time to make it more user friendly for the maintainer or added any non-essential manage features. I'm having a hard time of drawing the line between kusaba's feature overflow and a lack of features.
>>173
I'm just curious, but what was your reason for discontinuing Kusaba?
Just sick of Php?
>>174
A lot of reasons. Being sick of PHP was one of the major ones.
Another major one was constant service to help the people who used kusaba to host a direct 4chan clone, who knew nothing about MySQL/PHP and barely could get the thing installed without my help, let alone maintain boards with it.
After a little experience with Python and a lot more with Haskell (which is my new favorite language) I just can't bear to write PHP any more without thinking "I could do this so much cleaner/easier in Python/Haskell".
>>175
Yeah the big thing keeping me stuck on Kusaba is the well designed management panel.
I worked in Wakaba for awhile, and Kusaba just... I don't know, it's easier to manage.
an imageboard in haskell..now that's the kind of insanity i can get behind
Looks like 7chan is working on yet another fork of Kusaba.
>>178
They're just using parts of Serissa.
I was disappointed by Kusaba and documentation / support available. I understand that is hart to run project alone. I can understand pre-release code, bugs, little to none support. Its OK.
I was pissed out when you abandoned project like a child. No word of explanation, no warning, nothing. You should keep domain, make statement on the front page and let it run for a year befor closure. Just to make clear what happpened, why you decide to quit.
I will not have high expectation with your new shinny python imageboard. I know that sooner or later you will fall in love to another language and this project will follow Kusaba fate. Good luck, and next time try to quit as mature person.
>>180
Trevor knew, as well as everyone else, that a 4chan-in-a-box was a terrible idea. Although that's not what it was meant for, it's what it had turned into. PyIB is looking fantastic, from what I've seen of it so far (as far as performance and code).
>>182
And how will PyIB be any different? It doesn't take a genius to figure out how to add separate boards, etc.
The only reason why people love Kusaba so much is because it makes everything 10x more efficient to manage.
progress on img2 slowly continues... disregarding the broken css, any thoughts on thread watching? http://img2.info - Watch a thread then mouseover the "Watched Threads" title at the top right.
Installed python + lib modules, just gave it a test run. Yay for not having to deal with DreamHost's process killer!
I like the idea of a multi-threaded imageboard script, but, sadly I doubt most chans generate enough traffic to utilize it properly. It certainly sounds nice for the process to spawn multiple threads so templating and database reads/other work can be done concurrently, but although execution time will improve, I'd be more worried about the system load from the extra threads, especially since there are multiple threads spawned for IO operations.
>Being sick of PHP was one of the major ones.
To be honest, ever since I started working on my futaba hack (if anybody cares there are links to it in this thread...somewhere), I've come to a bunch of points where I just wanted to scrap it and restart the project in a new language, mainly because of the fact that the PHP dev team shuns proper security practices and PHP's overall sloppy nature (not to mention futaba is fucking horrid code-wise, even for PHP), but because I'm a lazy fuck, that's probably never going to happen. :(
;_;
A friend of mine asked me to do it, originally, so I really didn't exactly "wan't" to do it. I figured I might as well distribute it for anybody else who wanted it, but, to be completely honest I've really lost interest in the entire project myself, considering futaba's horrible codebase, the limits to CSV flatfile logs and the slow performance of the original MySQL table structure (which I'm not going to spend my time to go back and reformat).
>>184
He's just going to give up on PyIB sometime down the line too.
>>190
I doubt it. FIOC is awesome and isn't something someone would just "give up" on.
ÂiÂLÂEÂÃÂE`Âj Kusaba needs to finish dying, please cease the necromancy!
You know, I haven't seen one valid argument as to why Kusaba is bad in this thread. The only thing I've seen people say is bad is PHP itself.
>>194
PEBKAC is the only thing there. Just because of the stupidity of the users is no reason to hate the software.
serissa.org is exactly like kusaba?
>>196
I don't think the people at Serissa have any idea what they are doing. I'm looking at their code, it's written shitty as hell.
>>197
All they're doing is making it worse and more ugly. They have no clue what they're doing.
However, serissa actually works. Craperatorchan hasn't actually made any additions that work.
>>204
Serissa would be better if they started removing all the bloating features Kusaba had, rather than adding more.
I have not made a release version of kusaba 2 yet.
If you want a preview release i could make one over the weekend.
dongs
>No, don't waste your time.
>>204
i wouldn't say it works when it got taken down by "hackers on steroids", maybe you should fix the obvious bugs before you add more useless features.
>>211
What obvious bugs exactly? Do you have a clue what you're talking about?
>>212
Why the fuck do you have a different ID from your other posts?
Hey what happened to Suigintou did you give up on the project?
I liked the idea that you were going to make a script that could be expanded and have features you want, rather than have the software force features down your throat like Kusaba and it's forks.
And the way it handled youtube videos in a pop-up window was a plus. Only problem was it wasn't user friendly. (people who can't read errors in Japanese)
The project still lives over here: http://dataloss.we-is-experts.com/
You may remember it from the old 1.0 days, when I was too lazy to convert the Shift_JIS encoded characters to UTF 8 and translate them. I still am too lazy to do that, which was why I switched the primary codebase to a pre-translated futaba, which sadly meant that some functions I wrote were not re-implemented, simply because of (again) laziness. I can probably hack in youtube embedding if you really want it, I guess.
However, to be completely honest, I wouldn't really advise using the current release. The code is still extremely sloppy and inefficient (it is based off Futaba after all), which is why I'm pretty much spending some time here and there to re-writing it, using a saner, more efficient and secure codebase (well...at least as close to one someone could get with PHP...).
If I finish it I'll archive the source and throw it out there, but there's no real guarantee that I can be bothered to. We'll see how it goes.
Takana has been released tonight.
Demo can be seen at http://10chan.net
Takana can be downloaded at http://10chan.net/takana_r7.zip
