So, I had an 8 page script about why Fallout 4 is better than it gets credit for, all finished.  I transferred them over to an external hard drive and deleted them from the laptop only to discover that all the Word documents were corrupted and unusable. So I no longer have any of the scripts I've written for this channel. That kind of sucks but the bigger problem is I lost the new script and was so pissed off I couldn't bring myself to write it again. At least not yet. By next week I'll be playing and writing about my most anticipated game of the year in Deathloop and then after that we'll be Far Cry 6 and then the whole holiday season kicks into gear. But for now I wanted to quickly talk about a few games I played that were pleasant surprises on Steam and PS5. It was either that or a video about how Destiny 2 was currently fine and that sounds like a boring video. So let's hop to it. Steam surprises after the logo. Death Trash Death Trash is in Early Access and the game feels about a third complete so far in that the story feels like it's just finally getting started when the current build ends. Steam says I played the game for 8 and a half hours but it's probably more like 5 or 6 as I tend to keep games running even if I stop playing for a while. The game's still a bit rough around the edges but after I finished playing it the first thing that popped into my head was this is what I wanted to get out of the ascent. Now these aren't exactly similar games. Death Trash has guns but it isn't a twin stick shooter but there's something about Death Trash that made me think that. Death Trash is basically most similar to old time isometric RPGs but with an active real time combat system. Everything in Death Trash is simple and easy to understand but the game manages to be incredibly engaging despite a simple dialogue system, a very focused progression system and combat that actually doesn't really have a ton of depth. What it does have is what makes the first two Fallout games or the original Baldur Gate so memorable.  Combat in Death Loop is as simple as it gets. You can shoot, hit with melee weapons, dodge roll and occasionally use powers but that combat works really really well and it's challenging enough for it to be more than just an afterthought. The crafting, trading and looting is satisfying because it's balanced really well. ammo is scarce enough that finding 9 bullets or crafting 4 shotgun shells feels like a big deal but you'll also never find yourself without a viable way to kill enemies. There are some sections that require a few tries to get through and that's good because everything can be overcome by trying a different approach. It just feels really good to fight things in this game which is kind of crazy because again it's really simple. And that combat is probably the weakest thing about the game. Death Trash is so memorable because the worlds and characters are totally unique and consistently surprising. It has the same depressing dark humor as the original Fallout games and the same eerie post apocalyptic world but the setting itself is both absurd and insane. You're living in a world that's covered in flesh for some reason. You play as a person who's been kicked out of one of the robot run sanctuaries because you have the flesh infection. But everything going on is a total mystery. It keeps you playing just to see what's around the next corner. It could be a giant Cthulhu monster made out of bleeding flesh or a friendly android or a weird old nudist who's just loving life in the meat post apocalypse. It's one of the best times I've had playing a game in ages. Death Trash consistently surprised me. And it's a great example that balance and thoughtful design is more important than piling pointless complexity on top of a shallow combat system. If you liked the Ascent, you'll like Death Trash. And if you didn't like the Ascent, you'll probably love it. Project Warlock 2, the demo. I'm a huge fan of retro shooters, mainly because I love shooters of every variety. If I can shoot things in first person, I am going to like it. In fact, it is insanely rare for me to not like a first person shooter. What this means is I've played basically every single shooter that's released in the last 10 years, from all the Call of Duty's to games like Ultra Kill and Amid Evil, all the way down to deep cuts like D-Sync, Devil Daggers, and Get to the Orange Door. I've very much enjoyed what the original project Warlock was trying to do, though I stopped playing it shortly after buying it for a while because the game automatically resets your resolution after every loading screen. And in game with an old school level select system, this was basically a game breaking bug for me. I recently discovered you can actually stop this by unplugging your second monitor, but still that's pretty annoying. Although I did go back and play the game after finding that out. I had read about a sequel and was intrigued and saw there was now a demo available. Now it's only two levels, but the improvement from the first game to the sequel is significant. The game's sprites are now shaded in a way that makes them look almost like 3D models. And it manages to keep the old school look of the original while feeling way more modern to actually play. The graphics are brighter and more detailed and the levels themselves are easily four or five times as large and are multi-level labyrinths. Enemies take headshot damage now and have health bars which makes for a far more visceral and rewarding combat and arenas are designed just about perfectly. It's so surprisingly good I don't hesitate to say it's not just looking like it'll be a great retro shooter, but looking like it'll be just a great shooter period.  I've played through these levels three times already and loved it. And if you like shooters or pixel art, I am confident you will too. If you've got a love of shooters, $0 and a couple hours of spare, I could not recommend this enough. Skull the Hero Slayer. Already a few months old, Skull was a game I enjoyed, but wasn't quite good enough to justify its own video. A 2D side-scrolling roguelite that looks and plays like a super NES game, but has fully modern mechanics going on. It's an interesting blend that's pretty unique. It's very much a roguelite with inter-run progression. Early runs are difficult until you unlock the best classes.  Combat boils down to stun-locking groups of 7,000 mobs and chipping away at their insane health bars, which feels cheap at first until you get to later levels and realize it's not all that easy, actually. Boss fights are challenging. Enemy variety is pretty good. Levels are beautiful. And build variety is more than enough to get 20 to 30 hours before you beat it or feel like you've seen it all. Give it a look. Wrath, Aeon of Ruin. The last game we'll look at is the annoying, repeatedly delayed old-school 3D shooter Wrath, Aeon of Ruin. It's got some real stupidity in how it saves states or handle and some oddly annoying difficulty spikes, but overall it's another good throwback from 3D Realms. Now set to supposedly release in the nebulous window of sometime 2022, Aeon of Ruin fits nicely into the dusk-amid-evil genre of Quake II homages. The game has some design choices that sometimes annoy me like it's confusing levels and a stingy ammo economy, but it is a lovingly crafted 3D shooter and well worth giving it a shot. It might be a bit overpriced for what's there right now, but the quality and offer has me pretty hopeful it'll deliver in the end. Bonus round. Finally, let's talk about a PS4 surprise. I recently saw a YouTube commercial for a game with one of the worst names I've ever heard, Ultra Age.  It's story is awful. It's acting is so bad, it's hilarious, and it is severely Japanese in flavor, but its combat is surprisingly great, which is good because that's pretty much all you will be doing. Ultra Age is basically near-automata mixed with Devil May Cry's combo system and a pretty well-paced progression tree. Levels amount to a series of combat arenas that loop back to the starting area when you open the door and fight a boss.  You can have four weapons equipped at a time and you switch between them the same way you switch between stances in Neo. Different enemies are weak to different swords and the game isn't shy about throwing a ton of enemies at you at once. It's so fluid and satisfying that I stopped playing to see who I developed it because it's pretty surprisingly good and I still don't know who made this game. One of the developers listed is actually a subcontractor that makes art assets for other studios and the main developer sounds like it's an architecture firm or something and it has no English website. There are no other games by these guys. This game is legitimately hilarious because the story, acting, and character designs are like a parody of terrible Japanese PS2 action games.  If the action was bad, the game would be unplayable but because the action is actually so good, it's hard to know if this is a winking kind of joke or if it's just a bunch of people who made a badass action game and then wrote a story in a few hours at the bar after work. They were drinking sake and scribbling in a notebook every time someone had an idea. Okay guys, here, how about this? There's a guy named Age and he only has seven days to live but other people are immortal and he's like stuck on this world and there are these crystals that he can use to make big swords and then, wait, wait, wait, wait, wait, wait. Why does he have seven days to live? I don't know, don't worry about that. We'll figure it out in the sequel. It probably sounded reasonable enough but then they realized they had 2,000 bucks for voice actors.   I hope it sells well because whoever these guys are, they deserve to get the opportunity to make more games. I seriously can't recommend this enough as long as you understand what you're getting here. This is a game that does one thing and one thing only really well. Luckily, that thing is excellent.  It really is a diamond in the rough and a hidden gem that shouldn't disappear without you playing it. There looks like there will be a Steam release at some point but it's still listed as TBD. I played it on the PS5 but it's very much a low budget Japanese PS4 game. Wrapping up.  But I'm gonna hold off because I might actually do a whole video about it. It's one of those games that has a ton going for it but still pisses me off half the time because its mistakes are so glaring. Yet it's getting very good reviews because I don't know it has a rabbit in it. I don't know actually. I'll probably do a very fast video about it once I finish it and after I do a Deathloop review.  See you next time for Deathloop. Hey, if you're on my Steam friend list, invade me. If you haven't added me yet on Steam I am plenty the welder there. Include the spaces between the words, it's right here. There you go. All right, thanks for coming. I'll see you next time. Bye.


