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

WebRTC Browser-to-Server Blog Post #7

Closed
p-shahi opened this issue Nov 22, 2022 · 10 comments · Fixed by #18
Closed

WebRTC Browser-to-Server Blog Post #7

p-shahi opened this issue Nov 22, 2022 · 10 comments · Fixed by #18
Assignees

Comments

@p-shahi
Copy link
Member

p-shahi commented Nov 22, 2022

A blog post detailing WebRTC Browser-to-Server

@mxinden
Copy link
Member

mxinden commented Nov 24, 2022

@ddimaria would Little Bear Labs be interested in collaborating on this?

@ddimaria
Copy link
Contributor

ddimaria commented Dec 5, 2022

Sorry, I didn't see this come in my email. I'd love to collaborate on this ❤️

@ddimaria
Copy link
Contributor

ddimaria commented Dec 5, 2022

Let me know if you want to plan async (here or on Slack), or want to jump on a Zoom to start this.

@p-shahi
Copy link
Member Author

p-shahi commented Dec 8, 2022

@ddimaria there's a draft of the WebTransport blog up for review: https://github.com/libp2p/blog/pull/11/files#diff-d40abce954ad7025240faa602cca02d702fc4478aa933ef68a4331a1ae2f4a62

I think that post is one example of what the WebRTC article can look like (doesn't have to be the same structure though.)
It still needs review and updated diagrams but let me know what you think.

@ddimaria
Copy link
Contributor

ddimaria commented Dec 8, 2022

I like the flow of the post...very logical layout. When you get to the second part, it feels less like a blog post and more of a README, but that could be stylistically appropriate for an engineering-only audience.

@ddimaria
Copy link
Contributor

ddimaria commented Dec 9, 2022

@p-shahi I can start the first draft of the WebRTC equivalent, as well as follow the WebTransport format for consistency. Is there anyone you'd like me to collaborate with on the PL side (perfectly fine doing it solo as well)? Process-wise, would you like me to push to that repo, or did you want a first draft elsewhere prior to adding it?

@mxinden
Copy link
Member

mxinden commented Dec 13, 2022

@p-shahi I can start the first draft of the WebRTC equivalent, as well as follow the WebTransport format for consistency.

Sounds good.

Is there anyone you'd like me to collaborate with on the PL side (perfectly fine doing it solo as well)?

I will help and review.

Process-wise, would you like me to push to that repo, or did you want a first draft elsewhere prior to adding it?

No preference. I would have done a pull request against the libp2p/blog repository. That said, e.g. a Google Doc should work as well.

Thanks @ddimaria. Please open for feedback as early as possible. Happy to help guide an early draft.

@p-shahi
Copy link
Member Author

p-shahi commented Dec 13, 2022

Thanks @mxinden and @ddimaria

I like the idea of creating a first draft not as a pull request. It allows for quicker iteration imo
My preference is actually to use hackmd.io instead of Google Doc though. Everything will be Markdown by default and rendered as we expect (saving some time converting Google Doc to MD)

Once we get most of the content & structure agreed on in the hackmd doc, we can create a pull request for wider review.

I'll also kick start the process with our design team to get a blog post header and diagrams. A useful exercise here will be to create connection and flow sketches for WebRTC like we did for WebTransport

@ddimaria
Copy link
Contributor

That works @p-shahi! Are you able to create a HackMD document and invite me to it?

We can create interaction diagrams that auto-gen image files. The design team can take those and polish them.

@p-shahi
Copy link
Member Author

p-shahi commented Dec 13, 2022

Are you able to create a HackMD document and invite me to it?

Sent on slack 👍

@p-shahi p-shahi linked a pull request Dec 20, 2022 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants