Notices by 洪 民憙 (Hong Minhee) (hongminhee@todon.eu), page 11

@twilliability The pragmatic heuristics you mentioned is great, but I'm building a framework called Fedify, and I needed a more general way of doing things. 🤔

@twilliability The problem is that in addition to POST requests with an activity, GET requests can also be signed. When you receive a GET request, you have no way of knowing which actor the signed key belongs to. I asked the same question at the Fediverse Developer Network in Matrix, and we concluded that the only way to do this is to maintain a separate actor–keyId table in the server.

@tirr 고생하셨습니다

When an #ActivityPub server implements authorized fetch (aka secure mode), how does it associate the keyId in an HTTP request with the actual actor? I know major implementations (like Mastodon) use a fragment appended to the actor IRI as a keyId, but in theory a keyId could be any IRI that seems unrelated to the actor IRI, right? Should I maintain a table of actor–keyIds somewhere in the server?

#fedidev #httpsignatures #authorizedfetch

This document, edited by @snarfed.org, is really helpful for implementing Fedify in practice.

https://swicg.github.io/activitypub-http-signature/

木から六本木まで

#kanji #series #extrapolated

For an example of integrating #Fedify with #Hono, see here:

https://github.com/dahlia/fedify/tree/main/examples/hono-sample

Fedify 0.6.0 has been released! Here are the major changes:

• The docs website has been migrated from Lume to VitePress, is more beautiful, and is finally searchable with ^K/⌘K!

• To improve interoperability with servers that have authorized fetch turned on, also known as secure mode, Fedify has changed to use the authenticated document loader by default in as many cases as possible.

• New @fedify/fedify/x/hono module to help integrate with the Hono web framework has been introduced.

• Added small fixes to help with debugging activity delivery.

https://fedify.dev/changelog#version-0-6-0

@kimsm 다음에는 부디 괜찮은 집주인 만나시길… 🙏

@kimsm 아이고 고생하셨습니다. 양아치 집주인이 참 많죠…

I don't see why I should use Scala when I can use Haskell (unless I need to interop with Java).

@noim I found VitePress to be faster to build and the default theme is more beautiful.

Migrating the #Fedify docs website from #Lume to #VitePress…

https://unstable.fedify.dev/

Today's yak shaving: creating a #markdown-it plugin to create a #Fedify documentation website.

https://jsr.io/@hongminhee/markdown-it-jsr-ref

#Deno #JSR #Markdown

I've written a guide to integrating with web frameworks in the #Fedify docs, explaining how to use the built-in #Fresh and #Hono integration middleware, as well as the mechanisms for integrating with other frameworks.

https://unstable.fedify.dev/manual/integration/

@c_ssk 文相勳(ムン・サンフン)さんのオリジナルコンテンツ、刺激的でないのに面白くて私も大好きです！

Today #Fedify 0.5.0 was released, and with this version, it comes support for Node.js and Bun! It's available on both JSR and npm:

https://jsr.io/@fedify/fedify@0.5.0
https://www.npmjs.com/package/@fedify/fedify/v/0.5.0

@twilliability Although this documentation is being done as part of the Fedify project's docs, it would be great to have a more general docs project for the pragmatic aspects of Activity Vocabulary.

I'm writing a section in the #Fedify docs on the pragmatic side of the Activity Vocabulary APIs, and I want to list how each API is used and how it is displayed in the major implementations.

https://unstable.fedify.dev/manual/pragmatics/

#fedidev #ActivityPub

Where #Fedify came from:

https://todon.eu/@hongminhee/110971265294250919