I'm just coming around right seeing if and he's used home The internet's down and that and like my computers a bit old and stuff if I come in or something Could I just like hand in my rev may and have a like talk maybe to a manager there? I'll even do like free free trial run. I'll just be in the back like clean enough And now that I'm sweet and hook us up brother Like I can't apply for it because my laptops like But I need to work to pay for the Lappy, you know what I mean? So it's like a triangle. You see what I'm saying Well, how about I'll just bring some beers over and we'll just get on it Don't don't say yes. No yet. No, I can't give you an answer yet I bet by the end of this month from like up on like your level be running a managing the joint Seriously, I reckon I'm bored for the No


Hey stampers! Welcome to another week of Watch It Weekly Wednesday. I'm Aubrey and today I'm excited to share with you some information about our Stampin' Blends. It's been a while since I've shown you some projects with the Stampin' Blends and I just wanted to kind of go over some things with it. I was searching on Facebook the other day and I came across a post that said I haven't been sold on the Stampin' Blends. Who can tell me why they love them and why they're so great?  But as I looked through, her question had already been answered and somebody had showed her the difference between our regular Stampin' Wright markers and the Stampin' Blends and how different they look on different projects. Now, our Stampin' Wright markers are fantastic and they have a place, but our Stampin' Blends have their own value too. And I just wanted to show you a little bit of the difference between them when you're coloring an image. I want to show you how different they can look on a project. So that's what I'm focusing on today. I don't actually have a card to show you, but I'm really excited to show you the technique of the Blends and how you can use them to beautify your projects. So first I want to tell you which stamp set I'm using. I am using the Humming Along Kling Stamp Set. I thought this was a really good one to show you how to color these really big images here, this cute hummingbird and the flower here. One cool thing about this stamp set is that there are framelets that coordinate the hummingbird framelets. Let me show you this. This is what they look like cut out and it has this cute label that you can cut the sayings out on and cute details here. So this is a really fun stamp set. So if you want to play with that, I encourage you to do so. So let's get started. When you're using Blends, the best ink to use is the Memento Ink Pad. It's good because the Stamp and Blends are an alcohol-based marker and the Memento Ink Pad is a water-based ink. So when you use them together, the lines don't run. So just keep that in mind if you do use the Stamp and Blends. So I wanted to pull in some of the images here that I've already stamped and colored and I want to show you the difference between using the regular Stamp and Right markers, which this is what they look like here. They're awesome. They're double-sided. They just come like, this is the Bermuda Bay one. You just get one color in it. And here's the difference between the Blends. They're also double-sided, but instead of just getting one marker, you get a dark marker and a light marker. So and those go together to blend the colors. So here is a hummingbird from that humming along set. I colored this hummingbird with the Stamp and Right markers. He's super cute. I used Bermuda Bay and I used Mango Melody on him. Really, by himself, he looks great. And you could put that on a project and it would look fantastic. I just wanted to give you a look of what the Stamp and Blends look like. Let me tear this off here. You can see this is what the Stamp and Blends. The difference here is you can get a lot more depth from your image. You can use the Blends to add colors and to then you can also use the color lifter to kind of take some color away in places that you want. You can get a more realistic look with the Blends as opposed to the Stamp and Right markers. So there's our hummingbird. The next one I want to show you. This is that pretty flower that's in that humming along set. This is colored with the Real Red marker and some Old Olive Stamp and Right markers. You can see there.  So again, you can just see so much more depth in that image. Jill actually colored this one for me and she used again the color lifter just on the edges here to just give it a little more detail on the edges of the flower there. And you can just see the difference of what that image looks like. And one thing I want to point out, when you color such a big space with the Stamp and Right markers, you kind of get these lines in here. That is something you're going to get with any water-based marker. It just happens. But with the Blends, you don't really get those lines because you blend them all together. So let me show you one more here. I used this. So on this one I used Petal Pink Stamp and Right marker and Calypso Coral just here on the lines. And this, I think this flower is beautiful. I think you could put that on a project and it's really cute. Let me just show you what I did with the Blends. Oh, and this is Old Olive for the Stamp. And here's the blended one. Now the cool thing about this, I still used Calypso Coral and Petal Pink on this flower. And I was able to blend those two colors together. So let me show you. I used Light and Dark Petal Pink and Light and Dark Calypso Coral on this project. And I blended all four of those colors together. That's another really cool thing about the blends. You don't have to stick to just the two Light and Dark colors. If they're part of the same color family, like these are all a pinkish color, you can blend those together. Calypso Coral is one of my very favorite blends. They blend really beautifully together. And I've been informed, for ourselves at least, from Stamp and Jill, this is one of our most ordered blends color too. So it's a very popular one if you need a place to start. Calypso Coral is a great one to start with. So I just wanted to just show you a little bit what it looks like to use the blends on a project. And I'm just going to start here with the flower. And I'm going to use that Calypso Coral and Petal Pink together just to give you a look of what it is. Everyone kind of has their own way of using blends. I personally start with dark and work my way to light. You blending the dark in with the light. Some people do it differently, but that's what I find works best for me. So I'm just using my dark Calypso Coral here. And I'm going to just outline these lines in the flower and kind of give it a little bit here. Just some color there in the middle, like that. And then I'm going to take my light Calypso Coral. So that was my dark Calypso Coral. Here's my light. And I'm just going to color right around that. Just blend those colors together. And something to know when you're using blends, they do bleed. So like on the back side, you're going to get this bleeding. So make sure you have a scratch piece of paper underneath. And just like that. And then I'm going to go to my Petal Pink. This is my dark Petal Pink. And I'm just going to blend those colors together. Now, these aren't the exact same color. It's much lighter, you can see. But the more you work it, the more those colors are going to blend together. Sometimes it takes some time. But you can see it starting to work. I go in a circular motion so that I don't get straight lines. And I just work my way out. And then I'm going to take my light Petal Pink. And I'm just going to, again, blend right over it. And you go right over the colors you've already done out to the edge there. In a circular motion, blend it all together. Just like that. So I guess what I would, for somebody who is asking why blends over regular markers, if you're not sold on them, you can't do this with a regular marker, any regular marker. An alcohol based marker is the way to go. If you want to get that extra detail, that extra depth in your projects, it's a little bit more artistic, but it gives such a beautiful look to your projects. If that's your question, why the blends, that's my answer. You can get such a different look with blends as opposed to just a regular marker. So I hope that you enjoyed this tutorial on how to use the Stampin' Blends. If you have any questions, please post them below. We'd love to hear from you. And if you like this video, make sure you share it with your friends and give us a thumbs up. Thanks so much for watching. We'll see you next week for another Watch It Weekly Wednesday.


