ACTIVITYPUB(7) | Miscellaneous Information Manual | ACTIVITYPUB(7) |
activitypub
—
notes about the honk implementation
The honk(1) utility processes
status updates and other microblog activities using the
ActivityPub
protocol to exchange messages with other
servers. The specification is subject to interpretation, and not all
implementations behave in the same way. This document attempts to clarify
honk's behavior. It is not intended to be a complete description of
ActivityPub
, but may be useful as a guide to other
implementors looking to interoperate.
The following object or document types are supported.
Honk primarily supports HTML content, not markdown or other formats, with a wide range of permitted HTML tags in object content fields. The following tags are supported.
a, img, span, div, h1, h2, h3, h4, h5, h6, hr, table, thead, tbody, tfoot, th, tr, td, colgroup, col, p, br, pre, code, blockquote, q, caption, kbd, time, wbr, aside, ruby, rtc, rb, rt, details, summary, samp, mark, ins, dfn, cite, abbr, address, strong, em, b, i, s, u, sub, sup, del, tt, small, ol, ul, li, dl, dt, dd
The following tag attributes are permitted.
href, src, alt, colspan, rowspan
The following class names are used for syntax highlighting code blocks.
kw, bi, st, nm, tp, op, cm, al, dl
The following activities are supported.
The following additional object types are supported, typically as tag or attachment.
The replies array will be populated with a list of acknowledged replies.
Honk also supports a Ping activity and will respond with a Pong activity. This is useful for debugging networking connectivity issues without visible side effects. See ping.txt for details.
Honk uses http signatures.
Honk implements the webfinger end point and will use it for @mention resolution. It is not required for federation.
Not really.
The ActivityPub standard is subject to interpretation, and not all implementations are as enlightened as honk.
June 6, 2025 | macOS 13.7 |