scuttlego
scuttlego copied to clipboard
A Go implementation of the Secure Scuttlebutt protocol.
Or rather what is supposed to happen? Should that feed get removed? Probably not.
I just noticed the following sequence of messages exchanged with a peer (irrelevant payload redacted): ``` level=debug ts="2023-01-17 22:33:29.5185650 (UTC)" source=golang id="@CIlwTOK+m6v1hT2zUVOCJvvZq7KE/65ErN6yA2yrURY=.ed25519" header.flags="" header.number=3 header.bodyLength=14020 body="{\"@3PGWnoMIY5ebs6sJjkwc7DKjxrgcrOeIUC2YegkMtIY=.ed25519\":0}" name=gossb.peer-2188669348362399538.raw message="sending a message"...
Right now it is a mess and we can't decide if they should be there or not. Given that this is the main place that guards the program from bad...
Right now this would require reconnecting.
``` time="2022-09-26T12:22:56+02:00" level=error msg="mapping returned an error" content="{\"type\":\"post\",\"text\":\"a new photo from #dw eb-camp 2022! ![photo.bmp](&O0h21NiGLLmjCF1kD2xWllvPExwe6t5P+F7YK3HAX4g=.sha256)\",\"mentions\":{\"0\":{\"name\":\"photo.bmp\",\"type\": \"image/bmp\"}}}" error="json unmarshal failed: json: cannot unmarshal object into Go struct field transportPost.mentions of type...
Messages received from the message pubsub in the create history stream query are filtered by feeds and sent to peers. Those messages may be out of order. While the documentation...
Instead we need to adjust replicators to accept feeds which don't have the number of hops associated with them.
The idea is to prefetch some blobs, fetch others on demand etc. The data for this is already stored in the database but not used.