Remote Follow가 어떻게 구현이 되어있나하고 궁금해서 찾아봤는데, WebFinger를 응용하긴 하는 듯
- Akkoma 구현 - Server에서 Webfinger 요청날리고, 해당 서버 기준의 프로필 페이지로 안내
- Mastodon 구현 클라이언트에서 Webfinger 요청 날리고, /authorized_interactions 경로로 리다이렉트
Search results
Grrrr spent almost an hour debugging a problem. It was the receiver as:Public. as:Public is the devil !
Another nail in the coffin for #JsonLD:
That's a post that I edited shortly after I first made it. The corresponding conversation container contains both the original Create, and an Update with the changes. This means that the embedded Note object appears twice, with different contents, but with the same ID.
JSON-LD processing will kind of squish them together into the same object that contains both the original and the new
#ActivityPubDev
{
"id": "https://zotum.net/conversation/235e8736-1b3e-4d7f-ab9e-3d49f04ecda7",
"orderedItems": [
{
"type": "Add",
"object": {
"type": "Create",
"object": {
"type": "Note",
"id": "https://zotum.net/item/235e8736-1b3e-4d7f-ab9e-3d49f04ecda7",
"published": "2025-02-25T20:28:33Z",
[... original version of post ... ]
},
},
},
{
"type": "Add",
"object": {
"type": "Update",
"object": {
"type": "Note",
"id": "https://zotum.net/item/235e8736-1b3e-4d7f-ab9e-3d49f04ecda7",
"published": "2025-02-25T20:28:33Z",
"updated": "2025-02-25T20:29:03Z",
[... edited version of post ...]
},That's a post that I edited shortly after I first made it. The corresponding conversation container contains both the original Create, and an Update with the changes. This means that the embedded Note object appears twice, with different contents, but with the same ID.
JSON-LD processing will kind of squish them together into the same object that contains both the original and the new
content etc. Handling this as JSON-LD will mean recognising the high level structure of it first, and then iterating over the orderedItems and processing them individually, rather than trying to treat the whole thing as a single JSON-LD message.#ActivityPubDev
What to learn more about the #fediverse and #ActivityPub? This tutorial (https://fedify.dev/tutorial/microblog) from 
I've made good progress again in the last few days. My signature problems seem to have vanished into thin air. Still having some trouble with reject/undo follow(ing), but I need a break from that for now. Today I took care of the display of the 
@Kartevonmorgen events. I'm very happy, even if something is still going wrong with the redundant data.
I'm confused again. from a C2S perspective, “reject following” and “reject follower” look structurally identical, don't they?
@silverpill any idea if there's a FEP regarding how to sign an activity that gets propagated through the Forwarding from Inbox mechanism? https://www.w3.org/TR/activitypub/#inbox-forwarding
My first instinct is to use the instance actor for the server that received it, but I'm not sure.
Maybe the actor that received it in their inbox would be better, but that feels slightly unsanitary.
Anyone else keeping track of these tags feel free to jump in if you have any actionable ideas. :) TY
@silverpill any idea if there's a FEP regarding how to sign an activity that gets propagated through the Forwarding from Inbox mechanism? https://www.w3.org/TR/activitypub/#inbox-forwarding
My first instinct is to use the instance actor for the server that received it, but I'm not sure.
Maybe the actor that received it in their inbox would be better, but that feels slightly unsanitary.