Writing documentation was good for #GoActivityPub.

It gives me the opportunity to go through some user scenarios for the tools I'm documenting and make sure that they work the way I'm describing.

I've fixed a couple of issues in this way these past days.

https://man.sr.ht/~mariusor/go-activitypub/go-ap/pitfalls.md#changing-the-type-of-an-object

#ActivityPub #ActivityPubDev

For the past couple of days I've been hard at work writing documentation in the attempt to decrease the friction for developers that try #GoActivityPub for their applications.

I am of a mind to pay some #Go developers in the near future to do a weekend's worth of programming into trying to use the library in projects, so we can iron out potential issues with the use of the library itself and the documentation.

Anyone interested?

#go #ActivityPub #ActivityPubDev #fediverse

Is anyone aware of a FEP for that?

#ActivityPub #ActivityPubDev #FEP

I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)

An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).

Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)

#ActivityPub #fedidev #ActivityPubDev

Remote Follow가 어떻게 구현이 되어있나하고 궁금해서 찾아봤는데, WebFinger를 응용하긴 하는 듯

• Akkoma 구현 - Server에서 Webfinger 요청날리고, 해당 서버 기준의 프로필 페이지로 안내
• Mastodon 구현 클라이언트에서 Webfinger 요청 날리고, /authorized_interactions 경로로 리다이렉트

#ActivityPubDev

Grrrr spent almost an hour debugging a problem. It was the receiver as:Public. as:Public is the devil !

#activitypubdev #activitypub #hell

{
    "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 ...]
                },

What to learn more about the #fediverse and #ActivityPub? This tutorial (https://fedify.dev/tutorial/microblog) from @fedifyFedify: ActivityPub server framework is a really good starter. It explains how to implement a really simple #federated server and see how communication exchange are done with AP.

#tutorial #activitypubdev #fedify #typescript #library

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.

#activitypub #activitypubdev #rdfpub

I'm confused again. from a C2S perspective, “reject following” and “reject follower” look structurally identical, don't they?

#activitypub #activitypubdev #rdfpub

Anyone else keeping track of these tags feel free to jump in if you have any actionable ideas. :) TY

#activitypub #activitypubdev #fedidev

@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.

#activitypub #fedidev #activitypubdev