And baby, get the askin' Tell em, tell em, tell em, tell em This is what I checked, take some on, we are Rebellies I'm not sure we're cool, but slow down a little bit so we can see I got it Damn What was he doin'? Alright, I was a little girl in there I was gonna get you right now Obviously, we're gonna be kiddin' these motherfuckers 800 block Can't be on no style Grandma house, we just ate Really good We ate chicken and spaghetti and we had a lemon cake Think that's one of those? And I had Dr. Gabby That's it And change of plans, we're leavin' out Tuesday morning, not Monday morning 6am 6am What is it? What we goin'? Jeez We at her unhouse, we about to lay down Why do you gotta put me on there? We about to lay down in this comfortable bed Oh my God Anyways, we all got our bunnies on, we about to go lay down We look amiss With hot pecante sauce Getin' our breakfast ready Y'all look how we look I don't have no shorts I don't need to bro, I want pair of leggings It's hot outside I'm gonna go buy some though I'm gonna get some shorts Am I in it?  So how big does it get? To buy one of these is $3,500 $10 And like I said, I imported my shipment off This is it You know what I'm saying?   Yeah It's called Bill Street To the left Oh my gosh Where the hell Just gonna cross the crosswalk We're a little seasick right now I'm about to get a little five dollar piece Because we bought a number And all our money is supposed to be for Clothes and shoes and activities in Atlanta I thought you were on the phone I'm getting a pepperoni piece We made this fine dude He a trainee What you getting? I want a sausage I want pepperoni How much are they on planes? We got bags We got eight bags Six feet Converse Oh Could I get a sauce too? Can I get a sauce? You want to eat the sauce? It's separate We are separate We are separate Anyways this is about to be one o'clock And we're leaving out to Shhh We're leaving out to go to We're leaving out to go to Atlanta It's six o'clock in the morning We're going to wake up at like Five o'clock in the morning We're going to wake up at like Five o'clock in the morning We're going to go to Atlanta at six And after we're on the road I'm going to end the vlog there And then start another one for all the activities That we're doing down there So good night into six Good night, Dyches And Tay trying to find a show Good night from all to Dyches So I'm being a wrecked right now It is Can I see? I hope so It is Seven fifty five We're supposed to leave out At What? Six Wake up at five and leave out at six So we behind schedule because Somebody wants to sleep Neaky Take out of the world We're going to be here We're about to head out On the road You got my stuff down It is Straight to the gym And then this is my We're going to run down Goodbye Ashy Anyways we're about to go get something to eat And then after that We're going to be on the road In about a year At a gas station in Alabama It is called Flying It got a Denny's It have a Denny's in it Denny's there Let's go in the stove Look at this thing I don't like cinnamon like this I don't want one too I got that in my mouth I think I see a tree so much We just made it to One of her other aunts Houses in Atlanta And these are so cute They all look the same though But they're really cute She just fresh out of school I can't believe I'm back in Atlanta Like this is just the life Say hey best friend They're getting out of school right now I'll just say it then Niki Y'all excited?


Hello, hi. Oh, yeah, the mic is working. Hi, good morning. Wow. There's quite a crowd given we have daylight savings So thank you all for making the journey an hour earlier I've been really honored to Give the art to be asked to give the keynote here at scale and First of all, I'd like to wish OSI and open source A happy 20th anniversary as many of you know, it's it was 20 years ago that the term open source was coined and What we've been doing and what we see People that have been in the community for a long time doing is storytelling So what I'm going to do this morning is is storytelling and and talk about Some of the things we did in the early days that really Help kind of put together the building blocks to enable our success and a lot of the things that we take for granted and Looking at some of the popular projects and some of the key people that were involved So Yeah, one of so at 20 years on You know open source is one. That's what we're being told right and Linux is everywhere and Open source is also everywhere in the cloud We have one how many people here thinks we've won Okay, that's a lot fewer than hands and I thought So look at these numbers now these came from the Linux Foundation, you know, 23 million over 23 million developers 41 billion lines of code 64 million repos on github and 1100 new projects a day and So this is significant amount of growth. We're also seeing that, you know software is disrupting markets But it's really open source that has been the biggest disruption in the software industry We didn't do it overnight. It took us 20 years or more to get here and You know, it's open source. It's the 20th anniversary of food softwares also been around for a lot longer than that. So We've got a lot of people consuming open source and When I ask an audience how many people typically When I ask a non-technical audience, how many people here are using open source very few hands go up because they really don't understand That behind, you know, every device that they use And everything uses open source even the phone. So And we're we're gonna see a bigger group of developers joining our community from companies that are consumers and They're not yet contributors and they want to learn From kind of what we've been doing over the years. So I can see there's a lot of very Seasoned people within this community. I know this community has been Active for a very long time and scale has been going on for a long time as well. So it's gonna be important to tell our stories and not have folks Feel that this is like, you know, just a given this is like how it was handed to us and The work that went into getting to this place that we're at now And we have as a community a lot of sharing to do. I know that there's been some great talks This week here as well and really really packed rooms So in the beginning I'm gonna tell my story and that's what's happening this morning and You know Being asked to share my story I knew that I always wanted to travel the world and work with different cultures and learn about them And then I did a computer science degree and then this happened as my career so the various projects the companies that I worked with and some really like interesting Milestones for example, you know getting the UK government to select a standard for Open technologies so that all government software would it would enable open source to work alongside other software As well. So, you know, I guess the stars have really I feel very blessed very aligned within my career That I had some of these opportunities including summer of code setting that up and running that for the first two years and It's really taken me around the world and working with really brilliant minds in the industry and As a student, I guess most kids at all, you know, you can do programming Or do systems analysis and I guess back then that's those were the two options And I wanted to do both and I wanted to do more. So it wasn't until much later 1999 when I found open source and that just really felt like a calling and The journey with open source open office Started when it was announced in 99 The project, I don't know how many of you use open office or Libra office Fantastic, wow, that's pretty much the whole room. Awesome. So You know the journey started the code base was seven and a half million lines of code so for the time it was a really really large code base and It was interesting because the the company that was acquired by Sun Star division was based in Germany. So most of the developers were German English was not their native language They all sat next to each other working in an office where they've been They've been collaboratively developing the software for 12 years and and we then had to release that code base and Engage and build a community around that code base and evolve it as well We had some incredible help from Brian Belendorf who is one of the Apache founders and Also, he ran a company called collab net and we had You know all the things that you would expect in say an Apache project now with mailing lists all the right mailing list dev lists projects structured in a way that It was easy for newcomers to come and go and Figure out which of the pieces that they wanted to work on And they represented the various modules that was available in the software and We kind of learned from Some of the folks that had come before us, but there weren't too many of those back in 1999 and 2000 so For me open office was a really incredible journey after that I went to work on the net beans project and I had the chance to travel to China when we were releasing net beans 3.6 the localized version and and you'll probably recognize this gentleman on the screen James Gosling father of Java and James came along on this trip to release a local language version and Talk to kids in the university Talk to developers across China and we also got to travel Along the Great Wall walk along the Great Wall of China together as well At Google I was fortunate enough to Be part of the Well, actually, I was the only one that traveled with Vince surf through Germany and Austria visiting a whole bunch of Universities and taking long-trained journeys and part of that was trying to understand what would the universities teaching kids? and how much open source was included in that education and along with that having Vince on the journey we got to meet the commissioner of the European Union and Influenced at that higher level as well about the need for Open source in education You know on a trip to Kenya, I spoke in Nairobi and working sitting alongside the ICT ministers Minister for Kenya and The audience is really a government education group and We talked about I talked about Google Summer of Code and how it was easy for students all over the world to participate in that and and Mark shuttle with was also there as part of canonical Ubuntu and I got to travel back mark and the Canonical crew on a private jet back to London. So, you know some some fun things It wasn't all work and here's here's another opportunity where traveling to other countries and this was in 2006 so In the early days really kind of helping spread our message to lots of different Geographies and Individuals that were working within the community. So here we had, you know, my friend here Denise Cooper who's sitting at the front She actually took a lot of these pictures But Jim Zemlin who heads up the Linux Foundation. He was just starting up the Linux Foundation at the time Brian Belendorf David Axe mark from my SQL so it kind of felt like a now it feels like a who's who of open source But above all of this, you know, we kind of travel two conferences and Tell our stories and when you look at the 200 or so talks here, you know It's storytelling or teaching your craft and that's a really really key part of what we do It's, you know, not just the mentoring within projects, but it's also Sharing sharing what you know sharing and collaborating. So it's essential part of growing your community and Then events and conferences the open office community was very creative and There were community hosted conferences in different parts of the world. The last one was in Barcelona this one is in Copa and again all organized by volunteers on a very tight budget and You know, it's so great to come to community conferences like this and See kind of the networking and the collaboration that goes on so my first lesson is that our communities are global and seek out every opportunity To connect and in connecting you will also be recruiting for your projects as well And that's a really important thing to do. What a friend of mine who works at AWS and he was at Apache con last year and He said that we were all recruiters and I kind of I guess I kind of squirmed at that thought but you know Later realized no, actually, it's a big part of our job to go out and we engage with the community And when we make that connection That's when we get Individuals collaborating and coming and working with us. So it's a big part of what we do The next story is about finding your tribe How do you play now? How many here are new to open source? Wow, okay, one hand. Okay. Wow. So this is not the norm and I was expecting this to be a very seasoned Community and community of developers and contributors. So I Guess for the gentleman in the back, you can come and see me afterwards I am not going to spend too much time on Actually finding your tribe, but it sounds like those of you that have been contributing for a while have actually made a connection and Found and connected to your tribe, which is really really key. So with open office as well, you know again, very early days of open source it was really important to make sure that the values of your community were articulated well and You welcomed people that came to your community and you shared and you actually shared not just the information but You know your craft as well So so here's for I Guess I don't need to ask the question now. How many of you have been doing this for a long time But how many have been doing it for more than 10 years working in open source? Okay, fantastic. Wow, that's over still over half the room So, you know finding your tribe, I mean tribes are in different forms Some kind of I know for open office it started off mostly Initially was the German contributors and the community already working around the code, but it didn't take long for it to spread Globally particularly because it was an end user Application we were developing which mattered to many people Because they were looking for something to run on Linux. They were looking for it to run on operating systems that Current office productivity suites were not available in so and part of it is not just Contributing but also for the new people in the community is finding your mentor and You know in open office it was and this was taken in Beijing at one of our events but Mentoring was very very key early on and you know, you will hear this in many many talks now, but it's really The this is the reason why the community one of the reasons the community really grew and was successful that we were able to Mentor the first set of folks that joined the community and then they in turn did the same and we kind of had this like huge kind of like branch of a tree spreading out and Supporting the rest of the community that showed up remember people didn't know what open source was or how to even engage at that time I Felt we did a really good job in open office You know, I mean summer of code was a really good example of how mentors can engage with developers and help Bring people up to speed very quickly so they can be productive and this is the Apache tribe and I was very honored to actually take this photograph Of the Giants on his shoulders we stand so a lot of the lessons that I've learned From the early days of open source have come from a lot of the Apache community members people like Brian Bellendorf and Greg Stein and Given you know, so many hands were up in the audience The key to success in your project is also about leadership and building and using your leadership skills and I'm working on organizational development And it's not just about the code that you're involved in or the key activity But kind of looking around and looking at the whole community and even now going Okay, what's other communities doing that are? That are growing those communities, how can we change and improve on what we're doing and in the early days We did a lot of that so there was some conversations with the GNOME foundation with Mozilla We were trying to kind of also learn from each other so mentoring sharing collaboration and Also learning Just the key they're the key to learning and development and You know these lessons seem like yeah, of course duh, but really this these are the lessons from the early days that have kind of come forward and Enabled us to be successful in what we're doing today so This story is as kind of an entertaining one I don't know how many of you remember this ad on TV I wanted to play it but No, it's It's an Audi ad and I kind of grew up with this tagline, you know, war spring Duke technique now It really stands for Precision in engineering and and German engineering was kind of considered a Almost like, you know, what everyone else was striving to achieve and So I with the open-office community and the developers it was interesting because the developers really prided themselves in perfectionism and really building something that was going to go out and actually be perfect so in open office you know It was it was interesting because Yeah, we kind of needed to teach people how to do peer reviews how to let others look at their work and Putting putting out code that Wasn't complete because we would building we're doing developer releases and and they weren't complete But every build that went out the first couple of builds there was absolutely nothing wrong Like everything was fixed everyone was just hunkering down because it was their work that was being Displayed and nobody You know this they were used to working on a product, but they were releasing for end users and We had an incident where this build build 613 Was released and suddenly and it was broken It was broken, but What happened was up until that point the the engineers were struggling To really get engagement from the community we had We just had Like people lurking there were just a lot of lurkers. There was one guy who started working on the Linux PC port and he was a academic from Canada and He was working on this port, but there were very few because the code base wasn't very modular You know there was engagement and porting and in localization but the core part of the code was really really hard to get into and So many people just lurking and watching and then all of a sudden with the 613 build it went out and there was this hive of activity going on in the mailing list and the engineers were just mortified that they actually released something that was broken and But it was the best thing that could have happened to the community and to the project so What happened was a lot of people got involved in the conversation and we ended up Really kind of having a collaborative effort in fixing it and there was a there was a big lesson for for both the Sun engineering teams are active in the project and the rest of the community to learn as well so here, you know perfectionism is not always your friend and Leaves things for the community and of course we know that you know release early and often It doesn't have to be It's it's fine for it to go out with bugs because that's where you get a lot of engagement in the community But these were hard lessons learned by Teams that were releasing code and it wasn't just the open office community This was happening in many other projects and you know a lot of the time at the time There were a lot of companies that were pushing And releasing their code and making that available as open off open source Nowadays with GitHub a lot of the code already starts out as open source but there are still instances where companies are releasing code and Some of those lessons still need to be repeated so that people can actually learn from them now this next story is about being the change and You know whether it's an open source project or a program and like Google Summer of Code or like Outreachy You're working with people. I'm just checking time. Okay. Yeah, and we you know Linus is Is known for saying many people are known for saying that really it's about the people The technology is the easy part of what we do It's actually working with the people and getting that part of it right is the is the biggest challenge, right? So You get not just community but you also get you know the good the bad and the ugly that comes with it and I think it's important and from the very outset You know one of the things we did was show kindness to everybody that showed up and really understand and listen be transparent in what we were doing and show some compassion The other things we did was we displayed our Mission statement and our values very very clearly. There were no codes of conduct back then now every site has one You can just go grab one put that in with your project so these were all these are all things that were developed as a result of some of these projects and As well as you know stating your mission very clearly and that helped our project really a lot because you know When people come into the community and they want to do something different you can all go back to your Mission statement and say hey, this is what we're about That is not what we're about and having that clarity really really helped us So these are two of my mentors Brian Belendorf and Greg Stein again. I mentioned them earlier from They're both part of the early Apache project Brian was instrumental in helping with open office From from his work with collab net and Greg Stein as well the other person is Denise Cooper and Denise was instrumental also at Sun not just in mentoring Me and our project but in mentoring a lot of the Sun projects and she was pretty key in Really kind of the success of open source at Sun there's a lot of innovation that happened in the community and For example, we had a small team in Hungary and innovation happened on the fringes because the Main core part of the code base Really needed to be refactored and it needed to be much more modular So that was the work that was going on While the rest of the community kind of like gathered around the fringes and here we had a small team in Hungary that fed pizza and Coke Coca-Cola to students all weekend for three days and they translated the whole of the office suite into Hungarian office by you know by the Sunday night and Actually, there's somebody from the Guinness world's records there who captured it and they they had an entry in the Guinness Book of Records for the fastest translation The other innovation was the downloads for open office just grew like crazy, you know We started off with like tens of thousands and before we knew it. We're into hundreds of thousands and Our Sun budget was running out. So we were paying for Akamai servers and for the downloads and Because the money was running out. We didn't know what to do We just didn't hadn't factored that in and we ended up asking the community If there was anyone who could help with this and within literally You know two months two to three months. We had 45 mirror sites set up all over the world that helped us with our downloads and really the fact that we had Little money for it Wasn't really a problem. So there was a ton of innovation there and then See innovation Doesn't just happen on its own. You have to also set up an environment as well For the community to innovate. So in the early days You know, we had a lot of pushback from the community that it wasn't so easy to engage and one of the problems was a copyright Agreement and the Sun lawyers had written a copyright agreement that really required all the contributions to be assigned to Sun under this license and A few community members in the early open office Who took the time really to explain to us that this was a barrier to community engagement so they were not happy about it and of course there were lots of heated conversations and they wanted to really work collaboratively with us and Explain explain to sign explain to Sun lawyers You know why it didn't work for them and especially in Europe, you know There's something called moral rights and you can't transfer your moral rights over to a company either So this was a problem for European law as well You probably know this gentleman here Josh Burkus So there was Josh. There was an Italian lawyer on the key in the community John Luca Tocconi and and someone in France Geek apra and three of them. I remember were really instrumental in helping us understand the importance of changing this and Denise was also instrumental in this in working with our legal system into in Sun and making sure that we We actually got the Sun lawyers to Work on this and and not dismiss it. This was a key part of our success Right, so it took about a year to change so you can imagine the conversations the meetings But we did change it and we changed it to something called the joint copyright agreement Which meant but the individual also retained all the rights as well as providing those to the project and Yeah, it was quite it was quite a job convincing Sun to change it and It wasn't just changed for open office, but it was also changed for all of Sun's projects and everybody benefited So just in the same way that some of these things some of these Ways of working that have been tried and tested in these communities Getting shared and getting shared at conferences like this. They're the ones that actually help You know other projects and on a much broader scale so the lesson here, you know is really it's about people and communication It's about listening that's a really big part of it and really being open to change and You know, I was very blessed that we did have lawyers in Sun who were who were open to change and the community that really had the patients to learn and Help us fix this and that's what really led to a lot of that innovation so I Had to put in trolls in here, but unfortunately, I'm gonna disappoint you because we were very lucky as a community We had a lot of people He showed up in the community with a huge passion to help us and help us bring about change We don't recall any bad incidents. Yes, he took conversations and there were there were discussions. Absolutely You know, we formed a community council because a community wanted to have a bigger voice Across everything and typically when you have a project that's released by a company most of the developers tend to come from that Corporation initially because they have that knowledge base but over time that should change and It should change to have a much more inclusive voice and so as part of the change It requires some interesting conversations see one of the community members did fall out with a few people and He had some ideas and it wasn't around code. It was around documentation and he wanted he wanted to present the information in a very different way and Attribute it in a very different way as well and He fell out with some of the community members because they didn't Understand what he was trying to do because it wasn't the way they had selected to do this You know, there wasn't anything wrong with that But so they kind of dismissed him Maybe they thought he was a troll and they just kind of dismissed him and he went away This is what typically happens in projects if people ignore if it's not something that's invented here. They ignore the individuals and here what happened was he went away and he built a website and he Demonstrated what he really wanted us to do and then when I looked at it and others looked at it It just felt like yes, this is the kind of thing we should be doing within our community But our current infrastructure did not allow it and that was a limiting factor you know the the service that we had through collab net did not allow us to do that and But it was it was a really great example of a community member going away and actually doing the work somewhere else And he created this website called 000 docs And of course there are people unhappy about that, but there was also an overwhelming support of yeah This is something we should be evolving to to doing We knew that the infrastructure wasn't going to change at any time soon So we provided links to that site and we kind of embraced him And gave him access to a whole bunch of webpages. So he couldn't he could actually be a webmaster on the project as well and It kind of ended up being a really positive results for the whole community. So again, you know Innovation doesn't always happen within the frame of what you know It happens elsewhere and this is a great quote from Bill Joy So, you know, let people help and Understand if somebody is passionate and they're having a heated conversation they care about what you're doing and If they didn't care they would just go away So in this next tail, I'm gonna present I Guess I had I had depicted Companies and benevolent dictators for life of projects As kind of the dragons, you know, they contribute code They provide the sponsorship, which is much needed. They provide resources they provide support developers lawyers money And it's a great ecosystem when all of this works well and It's for the companies. It's really and the bdfl's It's a whole dance between control and support And I don't know I don't know how many of you work in large corporations here Releasing open source projects and and have worked on open source projects Where the code was contributed by a large company or a by bdfl You're kind of It's a really really fine balance, right? So for example in in open office We had we had son donated the code for the Mac port for open office to the community and often what happens is The code is donated and at some point the developers are moved on to another project and This happened with the Mac port the six developers that are working on the open office Mac port were moved to another project now Now We had one of the community engineers Developers we had we had an individual in the community who was proactively working on the Mac port once it was released and He created something called at near office I don't know whether any of you on the Mac have used that but he added an additional clause To his contributions for new office so he could take basically some financial donations to keep his work going and That really freaked out the Sun lawyers They were trying to break that he thought that he was trying to break open office and That it would reflect really badly on them the press really loved the Mac port because most of the press were Mac users and We got some really really great reviews and write-ups because of that But the company's reaction was really not to embrace this new office port So and meanwhile The former lead for the Mac OS project, you know the guy who was running this team of six developers His heart was still in that Mac port and even though he's moved to another project He actually came he actually left to the company and he joined the Ed or who had actually created a new office and he started working full-time with Ed on that project So the company lost, you know a really really good developer now It's it's a symbiotic relationship between the organization and Living as part of that community and it was in this story it kind of shows that that basically you can take your skills you can take your talents and Choose to go to the projects and the work that you want to do You know, it's companies are starting to realize they can't just move open-source developers off of a project Onto another one because you know that project kind of lives on and The control and support There were a lot of lessons learned by corporations and and still do and I think as we have more and more enterprises participating in open-source and Releasing their code as well. There's a lot of lessons here to learn In actually letting go when you're releasing it to the community provide the support But the whole need for control companies are going to find that The earlier they let go The more rewarding it will be as well as as a community relationship Okay, so The next story is on superpowers now You've worked with others that have excelled with superpowers and you see them you see them in your community, right? and So what are your superpowers, you know, maybe some of these I don't know But in reality right You're just brilliant at what you do as whether you're a coder where your creator whether you're a leader You know whether you're Great at creating and collecting people You may be a good listener You may be great in your community as a mediator when issues come up and that may be the best time That's when you really shine You may be the warm friendly person who greets everybody and that is your superpower But you all have superpowers and it's important not just to recognize your own but to recognize that in other people so You know, we looked at the Giants some of the Giants earlier and You know look at the people in your community that you feel are the ones that are The the leaders that are the Giants and why why what you're doing is successful And what can you learn from them because the one thing or open source affords a lot of great input into our careers But also it's learning from your peer network and if you're working in company, you're not going to have Necessarily the people with the same skills that you look up to as you will in your community as well so You know, how can you learn from others in the community? And the other thing that's really important I think really important for the I guess the kind of generation of Developers and community members that are coming into the projects is that it's actually really really hard work. We have all been doing this work for a long time and It's not something that You can transform overnight that people want to come into a community and It's like six months work. No, we've been doing this for you know 20 years and some of these projects have as well So recognizing that it's not something that you can just kind of speed through and it's an important It's an important lesson for companies as well. So here like yeah, everyone's got superpowers and You know, none of anything that's been accomplished in open source has happened with speed Okay, I just wanted to leave this page intentionally blank just a pause So the last story is on the reward. What why do we all? Working in open source and I think everyone has a different reason for Contributing and participating So the open office story here is that you know, as I said earlier natural gravitation Towards languages in the community just because you know, it was something that would sit on everybody's machine and It could be used globally by a large consumer base so typically with an office productivity switch or something like a Browser or some of the kind of the basic software you need on a machine To run your like your operating system as well and back then GNOME was very actively involved in this work but with languages typically company will only translate into maybe 25 languages maximum any any kind of users any user software and That was a big problem because when you look at India India alone has 200 languages so we look at how many people are not getting the opportunity to work with technology and the barrier to learn English is way way bigger than The barrier to actually learn technology That was a huge insight. I had at a conference. Actually. It was at the Copa conference When I had somebody from Cambodia saying, you know In our country people can't actually do very much of technology because there's such a big part of the population that just doesn't speak English, so Libra office was translated open office and Libra office now is available in over a hundred languages and We really supported the language community and we had this thriving Engaging group doing translation So that's my father on the Screen he's 87 this year and he came from a village in India in Gujarat and He really understood the value of education over 25 years He raised enough funds to buy some land a group of them had a high school built and then a junior school and And Now there are over 1500 kids that go to that school that would not have had an education Because the schools were too far away and for most parents in the villages. It really wasn't Important to send their kids because they wanted them to work in the fields. It really wasn't important to send them to school. So, I am I It's about my my my folks are from the Gujarat both my parents and With open office, I was given a CD of Open office in Gujarati Which I actually took to the school and installed on their donated computers So that the kids and the teachers could actually start to learn and use the technology and use the computers ahead of learning English really well and You know for me, it was a really huge reward to be able to be in service and support the education of this school and and support the work that my dad was doing and These are the kinds of moments that matter to me In the work that we do now those this kid who did that translation in open office and He and I got to know each other over the years and especially because he mentioned I kind of looked up Gujarati and he was doing the work so we connected and He did the work for Firefox. He did the work for many other applications as well and the really cool story here is that He got through his work in open office and through his reference he is now he did his engineering degree and Because everyone could also see his work He was hired as a release engineer for Wikimedia foundation and it's the kind of opportunity like he was in this small college in this remote village in India and it's a kind of opportunities that these kids like really only just dream about So open office has not only just and the work has helped, you know improve kind of the technology skills of People all over the world. So when I travel from Nepal in the south of India to sorry in the north of India To Tamil which is spoken in the south I've been given off open office translations or CDs back in the day For all of these languages and in Africa as well. So We're really as a community doing open source have Engaged a very kind of large global force out there that is passionate And we may not see this in the US But as you travel the world you really start to see how much support and Engagement there is for the work that we're all doing and so You know the rewards might be that you just love being in your community And you love the work you do the people that you work with But a lot of the TED talks that I've watched when they talk about like humanity and what is it we want to? What is our purpose what we what really sparks us a lot of it goes back to belonging and connecting to people that are share your passions and that you that you actually Collaborate with and enjoy It's a big part of learning as well which sparks people or in my case. It's also the being in service and the bonus for this kid and so many I mean there are just So many stories of people that have got careers in open source or careers in technology Because of the voluntary work or the work they did in open source So it really is your reference and the community is your reference So I want you to kind of leave you with a couple of things to think about one is you know What are your superpowers and how do you use them? What are your stories and I'd really like you to share them I am Zahid to be on Twitter So he to be at Amazon. I'd love to hear them Our work isn't done, you know, we have much more to do and it's not the end I'd like a few acknowledgements here for the folks that have Contributed to the storytelling and the book Yeah, so those are my that's my information if you want to connect with me I'd love to hear more from this community as well and one of my co-workers is speaking right after this So I said that I would give her a quick plug. Thank you I don't have them. I don't think we've got much time for questions Yeah, okay. No problem. Cool. So thanks everybody for for joining us this morning Zahid as is our as our custom. We'd like to welcome you to the scale family with a personalized jersey Oh, thank you everyone. Thanks for joining us and being part of the team Again a couple just a couple quick updates as I mentioned as Zahid I mentioned dear Joe be speaking in Room 103 at 1130 about marketing your open source projects Again, Ty shipman who is going to speaking about credentials and passwords and access control after death has Unfortunately, and is unable to join us, but Kyle Rankin has graciously joined graciously volunteered to give his sex sex God and Passwords his brief history of bad passwords at 1130. It's a longer version of his upscale talk That was that was given last night. So he'll be in room room 106 Other than that, please don't forget to pick up your scale t-shirts on the expo floor There's still quite a few of them in booth 431 and we look forward to seeing you throughout the rest of the day Thanks for joining us at scale and see you in 2019


