Everyday woman, woman, woman, in every way, yeah, yeah, I'm living my life, life, life, living day by day. Welcome to Every Way Woman. There are some major changes happening in the talk show world. Live from Los Angeles, here's Every Way Woman. And the two of you had the decision of the cast. How did you make that choice? It was easy. It was really, really easy. Yolanda and I knew sometimes within the first 10 seconds. First impression is everything. First impression is everything. Because we already knew what we wanted. And the discussion leading up to, okay, the show. What is it that you wanted? We wanted women on the panel that were not celebrities. We wanted women that other women can relate to. Because originally it was real women, real stories, real issues. A show for women, about women, and by women. Which everybody is using now. You know what I think is so beautiful is that we are all real women. But every one of you is successful in their own right. And I truly find you inspiring. Even though I know the real stories, okay. And it's still, you've all taught me so much. And that's really what it's about, to inspire other women. And create a community for women. And where we can talk about real things. Yep. And you never know when you're casting. We did an open casting. It was in Burbank at a restaurant. And we did a casting. And here comes in Stacey Lewis. Miss conservative. Turtle neck up there. I think it was like March. And dress all the way down here. Was she carrying her bag? I don't wear makeup. I haven't worn makeup in 20 years. That was Stacey at the time. And how far she has come since then. But you know, going through the interview process and we were asking these questions. We realized she is the perfect mom that we're looking for. And she, and then what we, because we wanted women not to just be diverse culturally. Right. And we also wanted to have them lead diverse lives as well. And I connected to Stacey right away. I was going to be a mom soon. And she was a mother working mom, two kids. She's the primary caregiver for her children and for her husband. Devoted wife. And it was funny because Stacey is never afraid to tell you who she is and how like that about her. That's what I related to her. She's like, you know what, I'm a conservative. And she doesn't apologize for who she is as well. And there are several things that we looked for that all of you have, that all of the co-hosts have. And one of them is that all of you move from here. All of our co-hosts move from here. And that was important for us. I remember when I first met Stacey, she was very dear to my heart because first off, I met her at her home. We had a rehearsal there. But she was so open about a certain topic that was brought up, which was molestation. And not knowing that it had happened to me, too. Or maybe knowing, but nobody really shared it. It really worked as therapy. And I looked at her as my therapist. That's the whole point of the show. We cannot cast women that other women can't relate to. The only way our show is going to be successful is that all the women actually are willing to open up and share their stories. And care about other women as well. All of you have a quality where you care about other people. And that was really important to us. Not just about yourself, but about your community. About getting out to the community. Ladies, don't get us wrong. We don't always get along. No, we don't. Of course, we're women. Going back to Jeslyn, let's talk about Jeslyn.  And she's the most giving. And sometimes too giving. Too of false. I would admit that. I give too of false. Those things about Jeslyn I love, she's really funny. She is very giving. But remember the first time I saw her on camera and I remember the guys coming out and saying, do not let her get away. And I was like, I don't plan on doing so. That was really great. And just to know that she's there. Because we've had a lot of great women come and go, which is great. A lot of women have grown a show. We've had every ethnic background. And we have great speakers and we have great guests. Every women has evolved for years. But we struggled in one category. We could not find the Latina that we needed. And it was so funny because we were in Los Angeles. I'm like, oh my God, why can't I find this woman? One day I'm opening my email. And I go, I know, Gina, Gina, she's a... Thank you, Gina. Gina has sent me. She's like, I got this woman for you. Her name is Anna. And I had other stuff going on. So I really wasn't paying attention. So this email come and this big picture comes up. This Latina. And I said, I emailed her back. I said, are you auditioning for the show? I forgot why she was coming on the show. And she was so perfect. And I remember when she came in for the audition and I was like, I'm just going to tell you what to say. Right. I'm going to tell you what to do because you already got the part. Right. And what we really love about Anna is that you don't represent a stereotype. Exactly. And that's kind of what was a little frustrating for Yolanda and I is getting away from the stereotype. We aren't stereotypes. You know, all of you, you're not stereotypes. And I can relate to Anna because she's this Latina woman.  And that is breaking so many rules. Yes. You're breaking Latina community. Absolutely.  She's a trailblazer. She is a trailblazer. And she's inspiring and we're looking for love together. Yes. That's why we have our different women, different opinions, and we always have great conversations. Great conversation. That's right. That's right. Thank you, the two of you, for including us in the show. More everyway women when we return. Coming up next, more everyway women. Are you an everyway woman? Everyway women are concerned about real health issues and topics. Stay tuned as we get real about our health. We're back with every woman and real women may do it all, but they are not invincible. Health care is so important to every woman. It is really important. It's really important that we create segments that's going to give women as much information as possible. And sometimes I feel like on talk shows, I think they glamorize illness. Yes, they do. They kind of make it, they do it. They glamorize it. They make it like, wow, this next cure, this next thing where it's really when it happens to you and your health is down, that's not how it is. Well, health care shouldn't be treated as something trendy. Yes. And that's what it has turned into. And we, as patients, we go into, we already go into an unknown. We really don't know what's going to happen. So we're trying to give or create segments where people know what questions to ask them. Because I know when my husband goes to the doctor, I make the appointment. I tell the nurse or the secretary on the other line, check him for this, this, this and this. He's not, he's going to remember. Well, because we all, let's not lie. We all go on the internet and we self-diagnose. Yes. We Google everything. Which is, I mean, there's a really bad habit of mine. I'm not going to lie. Well, here's the thing is that, you know, what is regulated on the internet, on search engines, is very minuscule. So people can put things out there that say that they do things that don't actually do. It's not until it's on the label that the FDA is regulated. Well, and what's interesting is actually there are a lot of talk shows in the hot seat right now for endorsing these trends. Dorsing these medications and pharmaceuticals without the proof.  Do you want to be able to give them the truth? I found our segments really useful for me being single, somebody that never really looked into going to the doctor when I was younger. Were you scared of that?  But now it's like everything, I feel like, oh my God, my back hurts. What is it? Right. And sometimes the truth isn't pretty. No. And sometimes the solution isn't easy. But my point was like going back to the segments that I watch you, even when I'm on set, it's like, wow, I didn't know that.  It wasn't pretty for me to be in my 30s to find out that I have menopause. It was a lot. I was like, what is going on? But it was more disappointing with the doctors who wouldn't admit it.  They didn't listen to you. And you know your body better than anyone. Exactly.  Is that that quite often? They're already intuitively understanding what it is that they need or what's going on. But having that intuition doesn't always help because sometimes that intuition is scary. And they don't want to know. And it's so great for me to be able to have you ladies to discuss that with. And I know maybe even for some of you as well, because when you talk to your grandmothers or your mothers, they're not exactly always open with it. Yolanda has a really funny story about that. And grandmother about menopause. I said, hey, what age were you when you went into menopause? Oh, I don't remember. And my doctor told me to take tongues. Tongue. And I'm like, yeah. Tongue. I was going to help. And it's from minorities. It's already a struggle for us to even talk about. Why? I don't know why.  Right. But why wouldn't she say it's God's will? Right. And but also it's not uncommon because if you think about those generations going back, they just didn't talk about those things. It was a no-no. Once it was said, it was solidified. Well, the Latinos are different. The Latinos, well, no, not Latino.  They're always in complaint. No. My mom took me to school with the chicken pox and told me that it was mosquito bites in the middle of winter. No. We wanted to face that there was something wrong with us so that we were sick.  Oh, you're serious? When I was younger and still to this day, I try and just power through. And I think women do that a lot rather than we listen to our bodies, but we're trained to tolerate so much pain, whether it's through our hormones or menstrual cycles. That's true.  I'll get through this. Oh, it's a headache. And we don't necessarily always listen to the signs that we need to be listening to. If we need to listen to those signs, those signals are coming clear because this is my thing. If you don't take her, but now it's going to cost you more later. And that's the message that we'll keep trying to hammer home everywhere. Preventative. Yes. Exactly. If you understand what's going on and you can relate that to someone in our audience and they're connecting to it, it might give them that opportunity to then connect and reach out, go to the site or go take a doctor's visit. And I Google. Watch Google. Google isn't always right. No, it isn't. I love Google. Well, and just because you have health insurance, you might not have health care. And it's really great to learn how to navigate that system and sort that through, especially with what our government's trying to figure out right now. And getting foreign to discuss it. And getting real information. Even if it's really scary. Take care of yourselves, ladies and gentlemen. We'll be right back. Stay with us. We'll be right back.  Sometimes it's knowing how to fold the laundry and sometimes it's singing that high note, even if it's in the shower. Another woman celebrates tomorrow's stars, but we have a few talents too. And what are you keeping from us? I paint. Draw. You paint. I draw, paint. Well, that makes sense. Painting. Right, right. But you can't, women's faces are canvas. Yes. So you paint women's faces. I love to blend.   I also bake, though. Really? Yes. You bake? I had a business that, other than my other business, but when I first started, I used to bake. You know what your hidden talent is? You have a lot of business.  I do voiceover, too. I do t-shirts. It's all type of stuff. So that's really cool. I love that you have all these hidden talents. Well, I speak French. That's one of my hidden talents. What did you feel taught? Well, I wouldn't exactly say self-taught, but it's always been a passion of mine. I think I was French in the past life, or, you know, a person in a course somewhere. But it's always just been a part of me. What is the best way to learn French? Because I've been trying to learn French. The best way to learn French is to live in France. Okay, if you can't live in France. No, but truly, like, I moved to France for six months, and I started dreaming in French. And it was one of the most beautiful moments when I woke up and I thought, wow, I truly understand. That said, I am very out of practice and I take some good French wine to really get that accent. I took French in college. Wait, wait, wait, wait. I can talk to that. I took three years of high school French. And we were only at IHELP. I did YouTube French. I try and speak Spanish, but I just say French words and try and make them sound Spanish, which I think a lot of people do when I try and speak another language. Or say English words and try to make them sound French. Oh my gosh, this is terrible. You know what I say? Roll trip to France. What are you hiding? So I cannot sing. I cannot dance. Yes, none of that. But I can pick up on your habit and I can start talking like you and I can start moving. So you're an impersonate. Yeah, I can impersonate people. That is true. All the time. That is true. Right now. I can't do it right now, but it's usually I can't do it. Okay, Stacy. Stacy, right now. Well, Stacy, I have to be moving because Stacy has, Stacy is different, but you have to have something about you. If you have a way you walk or you do something, I can... I'm an observer. Yes, I can pick it up on it. Madison? Okay, so mine, I grew up in a military family, so mine is, I can call Cadence and march a battalion. Okay, we'll take those marching orders and come back after this break. More every way, woman. You can do what? I can march a whole battalion. That is insane. I was like, what? That should have been... Are you an every way woman? Every way woman is breaking out, and our goal is to keep you informed no matter where you are or where you end up. Welcome back to Every Way Woman, so if we had a crystal ball, where would we be? I'm wondering, what's next for every way woman and Madison? The world. The world is in our hands, and it's going to be better off for it. It's so prophetic. I know, right? Yes. But I do agree, I think that every way woman has so many possibilities, and when we sit down, we talk about what can we go and what can we do, and who can we reach, we want to reach everybody. I mean, our show is built to be national and international. It's built to be taken out of the studio. Yes, it is.   For me, I mean, of course, it's getting to the top, but for me, it's more touching lives. You know, the whole incident with Starbucks, I would love to have more, to be able to touch more lives. To give people hope.  If there was an ever-way woman in Dubai, that would be amazing. If we could have a show from there, because a lot of people internationally move there, a lot of people from Sweden, Germany, you have the Arab cultures there. It's really a different kind of melting pot. And so they're dealing with all different other kinds of issues when it comes to socializing with each other and being what people say tolerant and that would bother me, but being tolerant of each other and each other's differences. Well, we have the opportunity to go beyond Southern California and reach out and reach into the lives of, you know, the places we grew up. I grew up in the Midwest. I want to go back there. I want to go to Chicago and my hometowns and really connect with those people, and it's such a great opportunity to give them a face. You mentioned Midwest, because that was one of the things when we actually put in consideration that our show, when we were talking about creating the show, the show is really built for Middle America. And I'm from Middle America. We love your Middle America. I know. Illinois. But, you know, the opportunities are great, but I can see us in workshops and networking events. Our green room comes alive. You should see the people networking in the green room. And it's great, it's because they see opportunity. They meet other like-minded women and they just go crazy in there. Well, and that's interesting you say like-minded women, because every way woman isn't just the name of a show. It's a lifestyle. It's being an every way woman. And one of the things that's really important to us is that we participate and give back to our community. And this is one type of community that we live in here in Los Angeles, but there are many different types of communities that have different needs and they have different hearts and they move with a different rhythm. And we want to be able to reach out to all of those different, like a symphony coming together, right? You've got the drum, it makes a sound, it has its own beat. Well, you know, it's been beautiful because for the past two holiday seasons every way woman has adopted several families and we went downtown Los Angeles and we wrapped the presents and we packed them and we hung ornaments on their Christmas trees and we shot for the children and it was such a beautiful thing because I got her name and her age and all she wanted was Hello Kitty and we really had just been blessed with the opportunity to bring hope and I'm so excited to be able to be a part of a platform night. That can really do that. Yeah, that shows the community that we care about. Yeah, it does make you want to cry because when I think about, I remember when we did that, then we also did the makeup bags for the girls at the orphanage and when she told us, she's like, oh, the teenage girls, this is what they need because everyone forgets about the teenagers and it's really how we, then she told me about the teen boys and no one thinks about the teen boys. Please, can we have some socks or some underwear? Some socks or some underwear and the undergarments and when we really realized it's beyond toys, it's basic needs that we're providing. That is where I envision every way a woman ending up everywhere and getting the women in that community to be involved in their community because I think that's become a lost art as well. As we move into technology, we become more isolated and... I'm sorry, Ellen. No, no, no, go ahead. So we become isolated with technology and sometimes we forget that it actually takes the hand to... I'm sorry.  Another thing is that we are main goal of creating every way a woman was to get other women voices. We have a voice here in the United States whether we like it or not. There are other women around the world that do not have the voice that we have. That's so personal to me because my sister-in-law is from the Middle East and she moved here and she got a voice and our family was able to give that to her and help protect her in that and that's such a blessing that we have in America. And being for me, Latina, being able to touch other people's lives and you tell them, yeah, you can do it too. Look at me. You can do it. Otherwise it's really important because the Latino woman is... she's still catching up a little bit. You know what I mean? Because we had to... okay, now the black woman, she's caught up because sometimes our culture can keep us down. I don't think it's a matter of even just the black women or the Latina women, it's all women. Sharing her story. Yeah, and bringing all women up regardless of, you know, the age or race or socioeconomic background. We want to celebrate you and we're going to continue to do that in the future in every way possible with Every Way Woman. Stay tuned. And you know what? Every Way Woman gives back to the community. Go to everywaywoman.com to find out how you can match our donations of undergarments for needy kids. Thanks for getting to know Every Way Woman. This has been an Every Way Woman production. Every Day Woman. Woman. Woman. In Every Way... Yeah, yeah.  Living day by day. Are you an Every Way Woman?


Hello, everybody, welcome to the functional update for GEO. I'm Stan Hu, no longer the GEO manager, but I'll get to that in a minute. For those of you who don't know, first of all, what GEO is, it is this project for GitLab that essentially does this. To a primary GitLab instance and a secondary GitLab instance, one of them is essentially a mirror of the other. And we can talk about more why if you want to know, but that's really in a nutshell. The team has undergone a few changes in the last few weeks. Rachel Neenabar has joined as the engineering manager for GEO now, so she'll be taking over with a lot of the responsibilities I had with GEO. Really happy to have her board. We've got two people who've moved from GEO to other teams. As some of you know, we staffed up GEO a lot this year to make GEO generally available to our customers, but also to do this Google migration. And now that the Google migration is over, we can refocus some of our team members to do other parts of GitLab. So thanks, Nick and Brett. You guys did a fabulous job, especially with coordinating this migration. Really happy to have you on the team the last few months and looking forward to working with you guys in the future. The team itself is this. Other than the changes I mentioned, it's pretty much the same as a few months ago. Still a full set of people to do a lot of great work. So yeah, let's talk about the Azure Google switchover. And as many of you know, at the summit, it happened about August 11th. And I think it was successful. We can all celebrate. And I was really proud of how the whole team, GEO, especially and the rest of the groups around GitLab, worked together to get this done. So yeah, this was a mission to accomplish. We moved over 200 terabytes of Git repository and Wiki data from Microsoft Azure to Google. And if we did our jobs right, and most people didn't even notice, right? We had a little downtime on the 11th, but as in that came back up and most people just picked up where they left off. And that's, to me, a success. And there's over five million projects on GitLab.com. So it was not a trivial matter. There were a lot of edge cases, weird things that were happening on GitLab.com that we investigated, we fixed, and we shipped it to our customers.  And GEO transferred a lot of them. And eventually we moved them all to object storage to kind of ease that burden, but if we proved that GEO could do that. And as I mentioned, just working on GEO was not just about working on a separate product. We were actually finding a lot of strange things with GitLab itself. For example, you know, error cases, you know, if repositories didn't exist, we'd see a lot of errors when people were kind of cloned them. So we dealt with those and we fixed a lot of issues, everything from database constraints to files not being in the right place. And so I think it was a great way to just kind of dig deep into figuring out whether we had everything in GitLab.com. And when we migrated, we actually double-checked that, you know, files were actually migrated properly. So as I said before, this is a huge team effort. It was a cross-functional group, coordination between the infrastructure team, database team, distribution team. Everybody was involved with this. So it really hats off. I'm really proud of what we did, but also how we also worked together. You know, there's so many different moving parts to this and in the end, you know, it took us a better part of this year, but we did it. So I'm really happy to close this chapter in the geo story and kind of talk about the future of geo. You know, after the migration, we actually discovered a number of things that geo should have done, but did not do. So for example, if you had a project that you created and then you changed your default branch later on in the process, geo didn't actually notice that. And there's actually, this is an issue within Git itself with what you do when you do a poll, you don't actually get the updates to this default branch and we shipped a fix for this, thanks to Douglas and 11.3 and we're talking to the Git maintainers on how to make this sort of part of Git itself because this is something that we solved kind of this three step dance, as I mentioned the issue, that really should just be done by Git. And we've got a lot of great responses within the Git community, but yeah, that makes a lot of sense. And Christian Kudair is looking at that. We found that when people were creating MergerQuest from forks, not always to commits. So normally what should happen is that the source, the target repository that you're trying to merge to gets synced with all the commits in that fork. And we found that that wasn't always happening and Mike shipped a fix in 11.3 to make sure that that would be taken care of for next time. And the last thing that we noticed is that we've got about 20,000 push mirrors on gitlab.com and when we migrated to GCP they actually stopped working. And the reason is because when we create a push mirror we assume that the git remote has been added when we create that push mirror, but that's not actually true in the migration because when we migrated, we didn't actually reflect that, we didn't ensure that that remote actually existed. So again, we shipped a fix that says every time we start this push mirror make sure that remote is there. So nothing here was in super major but the default branch was kind of a surprise. We should have got that earlier. But on that I think everything went pretty smoothly and all these things were rectified pretty quickly after the migration within weeks. So this is a feature, this feature we've been talking about a while is making the GEO more friendly to users because right now if you are working on a GEO primary you have to know that or a GEO secondary you have to know that what's the primary? What's the secondary? So if you're pushing to something you have to know that you're pushing to the right repository. So right now if I'm a user and I decide to push to a GEO secondary you get this error message that you can't push to read on the instance go to the primary. In 11.3 which we're gonna ship on the 22nd we've changed the picture here. Thanks to Ash McKenzie a lot of the hard work gone over the last couple months to make this more transparent. So if you're working on the GEO secondary you decide to push you'll actually proxy to the primary behind the scenes and then to the user it looks like it just worked. As you can see with this error message it looks like it goes to the secondary win in fact it went to the primary and then eventually the secondary will sync and get all the updates. So it's really cool if you wanna see in more detail how this works behind the scenes the issue there has the actual diagram of where all the API endpoints are working in this workflow. So that's again happening in 11.3 we just deployed the version on gitlab.com that would support this. So really excited about this feature it's a big feature. So things that we need help that are stalled with the first priority and I think everyone on the team would echo this point is that we need GEO backup and running on gitlab.com. We saw a lot of issues at scale when we had it running for the last year we found a lot of little problems and also big problems. This drinking our own wine really really helped and can underscore the necessity for this and we've been talking with the infrastructure team about doing this and it's just a matter of scheduling time and getting this done. So again, just wanna reiterate the importance of this because right now we don't have any feedback for 11.3, for example, other problems that we introduced and we can catch them locally but it would really be nice to have it on gitlab.com. A lot of the performance database queries in particular that we saw during our deployment would be helped a lot by upgrading to Postgres 10.0. Postgres 10.0 has this feature called aggregate pushdowns and what that means is if you do a select across two different databases it does some intelligence and actually makes that fast. Right now we have a workaround that basically is this really ugly query that's megabytes long because we don't have the support and so this is sort of again another cross functional task. We need help from the distribution team. We need help from the database team, infrastructure team to get this deployed, figure out the upgrade path. Not a trivial matter because every time you upgrade what they call a minor version of Postgres it's a significant undertaking. What are we going to do in the future? Well, I really see it as kind of breaking down these four different categories, reliability, disaster recovery, performance and UI UX and we're working on a number of these different issues. A lot of things related to just making geo kind of rock solid for the enterprise. So, for example, the reliability is the hash storage or we've been talking about this for a while about having immutable paths in our repositories and we're going through the stage roll out on GitLab.com. We've finished the first stage and then we're going to be continuing the next week to roll it out more and more to different projects. You know, on the DR front, we did a lot of manual things and this whole switch over because of time and because we're trying to understand like what we need to do, what users need to do and so we've got a runbook of what we did and we're looking at that and figuring out what are these things, what are the lessons we can learn from these things that we did manually on the console and how do we make that part of the product? How do we make sure that, you know, users don't have to worry about, hey, do I need to reset my verification status? Can we just do this automatically? As I mentioned, kind of alluded earlier is we have, you know, a lot of performance issues in terms of database queries because, you know, we have got five million projects. We're doing a lot of queries to figure out, hey, do we have all five million projects and that can be really expensive if you're talking about millions and millions of rows and so we're looking at different options there. You know, one of them is this feature in Postgres called logical decoding, had a long discussion with the UNGRESS consultants to figure out like, is this a right solution? Can it work? What are the limitations? So there's a lot of good discussion in that issue about that. Push to primer, I talked about that earlier. There's a lot of improvements that we can make with that feature that we just shipped. For example, a lot of the proxying is done in Unicorn, not in Workhorse and that can tie up a Unicorn worker if you've got a lot of busy pushes. So we're gonna be looking at moving that into Workhorse and other ledger improvements. And overall, there's UI UX improvements that we can always make and just make it easier for the admin to understand what's going on and GEO and so there's an issue there that kind of shows you the screenshots and things that we're thinking about. So that's really GEO. Happy to open the floor to any questions, concerns. Yeah, everybody's excited about push to primary. It's not push to secondary. Yeah, I guess it's technically push to secondary because it doesn't look like an actual push to the secondary. To anticipate needing security app reviews, I actually think we do. I think it'd be a good thing because GEO is sort of this feature that has access to all the repositories and all the Wikis, all the issues. We really should be looking at what are the holes. We've taken a lot of efforts to make sure we don't expose tokens and things like that. We use rotating token that's generated for the session but there may be potentially other things that we need to look at. So yeah, I'd welcome a security review as much as we can there. Do we think we'll make the GEO known and get a lot of public in the sense of recommending? That's a good question. I don't know if we, I think when we talked about in the migration, we didn't wanna do that because of a number of reasons but I think it's definitely a possibility if people wanna clone or poke around or secondary. There may be other reasons why we may not wanna do that just for just reducing the security scope and things like that. But what region are we thinking? I think that's up for debate on that issue. I was just saying, well, we probably want it in the US West just because if the East Coast goes down, maybe one on the West Coast, but there's an argument to me made that, hey, maybe Europe is a better place for that. Well, we do more than one. I'm not sure. I think we're looking at one right now. I think the main reason may be cost here. We've got over 200 terabytes of data and having one replica already is pretty expensive. But other than that, there's no other reason why I can't think of why we can't have multiple replicas. Okay, then other questions? Nope. Yeah. First of all, great work. Like that the fact that the migration went well and there were so many moving parts. It was great validation and really cool to see how ready GNO is for mission critical apps. If we're gonna use it for DR, I'm gonna prevent mass deletions. Obviously, we're also gonna do just plain backups, but are we gonna have something in place? I'm not sure what the easiest way is to do a mass deletion and get a lot, but are there operator errors? We're gonna make sure that don't get replicated or something like that. Yeah, that's a good question. I mean, one thing we could do is have a delayed replica, for example. So it could be lagging an hour or 24 hours or something so that things don't get actually reflected until later. That could be one avenue, but as far as mass deletion, I think we should probably create an issue around discussing if there are things that we can catch. Someone does a drop table, maybe you do something like you avoid that, but that's a database issue. But if you have something where you see a ton of delete events, maybe you should flag it and prevent that. Cool. And we had the problem with basically the cursor moving and missing things. Is that, is the issue geological replication case, issue 7420, where we discussed that? Yeah, we're discussing that in the logical decoding case. We've had a long discussion about, hey, does logical replication or decoding work? And yes, it does, but at the same time, it introduces another thing that we have to configure a more disk space that happens. Because you're basically, you're adding another replication slot. So it's like you're having another streaming replica. So there are some problems with that. You're adding more disk space as the replica goes offline. So we have to make a decision of, is it worthwhile to do that? Or there are, I think, Jose, potentially even volunteered some interesting ideas of, hey, maybe you can timestamp all your, all the events so that you're actually, when you look at, when you're looking through which events you have in process, you actually look at the commit times. And maybe that's a more immediate solution rather than try to go down this path of introducing logical replication or decoding. Yeah, simpler sounds better. But now that GEO is getting better, like we've got a lot of finishing up to do, but are there plans to, what are the plans for the size of the team? Yeah, so as I mentioned, I think the current size, that we already had two people move off the team this month. As far as I know, there are no other changes right now, but I'll leave that to Rachel and Tommy to discuss whether we need other people to be prioritized on other projects. Cool, thanks for the update. All right, thanks everybody for your time. Have a great day.


