 Uh, does someone want to kick off and whoever added a bot or can talk to it if they're here. Um, so D added it, but I'm speaking on his behalf. Oh, perfect. Hey, how are you guys? Um, so, uh, so I kind of know only like a little bit of the connecting dots, but someone approached Matt at KubeCon about using this bot. And it's supposed to help with finding doc links and like linking users to previously asked questions and answers. And so asking, I pretty much just bring it up to the community if we want to integrate this into the Envoy Slack channel. The only caveat is, is that it's not approved by Slack security wise. And it hasn't been approved in like at least past six, several months. So I don't know if that's a concern for us. Oh yeah. I'm the one that talked to Matt and I maintained the bot. So I was going to DS to Colin and like talk to you guys a little bit about it. So the one caveat, yeah, like that you guys mentioned is that it's not approved by security. It's not a, it's not like a thing about Slack and said, um, so like six months ago or eight months ago or something when the bot was being created, they were transitioning to a different set of tokens. The new type of security tokens. At that time, what they mentioned was that, you know, go build on this technology and then in eight months, whatever, when we approve it'll be in the store. What they actually did was after that, after like eight months of this, they kind of went back and said, actually, we're not going to do these tokens, we're going to do these other tokens. So because of that, it's not able to go in the store because these tokens. So it's, it's, it's one of those like, you know, we can battle Slack a little bit about it, but it's, we're not trying to right now it's it's that there's not really much benefit of going into the store at this point. So I mean, that's why it hasn't been approved by security, but in terms of like in every other aspect we can, I can talk about security if you guys have any, like, you know, thoughts or, or anything about it. I guess my question from security perspective, I mean, what would the install look like I assume it would basically just be a number, another member on channel who could post things. So I'm not sure that what's like, does it have an additional attack vector above and beyond what everyone else has there. The way that it's installed is that it's like actually shows up as apps, just somebody with admin permissions just grants it access to it and just uses regular off to grant permissions. It doesn't the only kind of maybe sensitive data that people assume that you that's like has is emails, we don't ask for that permission so we don't actually get any of the emails of any of the members. The only thing that we're really save time which we actually purge after 30 days. And the only thing that we do actually keep for longer than 30 days is if there's a conversation and we detect that like, somebody has a question somebody else responds to that question. We'll say like hey this looks useful to restore that so only with permission to restore. I can do a demo of like kind of that interaction and the whole interaction if you guys want if that makes it easier to kind of like set a level playing field for everybody around the product. Yeah. So do you guys see my slack channel. Awesome. So the idea here like this is my demo channel but like imagine somebody comes into the on voice like and just ask a question like hey how do I set up zone or we're routing. So what football does is it uses AI to detect the fact that somebody's asking a question, and it goes and looks through different aspects to like find the best answer. So in this case it's showing up as confluence because it's my demo but it actually just pull this out of docs. And this is coming from previous slide conversations. The message is only sent directly to the person asking that question it's not actually sent to the channel so it doesn't really pollute the channel anyway. And then we have this feedback mechanism where somebody can say that it's not helpful and this thing goes away it's helpful and so is a question or helpful answered question. And if the only kind of thing here is that if you click answer and helpful. If you click on helpful and answer question, then we'll notify the rest of the channel that this person's question is already answered. You don't have to worry about it don't have to try to answer anything else. So that's the first part of it. The second part I'm just going to kick off my demo script. So the idea here is that imagine that there's two people talking so in this case like Michael and K. So Michael asked a question K response. So what we do there is again we did so focal not only detects the question that Michael is asking but also detects the answer that K provides. And then it sends a message again only visible to K in this case it's saying to me but it would actually send it to K. And it would say like hey this looks like a useful question can we store this for the future. And then you know says like here's the question here's the answer and then she gets the, you know, she can ignore it edit the question answer and then like to provide more context or make it better whatever, and then finally store, and once you click store it becomes available as one of the central sources. Does that make sense. Sorry about that. So coming back to the original question of what were the only thing we store is the, like the thing where. Often my phone calls come first to my computer and then I can't do anything about it. Also sadly. Yeah I think going forward I mean it has to be installed by someone with admin approval of the slack channel. So I think we can kick off an email thread to the young women interest group and we can ask some questions about like what, what actual permissions it has, because I'm pretty slack naive personally as a Googler we use our one of our 15 chat apps. And we can just run through that I mean it looks super useful so I think as long as I'm an interest on a spirit concerns we can throw it back to the community and see if anyone else does and if they do we can just have a separate channel for I think, I think it looks pretty fantastic. So, so I think if we can just get a better handle on what else it could do if it got malicious then. Yeah, like individual users don't have to grant it any permission to it. No, it's just one set of moments. Yeah, I mean as long as it's not, as long as it's not grabbing emails CNCF doesn't really have an issue with it. Nope. And it's already installed on a bunch of other CNCF. What was the email you guys mentioned to email to. There is an on boy maintainers alias let me dig it up. The Google groups I think actually I'll just put it in the meeting notes. Okay, thanks so much. Cool. And then Chris I assume reminders are you. Just on my end, all the maintainers should have received an email to submit intro and deep dive topic for keep calm in Barcelona so I don't know who plans on attending keep kind of Barcelona but we have two slots essentially available for on voice so try to get that done hopefully by the end of this month would be would be awesome. Cool. Yeah, we've been chatting about it on the on voice slack I think. Do you lease on Hudson you're interested. No, I don't think I get the email that I will increase later. If I double check that. Okay, yeah, you should be on that list if not all I'll just forward it to you so. I'll send I'll just forward it to the maintainers list and go from there. Okay. And then the other reminder was it's going to be summer code season eventually so that opens up officially today so we're looking for ideas from CNCF project so mentors volunteers and so on so on boys interested. There's a simple repo you could PR some ideas depending on what you have in store for any students over the summer. I think that that is not just locked down to maintainers kind of contributor contributed in a sense substantial amount has interest just got us. Yeah, I'll send a reminder over the email list to next week. Yeah. So, I guess the TLDR is quick integration started. We're doing a bunch of work both on kind of a generic to be proxy, as led by Joji over an Apple, and then actual quick integration, which Mike warris is working on at Google and we'll have a bunch of the other Googlers joining it on the, you know, that'll that'll possibly enough we're using the FD refactoring work that's done by Chris and the Cisco people. I'm not sure that I'm going to try to pronounce your last name correctly. You know, essentially, we have a bunch going on in progress so the plan still is tentatively these keys, the Google quick library just because it's been vetted at scale and we spent years working out the kinks and random zero RTT security bugs and, you know, congestion control processes. So it'll such to be the exact code that people's using in house directly ported to its own repo and then pulled into on void already. It already is designed to be multi platform, and so it should adapt to the envoy of and it'll share kind of a common EDP based listener for the generic even proxy that the Apple folks are working on so we've got kind of like four or five people across three or four companies working on it right now. I can't say what the timeline is going to be because I think it's one of those things of as we start the work we'll see how many unexpected gotchas there are, but I'm pretty optimistic. So kind of quick and then integration was order of a quarter or two. And I think the plan again is to kind of hack something that's up and working market and on the API as volatile so essentially you will not have the same API guarantees that will work with like the three to six months application cycle. Right, we want a rapid prototype. So we'll be moving things around and renaming them at will, but it'll work, and it'll be essentially like a big monolithic code block that bypasses the listener filters the, the, the TCP filters that goes straight to kind of the htb codec and then we'll retrofit in all of the good envoy plug ability. You know, once we get the basic stuff up working. So that's, I think the plan, you know if anyone has questions. So I think that's it for today unless anyone has anything else to add. See you all in a couple weeks.