Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subdomain clones #25

Open
gsvarovsky opened this issue Aug 28, 2020 · 1 comment
Open

Subdomain clones #25

gsvarovsky opened this issue Aug 28, 2020 · 1 comment
Labels
feature A major, next-level feature investigate Extra attention is needed

Comments

@gsvarovsky
Copy link
Member

gsvarovsky commented Aug 28, 2020

what

Ability to clone only some sub-set of a domain.

why

Full replication on all clones restricts usage of m-ld to use-cases in which the entire domain fits on every deployment platform involved, including smartphones and browsers.

Without this restriction, a domain can have arbitrary size.

See also:

  • Ditto has 'big peers' (servers) and 'small peers'.
  • GUN has unstepped local graph cache size.
  • Col-Graph (from the makers of SU-Set)
@gsvarovsky gsvarovsky added the investigate Extra attention is needed label Aug 28, 2020
@gsvarovsky
Copy link
Member Author

https://gitter.im/m-ld/community?at=615db9d08c019f0d0b1d0cad:

BTW, I've been pondering something that may be related to Confidentiality. I may be interested in making much more data available in a domain than any once clone will need at any one time. I'm thinking it may be useful to be able to hold a "sparse clone" which only includes relevant triples, much like a git sparse clone. (It would be neat to do that by query, but that might be too powerful and lead to weird cases, so maybe by triple pattern? Or some new thing in between?)

If I'm really going all out asking for things, I'd love to be able to query against a sparse clone with some sort of useful semi-closed-world assumption, and be told whether I have all the relevant data, or whether there's potentially more data that wouldn't be matched by the sparse filter that I could be missing. I haven't thought that through nearly enough to understand whether that's even a sensible thing to want, though.

@gsvarovsky gsvarovsky added this to To do in m-ld backlog Jan 24, 2022
@gsvarovsky gsvarovsky added the feature A major, next-level feature label Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A major, next-level feature investigate Extra attention is needed
Projects
Development

No branches or pull requests

1 participant