julian@community.nodebb.org Yeah, being able to treat Mastodon and Lemmy/mbin/piefed like a bulletin board continues to feel like magic.

That instance runs Lemmy 1.0 which is still in alpha state, and the frontend is not compatible yet. So only the api works there.

Ah, yes, each previous topic needs to be federated manually. I have done this now with https://the.socialmusic.network/t/spotify-and-apple-etc-are-not-the-whole-problem/241. Please let me know if it works, and if it does I will federate the rest.

@deadsuperhero the "old" problem persists: https://the.socialmusic.network/t/testing-federation-of-new-topic-with-we-distribute/524/2?u=icaria36

Hey rimu@piefed.social thanks for responding (and sorry for the late reply!) I am not married to the Announce([Article|Note|Page]) approach, so I am definitely open to Create([Article|Note|Page]) with a back-reference. I think I went the former direction because there is a known fallback mechanism — the Announce is treated as a share/boost/repost as normal. However, sending the Create also is fine I think. However, do we need a backreference? In my limited research, it seems that Piefed, et al. picks the first Group actor and associates the post with that community. If I sent over a Create(Article) with two Group actors addressed, could Piefed associate the post with the first, and initiate a cross-post with the remaining Group actors? Secondly, is how to handle sync. 1b12 relies on communities having reciprocal followers in order for two-way synchronization to be established. On my end since I know it is cross-posted I will now send 1b12 activities to cross-posted communities, but can Piefed, et al. send 1b12 activities back as well, in the absence of followers? cc andrew_s@piefed.social nutomic@lemmy.ml melroy@kbin.melroy.org bentigorlich@gehirneimer.de

לאצי the usernames work fine locally (that is, on the site itself). It's when interoperating with other sites not running NodeBB where there are issues, it seems

projectmoon@forum.agnos.is I will 100% be working on addressing all three of those use cases. I'll rework it into my cross-posting functionality Relay support is on the list (awaiting NLNet funding) Auto cross-posting perhaps? (If uncategorized, it would just categorize it)

trwnh@mastodon.social before, I was not sending Accept at all, now I am sending application/jrd+json. FWIW testing with cURL showed the same Bad Request with application/json.

@julian@community.nodebb.org It would be good for outgoing posts if cross posting is used for synced categories. But it doesn't solve the problem of incoming posts. For that, it would make sense to still slot incoming posts based on the sync setup. But there is still the problem of Lemmy not accepting follows from category actors.

A little semantics thing: I'd argue that HTTP 410 and as:Tombstone are semantically equivalent, i.e.an as:Tombstone should always be served with the HTTP 410 status, andA HTTP 410 status should be treated as a tombstoneSoftware unaware of tombstones will then treat it as a hard delete. "Fully" tombstone aware software can then use logic likeif (status == 200 && contentType is as2) { // treat as normal} else if (status == 410 && contentType is as2 && in body.type) { // also treat as normal} else if (status == 410) { // synthesize a tombstone} else if (status == 404) { // hard delete?} else // existing error handling logic

@pfefferle@mastodon.social just wanted to poke you about this issue again. The latest updates to NodeBB now do a webfinger backcheck to ensure that the actor has a valid webfinger entry for their purported handle. If it does not, then the user is not properly created. Mastodon also does this. This check is probably for security as well as for preventing handle collisions. The multilingual plugin in conjunction with the ActivityPub plugin creates users that share the same handle, and that causes issues with federated content. For example, this article by @jonvt@vivaldi.com will load up just fine in Mastodon, but this japanese article by @akira@vivaldi.com will not, because that second article's attributedTo is https://vivaldi.com/ja/?author=176, which fails that check (the author's ID is actually https://vivaldi.com?author=176 as per the handle backcheck) cc @AltCode

thisismissem:This sounds like a wonderful FEP! This article published two weeks ago mentions the issue (highlight mine) ..Another example I personally encountered was a frustrating issue while implementing ActivityPub for this blog: updating a post propagated to Lemmy but not Mastodon. Despite the Update activity being accepted, Mastodon silently rejected it unless the updated timestamp changed—a logical but unofficial requirement. Developers must track down subtle implementation details that aren't formally documented, significantly complicating adoption and usage.https://chrastecky.dev/technology/activity-pub-the-good-the-bad-and-the-uglyI'd write it off as a Mastodon-ism, but it's actually better to have that property present, so now it is.So one that's becoming de-facto standard. Ideally if Mastodon introduces such logic, it is up to them to remember to inform the broader developer community via a FEP.---Aside: "If all we have is a Note .. "Overall it is such a pity that everything is to be a Note or else.. And the default pragmatic urge of most devs is to assign app-specific business logic to an existing or custom property within it, to create all the behavioral flavors. And then call it a day "my app works" and throw the protocol decay out in the ecosystem.There are other improvements regarding revision control as long-time open issues, see e.g. @trwnh's https://socialhub.activitypub.rocks/t/exposing-edit-history-via-activitystreams/2930 (mastodon issue # dd. January 2023). In this issue @stevebate suggests previousversions from the ForgeFed Vocabulary.What do we do when we "Edit a Note"? Is using the CRUD of ActivityStreams really the best option, or are we really "Creating a Revision". Shouldn't ActivityPub have a proper way to Revision Control across the board?If my new Fediverse app included both editable and non-editable posts, how I'd hack that in on top of the current mechanism? Just pondering this. It seems we go out of our way not to use the extension mechanism of ActivityPub as it was intended to be used, cramming everything in NoteCrud​. Is that official best-practice for the future fediverse now, I wonder.Many more examples seen in discussions. The ActivityPub specs state that you may ditch JSON-LD for plain JSON, but doesn't say that the whole idea of a semantic type model should be thrown out of the window as well. In https://socialhub.activitypub.rocks/t/distinguish-between-posts-and-direct-messages/2283 the example is people going out of their way not to define ChatMessage in favor of Note + property-logic.