Hi, this is your host, Aptin Bhartya. And today we have with us our vice CEO and co-founder of permit.io. Or it's great to have you back on the show. It's great to be here. Thanks for having me. This month's focus is on security, dev sec ops. I mean, when we look at security, it's so big, it's fear that we cannot just pin point at one thing. So depending on who I'm talking to, the whole discussion changes. That what you mean by security, compliance could be an issue. Permissions can be issue. Bucks can be issue. API, zombie APIs can be issue. Application never use can be issue. Anyway, so it's a big topic there. If I ask you that, if you just look at the multicloud, hybrid cloud word, how security landscape has evolved from traditional IT, where it was an afterthought, it was someone else's job. I think it's changed dramatically, especially, but it depends how back you have to go. But if you go five years back, 10 years back, it's a completely different ball game. I think we've seen both the complexity of the space itself drive the need for innovation in security. But we also think saw how companies trying to tackle these challenges are adopting more and more solutions to have better results with what's going on in their cloud. That being said, I think we haven't moved forward enough. I feel like we have a lot more security solutions, but the challenges have kind of ran forward much faster than the solutions that we've provided. And if we look at things like the OWASP top 10, a lot of the problems that we listed 10 years ago are still on that list. And some of them might have moved higher, some of them might have consolidated, but most of them are still with us. So we definitely haven't solved security. We definitely haven't become more safe by moving to the cloud, but we have definitely been investing a lot of energy in it. That's clear when I'm talking to customers and when I'm working with people that are tackling these challenges. I do remember that just let's look at CubeCon Kubernetes ecosystem a couple of years ago. They started talking a lot about security. They're like now dedicated days for security. So a lot of things are changing in the cloud, centric cloud, and you work with also the shift led movement. But reality could be different from what we see, what we hear when we go to these conventions. We get folks who are expert, but customers can be doing something totally different. So can you talk a bit about when you deal with your customers? You actually did touch upon that briefly there. What are you seeing in reality that how further are they in improving your security posture or they're still like, you know what? Yeah, we will deal with security when it's needed. When I talk to our vendors, our leaders in the space, everyone's talking about new solutions and new practices to get better security, like S-bombs, software bill of materials, like embedding security into your Kubernetes with solutions like Falco or with permission enforcement or authorization in general with things like open policy agents. So those have become prominent solutions as part of the CNCF ecosystem and everyone's talking about them. But when push comes to shove, you see that people are still implementing most of the things on their own manually. They're still struggling to adopt these projects and they are still, maybe the worst thing is most companies are still applying these as an afterthought. They are not applying this, even though they're doing shift left, they're giving their developers a lot more responsibility with security. That responsibility is coming at the end of the chain after they've built something. Instead of, okay, we're going to build something, let's think about how we apply security by design, how we bake insecurity as part of our fundamentals. Part of that is also because we're carrying a lot of technical debt. Most companies are not starting from scratch, they have existing solutions that they need to patch or apply security to. And that obviously adds a lot of friction, but I think people also use that as an excuse to not bake insecurity from the start where they can. Can you talk about what are some of the major security concerns that are still there? If we can look at some breaches, luckily we have not seen anything recently, but any major breaches where you're like, hey, this is a problem that should have been solved, or this is an area we should be focusing on. I mean, a lot of things that FMA thing happened or other thing, they're more about not updating a package. That's the kind of beyond that, but anything else that you see is a concern to you? So I think the areas of vulnerabilities are in pieces of software or solutions or architectures or even platforms, those will always be with us. It's an arms race and there will always be another vulnerability, it will never end. We might get a better equilibrium there, but it's not gonna end. I think the area that is now experiencing the most friction and causing most of the both hacks and leaks is the area around how we build solutions on top of the platforms and how we bake in controls on top of them, specifically and obviously aligned with this lot, but it's also the top item on the OWASP top 10, application level access control. That's something that most companies are still struggling to address. And the other part which also kind of relies to this is how we allow access to data. Data has become probably the most desired resource that companies engage with and the most sensitive, especially if you have PII's or PHI's and a lot of the leaks that we see, like there was one recently with Twitter and with Uber and a lot of those incidents are about stealing the details of the users that are on the platform and then selling them on the black market or using their financial details to sell them as credit cards on the black market, et cetera, et cetera. So data access and in general access to application level, I think where we see the most friction and the most incidents come from, at this point in time. And I think it's sadly, I think it's only gonna get worse because we're seeing in parallel as we're trying to solve these areas of friction, we're seeing these areas also grow dramatically, especially due to the growth with the machine learning components that we're baking into software. So machine learning components means two things. One, we're generating more data because we're having more user interactions with the systems themselves that become more complex. So we have more datasets and also the data itself becomes more valuable because more companies needed to train their own models. So there's essentially another race condition here between the growth of complexity around data access and application access and the tools that we have to organize, control and protect that access to the data. And currently we're not only lagging behind, we're not even accelerating enough to keep pace. Since you brought this up, I am also kind of curious to know if there are any new vectors, thread vectors that are there which should be concerned for organizations? Something that is new, but it's probably too early to tell but it's definitely, it's starting to kind of realize as a new area of friction is attacking generative AI agents. So everyone's talking now about chat GPT and everyone's basically thinking about how they're gonna embed similar agents into their software. And we're already seeing hackers and attackers manipulate these types of agents. So you see a lot of interactions with the agents where it tells you, no, I'm not supposed to give you an answer on that. I'm not supposed to share that information. I'm not supposed to do this kind of behavior. But then you can see that the agent can still be manipulated by telling it to pretend to be another character, by telling it to answer from a different perspective or context. So suddenly the system that used to be very deterministic in how we protect it, now has the attack surface itself has become much bigger and much harder to cover because it's fuzzier because of the machine learning agent acting there. So for now, these agents are mainly spewing out data. Sometimes that data can be sensitive or sometimes just the fact that they reacted in some way can be detrimental to the company. For example, think about the Bing open AI demo where the agent turned out to be somewhat racist, somewhat misbehaving and also pretending to be sentient, which also kind of troubled people. And that affected the price point for the Microsoft stock for that day. So even that is impactful and has friction today and can be an attack vector on companies that attackers can leverage now. But it's even, I wouldn't say scarier, but it definitely brings cause to think more about it. You can think of what happens when these agents not only share data with us or communicate things that they already know, what happens when they start performing actions for us. So for example, if you have an AI agent that is responsible on who's supposed to access your database and you trust it to only perform specific queries. And suddenly because someone attacked the way the agent behaves, you are seeing irrelevant data or sensitive data or actions, maybe even it can cause it to delete the database, for example. So these are things that are just around the corner and we haven't covered the basics yet. So I think we need to invest a lot more in how we build controls for the data sources that we have for the applications we have. And we need to find a way to not only make them good deterministically, we need to bring them quickly up to speed with the complexity that is waiting for us just around the corner. How much adoption are you seeing of these kind of approaches in the market where we can conclude that, hey, things are moving in the positive direction? I think that's another kind of ironic situation. I think companies have been putting zero trust as their top line for at least two years now and they've been looking to buy, especially the CISO suite. They've been looking to buy products for zero trust or that have zero trust as part of their offering for quite a while, but I think they've neglected to think how they apply it as a method to the way they're organizing their security posture and the software that they're building. Zero trust is not just a VPN, zero trust. And if you just apply it as a bandage, as a VPN, you're missing on a lot of potential A and B, you're probably missing on vulnerabilities that you're not protecting of just having a VPN or a monitoring service that has zero trust capabilities. Zero trust is a mindset that you build into your software. I can give us an example of our open source project that we've created as part of PERMIT. Opal, we had to solve the problem of how we communicate policies and data in real time into decision engines. And the naive approach would have been, let's have this bus and just load the data to the server, the management server and all of the clients will download the data from there. And on the surface, that's an okay solution. And we could have tried and apply zero trust elements to it later, but that honestly wouldn't have worked and that would have missed out on one of the greatest opportunities with the project. What we ended up doing is decoupling the control plane from the data plane. The server, instead of being exposed to all the data, sends instructions on where to get the data to each of the clients. So each of the clients, only if they are approved to, only if they subscribe to, and only if they have the right access, goes directly to the data source and fetches it themselves. That means that you get out of the box zero trust architecture. The server touches no data and there's no concentration of all the sensitive data in one spot. And each of the clients get only the data they need when they need it. And it would have been basically impossible to implement this as an afterthought. And this is a core infrastructure component that affects policy authorization, for example, in our case. And this, but this is just an example. There are thousands of other architecture solutions that developers are creating on a daily basis and they're not necessarily taking this mindset into account and they're missing out. What kind of cultural changes you're seeing that are happening there? So honestly not seeing a lot of changes. It's in that era, it's kind of like same old, same old. And it's somewhat frustrating. I feel like, in general, I like the DevSecOps movement, but I feel like similar to the DevOps movement, it's kind of missing on the point. With DevOps, the point wasn't to add more people that will do DevOps. The main, the core offering was, let's have the developers do ops. The same thing as with DevSecOps, you're not supposed to add security people alongside your developers or after their developers work to apply security. That misses the point. You want the developers themselves to be immersed in security. You want them to use security by design when they're building things. So now obviously you can't have everyone be a security expert, but you can invest in training people. You can invest in giving people tools, examples, methodologies that they can adapt and work with and be aware that they need to do so, have that as part of the expectation. You can rank your, well, not rank, but you can motivate and help your engineers work on security as part of their job and not just check it as an afterthought or when you have to do your compliance. In the end of the day, while it seems counter-intuitive, it will actually save you a lot of money and a lot of pain and friction later. So what I'd suggest for companies that don't have the DNA built in for security is hire, look to add per team one engineer that has some security background, but don't have them as the head of security or the responsible for security. Have them work with the other engineers to teach them. Have them turn your other engineers into security aware engineers. That's at least my two cents on the matter. Now let's talk about permit that I, of course, we cover you folks on a regular basis to our audience. Totally know about what you folks do, but just in the context of this discussion is that what role is permit.io playing to once again, help companies improve their security posture? I'll highlight two things. One is something that we kind of touched on. Access control is a critical aspect that you need in every bit of software that you're building. And it's really hard to build on your own. It's just like with encryption, just like with authentication, it's really hard to get this right unless you really are an expert in this. So you can build this on your own, but you really shouldn't. You can adopt this at day one and save you a lot of friction down the road. And I think even if you're not buying our product, you should at least review it and learn from the best practices and from the open source projects that we've created. So you won't end up repeating mistakes that we've done and learned from already, for example. And I think the second part is about commoditizing access. So what permit does, it's not only an infrastructure and API solution to add permissions and access control, it's a system to manage it. We provide end-to-end experiences that every application needs, like user management with the ability to assign roles, API key management, audit logs for yourself, audit logs for your customers, approval flows, invites, all of these interfaces that most applications need. So instead of building these on your own, you can have them ready-made. And through them, you can enable the rest of your organization. This is not just about the developers. So it's about empowering developers but allowing them to delegate to other people so the developers don't become your bottleneck for this. And as the tensions rise and as more and more security challenges surface at the table, so for example, around data access, as we mentioned before, you want everyone to be able to chime in on the conversation. You want everyone to be able to take effect on how you set your policies and how people and systems connect to what you're building. What advice do you have for companies so that they can work towards improving their security posture? So I think the best tip there is to apply security by design. Don't apply this as an afterthought. Don't wait for the product to be ready. Apply it at day one and to do so, you need to both adopt the mindset for it and adopt the DNA that you need for this. When touching on dev ops and dev sec ops, key point there is that you're supposed to enable your developers to be able to do ops and to be able to do security. It's not about separating this to a separate person. So what you should do or what I recommend people do is hire security aware engineers and have them not become your security person, but have them empower your other engineers, teach them the right mindset, give them examples on how to build things with security as a first leading principle and again, not as an afterthought. All right, thank you so much for taking time out today and talk about this topic. And as usual, I would love to have you back on the show. Thank you. Thank you very much. It was a pleasure.


