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

API to add a pinning bot to lunet #12

Open
Gozala opened this issue Feb 20, 2019 · 1 comment
Open

API to add a pinning bot to lunet #12

Gozala opened this issue Feb 20, 2019 · 1 comment
Milestone

Comments

@Gozala
Copy link
Owner

Gozala commented Feb 20, 2019

Goals

  • Use may want to pin data in the remote IPFS node for availability.

Proposed solution

At the moment dealing with UI is probably not the best use of our time. Instead we can create special URL pattern such that navigating to it would add a pinning bot to the lunet. e.g.

https://lunet.link/@invite/pinbot/https://mypinningbot.sh?token=apiAccessToken

Above will add pinning service with a name pinbot to the registry. On pin requests it would issue request to the provided url https://mypinningbot.sh?token=apiAccessToken and pass API access token via query argument.

Lunet will not know when user wishes to pin data there. In long term app will issue request to lunet triggering share user interaction, where user will be able to choose who (bot or person) to share with. But in the meantime we could introduce yet another URL pattern to address that e.g.

https://lunet.link/peerdium.gozala.io/${CID}@pinbot/`

Could tell lunet to load CID document into peerdium.gozala.io and pin all PUT requests into service named @pinbot.

@Gozala Gozala added this to the CRDTs PoC milestone Feb 20, 2019
@Gozala
Copy link
Owner Author

Gozala commented Feb 20, 2019

TODO

Look at the existing pinning service APIs ideally it should be possible to encode them as pinbots

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant