Catodon federating deletes of objects it doesn't own

Hey @panos@catodon.rocks, now that I'm tracking errors encountered, I've got a bit more visibility into things that normally would've just been caught and ignored.

Today I received a Delete(Object) from Catodon associated with a user from catodon.rocks.

Two things:

1. Its object referenced an item outside of catodon.rocks, and so it failed NodeBB's actor-object match check. Normally people can't delete other peoples' posts, so I think this might be a mistake?

2. The activity's audience matches the activity's attributedTo. While you're certainly allowed to put anything you want in there, threadiverse software uses it to point to a group actor. Wondering if this was intentional.

Thanks!

@panos@catodon.rocks I was wondering if maybe there was some group-actor shenanigans going on

@panos@catodon.rocks sure thing. I thought we did handle it but it's been awhile. I'll take a look!

@panos@catodon.rocks handling of Announce(Delete) is merged (but untested across real 1b12 generators)... do you mind doing a quick test?

@panos@catodon.rocks Thanks.

1. Fixed
2. Defer, not sure how to handle at the moment.
3. N/A, when an Announce(Create) arrives, NodeBB makes a call out to retrieve the object again, so if a Create arrives after a Delete, it won't be added.
   • We call the low level delete because it's an internal deletion. We don't need to call the api delete because that federates activities out. I don't expect your LLM to know this.
4. Fixed.
5. Fixed.
6. Fixed.