@jesseplusplus @julian@community.nodebb.org I've taken a closer look at the actual commits, and yeah, there's more already in there than I had first understood. Thanks for elaborating and best wishes for the process!

@silverpill Thanks, I totally missed this development. I blame the conference I was at.

@jesseplusplus Can I ask here, what's the ultimate scope of what you're upstreaming? I see https://github.com/mastodon/mastodon/pull/35959 is a building block, will you be pushing for Mastodon to publish context collections later? It's not clear from what I'm seeing here if that's part of the plan.

@julian@community.nodebb.org @swicg-threadiverse-wg

@dansup @julian@community.nodebb.org @jesseplusplus Maybe we want the option to backfill private contexts so you can join a group and then see its post history? Or follow someone and gain access to old followers-only posts? AFAIK Mastodon doesn't currently do the latter, so that might cause some friction around privacy expectations. Okay, I see there is room to think on this!

@dansup @julian@community.nodebb.org @jesseplusplus Are there any circumstances under which context backfilling has to handle non-public posts? The way that ActivityPub delivery works, I would think that if a post has a recipient collection that doesn't include "as:Public", everyone who ought to be able to see it has already received a copy at time of creation.

I guess depending on the internal data model you might need to "reconnect" them (if they are replies to posts you receive later via backfill).

@dentangle NodeBB is a forum software that optionally supports ActivityPub, i.e. it's part of the fediverse (if the specific NodeBB instance wants). In my experience its lead ActivityPub dev @julian@community.nodebb.org (same first name, no relation ) is very approachable if you have questions about why and how it does things. He is currently at a convention though and may be a bit busy today.

cc @onepict

@sarahjamielewis For what it's worth, @fedify fetches and parses your actor correctly (tested with https://github.com/fedify-dev/fedify/tree/main/examples/actor-lookup-cli), so it's gotta be something where Mastodon is more strict.

@sarahjamielewis Maaaaaybe it has something to do with the content type? It looks like you serve the HTML if explicitly asked for text/html, and the JSON otherwise. I usually do it the other way around.

I think Mastodon refuses to load plain JSON documents, for security reasons (long story), this might be linked to that. Only sending the AP JSON for the content types listed in section 3.2 of the spec could be worth trying.

I'm poking at this kinda blindly though. Tough situation to debug.

@sarahjamielewis Ah, no, that's my mistake. Going by the standard, the "acct:" schema isn't optional, I just have a bad habit of forgetting about it.

But there's still something going on with fetching your AP URIs from Mastodon. I can pull up your profile if I search for the double-@ handle, but not if I search for the URI, even though you appear to serve correct AP. Might be the same reason why I can't fetch your test post. I tried from my Mastodon server and from https://activitypub.academy.

@sarahjamielewis The JSON of 1749328245 looks normal/correct at a glance, but I can't pull it into my own Mastodon server because your WebFinger at https://tap.resistant.tech/.well-known/webfinger?resource=sarah%40tap.resistant.tech doesn't currently seem to resolve, so my Mastodon server fails to put together the actor's profile. Is that known and/or intentional? Maybe it was working previously and m.s cached it?