This is a testing post.

Did it work?

Evening all (from Kbin.social)

I think I figured out what may be happening with edits.

Take @HeartyBeast 's reply up there - you will notice if you go to the base URL it was in fact edited, but that edit didn't make it here to 1001.

This activity federated out to:

    "to": [
        "https://www.w3.org/ns/activitystreams#Public",
        "https://the.coolest.zone/u/ryan"
    ],
    "cc": [
        "https://kbin.social/m/random",
        "https://kbin.social/u/HeartyBeast/followers"
    ],

Notice how the originating instance's magazine is not in the to or cc - this is because kbin.social is not actually subscribed to my testingmag magazine, but pulled this thread into random.

When this message finally made it to the.coolest.zone (through the ryan account), to and cc became:

"to": [
        "https://1001.coolest.zone/m/testingmag",
        "https://www.w3.org/ns/activitystreams#Public"
    ],
    "cc": [
        "https://the.coolest.zone/u/ryan/followers"
    ],

Per activitypub standard 7.1.2 Forwarding from inbox:

When activities are received in the inbox, the server needs to forward these to recipients that the origin was unable to deliver them to [...] if and only if all of the following are true:

• This is the first time the server has seen this Activity.
• The values of to, cc, and/or audience contain a Collection owned by the server.
• The values of inReplyTo, object, target and/or tag are objects owned by the server.

An edit was not the first time, presumably, the.coolest.zone saw the activity. 1001/testingmag as a group is not an object owned by the server. Therefore, even though the.coolest.zone knew this message should have eventually gone to 1001, it had no obligation to deliver it.

That's my best understanding of what's going on here. I'll need to test a bit more to be sure.

This is not a testing comment.