@jupiter_rowland@hub.netzgemeinde.eu if you're seeing Hubzilla backfill "bit by bit" it is likely doing inReplyTo traversal, which is what NodeBB does if it cannot find a resolvable context.
@david@weaknotes.com in what way, that the category is cleared out regularly? I think that happens often already with users auto-deleting their posts.
https://activitypub.academy is another example of a test instance that is regularly cleared.
Either way I take no offense if try.nodebb.org gets blocked here and there
@freamon thanks! Happy to look into handling Create(ChatMessage)... I think the error aside, NodeBB would drop it anyway since ChatMessage isn't an expected post type.
Okay, now I am not sure. There is no valid webfinger response for renchap@socialhub... so perhaps there is no local SocialHub account.
I wonder why that post had a green AP logo then.
> Doesn't this mean Mastodon users et al will no longer get boost notifications when their posts are reshared into a topic?
Correct, only OP will be shared. Unless I am mistaken this is how Lemmy implemented it. Announce-ing activities only, and one single Announce(Note) for compatibility with Mastodon.
@trwnh@mastodon.social there is, and it'd work in this case. The issue is that as the condition is evaluated, if it doesn't resolve to boolean true, then the case won't execute.
In the example above it resolves (in JavaScript, anyway) to "bar"
@deadsuperhero@social.wedistribute.org @atomicpoet@atomicpoet.org we use the same synchronization mechanism that PieFed and Lemmy use, FEP 1b12.
Let me know if the follow doesn't take for whatever reason.
@deadsuperhero@social.wedistribute.org glad to hear it!
I'm planning to continue working on improving our ActivityPub integration in 2025, hopefully with NLNet funding again
@trwnh@mastodon.social given that one way a context collection is discovered is via reference via a collection member itself, that's one way to define it.
Admittedly, direct access to a context collection is also a legitimate use case (e.g. a NodeBB topic URL itself is the context collection), so something more explicit might be required.
@trwnh@mastodon.social correct. I suppose the easiest way to communicate permission would be that the thread deletion has to come from the context owner. In my case the context owner is a category, so it'd be federating out the deletion on behalf of the moderators.
