OCapN Demo: Capricorn Server #2931
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🐐
demo of "capricorn" OCapN server that facilitates turning http based APIs into OCapN functions.
Capricorn provides an admin facet exposed as a sturdyref that allows one to create new "routes". The routes are small javascript programs that get access to node.js
fetch. The result of a route is an OCapN function that can be passed around without exposing the content of the route program. Routes can be used to expose a constrained subset of an http endpoint with an authenticating bearer token without exposing the token or rest of the api to the route.this is a proof of concept. it proved useful in sourcing caps from non-capability systems.
the name comes from ocaps + unicorn (and obviously capricorn)