Welcome to All Hands Update. I'm Petty Officer Andrew Johnson.  Prepare for the cold weather to avoid frostbite and hypothermia by wearing layered clothing, eating properly, and drinking warm liquids to stay hydrated. Frostbite symptoms can include white, waxy, or pale-colored skin and cold, hard, or numb skin. If you or someone near you is affected by frostbite, move them to a warm place and seek medical attention immediately. Hypothermia symptoms include uncontrollable shivering, a change in mental status, darkened puffy skin, and unconsciousness. Victims of hypothermia should seek immediate medical attention while staying warm. For more information on how you can stay safe during the winter months, visit the Naval Safety Center website.


So I'm First Lieutenant Jones, Jeremy Jones, Juliette Echo Romeo, Echo Mike Yankee, Jones, Juliette Oscar, November Echo Sierra. I'm with the Murph DLCE. Currently I'm the engineer platoon commander for the LCE. I'm a 1302 combat engineer officer. I'm from Jacksonville, North Carolina. So today we celebrate Anzac Day, which is an important holiday for the Australians. It represents the partnership between the Australians and New Zealand, and it's basically the equivalent of the United States Memorial Day, where you remember the lost and fallen soldiers of the Australian and New Zealand forces. Yeah, so Anzac Day is nationwide. I guess you could say continent-wide in Australia. It's a day where they all get together and remember those who have been lost and fallen. Absolutely. So one of the objectives out here at Murph D is the interoperability piece, and I think that this parade really demonstrates that capability. It was an honor and privilege to be able to march alongside our Australian partners and participate in this wonderful parade today. Excellent. Yeah, I've always wanted to be here. It's, you know, Steve Irwin was like a child, a dear of mine, so being able to come here and even lead Marines while coming here is pretty excellent. I'd like to shout out to my mom and dad back in Jackson, North Carolina, Mark and Regina Jones, URA, hope you're doing well.


