# HG changeset patch
# User Laman
# Date 2015-09-01 22:49:52
# Node ID ab6a05aec0f8c85a44e1a4de0153cd7fca0a0873
# Parent  500e573f202d2d27911810731784d3c27e87b610

Backed out changeset: 500e573f202d

diff --git a/readme.md b/readme.md
--- a/readme.md
+++ b/readme.md
@@ -4,10 +4,10 @@
 Program to extract moves of a go game from a video and save them to SGF or broadcast them online.
 
 Modules:
-* Video: grabbing still frames from a video file / stream. Planning to use FFmpeg.
-* Graphic: extracting game position from an image. Using Pillow.
-* Watcher: interpreting sequence of game positions as a sequence of moves.
-* Broadcaster: interfacing with a go server.
+  * Video: grabbing still frames from a video file / stream. Planning to use FFmpeg.
+  * Graphic: extracting game position from an image. Using Pillow.
+  * Watcher: interpreting sequence of game positions as a sequence of moves.
+  * Broadcaster: interfacing with a go server.
 
 
 Graphic
@@ -24,11 +24,12 @@ Watcher
 Base case: we have two correctly recognized positions differing by a single move (single added stone). Easy.
 
 Issues:
-* illegal positions -> ignorable
-* positions unreachable from the previous state
-  * reachable from any past state. (Incorrect states inbetween). How to pick the correct leaf of such a tree?
-  * reachable by more than one move. Issues with branching factor.
-* board shifts -> repaired manually (or automatically), further positions have to be reevaluated
-* stone shifts
-  * stone stops being recognized -> fixable manually and even ignorable
-  * stone is recognized at an empty intersection. It can be occupied later for real. What do?
\ No newline at end of file
+  * illegal positions -> ignorable
+  * positions unreachable from the previous state
+    * reachable from any past state. (Incorrect states inbetween). How to pick the correct leaf of such a tree?
+    * reachable by more than one move. Issues with branching factor.
+  * board shifts -> repaired manually (or automatically), further positions have to be reevaluated
+  * stone shifts
+    * stone stops being recognized -> fixable manually and even ignorable
+    * stone is recognized at an empty intersection. It can be occupied later for real. What do?
+