Skip to content
  • Categories
  • Recent
  • Popular
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

NodeBB-ActivityPub Bridge Test Instance

  1. Home
  2. Categories
  3. General Discussion
  4. AP Test (community.nodebb.org)
  5. Bulk announce via 1b12

Bulk announce via 1b12

Scheduled Pinned Locked Moved AP Test (community.nodebb.org)
1b12fepthreadiverse
2 Posts 1 Posters 56 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • julian@community.nodebb.orgJ This user is from outside of this forum
    julian@community.nodebb.orgJ This user is from outside of this forum
    julian@community.nodebb.org
    wrote on last edited by
    #1

    I have a clarification question for @nutomic@lemmy.ml regarding 1b12. There are instances where a group actor may have occasion to announce multiple notes all at once. For example:

    1. New notes discovered while traversing upwards to root — may want to announce all parent notes
    2. An existing topic/thread (containing a variable number of notes) is assumed by this group actor (e.g. it was moved to the category/forum).

    What would be the expected behaviour from an implementor in that scenario? A single Announce(Collection)? Multiple Announce(Note) in chronological order?

    During our testing, @angus@socialhub.activitypub.rocks
    did warn me that a collection was announced, and that caused issues because NodeBB's implementation didn't (and still doesn't) account for that. I believe he changed up the behaviour now.

    @trwnh@mastodon.social, Angus did mention offline that you warned him about this in the past!

    julian@community.nodebb.orgJ 1 Reply Last reply
    0
    • julian@community.nodebb.orgJ julian@community.nodebb.org

      I have a clarification question for @nutomic@lemmy.ml regarding 1b12. There are instances where a group actor may have occasion to announce multiple notes all at once. For example:

      1. New notes discovered while traversing upwards to root — may want to announce all parent notes
      2. An existing topic/thread (containing a variable number of notes) is assumed by this group actor (e.g. it was moved to the category/forum).

      What would be the expected behaviour from an implementor in that scenario? A single Announce(Collection)? Multiple Announce(Note) in chronological order?

      During our testing, @angus@socialhub.activitypub.rocks
      did warn me that a collection was announced, and that caused issues because NodeBB's implementation didn't (and still doesn't) account for that. I believe he changed up the behaviour now.

      @trwnh@mastodon.social, Angus did mention offline that you warned him about this in the past!

      julian@community.nodebb.orgJ This user is from outside of this forum
      julian@community.nodebb.orgJ This user is from outside of this forum
      julian@community.nodebb.org
      wrote on last edited by
      #2

      Ah it looks like this was covered by Angus' post over on SocialHub

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Popular