It seems like T. Higgins' time in Cincinnati is coming to an end. Latest update around the situation, he has requested a trade and according to Adam Schefter, he loves being in Cincinnati, but he's upset that there's been no movement towards a long-term deal. And there's a lot of teams in the league that could use him. Who would you give the best odds for T. Higgins' new team?


The other day, I was speaking with a female friend. She was discussing her business idea with me. She had great plans on how she was going to get started.  She will have every good reason in the world to give as to why it cannot be achieved. Those reasons may sound like they are genuine but they are just like every reason she had given for not starting the other businesses she had discussed with me before. I knew she would never start that business because they were excuses she had believed but were holding her back. Listen to this. I'll tell you the simple way you can start a business right here and now. Find the problem. Find the right solution. Deliver the solution. And that's simple. No Britannica about it. No point arguing about my NTIA. Get on with it and get your business started. I can end this video and you can move on. But you see, I can bet you that like thousands of young people who will watch this video, you will not start. No, you won't. You see, it's not the first time you've read the simple straightforward business tip. So obviously, you know there's business truth. You know precisely what you need to get started with your first business. But you aren't starting your business. Why aren't you started? The reason is simple. You are making excuses. Mostly outdated excuses. If you have always dreamed of starting a business, I can bet you that one or all of the excuses below are the reasons you give for not starting your own business. Excuse number one. I don't have money so I can't start a business. How many times have you said this to yourself? Is this even true? I'll not be deceitful here, but there are two ways to kill this excuse. First, if you don't have money, get a job. No big deal. It doesn't make you any less an entrepreneur. It doesn't make you less competent, low thinking or failure. You only be earning to start a side business.  It's common advice but if you have the guts to stomach a week long of hunger, shame and disgrace for not having money in your pocket, while you are building your business, get started with what you have where you are. Your first capital could come from selling sashay water or from working as an office assistant. No matter if starting a business which eventually gives you freedom and flexibility truly matters to you, you can start with what you have right where you are. Excuse number two. Small businesses don't succeed in my country. This is not true. Small businesses do succeed in your country. Small-minded business owners are the ones who don't succeed. Most new entrepreneurs are so naive about businesses that they spend every income that comes into their business. I made this mistake too when I started a business. In the year 2016 I started a business where I made tons of money in very short months. Thinking things would continue to be this way, I didn't save or invest a thing. I was dead broke less than a few months later. That's just one of the mistakes most failed entrepreneurs in my country make. There are many others. If your habits are good, your business will thrive. If your habits are bad, your business will go to the gutters. Small-minded entrepreneurs expect quick success. They wait for success without working hard for success. They work short hours but take very long breaks.  They never invest back in their business. Excuse number three. I don't know enough to sell to anybody. A young man in my country, Bami Dele Onibaluci, who is barely 16 years old, used common knowledge of freelance writing to support himself after secondary school. He grew that small business into what sustained him and his family. And at a very young age now is one of the most successful people online in the world of freelance writing. When I started writing for pay, I was a fiction writer who turned to content creation because I was dead broke. Yet with a quick writing skill, I began to make money soon enough. When I started, it was tough but I kept practicing daily and kept becoming good at what I do. Whatever you know doesn't matter how similarly unimportant. There are people who don't know that and will gladly pay for it. You don't need to be the world's best, you just need to be better than some other people who need your help. Excuse number four. I don't have help. In my country, this excuse is very common. It basically centers on the religious belief that my helper will come. Well, I do not go against religious beliefs. But I do know this is so absolutely erroneous. It should not be allowed to live another minute in our society. Waiting on God to show some help while you are doing nothing is as good as standing in the rain with no buckets but expecting to gather rain. I am not saying God doesn't help people, of course he does, but only if you play your part by working hard and giving your best. Helpers aren't going to come your way because you asked for it. They will come because you deserve it or have earned it. And if you are truly religious, you know you'll only earn it through obedience, which of course puts the responsibility of diligence on you. Excuse number five. What if I fail? If you are in business not expecting to fail, then you are best of being an employee because you will undoubtedly fail in business. If business was that simple, the statement business is a risk will be irrelevant. Business is not that simple. You won't always succeed. You won't always break through. Things won't always go your way. But you won't always fail either. Don't scare yourself to death about it. There will be the days of glory and there will be the days of pain. The question is when you fail. What will you do about it? Envy's Asian failure doesn't make you a failure. It shows you from the start that you should prepare for failure, which is sadly what most naive entrepreneurs don't ever do. Prepare to fail. Then create ways you'll leverage your inability to succeed. You don't have to own the world to start a business. In fact, most successful businesses started small. What matters in starting a business isn't that you have it all together.  With the right attitude, you can create a business that succeeds, even when you go through hard times, which are inevitable in business. There may not be all the outdated excuses holding you back from starting a business, but know that there will always be an excuse for not doing what you are supposed to do. So, the best thing is to get on to do what you have to do anyway and damn all excuses. If this video inspired you, share this video. We love you.


