Secure peer-to-peer code collaboration without intermediaries.
We’ve known the Radicle team for a while, and recently @abbeytitcomb was asking for more feedback on some of their plans:
We’ve invited Abbey Titcomb @abbey_titcomb to come chat with us, tell us about Radicle and their work around open source sustainability and direct payments.
https://vimeo.com/fission/radicle
Video on IPFS
Thanks @abbeytitcomb for presenting!
Fission uses DIDs as did:key – if y’all use a similar format, there is an opportunity for interop.
Our whitepaper section on identity: Whitepaper – Fission
UCAN is what @expede designed in order to handle OAuth-like scenarios with DIDs and no central server.
Also in the whitepaper: Whitepaper – Fission, plus a more high level blog post.
Documenting the idea I had about using Radicle:
What if “issues” could be implemented in the “front end” of an app?
What if Radicle used funding.yml?
funding.yml as part of default app scaffolding?I’ve also always thought that funding.yml might also be paired with FUNDING.md as a default file, and could talk about the intent of the person. e.g.
Bob maintains this library for his own needs. Donations are welcome but not necessary. Paid support or feature requests can be considered, please contact Bob if interested
Or:
Alice maintains this application as her day job. Your donations and commercial license purchases enable her to work on it full time, keep it bug free, and implement new features. Donations, sponsorships, and professional support, as well as custom development and implementation, are all available through Alice and the partners listed below.