Forum/board software?

Why has this field stagnated so much? All solutions I am finding are pretty old, mostly Php/MySQL and apparently a big security liability. And the one of new iteration like Vanilla forums are on the other hand mostly featureless and with a UX that doesn't particularly incite user activity. What the heck are communities running on these days?

vBulletin and Invision Power Boards

wakaba and kusaba

does it mean nikita is finally moving to his own forum?

>>2

vBulletin

Apparently this is truly the only option if you want a forum that doesn't suck. Ironically we can't go with it though. We are trying to build a place for a local free software community.

>>1
Why has this field stagnated so much?
Social networking.

>>5
IPB works too, but the modification community for vB is better in almost every way. I love how IPB is, its really neat and easy to navigate through things.

But my freedoms man... freedoms.

>>6
Social networking is thankfully dying, blogs are coming back.
Solution: collaborative blogs

and apparently a big security liability
Only if you don't audit the code first.

>>6

Also reddit

>>9

Tbh I wouldn't be keen to go over 1000s of LO<?PHP>C either.

>>10
reddit is a kind of forum

Seconding Wakaba/Kusaba.

It's 2013. Nobody wants to sign up for shit any more.

>>8
Social networking is thankfully dying
What the fuck makes you say that?

>>13

Social means narcissistic these days. Everybody focus onto itself instead into others.

>>13
http://dendory.net/blog.php?id=5116e01b
I misremembered the specifics (as in, it's actually just speculation), but there you go

>>14
Uh, what? If that means prettier Fagbook profiles, people will just stay longer and not abandon social networks.

>>15
2013 will see a shift from social networks back to blogs
Yeah, and this is the year of the Linux desktop and the year Lisp will finally achieve mainstream popularity.

>>16
But this time it actually has economical basis.

I always wondered. What goes in the making of a forum?

I imagine all revolves around the database design. Besides that and the basic logic of managing topics, threads and users is there anything else a non-initiated might mistakenly miss?

>>9
Oh, look, it's you again. Do tell us, how many software packages have you audited to make sure they possess no vulnerabilities.

>>19
None because the community does it for us. Examples include the community finding problems in Debian's bug in OpenSSL and Noscript working improperly.

smf, phpBB

>>20
If you don't do it yourself, then what do you know of auditing massive open source applications?

>>22
If I wanted to, I'd take the effort to do comprehensive systems documentation of a project. I routinely process different codebases to do abridged systems documentation for any codebase that doesn't have them, it's far too difficult to fix or extend any project without taking the time to document it.

If a project has a history of security issues and I decided to use it, then I would take the effort to document it more thoroughly. For any project that isn't so critical, I am happy just to let the community maintain it and rely on them to deal with any known security issues.

>>23
If I wanted to, I'd take the effort to do comprehensive systems documentation of a project.
That's very vague. Even if you are moderately thorough, it will  help you understand the project's architecture and would help finding very obvious backdoors, but what will it do to about the potential buffer overruns, DoS attack vectors, SQL injections, and all the sorts of issues for which you require actual fucking expertise in whatever it is you are auditing, as to know what to look for?

If a project has a history of security issues and I decided to use it, then I would take the effort to document it more thoroughly. For any project that isn't so critical, I am happy just to let the community maintain it and rely on them to deal with any known security issues.
Not all projects benefit from having the sort of expertise available that OpenSSL or the Linux kernel have. Working under that pretence is just deluding yourself. And face it, you just stated, implicitly, why is it that you don't audit the applications you use; it's too expensive. Nobody is in the position to audit their applications before using, either because of money, time frames or knowledge, framed in the other two.

And the fact that you say that after continuously chastising people for not wanting to use bug-riddled PHP shit, because it's open source and you can fix it yourself, is just hilarious.

All in all, I would give you an 8/10 for your trolling, if you weren't actually that stupid.

>>1
Woah, rewind. BBS Have been here for ages, and well developed and matured. Even to this day, you can find people in FidoNet, KOM BSS, WWIVnet, etc.. What killed off BBS was http, and is stupid ass backwards standard. When companies decided to market to ``web'' and give good money for it, people then created HTML like _BBS_, or what I call web forums. In the early days, lisp and perl were most famous languages uses to create the stupid web forums. There was little to no Databases in does days, most things were written in flat files. But when hard drives got cheaper over time, and things grew, then Databases were implemented. Still, the flat file versions were made, even at event new stuff was added. Then came PHP, the cancer that ails the IT world. Then you all those shitty broken ass web forums that you can break with any base function you use, since the scripts were executable by the public. That is the drastic change, allowing the public to execute scripts publicly, and give it information users should not be allowed to yield.

What happed to good old forms, authentication, approval, CPU time and bandwidth conscience. I know, the rich got cocky, and said to its users, Deal_with_it.

>>25
use wakaba, it's written in perl and is very robust and reliable

>>26
written in perl
very robust and reliable
Mutually exclusive.

>>1
Software age is like wine, so old isn't a bad thing, apart from that PHP makes things into shit beer.
>Things that let anybody post text files somewhere for others to read.
Not reinvented into exhaustion at all.

>>28
Software ages like a shit on a summer's concrete.

>>29
but new software won't even run on old hardware..?
next minute win95 blows win8 away on new hardware ^^

0.0 i can see skynet v0.1 from here

ai-cloud-os..?

CAI_OS ^^