Henry
Currently, the size of an entry is abused to indicate that it was deleted (the size is negated) It would be better to have a user metadata thing for this...
right opening a query on offset2 with reverse and greater or less then constructions doesn't work correctly. Re-enable the tests and add the needed handling to qry.Next.
test against static test vectors. see cryptix/secretstream#1
Right now there is no bound on incoming requests. Each new call starts a goroutine. Especially for legacy ssb replication this means ~9k once the connection is established. Depending on...
This is really annoying.... The creator of rpc streams has to take care that they don't deadlock each other. This means: a caller needs to drain the whole stream and...
The dashboard page might timeout. I suspect this has something to do with the active connections listing, the database queries should be fine.
Currently the set of allowed characters for aliases is rather small. The reasons for the restriction and possible moves forward are outlined in the go doc string of `aliases.IsValid()`: https://github.com/ssb-ngi-pointer/go-ssb-room/blob/77d85824ffe088b31dc44e7afaf7688337aa7366/internal/aliases/names.go#L5-L14
https://github.com/ssb-ngi-pointer/go-ssb-room/issues/33#issuecomment-784333610
> Something like > - go-ssb-room creates invite > - Node.js client accepts an invite from the Go server using ssb-http-invite-client > - Node.js client connects to the go-ssb-room >...