I’ll reply in the comments with a example of what lemmy sends for each thing you can do (I think I’ve thought of everything, but you can probably guess the format if not, or I can always add it).

So, the setup for these is:
Our instance is called ‘local.com’
Our user is called ‘freamon’
The other instance is called ‘remote.com’
The community on that instance is called ‘interesting’

For many of these, remote.com will receive them, and rewraps them in an Announce to send out to all the other instances with a copy of the community, so everyone stays in sync.

Sort by ‘Old’ for the best hope of these making sense.
I’ll follow this post up with a script, that can be used to send these activities from the command-line, as I think it can help to understand Lemmy if you’re using something much simpler than Lemmy to do some of things Lemmy does.

EDIT: As nutomic as mentioned, a better list is in the docs. It’s the kind of thing I should read first, I guess.

  • maegul (he/they)@lemmy.mlMEnglish
    3·
    9 months ago

    Yea but repetition legitimises! (A reference/joke BTW)

    Seriously though @freamon@endlesstalk.org , how are you deriving all of these? From theoretical understanding of what should happen or actual observations of a test system?

    • freamon@endlesstalk.orgOPEnglish
      4·
      9 months ago

      Observation, mostly. Also guesswork and trial-and-error, because I never realised these were all in the docs.

      The comments in here are from me running lemmy in a VM, and subscribing to a fake community on a VPS (you can mimic a community with a webfinger response and a bunch of static files). The activities sent by lemmy just went to a basic server, that dumped out the JSON files it received.

      I mostly made this post so I could point to something when posting about a Ruby script that can be used to interact with lemmy from the command line. This provides the opportunity to learn about ActivityPub, separate from the more complicated applications that currently implement it.