@steve@social.technoetic.com is vibe coding ActivityPub in C++ and this is making me feel unsettled When will Claude join the Forum and Threaded Discussions Task force? Eagerly awaiting...

@beaware@mementomori.social @andypiper@macaw.social as I heard from Peter directly, the legal issues also come from internal pressure. Fediverse integration implies giving up control over content, and that's a huge pill to swallow for a company that is literally described as a data silo.

@jsit@social.coop that's fair, it's late! As an advocate of long form content on the open social web I'd love to chat about it. There might be some things we can learn!

@jwildeboer@social.wildeboer.net Right, there's a possible social engineering vector at play here, which I think makes this a little concerning. I certainly don't like my time wasted either cc @thisismissem@hachyderm.io @mariusor@metalhead.club

@osma@mas.to the default assumption is that announces are delivered back to the origin server in order to close the loop. However it is not a requirement. For example I am considering not doing so for group announces.

@OddDev At least since a year ago. I found my old toot about it https://floss.social/@carlschwan/111794187164928611

@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.