| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
This fixes chat message echoing consistency too.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
documenting well ahead of implementation now
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do include it in the data that gets signed, so it can be recovered
by trying each likely (recently seen) Activity as the prevMessage, and
checking the signature.
The UserState and DeveloperState already had the necessary state about
recently seen hashes, so this does not impact data use.
One tricky bit is that relayFromSocket needs to wait for the TMChan
to be empty before calling restorePrevActivityHash. Otherwise, the
hashes of items in the channel that have not been processed yet won't be
tried. The TMChan is not really being used as a channel since only 1
item can be in it. It could be converted to a TMVar, but closeTMChan is
used so I left it as a channel.
Note that the server does not restore hashes of messages that pass
through it; it's just a dumb relay.
Sending a single key press now only needs 94 bytes of data to be sent,
down from 169!
---
Also switched to SHA512, since hashes are no longer being sent over
the wire and so the larger size does not matter. SHA512 is slightly
faster and more secure.
This commit was sponsored by Ewen McNeill.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This way it's not tied to details of the haskell binary library,
and implementations in other languages should be fairly simple to do.
The haskell protobuf library was used because it does not need extra
tooling or build steps. So I didn't write a .proto file, but one could
fairly easily be written by following ProtocolBuffers.hs and translating
it.
ProtocolBuffers.hs is *extremely* repetative and tedious code. Surely
there must be a way to not need to write all of that? Oh well, I wrote
it..
Sizes of serialized messages:
">>> debug-me session started": 121
sending a single key press: 169
This seems equally as efficient as the binary serialization was;
that was 165 bytes before elapsedTime was added.
This commit was sponsored by Ethan Aubin.
|
| |
|
|
|
|
|
|
| |
And part of what we need to have users verify them.
This commit was sponsored by andrea rota.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Time is relative, so the debug-me proof chain doesn't prove when things
happened, but it's still useful to have some idea of how long things
took to happen. This makes --replay work with logs gotten by --download.
Log still includes loggedTimestamp. This is a bit redundant, and is
unused now, but it's useful for log files to record when messages were
received.
This commit was sponsored by Riku Voipio.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
messages
This makes --download always work, which was the real motivation.
It's probably a good ways to having multiple connected developers able
to simulantaneously interact. I tested that breifly, and it seems to
work ok! It may however, not handle it perfectly when both developers
are trying to type at the same time. Still, nice that's basically
working for free!
This commit was sponsored by Jeff Goeke-Smith on Patreon.
|
| |
|
| |
|
|
|
|
|
|
| |
Including the process exit status.
And cleaner Role.User shutdown sequence.
|
|
|
|
| |
Now when the user quits, the developer also exits.
|
| |
|
|
|
|
|
|
|
|
|
| |
Multi-user client-server debug-me is working, almost perfectly.
All that was missing was replaying the log when the developer connected.
A number of race conditions had to be avoided to do that sanely.
This commit was sponsored by Ignacio on Patreon.
|
| |
|
|
|
|
|
|
| |
For some reason, runClient throws ConnectionClosed on apparently clean
shutdown. This happens even though clientApp uses sendClose, and the
server receives it and shuts down entirely cleanly.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Incomplete, but the client is able to connect and send messages which
get logged.
Split up debug-me.hs into Role/*
Switched from cereal to binary, since websockets operate on lazy
ByteStrings, and using cereal would involve a copy on every receive.
This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
|
|
|
|
|
|
|
|
|
|
|
| |
I tried both binary and cereal. For a ActivityMessage that takes 341
bytes in JSON and has a dataSize of 129, both used 165 bytes. Went with
cereal since lazy bytestrings are not needed, and I might want to use
https://hackage.haskell.org/package/safecopy later.
(Perhaps I should be using protocol buffers or something to make it
easier for non-haskell implementations? But that would complicate things
a lot.)
|
| |
|
| |
|
|
|
|
| |
This commit was sponsored by Ethan Aubin.
|
|
|
|
|
|
|
|
|
| |
Make Control messages be out-of-band async messages, without a pointer
to a previous message.
And then followed the type change through the code for hours..
This commit was sponsored by Nick Daly on Patreon.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prevent DOS of user side by limiting the size of the BackLog that
is maintained. This should not cause problems in even high latency
environments, and should prevent memory use > 16 mb.
The developer side does not keep much data, other than a list of the
Hashes of things it has recently sent, so is not susceptable to memory
DOS.
This commit was sponsored by Brock Spratlen on Patreon.
|
|
|
|
| |
This commit was sponsored by Ole-Morten Duesund on Patreon.
|
| |
|
|
|
|
| |
Including adding a timestamp to logs
|
|
|
|
| |
would make it more complicated to prove correct, for no gain I think
|
| |
|
|
|
|
|
|
| |
That I was stuck on for hours yesterday, oops!
This commit was sponsored by Bruno BEAUFILS on Patreon.
|
|
|
|
|
|
|
| |
Seems to work well with networkDelay on both sides now.
However, typing "top" causes the "to" to be accepted, but the "p" is
rejected.
|
|
|
|
|
|
|
|
| |
So when the developer makes 2 keypresses close together, they send the
second Activity Entered with the first Activity Entered as its HashPointer.
This allows the developer to prove the order they did things.
This commit was sponsored by Peter Hogg on Patreon.
|
| |
|
| |
|