Comment on Why is Pixelfed an extra network and not just a Mastodon client?
rglullis@communick.news 4 weeks agoand building an “everything server” that implements every message you might want to send is prohibitive just in terms of complexity and scope.
It is not. A server that “speaks” the ActivityPub is not that difficult to build, I’ve done it. The complexity is in getting the data from the social graph into and creating a good UX for users who are too used with the “app-centric” mentality.
CombatWombatEsq@lemmy.world 4 weeks ago
rglullis@communick.news 4 weeks ago
Not “stored on activitypub”, but each book could be represented with RDF (it could be something as sophisticated as using DublinCore or as simple as just using isbns to uniquely identity the books (
urn:isbn:1234556789) , and then each activity for “CombatWombatEsq read a book” would be an activity where you are the actor and the book is the object.CombatWombatEsq@lemmy.world 4 weeks ago
rglullis@communick.news 4 weeks ago
You know that the whole of wikidata can be copied with just a few hundreds of GBs, right? There are plenty of examples of community-driven data providers (especially in the *arr space), so I can bet that there would be more people setting up RDF data servers (which is mostly read-heavy, public data sharing) than people willing to set up their Mastodon/Lemmy/GoToSocial server - because that involves replicating data from everyone else, dealing with network partitions, etc…
Also, there are countless ways to make this less dependent on any big server, the client could pull specific subsets of the data and cache data locally so the more they are used the less they would need to fetch remote resources.
Think of it like this: a client-first application that understands linked data would be no different than a traditional web browser, but the only different is that the client would only use json-ld and not HTML.