IPFS Core Implementations Weekly, 22 Jul 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 🚀 IPFS Core Implementations Weekly Sync 🛰 2019-07-22

Description

Notes: https://cryptpad.fr/code/#/2/code/edit/2t74pnRUv3doU1lRVNqpLrb7/

A

Okay, I guess we can get started so initiatives. First, oh yeah. The principle agenda. Okay, initiatives up wait to go up first, release process. This is me. We have entered into stage two release process for encoder chef. S is your book which Mike we already have early testers running it in deaf deployments. We will probably enter stage three next week. Assuming nothing goes weird where the testing process also may then Russell assistant team.

A

We now have regular meetings. Every Wednesday, 18 PST here at the to local timezone Allen, is currently reviving Ibis benchmarks and then we're gonna try getting go testing as well. This is currently this is built in JavaScript, but they can work with both. I roland has done some architecture. Design work for the test lab I and jim has done a bunch of work I for like UI mock-ups. We still need to like make sure we seem to be mean. Thank you.

A

We're gonna, pull it now at that meeting and sync up on like what this benchmarks currently does, because we can probably reuse some instructors. Some of the UI I, depending on like the test, we're going to run I'll hand it off to whoever wants it about championing adjacent. Yes,.

A

This might have been an ally doing.

B

Great, like it is a Dirk yeah I can talk about that, and so basically we're trying to just kind of close out that garbage collection, PR, that's been running for quite a while now and so with Alan I was talking about it and we thought it would probably be best to try to get something something out there, because it was kind of like a lot of ideas about improvements that can be made to it and ways of doing it better and so we're just trying to kind of narrow down the scope to a minimum, labeled garbage collection and then poking issues for her outstanding stuff and I'm kind of splitting.

B

My time between that and ramping up on improvement like the a bad performance or go like the FS.

A

For delegated routing is that a Alan thing and Alan happens not be with us, is that's what Ellen and I.

C

Can talk about it.

D

Yeah I, can you hear me yes yep? So it's something I've been looking at for for my integration with brave. Basically, it's a nice stopgap.

D

Until we implement actually beautiful transport, we would ship embedded, Jess ipfs does delegated routing and having debugging performance deeper last week and today and basically we need to like that, there's a performance problem of how those modules are implemented right now there are no trolling and we have the limitation of how many concurrent requests we can do for single domain in web browser and also we are doing swarm Connect constantly, which is not necessary. At least we could short over some time windows. So I got some changes.

D

Luckily, that I will PR that should address that. That's a separate topic of gateway, API commands configuration option in go ipfs, not wired into anything. I talked about this briefly with Stephen that, like it's like, eventually to be worried up, but for immediate immediate need its to get those Lippe to be modules responsible for delegated routing, to the point where we can actually ship them with Jessica fest, like the current version, will just float not only the browser but also our preload nodes, toggle DDoS protection.

D

So when I decrease that the flawed it still got blocked on the other end, so we need we need to figure out box library and also configuration of our pre handle a lot of requests, because we can. We will decrease the number of requests and from individual node, but if we deploy it as a default or like as opt-in and people by default, we'll use our pre old notes, just like they did with WebSockets. Tar will quickly run into similar problems. I guess: that's like current state.

A

C

Think Bosh goes out, but he's working on I believe getting the fallback implementation finished up the base, gossip supplementation is done and I think we've got the work done for falling back to flood sub, but we need to finish up interrupt tests in for go nsj, and then we should hopefully be able to release that soon.

A

So I guess it's to make it with. No. That would be.

D

Yep I believe we sort of got a better idea how to handle this, for the local host had a thing yesterday with Stephen, we there's like a sort of clear, clear path for works for localhost isolation between subdomains and path based gateway. An unknown problem is how to handle those all those bash scripts that expect half base gateway, I mean if we suddenly start redirecting path based gateway and point to the subdomain one that will introduce HTTP redirect and a lot of scripts out there.

D

The wild are not expecting redirect and will just crash, but that's something we can mitigate by, enabling redirect only for web browser user agents. Initially mostly will like will care about origin separation, the web browsers, so that makes sense.

D

It's anything. I missed even.

A

Though this one will think you're a variant, encoding, purities series I'd like to give you look at this of course, so the people really put this recipe folks, so I guess is here, even so: no music, okay. Secondly, who are here I, yeah, basically jobless. We can you the distillate b2b and make this work for all say IDs or we can do. This are sorry all parodies or we can do this as an half of the Gateway I'd like to do it. Hello, er, just because makes it simpler.

A

So I guess next is replica solid Asian.

C

Yeah so similar to what go, let me beat core. Did I'm Ana Paula dated all those repos we're going to do some of the similar with J slippy to be core modules and then with the J's will be to be. Interfaces will join us something to be working on that this week start with the interfaces, because that's the least obtrusive thing and then work my way to KS and that'll. Probably just do a repo consolidation first, but then look at what we can do to optimize tests. Steven I.

A

Had a good concert here in Joe ffs go destined to be core, are thee, but that's the interface for echo. I want to make sure that we don't have situation where, like that's our interfaces and then GS has an inch base record core meet something totally different confusing. um So what do you mean by core? Do you mean like core primitive support like what so.

C

It will be so it's basically all of the modules that Jay s, lipid B, needs to function by itself. So add the connection manager repo, not the interfaces themselves, but the actual code we're gonna, bring the new one. Central repo is.

A

There any way we could change this around I'm just like yes, this makes sense, but it's going to really cause a lot of confusion because you go. We have all been in quark who say like this: is there all the interfaces and our like basic the instructors, like PID definitions, all that kind of stuff in this one repo? So it's like the idea is that you should build or import any lipid P implementation, but they use the interfaces in court. It's like a standard thing.

A

I'm just goes like are.

C

You just getting hung up like. Is it the naming that you're you didn't turn about it cause? You know it'll just be J slippy to be so. Will we pulling those sub modules into the libertage, a slippy tepee repo.

A

Oh okay, okay, servers like if you have a DSS for repo and it doesn't go then go just with a few desk or you know.

C

So well how it will end up with JSL of p2p, which will have those other those space, those core modules in it, and then we'll have the jeaious interfaces repo, which will have all of our our combined interfaces. Yes, okay, wonderful got it.

A

Then I guess for now on to blockers and tasks. I have one asked I said: I have a lot of one-on-ones on Mondays to distribute knowledge and have time to stick with people so that I keep this much like visible. If you want one I mean I guess next, when Hannah is wondering, if there is a JSP swap person, okay, they do exist.

A

Who is that I guess.

B

That's me: I'm the requirement in.

E

Team week, who is like I've just been brought on to do Jess bit swap I, don't know if they're so they're good.

B

I said: hey you.

B

E

Well, honestly, I just want to make sure you, if you need, if you ever need time to check in with me about like things that have happened in that you're looking to bring over to Jess ipfs bit, swap just I just want to. Let just say that I'm available, but you should be so.

B

A

Any other blockers or initiatives.

F

Now I can talk briefly about where I cast things are at right now, which is just there's in my me list down below there's a PR, that's tracking, all the pub sabaki and I stuff. There are an issue tracking all of the PRS there's four that are outstanding, that are like. Basically, there I showed a demo during drying. Ipfs camp just didn't get those over the line, and then we probably will need to start working on like these features of IPs that we have neglected because it was slow like local pinning.

F

There have been some pre-existing issues about that I linked one of them I did just. You should be able to start up your node and the same way you have 10 to content.

F

You should have 10 by pianist records, it's as simple as that, and then there's there's sort of two tangential issues like one is: maybe splitting off I can ask from ipfs, because they've been request from a number of parties about that, just being able to use that separately and then also figuring out like how much and when do we need Jesco compatibility between these things.

F

That's the current state there's any questions.

A

A

That's it unless selection of parking lot I.

A

Because I think most about that, what.

E

A

Wants to put the perk law issue.

A

Many years coming, Congrats.

E

Yes, now we just need to see it fail when production without coin I mean are like not like, you know, fix it.

A

Okay, I think that's it. I have a wonderful week. Seal.