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

Implement selective sync #486

Closed
csuwildcat opened this issue Aug 28, 2023 · 4 comments
Closed

Implement selective sync #486

csuwildcat opened this issue Aug 28, 2023 · 4 comments
Assignees
Labels
feature New feature or request

Comments

@csuwildcat
Copy link
Member

No description provided.

@csuwildcat csuwildcat converted this from a draft issue Aug 28, 2023
@thehenrytsai thehenrytsai added the feature New feature or request label Sep 7, 2023
@csuwildcat csuwildcat moved this to Backlog in Web5 Roadmap Sep 12, 2023
@csuwildcat
Copy link
Member Author

Liran to consider application of selective sync for propagation pulls.

@csuwildcat csuwildcat moved this from Backlog to In Progress in Web5 Roadmap Oct 3, 2023
@csuwildcat
Copy link
Member Author

Liran to provide update next week after group chats.

@csuwildcat csuwildcat moved this from In Progress to Needs Review in Web5 Roadmap Nov 14, 2023
@csuwildcat csuwildcat moved this from Needs Review to Backlog in Web5 Roadmap May 31, 2024
@csuwildcat csuwildcat moved this from Backlog to In Progress in Web5 Roadmap Jul 29, 2024
@johnandersen777
Copy link

johnandersen777 commented Aug 22, 2024

Just FYI, have been working on some IETF SCITT policy engine based patterns for evaluation of GitHub Actions schema based workflows which load data for evaluation leveraging content addressable ontologies. This work is still in early stages but the intent I believe is the same as DWN propagation evaluation.

The goal is that nodes federating will dereference manifests which declare the admission control/ registration policy (defined by workflow objects) by which a new data event was accepted to be federated within a particular feed / context.

Nodes can then propagate events by feed / context and leverage existing trust relationships to determine if policy re-evaluation or additional context dependent validation is needed.


SCITT Federation as firewall demo: https://github.com/scitt-community/scitt-api-emulator/tree/64cc40e269feba5cec8fb096d0ba648e921b6069

SCITT Federation as Firewall

@thehenrytsai
Copy link
Contributor

This is done.

@github-project-automation github-project-automation bot moved this from In Progress to Done in Web5 Roadmap Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants