Contact

ebyte.org would like to hear from:

• Anyone trying EByte out. Which format you pointed it at, what worked, and what got in the way.
• Anyone who found a bug. A file that didn’t come back byte for byte, an offset that looked wrong, an error you didn’t expect.
• Anyone with a format EByte can’t describe yet. Bit fields, floats, offsets, checksums: knowing which ones people need decides what comes next.

Write to [email protected].

Bug reports are also welcome on GitHub. It helps to include what ebyte --version prints, your operating system, the schema and the JSON diagnostic the tool printed. Please don’t send real customer files. A small made-up file that shows the same problem is enough, and EByte’s diagnostics never print file contents, so they’re safe to paste.