Robert Mustacchi

That was a, I think, I guess I think to, to, to begin, I think there's, there's, there's something around like the accessibility of this stuff. Oxide has always been like, um, really kind of engineering driven. Um, and engineers are really familiar with GitHub and that's really easy for them.

That was a, I think, I guess I think to, to, to begin, I think there's, there's, there's something around like the accessibility of this stuff. Oxide has always been like, um, really kind of engineering driven. Um, and engineers are really familiar with GitHub and that's really easy for them.

But, uh, I think if you want this process to be used outside in kind of like kind of sales and operations and, and, and, and design, then, um, really, you have to make this stuff as accessible as possible. And we're not there. And I think we're working towards it. But getting GitHub discussions directly into the RFD site felt like a big step towards that.

But, uh, I think if you want this process to be used outside in kind of like kind of sales and operations and, and, and, and design, then, um, really, you have to make this stuff as accessible as possible. And we're not there. And I think we're working towards it. But getting GitHub discussions directly into the RFD site felt like a big step towards that.

Essentially, what's nice about the GitHub discussions is you're leaving line comments. And one great feature of our ASCII doc is that you can trace you can kind of, given a line in an ASCII doc document, you can get the, no, in the return, in the render document, you can get the associated line number.

Essentially, what's nice about the GitHub discussions is you're leaving line comments. And one great feature of our ASCII doc is that you can trace you can kind of, given a line in an ASCII doc document, you can get the, no, in the return, in the render document, you can get the associated line number.

So what it meant is we could query the GitHub API, get all of the comments, kind of collect them in,

So what it meant is we could query the GitHub API, get all of the comments, kind of collect them in,

kind of a format that can be kind of rendered easily which which is which is pretty kind of tricky to begin with um and then we go through sort of line by line and and we we position them alongside the content directly if they're still relevant um and then we have this sidebar which kind of you can see the kind of full canonical discussion and you can kind of jump to the the relevant part um but yeah just that little bit of kind of being able to associate the original

kind of a format that can be kind of rendered easily which which is which is pretty kind of tricky to begin with um and then we go through sort of line by line and and we we position them alongside the content directly if they're still relevant um and then we have this sidebar which kind of you can see the kind of full canonical discussion and you can kind of jump to the the relevant part um but yeah just that little bit of kind of being able to associate the original

document with the rendered document uh was enough that we could pull like from the api people's avatars and we can kind of have this little this module that people can click on and can and and and view um yeah and i think my kind of first experiment was this super ugly way of getting like a little avatar alongside the text but that yeah that felt kind of a real um kind of a huge improvement

document with the rendered document uh was enough that we could pull like from the api people's avatars and we can kind of have this little this module that people can click on and can and and and view um yeah and i think my kind of first experiment was this super ugly way of getting like a little avatar alongside the text but that yeah that felt kind of a real um kind of a huge improvement

Because one of the reasons to do that is the longer the discussion, the longer the response takes. So I think there's one RFD, something to do with time. And yeah, why would that have lots of comments? RFD 34. And it crashed. It crashes every time, I think, because I think it basically timed. Oh, no. Oh, wow, this worked. What a miracle.

Because one of the reasons to do that is the longer the discussion, the longer the response takes. So I think there's one RFD, something to do with time. And yeah, why would that have lots of comments? RFD 34. And it crashed. It crashes every time, I think, because I think it basically timed. Oh, no. Oh, wow, this worked. What a miracle.

But essentially, the more comments, the longer the response takes. And so I think there's some kind of funkiness in the GitHub API, which is, yeah. We do have something where essentially we serve the regular rendered version of And then David might want to talk a little bit about this, but there's a Remix feature.

But essentially, the more comments, the longer the response takes. And so I think there's some kind of funkiness in the GitHub API, which is, yeah. We do have something where essentially we serve the regular rendered version of And then David might want to talk a little bit about this, but there's a Remix feature.

Remix is the framework that we're using to do all this, where you can stream data from the server later on. So what we do is we give you the main document first, because that's important. And then later on, asynchronously, we give you the comments, just so that's not holding up the ..

Remix is the framework that we're using to do all this, where you can stream data from the server later on. So what we do is we give you the main document first, because that's important. And then later on, asynchronously, we give you the comments, just so that's not holding up the ..

And then your mileage may vary on the actual GitHub portion.

And then your mileage may vary on the actual GitHub portion.