onUnverifiedActivity() only runs when signature verification fails: missing signature, bad signature, or a key lookup failure. It gives you a chance to handle those cases yourself instead of Fedify immediately returning 401 Unauthorized. If the signature verifies, this hook is not involved.
If you want extra validation for verified activities, do that in your normal .on() handlers. Those run after signature verification, so that's where app-specific checks belong, like rejecting certain actors or applying your own rate limits.
Thanks for the feedback! The style choices are intentional and all valid CommonMark:
Heading styles: Setext (===/---) for H1/H2 makes major sections visually prominent in plain text, while ATX (###) is used for deeper levels. This hybrid approach optimizes readability in the raw source.
Four tildes: Tildes are valid CommonMark delimiters, just less common. They're chosen because code often contains backticks (shell commands, string literals), so tildes avoid visual clutter.
The core philosophy is that Markdown should be readable as plain text, not just after rendering. These choices prioritize scanning structure in a text editor. That said, it's definitely an opinionated style—not for everyone!
It has zero dependencies, and supports virtually every JavaScript runtime (browsers, Node.js, Bun, Deno, and edge functions). It also organize loggers in hierarchical categories, which allows you fine-grained control over log levels for different parts of an application.
Thank you for your advice. As you mentioned, Fedify currently has actor URIs consisting of handles. This limitation is due to the early design of Fedify and will be fixed before we release v1.0!
Thanks for your kind words!
Thank you!
onUnverifiedActivity()only runs when signature verification fails: missing signature, bad signature, or a key lookup failure. It gives you a chance to handle those cases yourself instead of Fedify immediately returning401 Unauthorized. If the signature verifies, this hook is not involved.If you want extra validation for verified activities, do that in your normal
.on()handlers. Those run after signature verification, so that's where app-specific checks belong, like rejecting certain actors or applying your own rate limits.Thanks for the feedback! The style choices are intentional and all valid CommonMark:
Heading styles: Setext (
===/---) for H1/H2 makes major sections visually prominent in plain text, while ATX (###) is used for deeper levels. This hybrid approach optimizes readability in the raw source.Four tildes: Tildes are valid CommonMark delimiters, just less common. They're chosen because code often contains backticks (shell commands, string literals), so tildes avoid visual clutter.
The core philosophy is that Markdown should be readable as plain text, not just after rendering. These choices prioritize scanning structure in a text editor. That said, it's definitely an opinionated style—not for everyone!
Basically a combination of GFM with a few extensions such as definition lists!
It's on the roadmap, but not yet.
It means postage stamp in Korean.
It has zero dependencies, and supports virtually every JavaScript runtime (browsers, Node.js, Bun, Deno, and edge functions). It also organize loggers in hierarchical categories, which allows you fine-grained control over log levels for different parts of an application.
Thank you for your advice. As you mentioned, Fedify currently has actor URIs consisting of handles. This limitation is due to the early design of Fedify and will be fixed before we release v1.0!
LogTape author here.
LogTape also supports structured logging. Structured values are kept in
LogRecord.properties. Please see how to use the JSON formatter.