Conversation

Notices

1. Embed this notice
   Christine Lemmer-Webber (cwebber@social.coop)'s status on Thursday, 21-Nov-2024 05:27:58 JST Christine Lemmer-Webber

   Did you know you can use ActivityPub with static site generators? Well anyway, we made space to help ensure it's possible during the standards process! This is one reason there are two fields in ActivityStreams, both `id` and `url`, and ActivityPub supports both

   So you can have a static site and have an AP account which aggregates said posts, allowing users to use simple static sites but offload the pubsub work

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 21-Nov-2024 05:27:55 JST Evan Prodromou

     in reply to

     @cwebber I think you can get pretty far with building ActivityPub objects and even with readable streams but I don't think you can handle POST requests and the side-effects of different activity types with a static site.

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Thursday, 21-Nov-2024 05:27:57 JST Christine Lemmer-Webber

     in reply to

     I've seen a few "activitypub for static sites" implementations but haven't looked at if they did it the way we had talked about during the SocialWG tho

     (We never expanded on it super far, would love to see an implementation)

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 21-Nov-2024 05:33:29 JST Evan Prodromou

     in reply to

     @cwebber I think you could definitely host a ton of things like vocabularies for music or geography or whatever, and not actually have any inboxes or outboxes for them. So they'd be useful data repositories, but not really good for interactions.

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Thursday, 21-Nov-2024 05:33:30 JST Christine Lemmer-Webber

     in reply to

     • Evan Prodromou

     @evan Well that's the part that gets hosted out to the "AP provider" https://social.coop/@cwebber/113517165291965271

     But yeah the static site itself wouldn't handle the inbox/outbox or federation. Really, a way to look at it is that we left space in the spec to permit aggregation this way

     Or at least, I remember that being discussed IRL at one of the meetings and was the reason I decided I was good with both id and url being supported as separate AS2 properties

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 21-Nov-2024 05:35:23 JST Evan Prodromou

     in reply to

     @cwebber Oh, yeah, I remember this.

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Thursday, 21-Nov-2024 06:01:33 JST infinite love ⴳ

     in reply to

     • Aaron Parecki

     @cwebber @aaronpk i... may or may not have something i'm working on, personally, that does basically this 🤐

     all i'll say is that Hugo recently released a feature for "content adapters", which let you dynamically "add pages" to your static site even if they're pulled from elsewhere... where "elsewhere" can mean "local json data files" or "live http api". it's pretty cool from my toying around with it. maybe by end-of-year i can show or tell a bit more...

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Thursday, 21-Nov-2024 06:01:34 JST Christine Lemmer-Webber

     in reply to

     • Aaron Parecki

     This was something which @aaronpk pushed for, and ultimately I think was right. The general idea is that your user can live off-site and have the same inbox/outbox as your posts but *aggregate* the posts from your webpage. "id" is the uri of the json-ld object that is distributed for activitypub purposes, "url" is the uri that existed on the source blogpost.

     Of course, I'm not sure if any implementations of AP actually are implemented to support this; they could tho

     Blaise Pabón - controlpl4n3 repeated this.