- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
ActivityPods is a wild project that’s bringing the architecture and data capabilities of Tim Berners-Lee’s Solid Protocol to the Fediverse. We dig in to what it is, how it works, and what’s currently possible with the framework.
You must log in or # to comment.
@deadsuperhero
Exciting times!!Oh heck, that sounds promising. 😺
What ActivityPods effectively provides are automated mechanisms. They constantly check the contents of the Solid pod, and are notified whenever a change gets made.
Let’s say you’ve just made a post with your Fediverse app: a document representing a post is written in the Pod, then a dispatch mechanism acts as the user’s outbox and sends the activity out. Meanwhile, the corresponding inbox mechanism waits for replies.
What this could mean in practice is that editing a Fediverse post may be as simple as editing a corresponding file, while a mechanism pushes out an Update activity through your Outbox to make changes on the network.
I think I need an even more higher level explanation of Solid & Solidpods, but so far that sounds cool!
Would the data still live on your instance’s server or on user devices? If it’s the latter, how would it work if some people have really slow connections, or lose internet all together.
IIRC your data would live on your chosen pod server - which does not have to be a fediverse instance.
IIRC, Damon is working on a platform built on this right? Made a decent amount of progress?
They have a community: https://lemmy.world/c/memory
Yes, we have an article in the works about it. 😁
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
Cool. I’ve been hoping for solid pods to be widely adopted for sooo long now ;-P