Hi everyone, so my name is Benjamin Feng, I'm an Associate Solutions Architect at AWS and I'm part of the AI-ML technical field committee. So I know what some of you guys might be thinking like that guy's the technical guy from AWS, let's get him, let's ask him all the questions. I'm not here for that today, but definitely contact your respective essays or account managers that are in charge of your AWS account. So also for some context, I was told that this was going to be a 10 to 20 people AI-ML meetup interest group. So you can imagine my shock when I saw like 100 of you guys, so while you're young, just try everything, just make mistakes, so that's what I'm doing here today. So of course some of you might also be thinking there's a young guy here recently joined AWS not more than a year, what can he tell a room full of professionals that have been doing this for years, yeah. And actually I'm not here to tell you how to run your business, but I'm here to introduce a new topic that you might be able to take advantage of in your business. So I'm really passionate about this topic and I've been researching this topic for about one and a half years now and collaborating also with some of my AWS peers in Seattle. And I think it's really exciting this new technology that can unlock a lot of possibilities for your business. And this will be some sort of surface level technical introduction to federated machine learning. And I feel it's quite nascent, so for some of the questions that you might have, actually maybe nobody has an answer for it, so please do be patient if possible. And of course this will be slightly technical on the machine learning side. So I hope everyone here at least has some experience with ML. And the presentation was also built on top of the research of some of my colleagues overseas, Kristoff and Chong Zhang. So thank you for that. So without further ado, let me just get into it. The first one will be the agenda. So what is federated learning? Why is FL growing in importance? And of course how to build it on AWS. So first of all, what is federated learning? So federated learning is a distributed ML approach that trains ML models on distributed data sets. And it's also commonly known in the field as privacy-preserving machine learning. So why I was personally very interested in this topic, I'm sorry my slides has been switching. Okay, so why I was personally very interested in this topic was the possibility of it solving a lot of healthcare problems. And yeah, so let me just give an introduction of what that might look like, what federated machine learning might look like for you. So in healthcare data is quite really, really sensitive. And you can technically reconstruct someone's entire face from a couple of MRI or X-ray scans. And I mean, there's no wonder why hospitals are so uptight on data privacy. And federated learning actually has been touted as a way to cross these barriers. And this is a demo on how. So over here we have long MRI scans, I believe. Yeah, so it starts with a global model. Let's just say your company is the server with a global model. And there's a small clinic, there's a hospital and a research center. As you can see, these different clinics and hospitals and research centers have different varying amounts of data. And the research center obviously a petabyte scale of data and they've been using it to train their own models. And so with this federated learning, the next thing would be to distribute this global model that you have. It might be a model that's already been trained on detecting MRI scans, cancer and MRI scans. And what happens is that you distribute this to everybody. So everybody has a machine learning model to train on and to utilize their data for. And then the next one is that each endpoint will incrementally train a global model based on their local training data. So each of the models that we send will be trained on the small clinic, hospital and research center. And these models will be adapted to the data in their respective areas. So afterwards, we upload actually not the data, but actually we upload the model, the weights and other artifacts that the model might have to the centralized model which is your company. So what the company actually does with this model is that we aggregate it. So aggregating the sense we combine the weights, there's several ways of doing it. There's a lot of research coming out on how best to aggregate your models. But what happens is that this actually gives a chance for a model to have seen all the different types of data. So not just the gigabytes and the clinics, the terabytes in hospitals, but actually the petabytes of data available everywhere. And it's possible that this small clinic is somewhere in another country. And for example, dermatology data, people with different skin colors. This actually will help your model adapt and generalize better to these big different data sets. So then we send these models to the small clinics, hospitals and research centers and continue training it on new data or just to improve the accuracy until we see an improvement in test accuracy. So that is a gist of what federated learning is and how it works. And of course, like I'm mentioning, for example, a hospital might have an image diagnosis for dermatology on skin types that are mostly on the light side. You might not have the same accuracy if you had darker skin and going and you went to this specific hospital. The model might not be able to generalize to your skin type. So this is one of the problems that federated learning can actually help with your model to generalize. So the power of federated learning is beyond just privacy. I think that federated learning has the ability to unlock hard to reach data for machine learning training. And of course, in hospitals, some of you might be wondering, why do I have to wait seven days for my heart scan to return any result? Is it because of shortage of doctors or lack of technology? And I believe that we already have the tools to equip doctors with such assistive tools and increase efficiency in healthcare. But these efforts are actually unfortunately covered in a lot of red tape. And in fact, it should be covered in red tape, right? After all, there are lives at stake in hospitals and whatnot. So federated learning presents that chance to cross that red tape and be compliant with laws in order to build models that are at the level of the biggest companies. Why do all the big companies with the richest companies have the money to buy data sets, right? Why not everybody else build and chip in in order to build something like that? So I'm going to go a little bit more in depth with what that might look like for the technical folks. So there's different types of flavors of federated learning. So you might be asking, you know, not all data sets are the same. This data set in the clinic might be different from data set in a research center. So there's two types of federated learning as well. There's being research as of now. There's horizontal federated learning, which is where the data is the same. We only take the columns, sorry, yeah, the features that are the same across different data sets. Bank 1, Bank 2 has the same type of data set, sorry, features for the data. And of course, there's also vertical federated learning, which is where the data sets are not similar. So instead of going just by features, they go by the person. So I'm sure a lot of us have data set, sorry, more than one bank account in UOB and DBS. So what is, what federated learning, vertical federated learning can do is identify the person instead of the features of that person. So it can actually expand the data set. Maybe your first bank has only three features and the other bank has five. Federated learning can extend this to five features for you specifically and of course, have more insights to perform predictions or whatnot, okay? So this is really, really new. So there's a lot of research online that's being done. So feel free to Google and reach out if you need to. And of course, there's other ways of federated learning where the server can be positioned. So quite commonly, the federated learning server is at the center and federated learning clients will send the weights to this centralized server. But it's also a peer-to-peer. I'm sure a lot of you get very excited when you hear that word, peer-to-peer. This is like a mesh connected clients where we can keep updating our models asynchronously or synchronously based on the people that are around us. And this sort of democratizes that in a sense. But of course, there's other ways that we can, other benefits of this as well. So lastly, when do we aggregate a federated learning server? There's synchronous and asynchronous. Definitely, you can aggregate a set of local models into a global model. Or you can do it asynchronously. This is where you update the global model once a local model is received. So I think this hits home a little bit. I took this from Apple. I think that's allowed. So actually, I think your phone is already performing federated learning in a sense. Like Apple has this face detection and of course speech recognition services that they provide. And what they do is that they probably, I'm a disclaimer, I don't know, but they probably take the data from your phone, train it on their local models and then just send these weights and parameters to their centralized place where they aggregate it. And then of course, that's why everybody can have face ID. Everybody can have a facial detection. Everybody now you can separate the face from your photo and stuff like that. I believe that's what a lot of phones actually do. So you may never know federated learning is closer than you think. Okay, so why is federated learning important? I'm going to go through really quickly. So as you can see with the example of mobile phones, we enable the possibility of ML cross devices and of course cross silos. So being able to access silos of data sets and crossing different organizations as well. So of course, there's a possibility of reducing costs instead of buying data. Now there's a lower barrier of entry to train really, really great models. And of course, there's also a flexibility in the form of being able to perform machine learning operations on-prem or on-cloud, adapting to the multitudes of data sets with a vertical federated learning. So last one I want to mention is why I'm so passionate about it, which is I hope that federated learning can actually promote healthcare equity. Where the smallest players and smallest clinics can benefit from the capabilities and data sets that these big research centers and organizations might have. So rural clinic somewhere in a certain country can benefit and have the same type of accuracy as the model that are possessed by these big research centers. Okay, so another example of course is the bank example that I gave. There's banks with different type of data sets and of course they can work together to have a fraud model that can really detect across banks. If a bad actor were to port from bank one to bank five, bank five would also be able to detect it because it has seen those data sets and these type of examples from bank one without even needing to see their data. So there's a lot of places where you can use federated learning. This is just a small subset of it. And of course with every new technology there's a lot of challenges and there's few uncovered but not fully solved challenges. With this seemingly, sorry, I would like to add also that I mentioned how big a part of FL is. It's also about aggregation of weights. I think there's a lot of research coming out with aggregation methods. Concatenating the weights most likely won't work. Averaging out might work a little better. And I recently saw research on layer by layer aggregation, which is really complicated, a lot of math involved. So if you're interested just find it online. And I might not be able to answer your questions really well on this. So a lot of problems feel free to maybe solve some of them with you and your companies. So also another problem is that who is going to be the host? I think this is a big problem when governments are asking like, why should you be the one with all the power? Why not me? Why not them? So a lot of problems and a lot of related that you still have to work through in order to implement something like that. So really, really quick demo how to implement this on AWS. So let me just press play. So as you can see here, there's a top notebook and a bottom notebook. The top one I believe is on-prem. So this is where they hold some of their machine learning models. And the other one is on the cloud. The one below is on the cloud. So this also holds another machine learning model. So the one on top on-prem has different data sets. And the one below has different data sets as well. So what it's doing here is actually performing federated learning, like I mentioned. What we're going to do on the cloud is that we're going to give a global model to these two notebooks in order to perform training on their respective data sets. Let me just skip ahead a little bit if you don't mind. Yeah, so when you start AWS Step Functions, I personally love AWS Step Functions. It automatically performs this training. It sends a signal to these notebooks. Here's the model start training. And then the model will train on their data sets. And of course, it also goes into a loop as you can see somewhere over here. Yeah, it goes into a loop. It keeps going into a loop because if a model trains on a data set and it's not improving on test accuracy, why bother at all, right? So this Step Functions actually helps you automate this. You automate a lot of things, but it automates this and it checks whether the test accuracy improves at all. So as you can see, the model is being trained above. It's checking whether the accuracy is good, whether it's bad, whether it's improving at all. So with AWS, it's definitely possible. These two are actually on SageMaker itself. So that's where the AWS ML is involved. Okay, sorry. So yeah, let me just skip ahead. The gist is that the training will finish. It says that, okay, yeah, the accuracy has indeed improved and research has shown that federated learning actually improves accuracy quite often. That's a lot of proven results. And of course, yeah, this is something that you can do on AWS with your notebooks and you can go really in depth on how your weights are looking and what actually went into that training. Okay, and it's a little bit complicated, but how to build it on AWS. So like I said, there's an on-premise one and there's an AWS one. Whoops. Yeah, there's an AWS one. And of course DynamoDB will store some of the metadata that you need and the S3 buckets will hold the ML models. I'm not sure if someone's clicking this for me, but I'm just not sure what's going on. But anyway, yeah, so the S3 bucket will store the weights and the models and what not. Tech nowadays, yeah. So AWS Lambda will start the sort of start the training process and start the step functions. And of course, Amazon SNS and SQS will let the on-premises servers know to better to start retraining, whether to signal a lot of different steps that you want to do and maybe even aggregate a model in a sense. Yeah. So yeah, despite the challenges in federated learning, we do see tremendous potential. We being the people involved in AWS in this community that's trying to build up something interesting for healthcare. And of course, there's a lot of places that you can use it. And there's a lot of regulatory pressure on ML, ethical ML and stuff like that. So federated learning could be a possibility where we can go beyond these regulations. And of course, there's a lot of promising signals that are being showed with federated learning. So I hope today this introduction, everyone has actually a better idea of what it might be. Maybe some of you have never heard it before. Great. I hope you guys understand federated learning now. But if you're an expert already, yeah, that's great. Yeah, I hope we can solve more problems in the future. So yeah, thank you so much for that. I'm actually here to also talk about something else. So I hope you can hold up the questions for now. Feel free to talk to me afterwards. I'm already about 16 minutes. So I'm going to really quickly go to my other presentation that I am obliged to give. So this thing called AI ML Reactor that AWS is hosting. It starts on 10 October and ends in about a one month program, I believe. So what it is is that it's a five-week hands-on practical program enabling startups to implement and deploy their ML solution. And of course, we had it in Pakistan already and we're trying to take it across ASEAN. And of course, there's a lot of exclusive workshops, there's mentorship with AI ML specialists from AWS, cash prices, AWS credits, and exclusive SWACs that you can get from there. But of course, that's the least of it. And of course, the target audience is for people that are AI ML first startups. And startups has also reached a stage where AI ML is in their roadmap to drive sales conversions and their business goals. And of course, bring in net new startups that are not on our view as of now. So the five-week program will provide you with these benefits as hands-on guidance as tech mentorship, business mentorship, demo days, cash prices, visibility, stuff like that. And of course, this is a more detailed description of what the timeline might look like. Feel free to take a picture. There's a validation workshops, they'll teach you about all the AI ML solutions on AWS itself. And of course, you can build your MVP together with hands-on guidance from our AI ML experts, one-to-one tech mentorships, one-to-one business mentorships, and of course, a final demo day. So this is done in collaboration with Epiphany, which is, I believe, the business side of things. Okay. And of course, we have a lot of AWS startup ecosystem partners and things like that. There's more people that's coming on board. And of course, we have our own people like Udo, which is a really, really... Oh, sorry, I thought my time was up. So Udo is an AI ML expert in AWS. So there's definitely really, really great people that you'll meet in this bootcamp. So applications are actually open now. Please apply by 5th October. I'm going to leave this QR code on the screen just a little bit for everybody to take out their phones and just take a look at the program if you want to. And of course, thank you. That's my presentation. And maybe I can get one or two questions. Yeah, thank you. Oh, no questions? Oh, please. Can I leave this here? No, no, one guy here. Oh, yeah, yeah. Sure. In the demo that you showed for a step-up response to world property, the client is sitting to be on at the same time or the server is going to be on at the same time? Which level is that you're talking about? So earlier you showed the step function. Yes. And for that to perform flawlessly, do you need to have those two servers on at the same time, the servers that aren't connected to the servers? Yeah. The reason being is that those step functions actually, oh, you could actually have a function that will activate these two servers and maybe switch on the servers when you're not using them and only switch it on and spin up those instances to train those models when you need to. Otherwise, I don't believe that you need to switch on those servers before the step function can work properly. So you need both of them. You cannot check. Oh, yeah, yeah, good question. Yeah, there's asynchronous and synchronous. So you can train one first and of course asynchronously train the other one and propagate the weights and whatnot. So both are possible, but the demo that you showed was the synchronous? Yeah, synchronous, yeah. The demo that I showed was synchronous, yeah. That's a good question, yeah. Thanks for asking that. Any one more question? Yeah, over there? So, you said that you can use multiple? The global model. So it seems that if you just download an open source model online, you're going to have to trade it to make something from scratch. You can just use federated learning and new model. I think you know how the global model that you can download for free is quite good already. Federated learning is a chance to expand that. And for some startups that might not have the resources to reach a lot of data sets, federated learning will post an advantage in that sense to be able to train on new data sets. Because these models might have been like CIFAR 10, like many years ago, not even CIFAR 10, like a Cocoa data set. It's so long ago. It's many years ago that there are new data sets, new types of cars and whatnot. So instead of buying those data sets, you can possibly lease those data sets by pushing a model and just getting back the weights from whoever you're leasing it from. So that is the opportunity in that sense for that side, yeah. Okay, thanks so much. Yeah, have a good day, guys.


