And a followup question: wouldn’t it be more efficient for big instances to use WebSockets to federate? Making a HTTP request for every action your users take seems unnecessarily wasteful.
And a followup question: wouldn’t it be more efficient for big instances to use WebSockets to federate? Making a HTTP request for every action your users take seems unnecessarily wasteful.
Amazing blog post! Been reading the ActivityPub spec and found it rather lacking. It’s only when you add WebFinger and signed messages that things start to make sense.
Same here (love Pages and Workers). Just wish their support for top level country domains (particularly .be for me).
I’ve started using it a couple of weeks ago. For now, I’m having it capture emails with invoices and moving the PDFs to a folder in my Google Drive.
From my experience, the electricity consumption of e-bikes is low. We have a Babboe cargo bike and we drive 5km every day. I measure the electricity consumption of the charger, and it comes down to 0.5-1kWh per month. I assume regular e-bikes have an even lower consumption.
I live in a small town in Belgium and we have a saying that says: “there’s no bad weather, only bad clothing”. Granted, the weather here is mild. Doesn’t get too cold, not too hot (except for this week). We do get a lot of rain though, but nothing that a pair of rain trousers and coat can’t handle ;)
These posts are really useful to get a grasp of ActivityPub (if you have a programming background): https://rknight.me/building-an-activitypub-server/ https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/
And of course the official spec (although its less useful): https://www.w3.org/TR/activitypub/