Untitled attachment

Notices where this attachment appears

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Tuesday, 05-Sep-2023 14:49:51 JST silverpill

   in reply to

   @justin These are coming from deleted actors (type == Delete and actor == object.id)

   I think HTTP signatures should be correct. The server should not try to fetch the actor, but otherwise such Delete can be processed like any other activity.

2. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Monday, 26-Jun-2023 01:21:13 JST Alex Gleason

   in reply to
   @3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d @de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645 The original object has its own globally unique ID. Eg event.id on Nostr, object.id in ActivityPub.
   
   So you expose that ID to the bridged network, and implementations can combine objects that share the same proxy ID.
   
   For AP objects bridged to Nostr, it could look like:
   
   ["proxy", "activitypub", "https://gleasonator.com/objects/123"]
   
   Clients could combine events with the same proxy ID.
   
   There are obviously problems with trust (among other issues). But I think it will be necessary to solve this problem.