Hi everyone Joe for jazby's case breaks.com This is a five-star break right here in 2022 tops five-star baseball, and I'm a five-star man eight bucks pick your team number 38 Let's go. Let's see what we got here last break of the night. Let's finish strong Good luck everyone Joe Locust last-ball module raise Good luck to Joe. Good luck to everybody. Thank you very much everyone for making this happen I don't think I can save it. I think it's just gonna be a mess There you go four and four make eight. It's an eight box case Thanks everyone for making this happen. I appreciate it. I'm looking at two autographs Her box. All right. We're gonna start off with Cal Raleigh 10 out of 75 rookie auto for the M's That will be for Michael Lossia and the Mariners Real nice season for him real nice season for the Mariners Good cheap fantasy option right there. Hey, Bo Jackson. Look at that. This guy knows Who's got the Royals? That's for Ryan Gansby Bo knows nice first box. We got Tony Perez part of the the big red machine Cincinnati that's for Jason Bell Gotta hit the bell for Jason Bell and The silver signatures three out of 15 Paul Canerco Silver six Silver six It's big hit time in the city That's for the white socks. That's gonna go to Jason K back-to-back Jason's We got Jose Barrios for the Blue Jays Could be a bounce back season for Jose Barrios Maybe maybe someone to get in fantasy Probably get him for a little cheap or in later rounds Toronto Marcus And then we've got Blake Snell Padres that's gonna be for Justin Martin some health issues for Blake snow, but you can say healthy. He's pretty good, too All right next box. I start putting my brain into fantasy baseball mode Oh, it seems like a thin pack probably good sign that this is a redemption in here Oh redemption and a thin car. That's probably even thinner than usual So the card is that see-through acetate design and That's gonna be Corbin burns nine out of ten Nice a trade that I would love to sound of this is gonna happen or not The trade that I would love to see the Dodgers make before the season starts Let's swing a trade for for Willie ademis and Corbin burns Move some of those prospects get those two guys in solves the Solves the shortstop problem after Gavin Lux is a seasoning knee injury and adds pitching depth Like I can stick right at the top of the rotation. All right, we've got five star base autograph purple Congratulations, someone is due to receive dot dot dot. Good luck everybody be Baltimore Boston Oh Boston Jaren Duran Duran, her name is Rio and she And it goes to Todd and the Red Sox and I won't cry for yesterday It's an ordinary world It's also Duran Duran you'd be surprised how many hits they have and we've got Randy aros arania For the Tampa Bay Rays last spot mojo There you go, Joe. Let's see if we can find his teammate. Oh From Joe to mo 7 out of 15 gold ink autograph Mariano Rivera Russell Barney picked up the Yankee straight up. That's five-star quality right here. That's a five-star man That's a five-star man. You got the little dot dot right there, too Didn't you do some recent commercials for like indeed or something like that? They got him through a commercial or some like resume service or something like that someone got him It's kind of a funny commercial. Look it up. We've got Hoy Park rookie auto for the Pirates Pirate Park Going to Justin Yeah, am I right? Yes. It was some commercial where he It was about like closing the door on a job or something like that and you're getting in the job or something Like closing the it was like that and I don't think I've ever seen Mario on over at least in a national commercial I haven't seen Mario Rivera my silver signatures Tim Reigns 35 out of 40 that is a expose Tim Reigns, which of course expose stuff go to the nationals And that'll be for Daniel Silver six. I guess we're not getting a golden graph then All right, we got rookie auto Videl brujan another ray for Joe If we can find his teammate and then we've got Paul O'Neill 53 out of 75 Another Yankee for Russell Final two hits ladies and gentlemen. Thanks very much for watching. Thanks very much for breaking with us. I appreciate it We had a great week Sunday through Thursday, which is my week. We had a great week make it a great weekend with Jason on Friday and Saturday And then you'll see me back here on Sunday. Actually, I'm actually popping the sort of do some other do some non-breaking work tomorrow So you might hear me Shuffle around in the background tomorrow All right, we got Jake Meyers rookie auto for the Stroh's terry with the Astros Terry on the board and The last one here is Adrian Beltrae and we're closing the night with a train whistle one out of five Adrian Beltrae. He's a five star man. That goes to Dilo and the Rangers I know Daniel. It's a nice little cherry on top for your night Yeah, okay. All right Dilo do it with me. Don't wake up the house All aboard the big hit express And There you go ladies and gentlemen, I'm Joe for Jazz piece case breaks calm. Thanks for watching. Thanks for breaking with us I'll see you next time for the next baseball break. Bye. Bye


Zoom has blossomed into more than just a video conferencing tool. You can do all these things that really allow you to have more enriching in-depth conversations and engagements with the folks on the other end of the phone. There's so many tools out there that allow you to really level up that legacy appearance that you have had before. We no longer will settle for lower resolution video, low quality audio. So if you don't prepare yourself for that, if you don't learn how to use those different aspects of those tools, instead of just clicking on the Zoom look and saying, I'm here for the meeting, if you don't raise your awareness and raise your appearance, raise your engagement for those particular sessions, then you're really doing yourself a disservice.


The epistle to Titus is the Donald Trump of Holy Scripture, full of brash insults, dehumanization, and ethnic slurs. It is authoritarian, demanding obedience and submission. It forbids civil disobedience and speaking truth to power the very way of Jesus. It even endorses slavery. Titus has done great harm. It is an epistle of oppression, a 650-word letter that has left a long trail of brutality. It is a wound of Scripture.


This research has developed a new type of catalyst that can reduce carbon dioxide, CO2, efficiently. The catalyst consists of a nickel atom surrounded by two nitrogens, which allows it to be more selective in reducing CO2 than other catalysts. The catalyst also has high activity and a high faradaic efficiency of carbon monoxide, CO, meaning that it converts CO2 into CO quickly and efficiently. Furthermore, the catalyst's performance remains stable across a wide range of voltages, making it suitable for use in real-world applications. This article was authored by Youshu Zhu, Kuan Zhu, Heng Jiu, and others.