Conversation

Notices

1. Embed this notice
   marius (mariusor@metalhead.club)'s status on Friday, 15-Aug-2025 21:21:48 JST marius

   I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)

   An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).

   Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)

   #ActivityPub #fedidev #ActivityPubDev

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Friday, 15-Aug-2025 21:21:45 JST Evan Prodromou

     in reply to

     @mariusor it's not easy; the ID is really where the thing is, as well as what it's named.

     We have some work going on it; try LOLA.

     https://swicg.github.io/activitypub-data-portability/lola

   • Embed this notice
     marius (mariusor@metalhead.club)'s status on Friday, 15-Aug-2025 21:21:47 JST marius

     in reply to

     Is anyone aware of a FEP for that?

     #ActivityPub #ActivityPubDev #FEP

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 16-Aug-2025 02:05:44 JST silverpill

     in reply to

     @mariusor Move is used for migrating actors from one ID to another: FEP-7628. It can be used for migrating objects too, but I don't think it's practical.

     FEP-ef61 solves the problem by making identifiers portable.