Did you know you can use ActivityPub with static site generators?
-
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
-
cwebber@social.coopreplied to cwebber@social.coop last edited by
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)
-
cwebber@social.coopreplied to cwebber@social.coop last edited by
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
-
trwnh@mastodon.socialreplied to cwebber@social.coop last edited by
@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...