I’m trying to better understand Activitypub and I understand that there’s a signature to avoid forgeries of known accounts.

However I’m having trouble understanding what prevents a malicious actor from sending a private spam message supposedly from a never before seen account name with valid generated key pair but for a domain they’ve never bought since there is no DNS lookup or test.

Thank you!

  • @WanderOPAEnglish
    1•1 year ago

    Ah, that makes sense. The server tries to retrieve the actor object from the actual url and would notice a discrepancy. That makes sense and is an easy way to implement validations.

    I was wondering if I could ask you something else related to activity pub since you seen knowledgeable in the matter. I’ve been going over these all day and haven’t been able to find a good answer:

    1. My understanding is that a create activity doesn’t need to have the content itself in the message since JSON-LD exposes the permanent uri in the id property and the receiving server can then make a subsequent request for the content.

    Is there a consensus on which approach is better and what would happen if the content field in a note is different from the content that would be fetched by a url?

    1. I’ve seen that groups are implemented by doing announces. In theory announces could be private based on the view permissions of the original activity. Does that mean that we could potentially have private Lemmy communities at some point?

    In that regard, I was wondering if it’s possible for an organization or group type actor to forward the activity not with announces but by simply delivering the content to the user’s inbox in a transparent manner, similar to an email distribution list.

    Thank you <3

    • terribleplanEnglish
      1•1 year ago

      1. I think implementations often embed the the content into the activity to prevent the need for the receiving instance to immediately connect back to you to fetch the activity in the case of something like create or update. I think it is a bit more unclear whether that makes sense in the case of something done that doesn’t modify the object like such as Like, Announce, etc. (possibly even Delete) and probably makes sense to only include it by reference. AFAIK it is entirely up to implementation and I don;t know of a consensus.

      2. I am unsure on that one… You can certainly target a Delivery. I am honestly a bit confused as to the choice to use Announce at all for Lemmy, as I was expecting “communities” to work through some sort of Collection shenanigans. You can target a Collection of Actors via a Delivery, such as the followers collection. You could manage the collection Using an Offer (request to join a community) and Accept pattern. Certainly seems possible with AP, unsure how easy/hard it would be in Lemmy.