Post AQTLG3IYo2zi8IRNFw by tmcw@mastodon.social
 (DIR) More posts by tmcw@mastodon.social
 (DIR) Post #AQT5hYc6t073o8g72u by tmcw@mastodon.social
       2022-12-09T21:52:17Z
       
       1 likes, 0 repeats
       
       Published something about ActivityPub and my journey to getting @photos to be a Mastodon-compatible entity https://macwright.com/2022/12/09/activitypub.html
       
 (DIR) Post #AQT68nvK4Y3V6penz6 by shadowfacts@social.shadowfacts.net
       2022-12-10T15:52:48.786612Z
       
       0 likes, 0 repeats
       
       @tmcw this is awesome! I was idly thinking about doing a mostly static AP implementation with edge compute a while ago and I’m glad someone actually built it!A couple things I noticed about your implementation:This is not a safe assumption about inbox endpoints, you need to read and store the inbox property from the following actorsActors may have a shared inbox, which server- rather than actor-specific Unless I’m misunderstanding what your publish hook is doing, you shouldn’t need to send an activity for every single post on each deployment if you keep track of which ones have federated out before
       
 (DIR) Post #AQTLG3IYo2zi8IRNFw by tmcw@mastodon.social
       2022-12-10T18:20:52Z
       
       1 likes, 0 repeats
       
       @shadowfacts thanks, i'll look into that - i've been triangulating between mastodon's docs, reference impls, and the activitypub spec, and a lot of the decisions in the edge fns is simply that's what i found to work from existing implementations
       
 (DIR) Post #AQTLfRb5bJ3ijZDOfA by shadowfacts@social.shadowfacts.net
       2022-12-10T18:46:46.602176Z
       
       0 likes, 0 repeats
       
       @tmcw yeah, the state of AP standardization/interop is a lot more theoretical than practical. my experience adding AP support to my blog was a lot of tweaking things (mostly http sigs) until mastodon stopped complaining