home.social

#protocoldesign — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #protocoldesign, aggregated by home.social.

fetched live
  1. I used ChatGPT + OpenAI Codex to extract a Reticulum protocol specification from the Python implementation.

    The result: an explicit SPEC.md, plus audit reports comparing several Reticulum implementations against that specification.

    A protocol without a specification is a novel concept to me; now there is something concrete to compare against.

    salemdata.net/johnpress/?p=861

    #Reticulum #Codex #OpenAI #ProtocolDesign #SoftwareSpecification #Python #Rust #EmbeddedSystems #AIcoding

  2. Looking at two Rust paths toward #Reticulum: Reticulum-rs, a smaller MIT-licensed library, and Leviculum, a much broader AGPL implementation with a no_std core, daemon/CLI, interop tests, and embedded ambitions.

    My practical question: could either help with #ESP32 / #TBeamSupreme transport work, or does #microReticulum still win today?

    salemdata.net/johnpress/?p=850

    #Rust #EmbeddedSystems #LoRa #NoStd #ProtocolDesign

  3. A house is not a building code.

    I wrote about using ChatGPT + Codex to derive a protocol specification for Reticulum/LXMF from its Python implementation—turning “look at the source” into something closer to a language-neutral contract, with test vectors to follow.

    salemdata.net/johnpress/?p=812

    #Reticulum #LXMF #Codex #AIcoding #ProtocolDesign #EmbeddedSystems #TBeamSupreme #ESP32

  4. Some protocols begin life not as RFCs, but as “read the source; that’s the spec.”

    I’m experimenting with AI agents to extract an implementable protocol specification from Python code. See diagram.

    Has anyone else used AI for protocol archaeology / reverse-specification?

    #ProtocolDesign #ReverseEngineering #SoftwareArchaeology #AIAgents #Python #Interoperability #DistributedSystems #OpenSource #MessagingProtocols #ProtocolSpecification #ImplementationDefined

  5. "During the workshop, participants from industry and academia brought up topics about #protocoldesign and development. Participants were interested in misalignments between protocol designers and users. Designers and engineers shared insights and lessons learned, especially about the mechanism of data deletion in these protocols. For instance, BlueSky designed its protocol to make data unremovable, but it turned out that users preferred the content to be removable."
    freedom-to-tinker.com/2024/03/