Duplicating the object would mean the discussion is split between objects. The ideal implementation would be the same object present in multiple categories/communities. Is there desire for this in the threadiverse? If the link goes to a controversial news article and it's get posted into pro- and against- community/group the comments will spiral out of control and it won't be a pleasant place. Maybe it could be implemented as a toggle per group/instance within one fedi software. It shouldn't be in Activity Pub protocol.

@renchap@oisaur.com how does RFC9421 differ from Mastodon's existing support for HTTP Signatures? Does this mean you're moving away from cavage-12? That's important to know, and if you're looking for an implementor to handle double-knocking, that is something I can put together for you.. we don't do it at current.

@mastodonmigration@mastodon.online while this is a known workaround, I don't think it's a tenable long-term solution. You can have "real decentralization" without the quirks, too.

@trwnh@mastodon.social yes, it is in regards to audience no longer being sent out by Lemmy. While it's defined in 1b12 it seems to be ancillary now, so updating that property would mean Lemmy would need to add support for it back.. not the end of the world.

@obenland@mastodon.social wonderful, good work!

@julian yes we've had this for 6+ months

@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