Conversation

Notices

1. Embed this notice
   django (django@social.coop)'s status on Thursday, 25-Jan-2024 05:57:37 JST django

   Tweaking my site today, and realized again how terrible my permalink structure was when I started.

   And it’s bringing me back to a peeve about the severe limitation that is setting ActivityPub object `id` to something as flexible as pretty permalinks.

   #WordPress #ActivityPub

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 25-Jan-2024 05:57:33 JST Matthias Pfefferle

     in reply to

     @django let’s change it to ?p={id} … the tricky part is content negotiation!

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 25-Jan-2024 06:00:19 JST Matthias Pfefferle

     in reply to

     @django 🤔

   • Embed this notice
     django (django@social.coop)'s status on Thursday, 25-Jan-2024 06:00:20 JST django

     in reply to

     • Matthias Pfefferle

     @pfefferle I agree about the conneg, i think rest api might be a better choice

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Thursday, 25-Jan-2024 06:58:21 JST Matthias Pfefferle

     in reply to

     • André Menrath

     @linos @django pro API: we could simply return JSON. Con: it might be loaded in the browser and then we would have to forward an API call to the permalink… I have done that with the users endpoint and hate it 🫣

   • Embed this notice
     André Menrath (linos@graz.social)'s status on Thursday, 25-Jan-2024 06:58:22 JST André Menrath

     in reply to

     • Matthias Pfefferle

     @django @pfefferle Interesting. Hmm.

   • Embed this notice
     django (django@social.coop)'s status on Thursday, 25-Jan-2024 06:58:24 JST django

     in reply to

     • Matthias Pfefferle

     @pfefferle … activitypub/1.0/post/{id}

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Friday, 26-Jan-2024 00:54:04 JST Matthias Pfefferle

     in reply to

     • André Menrath

     @django @linos the URL property is not implemented by every platform. Micro.blog, for example, only had the ID for a long time and fed.brid.gy has a list of URLs, so it is difficult to know which one is the profile.

   • Embed this notice
     django (django@social.coop)'s status on Friday, 26-Jan-2024 00:54:06 JST django

     in reply to

     • Matthias Pfefferle
     • André Menrath

     @linos @pfefferle I was thinking the same, the spec says we can use a url property

     > url
     A link to the actor's "profile web page", if not equal to the value of id.

     https://www.w3.org/TR/activitypub/#actor-objects

   • Embed this notice
     André Menrath (linos@graz.social)'s status on Friday, 26-Jan-2024 00:54:07 JST André Menrath

     in reply to

     • Matthias Pfefferle

     @pfefferle @django But isn't that only needed due to implementations misusing the id for the url field?

     E.g., Mobilizon does not seem to distinguish between id and url atm, at least that is what my conclusion was by reading the source. But anyway I think we should push others to fix their non-spec compatibility bugs than to think of workarounds from the beginning.

     I see, I have to study the specs again, cause I am not sure about the usage of both.

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Friday, 26-Jan-2024 00:59:01 JST Matthias Pfefferle

     in reply to

     • André Menrath

     @django @linos sure, but we can not wait until every platform has implemented it and try to be as compatible as possible… as sad as it is 😔

   • Embed this notice
     django (django@social.coop)'s status on Friday, 26-Jan-2024 00:59:02 JST django

     in reply to

     • Matthias Pfefferle
     • André Menrath

     @pfefferle i agree with @linos that this should be brought to the attention of and addressed by other implementators