docs: improve ALAR format specs#118
Merged
Merged
Conversation
pleonex
commented
Apr 28, 2026
Collaborator
Author
pleonex
left a comment
pleonex
left a comment
There was a problem hiding this comment.
I don't approve myself 😄
priverop
requested changes
Apr 30, 2026
Owner
priverop
left a comment
priverop
left a comment
There was a problem hiding this comment.
Great job! It's fun to see the true meaning of these former "unknown" bytes.
I added a couple of improvements to really understand the document.
priverop
reviewed
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Document unknown fields of the ALAR format. It also includes a guess of how the v1 format should look like from the remainings of unused code left.
There are still some unknown bits. We will have a better guess once we know more about the .amt and .dig formats.