- cross-posted to:
- fediverse@lemmy.ml
- cross-posted to:
- fediverse@lemmy.ml
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.
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.
The data lives in both places. Your pod is all of your data held in one place. The interaction is a copy of that data sent in and out to the various social networks.
I would expect that you could adjust how much context to save around your comments. Maybe it pulls down the while thread on whatever service, or maybe just the comment you replied to with a url.
This is a bit of a deviation from the initial “Solid” concept, as that was a fully standalone controlled data warehouse that you allowed social media to access only during using the service. It was a way to have control of your data because you hold the data instead of social networks.
With the fediverse’s replication between different hosts, there wouldn’t be a way to gate this data, so the concept looks like it was adaptived. A big advantage for the fediverse? Your account is actually on you pod, not someone elses server. The data is replicated via the servers is all. You would basically be “federating” your identity with a server, not depending on it.
I don’t understand. What data do you mean for an instance?