Webforms/IPFS attestation milestone completed.
View article
View summary
The Hubzilla Webforms publication chain now works end-to-end: Hubzilla/Webforms → orchestrator1 → ipfs1/Kubo → IPFS pin → git/POSIX path reference → read/verify result
Verified durable publication result:
CID:
bafkreierfjh465dkryibez3fhiuvpd5minb4tmwrkq2ndcklpcf7nfztya
IPFS URI:
ipfs://bafkreierfjh465dkryibez3fhiuvpd5minb4tmwrkq2ndcklpcf7nfztya
Git/POSIX reference:
kane-il/hubzilla/attestations/own-posts/git64bit/2026-05-31/95899a79-0c4d-4c39-aa8a-45cd17bcbbc7.json
Commit:
7e263039842019fe19fa4ea4db68352e30d29234
Final verification:
status: verified
pin_status: pinned
retrieval_status: retrievable
content_verified: true
git_reference_verified: true
This confirms that a Hubzilla post can be selected, prepared as an attestation package, published through the controlled orchestrator/IPFS path, pinned, referenced in the git/POSIX index, and read back for verification.
The important boundary remains intact: Webforms does not call raw Kubo RPC, does not hold backend credentials, and does not write git/POSIX references directly. Hubzilla remains the participant-facing surface, while orchestrator1 performs the controlled backend workflow.
The interface will need a lot of work, and now that I have the functional reference a rename - rewrite is coming.
