-
Notifications
You must be signed in to change notification settings - Fork 40
feat: Blog post about custom transports in general and the tor custom transport in particular #423
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Add first graphics
ramfox
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Some nits for grammar!
|
|
||
| Implementing a custom transport is not quite as simple. But it also isn't extremely complex. Dealing with the quirks of the actual transport will certainly be more work than wiring it up into iroh. | ||
|
|
||
| The custom transport API consists of a number of dynable traits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The custom transport API consists of a number of dynable traits. | |
| The custom transport API consists of a number of dyn-able traits. |
I think this is how I've seen it written before, but feel-free to ignore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
works for me.
ramfox
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Some nits for grammar/punctuation!
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Co-authored-by: ramfox <kasey@n0.computer>
Implements #424