_______________
         ,-^            ,-^|
      ,-^            ,-^   |
   ,-^------------.-^      |
   |              |        |
   |              |   6    |
   |              |        |
   |      vi      |        |
   |              |      ,-^
   |              |   ,-^
   `--------------+,-^
   vichan - teh imageboard engine
   -- preliminary website, until someone comes up with something better
   * vichan github project page
   * new support board
   * irc support channel (#vichan-devel @ irc.6irc.net)
   * historical support board
   Announcement
   vichan engine is not dead yet. We still support the code, but the old
   cruft has accumulated beyond repair.
   If you are looking for a modern imageboard engine that works, this is
   your best choice at the current time.
   Recently, there has been a wake of new imageboard projects. That's a
   good thing, but in our opinion, we should
   unite and not divide. The imageboards are going to look differently a
   few years from now. It's the time to
   shape that future.
   If you own an imageboard, you know that your community may demand some
   changes, or maybe stability. If you write
   code, you listen to those demands. There are many approaches to that,
   as every community is a different one, yet
   they all share some common goals.
   I am proud, that our code launched some kind of evolution, after a long
   stagnation from Kusaba times. Our job is
   now mostly complete, now that we have somewhat hit the limits. But what
   did impose us those limits, what should
   we do to go beyond them? Is the job really complete?
   Everyone has different ideas about that. If we try to solve only our
   ideas, we may hit a similar problem a few
   years from now. How about, if we all collect together and talk about
   those possible problems? It's always easier
   to think about it, when the project is in a project shape, than when
   it's near its finalization.
   We've launched an IRC channel, that should be a think-tank to everyone
   having fresh ideas about imageboards. The
   channel is mostly open, yet we should all try to stay on-topic. We
   already have some people doing code, owning
   big imageboards. If you think you have a worthy addition, or just want
   to sit and watch how we shape the future,
   we invite you there:
   #metachan on Rizon
   The engines are tools. The tools are not communities. But the
   communities do depend on tools to exist. What is
   the tool your community needs? And what will your community need in a
   few years from now?
   ~czaks