diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-04-18 12:28:15 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-04-18 12:28:15 -0400 |
commit | b936e6f9df8364701eefd59720c9d85afea5e7e1 (patch) | |
tree | b70bbc387ef523c78081921dd2d6a91746b55df7 | |
parent | 9d1c9bcf99e4b5dc4f3c0ede46bcda84203bfeac (diff) | |
download | debug-me-b936e6f9df8364701eefd59720c9d85afea5e7e1.tar.gz |
decided not to do this TODO
would make it more complicated to prove correct, for no gain I think
-rw-r--r-- | TODO | 10 |
1 files changed, 0 insertions, 10 deletions
@@ -1,13 +1,3 @@ -* 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 |