atproto pds in zig pds.zat.dev
pds atproto

space: accept unpadded base64 in $bytes master

the data model says `=` padding is optional; the reference PDS sends notifyWrite hashes unpadded, and every one was refused with "Invalid hash", so a remote member's repo never reached listRepos on a zds-hosted space. both $bytes decoders (space wire fields, record JSON) now strip padding and decode with the no-pad codec. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>


+26 -5
3 changed files