It seems like the #ActivityPub Recommendation primarily focuses on behaviors related to *received* Activities, especially in an S2S federation context. Exceptions include inbox forwarding (7.1.2), shared inbox delivery (7.1.3), and broadcast of public ...
-
It seems like the #ActivityPub Recommendation primarily focuses on behaviors related to *received* Activities, especially in an S2S federation context. Exceptions include inbox forwarding (7.1.2), shared inbox delivery (7.1.3), and broadcast of public messages to all known servers (7.1.3). However, for specific activities, like Delete, the behavior related to sending them is unspecified (e.g. which recipients should be included and so on). Am I missing something?
-
@[email protected] I recently thought about something similar.
On a create we send the activity to all followers (and mentions' inboxes).
On an Update, however, we'd need to also notify every user who boosted, as well as their followers.
I imagine it'd be the same for Deletes.
-
@julian That's close to what Mastodon does for Status/Note deletes, except I don't think they send the activity to followers of boosters. They do send it to relays that distributed the original activity. My point was not that I couldn't imagine a way to do it, but that the ActvityPub Rec doesn't specify any expected publishing behavior for it (and similar activities). Even servers that don't publish Deletes at all are AP conformant.
-
@julian @steve @steve @tallship
Just jumping in here for a sec, I'm so elated with the level and penetration of ActivityPub support in NodeBB. There's obviously a few things that have raised a couple of issues here and there, circular loops when topics subscribe to individuals on various platforms, etc., but all that's getting worked out just fine.
Generally speaking this is a really good thing, and at least for me, I got to enjoy the experience first on #NodeBB instead of Discourse
#tallship #ActivityPub #FOSS #Fediverse
.
-
Oh yes! It wasn't #NodeBB related, actually, (sorry if that statement alarmed you, and apologies for taking so long to respond), it stemmed from an 'uncomfirmed' report I received concerning "Discourse", that if a "Topic" being followed from a #Fediverse (masto) account were to follow that masto user, there were certain issues related to loops - Why an actual #Discourse "topic" would even be enabled to follow accounts elsewhere in the Fediverse was beyond my immediate comprehension as to why it would have utility in the first place though.
Perhaps there's cases, but I see it more the other way around, with user's following topics (Like Lemmy, NodeBB, Discourse, and PieFed), and then boosting comments in those threads.
I hope that helps
.