Look, she's still, she's touching my stuff. Why hunger jack? It's sheep. Why not red rooster? I don't like chicken that much. Emotional damage! You like spicy food? No. Why not? It hurts my mouth. What are you doing here at Jindal? I'm getting clothes. Um, trackies. Trackies. Are you getting champion ones? No, I don't like them. What brand of trackies are you after? Probably Nike. Nike. Why Nike? I like the look. I like the logo. You like the ticket? Yeah. Do you get texts and tests in the school? Sometimes. Why sometimes? Because some classes are not good at. This girl wanted to be interviewed before, but then she changed her mind, so decided to interrupt. What are you? The press is... Excuse me, I'm interviewing someone. Thank you very much. I'm interviewing... These kids need a better education, not being rude and interrupting. And this is an example. Teachers do better. Look, she's still, she's touching my stuff. Teachers do better.


Hopefully the slides will hold together enough for me to actually give this talk. Thank you for the introduction. As it was said, I'm Ariela Hamlin, and today I will be presenting our work on private anonymous data access. This is a joint work with Raphael Strausky, Moore Weiss, and Daniel Wicks. So without further ado, let's consider a setting where we have a server, a single server storing some database, in this case, a medical database. And we have a set of clients who want to make queries into this database to get information about flu symptoms, especially given the flu season we've had here in the states. You might have someone who is concerned about their headache or headache causes. But for other clients, they may be concerned about sort of their queries and their identities being linked to those queries. So in this setting, they want maybe both privacy for those queries and anonymity for their identity. So this is the setting that we consider within Panda, essentially a single server with multiple clients, and we want to be able to provide privacy and anonymity for the client's asking queries. So as with all works, we have an acronym, namely private anonymous data access, or as we like to call it, Panda, because who doesn't like adorable fuzzy creatures? So for the rest of the talk, I'll be referring to our system as Panda. So without further ado, what does Panda actually consist of? We have a set of protocol that takes in database and generates for each of our clients essentially a unique client key and gives the server an encoded database. So in this case, both the client and the server are stateful. We also support writing or, sorry, reading. So a client may have a value that they want to read within the particular database. Using their client key, they interact with the server and get the value back at that particular database location. We also do support writes in Panda, but in this talk, I will be talking primarily about our read-only Panda scheme. If you're interested in writes, we do present the sort of high-level work, but I would encourage you to refer to the paper or track me down after this session. So now that we sort of established the syntax, let's talk about what we want sort of in this setting in this definition. As I mentioned in our motivating example, we want security against a server who may be trying to learn client's queries and their identities, namely what we want privacy of access patterns against the server, and we want anonymity of the client's identities, meaning the server cannot cross-correlate client's identities between different queries. We want this not only against a server who might be observing these actions and interactions with the client, but also with a server who is allowed to collude with some number of clients and gain access to both their sort of actions and their secret key. And we set at setup time an iProary bound on the number of clients that the server may collude with, and we call this number T as our collusion bound. We also want a single server scheme, so not necessarily something that relies on multiple servers, especially not servers that don't collude. And finally, we want efficiency goals, namely we want the client and server read or write if we're talking about it, complexity to be sublinear in this collusion threshold T, or sorry, in the number of clients, N, and the database size. And we want it to be linear in the collusion threshold. So it's this combination of privacy and anonymity with bounded collusion and the certain efficiency goals that we call the panda setting. So without further ado, this may sound fairly similar to some of the primitives that have come before me in this session, namely oblivious RAM and another primitive called private information retrieval. So I want to spend the next part of the talk sort of comparing and contrasting the panda setting and whether O-RAM and peer are things that actually work to solve our problem. Spoilers, they don't. So I think previous talk did an excellent job motivating and explaining O-RAM. So at a high level, we have our single server. We have a single client who wants to make queries into a database that the server is storing while hiding their access patterns. O-RAM itself, there's a huge asterisk on the snow up here, but it's not inherently multi-client. There are schemes that attempt to support it, but most of the common schemes do not. One time is going to be polylog in the database size, and we have set up, assumed, and the server has state. And we're able to build O-RAM essentially from one-way functions. We also have a primitive called private information retrieval. We're talking here about the single server peer constructions. And in this, again, we have a single server and multiple clients who want to be able to make queries and hide their sort of access patterns. Unlike O-RAM, peer is inherently multi-client. Namely, the client does not need a secret key to make a query. So anyone can come along and sort of query and is not needed to be defined at setup time. Unfortunately, this requires linear server side work for any read accesses. And we're able to get peer from public key crypto. So how we compare with Panda, particularly O-RAM, we are able to get multi-client. And unlike peer, we're able to achieve polylog performance in terms of our database size. We do allow for setup and sort of state, and we're able to construct Panda schemes from FHE. So these are common primitives that you might compare Panda against, but there's actually a third one that I want to talk about a little bit. And that's doubly efficient peer or D-peer. This was first introduced by the Maladol in 2000 as a multi-server scheme. And basically what it does is D-peer allows for pre-processing unlike typical peer. And what you get as a trade-off there is that you can now achieve a polylog runtime for server access complexity during reads. And essentially what I want to compare against is the more recent work by Kennedy et al. and Boyle et al. in 2017 that reduces the multi-server D-peer down to a single server, and namely their public key D-peer variant. As with peer, we have a single server and sort of any person can come along and make queries against this sort of database the server is storing. We are, as I said, able to get multi-client, polylog runtime. We allow for setup in state or peer with pre-processing as it's also called. However, in order to achieve this, we require or it requires new coding assumptions and virtual black box obfuscation. So public key D-peer does in fact solve our Panda problem, but it does so with some fairly heavy assumptions or heavy duty tools. And we were wondering, is it possible to get a construction that relies on sort of less onerous assumptions? And yes, because my talk isn't ending and I have 14 more minutes to talk at you guys. So without further ado, I want to go into our results. So we're able to achieve a read-only Panda scheme relying only on FHE with T, our collusion bound, polylog L, our database-sized client-read complexity. We also support two variants of Panda that supports writes. We have a public writes Panda where we essentially have a public database that everyone writes to, and we have a secret writes Panda where everyone essentially has their own personal database. I want to spend most of the rest of the talk talking about how we construct our read-only Panda scheme. So without further ado, our main starting idea here is the original multi-server DPR scheme introduced by Bamal. And in this scheme, we have multiple servers. And in fact, we have K servers, and sort of they're all involved. And for setup, we have essentially trusted setup that takes in a database and outputs an encoded database. And it gives essentially this encoded database to each of the K servers. It is the same copy. There is no difference between the databases that each of these servers gets. When someone wants to come along and make a query, what they do is essentially send out K unique indices into this encoded database for codeword symbols that they want to read. The servers then go ahead and return the codeword symbols at that particular location. And the client is able to decode them and get the message symbol that it wanted to read at that particular address in the database. We say for correctness that the client must issue these K queries to the server. And we say that privacy holds in essentially multi-server DPR if less than s of the servers collude. And in that case, when they have less than s indices that they're comparing, these indices appear to be uniformly distributed. So that's what, when I say multi-server DPR privacy, further in the talk is what I'm alluding to. So obviously, if you'll remember, we had a sort of a list of requirements that we wanted for Panda, one of them which is we wanted to use only a single server. So how do we move essentially a single server scheme or a multi-server scheme to a single server? And we do this by essentially having one server emulate all of our K servers as virtual machines or virtual servers. Now, we're down to a single server, but obviously in this case, privacy is not preserved. As the single machine is emulating all of these virtual servers, it gets to see the access patterns into these encoded database. So when we're considering access patterns and the sort of wanting to hide them, the primitive that jumps to mind that we want to use might be something like oblivious RAM or ORAM. And so what if we did, instead of essentially encoding the same copy and sort of handing this out to all of our virtual servers, before we did that, we essentially put these encoded databases into K unique ORAMs. And each of these ORAMs now would have their own secret key. The question is now, how do we query these ORAMs when a client wants to come along and make their sort of K accesses to these virtual servers? So we now have to give each of the clients essentially all of the ORAM secret keys. So this would seem to work, except if we remember that Panda allows for collusion between clients and servers. So as soon as this collusion happens, the server gets access to the client's secret keys, which is all of them, and any notion of privacy provided by this ORAM is now lost. So why even put it in an ORAM in the first place? So we need to now essentially have that each client has some unique secret state that is not shared with all of the other clients. So when collusion happens, we still have some notion of secrecy. So what we do here is to introduce the idea of committees. So what instead of getting all of the secret keys for the sort of ORAMs, instead, clients get the keys for virtual servers on their assigned committee. And this is done at setup, and they essentially get assigned some subset of the servers, K of them, essentially, that they can now make their queries to. So in this case, in this example, client one gets access to the first and K virtual server, client number two is going to be given access to the first and the second virtual server, so on and so forth. As you'll note, we actually have to use more than K virtual servers in this case because we do want some additional servers so we don't have sort of entire overlap on all of our virtual committees because we want those committees to be unique for each client. So what happens now when collusion happens? The server only gets the keys for the committee of the colluding clients, which means that it only gets to see some accesses in plain text, only for those where there is an overlap between your committee and a colluding client's committee. So essentially, we can say that the server, because the overlap between your committee and the colluding client committees is going to be less than s, based on how these committees are generated, we can say that the multiserver deep peer privacy still holds because the server only sees less than s accesses essentially in the plain text. The rest of the access patterns are now going to be hidden by O-RAM. So privacy holds. So we have single server, we have privacy, but if we remember in Panda, we also want anonymity for clients, but now clients essentially have some unique information, namely, they have a unique committee associated with them. So servers can tell sort of clients apart based on which virtual servers they access as they have been assigned to their committee. So we lose anonymity. So how can we fix this? One could say, well, when we query the things on our committee, we can simulate sort of random accesses into the O-RAMs that are not on our committee and the server, excuse me, won't be able to tell the difference. However, this comes down to the fundamental problem. We don't actually know how to simulate these accesses into the O-RAM because you remember we don't actually have the secret keys for those O-RAMs. And what's even worse, our adversary, the server, might even in fact have the secret keys if it's colluding with a client that has that server on its committee. So essentially what we need is this ability to make smart dummy accesses, the ability to simulate a random access without the secret key. And this seems a property that most O-RAMs outside of trivial ones don't necessarily have. So instead, what we do is we try and get the next best thing. We get O-RAM-like behavior up to a certain number of queries. And what we do to achieve this is introduce the ideas instead of dropping our encoded database into an O-RAM, we instead simply permute it based on a pseudo-random permutation essentially. So instead of each encoded database in these virtual servers being dropped in an O-RAM, instead it is uniquely permuted as defined by a permutation key. And these keys are given to the clients in lieu of the O-RAM keys. So when we want to make a query, a client simply gets the index that it wants to query sort of in the unpermuted database. It permutes it according to its permutation key and asks those queries to the virtual servers on its committee. For things that are not on its committee, it simply asks for a random index in the encoded database because now it can simulate a totally random access and the server, even if it has the key, can't tell the difference between that or sort of an actual legitimate access. So for things that are not on my committee, I have sort of uniform queries by definition. I'm just asking things randomly. For things that are on my committee but the server doesn't have sort of access to it, we say that for a certain number of bounded number of queries, excuse me, that essentially it achieves an O-RAM-like hiding of access patterns thanks to a lemma from Kinetti et al's 2017 paper and for things that are on my committee and that the server does have the key for, it is going to appear to be random based on the multi-server DPR privacy. So we're kind of covered in all three of our cases. So we're able to achieve essentially up to a certain number of queries. And how do we move beyond this bound? And this is where our reliance on FHE comes in. Essentially for every B reads, where B is our bound, the server is capable of regenerating the permutations on its own because instead of having them sort of specified by sort of a pseudo-random permutation, we have them defined by a PRF. And this PRF key is essentially encrypted under FHE, allowing the server to essentially evaluate the permutation on its own and refresh it. For worst case efficiency, I think it's telling me that y'all are hungry for lunch and that I should hurry up. But we can say that for efficiency, we can amortize this action across our bounds or essentially our epoch in order to obtain sort of reasonable worst case efficiency. So this is how we achieve unbounded read-only panda. We also have, as I alluded to previously, panda that supports writes, namely a public rights panda with a public database where essentially rights are public, so both their content and where you're writing it to. But the identity of the writer is still hidden, so we still have anonymity. Reads, of course, are still private and anonymous. We also have a construction for secret rights panda where essentially each client has their own database that they can write to. And in that database, privacy and anonymity of rights is maintained. Obviously, reads are also still private and anonymous. The cost of this, however, is that performance where we have database size, namely L, now scales with the total number of writes across the entire system. That's not the end of my talk. Hello. It really doesn't want me to show you guys performance numbers. I'm almost at the end, so I can finish up if we have to without. I don't necessarily... This one, try this one. Enjoy Beautiful Seals. This was taken at Crypto in Santa Barbara, so. Anyhow, while they were fighting with that, I'll simply sort of finish off. So we're able to achieve public rights panda with the same read complexity and secret rights panda with the same read complexity as read-only panda. All you have to do is hit, I think, just Start, and it should work. Nope. All right. This is going to be, actually, my second to last slide, so if you guys will bear with me. So client write complexity is simply going to be O of log L, where L is database size, for client write complexity, secret rights panda achieves the same sort of complexity as reads, and server write complexity has a reliance on both the number of colluding clients and our database size. And here, Epsilon is for any Epsilon greater than zero. So that's what we achieve for panda with writes. In summary, we're able to achieve a read-only panda scheme from FHE where clients and server complexity is polylog in database size and linear in the collusion bounds. We support two forms of writes, secret and public, and we are interested in pursuing the panda problem sort of in other directions, namely, it would be interesting to see if we can remove this bounded collusion aspect of panda and have performance scale independent of sort of the number of collusions or corruptions and to remove this reliance on FHE in favor of more efficient primitives. So thank you for sitting through this before lunch with all the technical difficulties, and at this point, I am happy to take any questions. Thank you very much. Any questions about panda? Yes, they're adorable.


There are traditional ideas of eco-house designs and there was also a development in architecture that is looking at architecture in a different way and this is by Christopher Alexander and it's called a pattern language and this is a different approach to design of houses and this is especially good for eco-towns because the center of this approach is, is this alive? Is this design living? Is it beautiful? Is it working out in all aspects?


Revolutionary love is failing one another and coming back again. Revolutionary love is hearing what you did not put on your own playlist and coming back again. Revolutionary love is grabbing grace that isn't cheap and coming back again. It's tasting bitter herbs and sweet forgiveness and coming back again. It is fighting only honest fights and coming back again. Thank you for watching!