## Bitreich.org

Gopher:
gopher://bitreich.org
gopher://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion

SSH (member services):
ssh://bitreich.org
ssh://u4y6hueilfgjvm643n45ekhbnvqnl6ubdqok2dqdzmmj6bpvrrbecyqd.onion

HTTP (just for legacy):
http://bitreich.org (Don't use it!)
http://pujir2ibife7abuwdiag4c27de5xsgqbggc2agsllmignfx3u63j32ad.onion (Maybe use this.)

IRC (community access):
ircs://irc.bitreich.org:6697/#bitreich-en
ircs://irc.bitreich.org:6697/#bitreich

Founded: 2016

by

Christoph Lohmann <[email protected]>

## Why do we need bitreich?

gopher://bitreich.org/0/documents/bitreich-manifesto.md

* »We live surrounded by complex software. (...) RAM and CPU consumption never
 reduce. (...) This has to change!«
       * Ugliness has brought us consumerism.
       * Consumerism leads to wasting resources (lifetime is a resource!).
       * People are clueless about the ground problem.
* »Suckless failed.«
       * It forced too much on one language.
       * It was not really pure, see http presence.
       * There is some hidden organisation which does pretend to represent
         suckless.
* »Unix principles«
       * One application does ont thing right.
       * Commandline access.
       * KISP (see next slide)
* »binary blobs evolved into a complexity no young programmer can understand
 (...) This circle is producing even bigger binary blobs. (...) This has to
 end!«
       * We have to be examples how to change this.
       * Be prepared when we get cool. (Hipsterdom is evil!)

## The Bitreich Movement

gopher://bitreich.org/0/documents/bitreich-manifesto.md

* »We form a movement to improve our _daily_software_life_. Software has to not
  misbehave, it has to follow our rules, it has to be reusable, it has to be
  easily maintainable, it has to provide its recompilable source and it has to
  be easily understandable.«
       * Software has to do one thing right.
       * Software has to be controllable. (No lock-ins!)
       * Simple software can be reused in situations where the original
         author did not think of.
       * When you cannot maintain some sourcecode anymore, stop the growth,
         keep it as-is and start a new project for your »big feature everyone
         needs«.
       * Opening the source is something which is achieved. But code has to
         be compilable, by simply typing »make« or similiar steps. More than
         three steps is a waste of lifetime and makes you suspicious to not
         like to open the source. Pretenders are worse than people not open the
         the source for monetary reasons.
       * Code has to be readable.

## Bitreich Principles (0 of 1)

gopher://bitreich.org/0/documents/bitreich-manifesto.md

* »KISP – Keep It Simple Perfect«
       * Once something is done, keep it done.
* »Commandline Interfaces«
       * Commandline flags
       * Configuration files are evil
       * If your application is too complex, allow some typing interface
         without moving the mouse.
* »When Possible Use GPLv3«
       * GPLv3 can be enforced in front of court. Military usage of software
         has proven that MIT is not enough. Do not live in your BSD bubble.
         If you need to earn money, become something useful to the world,
         like a street cleaner.
       * Other licences can be used, but think about the consequences.
* »Users are Programmers«
       * When you lower what your users can become or are you will get idiot
         users. Allow them to modify the application, but do not let them
         become consumers (mindless complainers).
* »Bugreports Are Patches«
       * If you consider the point before this one, get users to be
         programmers and they will contribute patches instead of bug reports.
* »Applications Can Be Done«
       * See KISP.
       * When something does it's original intention, it's done and something
         else will be used to pipe to or from it.

## Bitreich Principles (1 of 1)

gopher://bitreich.org/0/documents/bitreich-manifesto.md

* »Freedom Of Language«
       * We are small, we cannot change the whole software world. We can just
         change our small software bubble, we live in. So allow other
         languages, which adhere to interfaces like pipes. Do you really want
         to force C programming to hack into android applications and services?
* »Ineveitability Of Change«
       * Our manifesto will be adapted to space and time. The democracy by our
         secret leaderboard will assure this.

## Branches

gopher://bitreich.org/0/documents/bitreich-organisation.md

* Branches are meant as idea groups. They will be useful when we grow.

* »New Applications«
       * Write new applications with the bitreich principles in mind.
* »Graphical Interface«
       * See what suckless has achieved so far using tabbed(1), dwm(1),
         dmenu(1) and my plumber(1)
       * finally get a sane graphical programming into this world
* »Abstractions«
       * Adapt to the ugly world outside and make it useful in our small
         software bubble.
               * surf(1) as an example for web abstraction
* »Ugly World«
       * If something is too complex out there, make it simpler. For example
         have easy access to cloud crap because your employer needs you to
         access it. Do not bend over for PHP.
* »Code Cleanup«
       * Experience has shown, that hobbyists write pretty good software. It
         needs some cleanup to be useful for others. Just do that.
       * Reduce ugly code constructs in open source software to simpler (for
         example functional) code constructs. This should reduce github
         codebase by 75%, when it is done.
* Add your lovely branch here.
       * If you find more groups of what needs to be done, discuss and apply
         them to our little software world.

## Organisation

gopher://bitreich.org/0/documents/bitreich-organisation.md

* »Inner Circle«
       * »bitreich-leaders« group on bitreich.org
       * holds polls about new members
       * is kept small so we can have »sane« decisions
       * the secret meetings are held open in the IRC channel
       * thus they are legitimate
* »Services«
       * See next slide.

## What have we done so far.

* Server is running at bitreich.org.
* Tor domains have been set up.
* $(grep bitreich: /etc/group | cut -d':' -f 4 | sed 's#,#\n#g' | wc -l)
       = 8 (# members)
* services for members:
       * bitreich-paste(1)
       * bitreich-ln(1) (link shortener for gopher)
       * members pages
       * member phlogs
       * internal discussion board at /br/dis
       * internal documentation at /br/doc
       * bitreich-mnt-share(1)
       * bitreich share service for ~/br
* IRC channels are working
       * #bitreich-en has high daily activity
* Gopher lawn project has been founded (see talk)
* at least two projects are considering to switch over to bitreich
* three successful democratic polls by the bitreich leader board
* our conference is held today

## Further Readings

gopher://bitreich.org/0/documents/bitreich-organisation.md
gopher://bitreich.org/0/documents/bitreich-branches.md

## Thanks

Thanks for listening!

See you at bitreich.org!

You are viewing proxied material from bitreich.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.