From fe2a32e55ca3293b97a89e7b9950b9c395a4376396e62c555139edc7203316e9 Mon Sep 17 00:00:00 2001 From: brent saner Date: Wed, 10 Jul 2024 01:17:03 -0400 Subject: [PATCH] update ref links --- README.adoc | 4 ++-- README.html | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.adoc b/README.adoc index e43dc14..bda1eb8 100644 --- a/README.adoc +++ b/README.adoc @@ -52,7 +52,7 @@ NOTE: In the event of the embedded text in this document differing from the onli [id="proto"] == Protocol -The WireProto data packing API is a custom wire protocol//message format designed for incredibly performant, unambiguous, predictable, platform-agnostic, implementation-agnostic communication. It is based heavily on the https://github.com/openssh/openssh-portable/blob/master/PROTOCOL.key[OpenSSH "v1" key format^] https://git.r00t2.io/r00t2/go_sshkeys/src/branch/master/_ref/KEY_GUIDE.html#v1_plain_2[(example/details)] packing method. +The WireProto data packing API is a custom wire protocol//message format designed for incredibly performant, unambiguous, predictable, platform-agnostic, implementation-agnostic communication. It is based heavily on the https://github.com/openssh/openssh-portable/blob/master/PROTOCOL.key[OpenSSH "v1" key format^] https://sshref.dev[(example/details via sshref.dev)^] packing method. It supports arbitrary binary values, which means they can be anything according to the implementation-specific details; a common practice is to encode ("marshal") a Go struct to JSON bytes, and set that as a WireProto field's value. @@ -120,7 +120,7 @@ Throughout this document, you may see references to things like `LF`, `SOH`, and These refer to _ASCII control characters_. You will also see many values represented in hex. -You can find more details about this (along with a full ASCII reference) https://square-r00t.net/ascii.html[here^]. Note that the specification fully supports UTF-8 (or any other arbitrary encoding) -- just be sure that your <> are aligned to the *byte count* and not *character count* (as these may not be equal depending on encoding). +You can find more details about this (along with a full ASCII reference) at https://asciiref.dev/[asciiref.dev^]. Note that the specification fully supports UTF-8 (or any other arbitrary encoding) -- just be sure that your <> are aligned to the *byte count* and not *character count* (as these may not be equal depending on encoding). ==== Each *message* is composed of: diff --git a/README.html b/README.html index b1f8568..74150b9 100644 --- a/README.html +++ b/README.html @@ -632,7 +632,7 @@ pre.rouge .gs {
Brent Saner

-Last rendered 2024-07-10 00:43:17 -0400 +Last rendered 2024-07-10 01:17:03 -0400
Table of Contents
@@ -1235,7 +1235,7 @@ In the event of the embedded text in this document differing from the online ver

2. Protocol

-

The WireProto data packing API is a custom wire protocol//message format designed for incredibly performant, unambiguous, predictable, platform-agnostic, implementation-agnostic communication. It is based heavily on the OpenSSH "v1" key format (example/details) packing method.

+

The WireProto data packing API is a custom wire protocol//message format designed for incredibly performant, unambiguous, predictable, platform-agnostic, implementation-agnostic communication. It is based heavily on the OpenSSH "v1" key format (example/details via sshref.dev) packing method.

It supports arbitrary binary values, which means they can be anything according to the implementation-specific details; a common practice is to encode ("marshal") a Go struct to JSON bytes, and set that as a WireProto field’s value.

@@ -1348,7 +1348,7 @@ In the event of the embedded text in this document differing from the online ver

These refer to ASCII control characters. You will also see many values represented in hex.

-

You can find more details about this (along with a full ASCII reference) here. Note that the specification fully supports UTF-8 (or any other arbitrary encoding) — just be sure that your size allocators are aligned to the byte count and not character count (as these may not be equal depending on encoding).

+

You can find more details about this (along with a full ASCII reference) at asciiref.dev. Note that the specification fully supports UTF-8 (or any other arbitrary encoding) — just be sure that your size allocators are aligned to the byte count and not character count (as these may not be equal depending on encoding).

@@ -2368,7 +2368,7 @@ ae88bed2 // Checksum Value (2928197330)