You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run an ActivityPub service that occasionally gets inbox deliveries activities from Guppe groups. Great! I'm not seeing a way to check authorization for them, though. They include a valid HTTP Signature from the group actor, but the activity's actor and the object's attributedTo are the original author, and I don't know that the group actor is authorized to post on behalf of them.
The most common way to authorize this kind of AP inbox forwarding is with an LD Signature. Eg this is how Mastodon does it. Any chance you all would consider including LD sigs from the original activities, if they exist?
Here's an example of an activity we received from a.gup.pe recently. It included a valid HTTP Sig by the group AP actor https://a.gup.pe/u/allstartrek, but the actor and attributedTo are https://mindly.social/users/joewynne:
Hi! Apologies if this is already answered somewhere, I didn't see it on https://a.gup.pe/ or https://github.com/immers-space/guppe/wiki/Guppe-Groups-FAQ .
I run an ActivityPub service that occasionally gets inbox deliveries activities from Guppe groups. Great! I'm not seeing a way to check authorization for them, though. They include a valid HTTP Signature from the group actor, but the activity's
actor
and the object'sattributedTo
are the original author, and I don't know that the group actor is authorized to post on behalf of them.The most common way to authorize this kind of AP inbox forwarding is with an LD Signature. Eg this is how Mastodon does it. Any chance you all would consider including LD sigs from the original activities, if they exist?
Here's an example of an activity we received from a.gup.pe recently. It included a valid HTTP Sig by the group AP actor
https://a.gup.pe/u/allstartrek
, but theactor
andattributedTo
arehttps://mindly.social/users/joewynne
:The text was updated successfully, but these errors were encountered: