Update readme
This commit is contained in:
parent
74d5fc1f43
commit
82d04e347c
1 changed files with 1 additions and 4 deletions
|
@ -2,8 +2,7 @@ TextSecure Chromium Implementation
|
||||||
==================================
|
==================================
|
||||||
|
|
||||||
This is very early stuff and exists primarily to get the crypto in place.
|
This is very early stuff and exists primarily to get the crypto in place.
|
||||||
Note that the code is currently quite messy (its all in one file!), but it
|
*This does not currently work, dont bother trying to use it seriously yet*
|
||||||
needs to work first, then it can be heavily cleaned up later.
|
|
||||||
|
|
||||||
Getting Started with Development
|
Getting Started with Development
|
||||||
================================
|
================================
|
||||||
|
@ -25,8 +24,6 @@ chai:
|
||||||
|
|
||||||
Tips/Tricks
|
Tips/Tricks
|
||||||
===========
|
===========
|
||||||
|
|
||||||
* For Dev purposes, the test server always uses code 111111
|
|
||||||
* Loading the `test.html` page may read, write or clear localStorage. To avoid
|
* Loading the `test.html` page may read, write or clear localStorage. To avoid
|
||||||
having to choose between running tests and preserving your existing messages,
|
having to choose between running tests and preserving your existing messages,
|
||||||
keys, and other extension data, much of the test suite can be run by starting
|
keys, and other extension data, much of the test suite can be run by starting
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue