this post was submitted on 31 Jan 2026
48 points (96.2% liked)
Fediverse
41329 readers
170 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Right, but I don’t want to enter the isbn to say that I’m reading a book, I want to search by title or author. Once you achieve any kind of scale, whoever your client is querying to get the book data for those kinds of queries is going to block you; practically speaking you need to keep an index of books on your server to allow people to discover the books that are available? Clients have pretty limited abilities in practice, because there aren’t a lot of services that vend well-curated data for free.
Edit: I’m not trying to disagree, I’m seeking to understand because it is clear you have a vision that I haven’t got my head around.
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 main difference is that the client would only use json-ld and not HTML.