blob: 4ef7eb47f333e431ecdfa4999b85478afa7657e5 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
* Under heavy lag, typing a lot results in a graph that splits into many
branches, and never re-joins. While this works, it's ugly. Find a way to
add in explicit join points, so the graph re-joins.
Probably this entails making a Activity Entered be able to point to
the previous Activity Entered. Then in eg:
Entered: A B C D E F G
Seen: A
An "H" entered can point to the "A" seen, but also point to the "G"
entered.
This should only be ugly, not a security hole.
* Improve JSON, removing use of "tag"
* potential DOS where developer sends Activity Entered that all
refer back to the first Activity Seen. This requires the user
side to keep a Backlog containing all later Activity Seen, so uses
up a lot of memory.
For this to work, the developer would need to include
in their Activity Entered echoData anticipating all the Activity Seen
that they have generated. This is doable; for example the developer
can send a stream of A's, and then needs to only include the right
amount in the echoData.
Should probably cap the BackLog to some maximum size to prevent
this kind of DOS. Dropping old items from the BackLog after some
amount of time would also work; after eg 10 seconds it's very
unlikely that a Activity Entered will legitimately refer to an
old backlog item.
* Encryption!
* Add random nonce to start message, to avoid replay issues.
(Or perhaps the encryption derives a RSA key in a way that avoids
replay..)
* Network!
* Server!
* gpg key downloading, web of trust checking, prompting
|