So we can move on to the next speaker. So thank you, Julio. So what I forgot to mention was that we had many people applying for this. There was a stiff competition. And it was pretty hard to make a decision on who won the prize. And the second running up was actually Rachel Glade. Rachel is a student here at the University of Colorado. And she's going to present her modeling work on blocky hill slopes, erosion of blocky hill slopes. All right, check. All right, just before I start really quick, I want to thank my advisor, Bob Anderson, and also Greg Tucker for really helpful discussions and collaboration work that I'll present today. So if you look at Earth from above in this picture, in a plane or even from space, a lot of times you can see signatures of geologic structure and rock type on Earth's surface. So for example, this is in Fort Collins, just an hour or so north of here. And here we have tilted layered sedimentary rock. And you can see that you can see the rock type stretching across the landscape. And resistant layers of rock set the relief of the landscape. They set drainage divides that can migrate over time. We can see, if we zoom into that same landscape, not only do you see soil, which is what you expect on hill slopes, you also see these discrete large chunks of rock that fall off of these resistant layers. In other locations around the world, this is in Moab. You have horizontal layered rock. Here's a place where the hill slope would be tightly coupled to the channel. You can see debris on the hill slope. This is Shiprock, New Mexico, where now we have vertical rock that's actually basalt. So this is a vertical basalt dike. You can see these big blocks have fallen off the dike and they mantle the hill slope. And one thing you can notice in this picture is that the presence of the blocks ends pretty abruptly at the base of this slope break. Just for fun, I think it's a cool criterion to show that your work is important and curiosity has a selfie with it. So you can check that box, that's good. So in general, there's sort of characteristic features of these layered landforms are two or more rock types that have differing erodibility or weathering rates. So here is in Morrison, we have a layer about tilted about 30 degrees of sandstone.  And that's overlying softer shale that produces soil. You can see this side, the dip slope pretty closely mirrors the bedding plane of the resistant rock in this case. Then the other side which we call the ramp is a hill slope developed in the soft rock mantled with this resistant stuff that fell off from the hard layer. And this ramp is generally linear to concave and profile. So steeper at the top than the bottom. And again, we have the blocks ending at the base of the ramp. I just wanna point out that one unique feature of these landscapes is the shape of this ramp. So in general on hill slopes, we often expect them to be convex upward. So steeper at the bottom than at the top. And Hilbert in 1909, believe it or not, came up with a really elegant explanation for this. If you have bedrock that's producing soil at some rate and that soil needs to be transported down slope, you wanna maintain a constant form and you assume that the transport of the soil depends on the slope, you need to move more and more stuff as you move further and further down slope. So this slope has to increase. So we really wanna ask two main pretty fundamental questions about these landscapes. How do they evolve over time and what is the role of these discrete blocks that aren't usually treated in hill slope models? So we can come up with a conceptual model of the ingredients that we need to think about to try to understand these landscapes. We need to think about block dynamics. So how the blocks are released from this little cliff, how they move down slope, if they move down slope and how they weather over time or break down and become smaller. And then what are the feedbacks between that and then our mobile regular, their soil production and transport down slope? Because hill slope processes have happened over long periods of time, hundreds to thousands, millions of years, numerical modeling is a really good approach to try to understand that. So we developed a pretty simple numerical model of hill slope evolution. That's kind of a hybrid continuum discrete model. The continuum part, we have a rule for soil transport where soil moves in a diffusion like way according to the topographic slope modified by how much soil you have. So if you have no soil, there's no soil flux, which is good. If you have a lot of soil, then more of it moves. We also have a depth dependent soil production rule. So bedrock turns into soil at a rate that's dictated by the soil thickness. If you have thin soil, it happens faster than if you have thick soil. And then sort of the discrete part of our model is, yeah, okay, we have these discrete blocks. So the way this works is that each model cell either does or doesn't have a block. It's a binary rule. If it does have a block, then it has a weathering rate that in this case we said to be constant and a transport rule. So our rule is a very simple terministic rule where we say this block will move down slope if the relief between the block and the next cell is equal to the height of the block. So this would indicate that big blocks move more slowly than small blocks. And we could show analytically actually that with this rule, we should expect an exponential decay in block size with distance from the crest of the hill slope. So just before I start this, this is our model run, a video of it. On the boundaries, you'll see incisions. You can imagine these are streams or something like that. And everything that's white is shale or something that's very rotable. The red layer is a tilted resistant rock, like something like sandstone. You'll see that blocks fall off of this cliff when the relief becomes high enough and they'll move down the slope and decrease in size over time as they weather. Let's see if this will play. And I wanna point out that the parts of the hill slope that don't have blocks follow that Gilberty expectation that I talked about before, where the slope is higher, further down the hill slope. But if you notice over time, the part, the ramp, the part that's covered in blocks, develops this opposite concave up shape. So the slope is much steeper at the top here than at the bottom, where the blocks are small. So here's a printout of the model over time. And you can see if we zoom into the model, what's actually happening is that when these blocks sit there on the hill slope, they act as obstacles and soil gets stuck behind them like a dam basically. And you can see that the, here's an example in the field, if you looked at the sort of average slope, what your eye sees when you just look at this from far away, that is much steeper than the local slope that the soil feels when it's dammed up behind a block or this effective slope. You can see that this is happening in the model. This lower line is bedrock and the top line is the soil. And we showed in our password that the slope is directly related to block size. So because the blocks are bigger up here, the slope is steeper and as they get smaller, the slope decreases and you get that concave up shape. But something unexpected happened in our model that we didn't build in and really didn't think would happen. So if you look at the time slices, you'll notice maybe the last three of these look pretty similar in the reference frame of the hogback. The amount of erosion for a given amount of time is constant and the shape of the hill slope and the length of this ramp looks pretty similar. So how does this happen? The, whoa, yeah, how? The model is a simple model, but we have a lot going on. We have blocks moving and weathering down slope. So it's kind of surprising that we get this nice result. And if we turn, just take a step back and look at sort of a geometric analysis. Let's look at this side of the feature. So the dip slope, we have a given vertical erosion rate at the base of this hill slope. And we want to see how this could maintain a steady state where the consistent layer is keeping up with this vertical erosion rate. We can do just really simple trig and say, okay, the dip parallel erosion rate has to be that modified by the dip of layer. We can go into our model and check that this actually happens. So is it really becoming steady? Yeah, it fits pretty well. So we changed our model to have dip angles from 10 to 83s. And you can see that the dip parallel erosion rate fits with our analytic expectation. But how is this happening? Well, if we look at some different model parameters, these are all plotted with distance from the crest. So down ramp, you can see this average topographic slope measured over a length longer, bigger than one block size decreases. This is our concave up shape you see. The block size is strikingly linearly decreasing with distance from the crest. If you remember before I said that the rules we put in the model said that it should be exponentially decreased. Something weird is going on there. If you look at vertical erosion rate, we also see that it's decreasing somewhat linearly with distance from the crest. But the flux of soil is increasing as you would expect from a sort of normal hill slope theory that you need to move more and more stuff. What is going on? Well, if we go back to our little picture and focus on this side of the picture now, if we imagine that our definition of steady state is that the shape of this ramp stays the same through time and the reference frame of this dip direction, then you can see that, okay, if we have a vertical erosion rate down here, where the slope is steep, you actually need a much higher vertical erosion rate to keep the same form of the hill slope. And then as the slope gets shallower, you get closer and closer to this vertical erosion rate down here. So we actually expect the erosion rate to be decreasing down ramp for the feature to maintain a steady state. And we can cast this as another just trig relationship. So trying to tie this all together, what do we know? We know that block size decreases because I told it to you at a constant rate. We know from our previous work that the average slope goes with block size. So bigger blocks lead to steeper slopes because of this damming effect. We know from this geometry thing we just did that the vertical erosion rate should also decrease down ramp to maintain a constant form. And then with the block velocity rule we have, where the blocks move according to the vertical erosion rate downhill of them and their size, because these two terms are both decreasing, it ends up actually self-organizing to give you a constant block velocity, which is why this is such a linear decrease. But even though smaller blocks shouldn't be faster, they're seeing a lower vertical erosion rate than the ones up here. And it all kind of evens out. And then this also feeds back into the slope and gives everything this linear look that it sees. This is also interesting because it points to the importance of depth dependence in our soil transport rules because even though the vertical erosion rate is decreasing and therefore soil is increasing down ramp, soil is not actually accumulating at the base, the flux is still increasing because of this depth dependent flux rule. So now that we think we have a better understanding of what is happening in our model, we can look at ramp length. So you have to imagine that this feature was projected up into the sky before and a block was released. And the ramp length will be how far that block moves in its lifetime before it's gone, plus the amount of cliff retreat you have during that time. So we can cast that quantitatively and just say, the blocks might go an initial distance when they first fall off the cliff. This is a time scale for one block lifetime. If this is the block weathering rate, and then it depends on how fast they move. And then this is just the horizontal retreat rate of the resistant layer. I don't have time to go through all this, but if we include what we learned from the self-organization slide before and just sort of rearrange this, we can see that we can relate ramp length and the dip of the layer and the topographic slope and initial block size to the vertical incision rate at the base and the weathering rate of the blocks. And this is cool because those are two things we'd like to know often, pretty hard to measure. And these are all things you can measure in the field. So we've taken this simple 1D model, try to understand it really well and come up with testable field predictions that now we can go test. And just to make sure that we actually understand what's going on and just make that up, we can change the model to have different ratios of this incision rate to weathering rate of blocks, then we can measure the ramp length and the model, all these parameters here and calculate what it should be and you can see that it fits really well. So we really have confidence that we understand the behavior of this 1D model. And I just want to really quickly wrap up and point to the work I'm doing now with Charlie Chobh, who's another grad student here. And he is a model of fluvial incision in the presence of blocks. So big blocks land in the channel, they inhibit erosion through form drag and cover effect. And we've put both of our models into LAN lab. So I went to 2D and he also went to 2D and coupled them. So now my hill slope produces blocks that fall into the channel and we can see feedbacks between them. Just as a teaser, here's some cool looking, colorful output from our model. The river is on this edge and there's base level is proven in this corner. So in conclusion, I hope I've convinced you that blocks matter in landscape evolution, particularly in layered landscapes. I also hope that you can see that sometimes it's useful to really analyze what your simple model is doing and really try to understand it. And it might have even surprising things that you didn't build into it. And that is, I hope, useful for coming up with field testable prediction. And also, if looking at smaller scale morphology and processes can help understand larger scale landscapes. Also, Charlie and I have dual posters tomorrow. Thank you. Thank you, Rachel. Are there any questions? Rachel, thanks for a great talk. So my question is looking at your nice one dimensional model, what I wonder is how either rate constant or the shape of the hill slope might change if you had a two dimensional hill slope surface or soil to creep around the blocks. I'm curious if you're proud about that. Yeah, so I mean, that's what this is. We, the blocks exist. It's basically the same as the 1D model, but soil can flow around the blocks. So I was wondering, you know, would we see the same effect? And yeah, we do. You can see in the background here actually it's concave up slope. This slope has more blocks than this one, which is closer to base level. You can see it's sort of, this one is, you know, becoming not blocky, and this one is still feeling the presence of blocks. So it still has an effect. Thanks for the great talk. So I was wondering, looking at your conclusion slide, and that input you're showing us, can your model tell us anything about the spacing of where the rivers are cutting through, how both river and the slope are going? Yeah, so that's a great question and that's the other thing that I'm working on now that I didn't have time to talk about. But if you notice in the background here, there's this sort of scallopy pattern for it, but where the rivers are actually cutting across the hill slope. And yeah, I think there could be some explanations for the block release mechanisms. You know, this side of the hill slope has felt the channel incision sooner than this part. There are places you can go where the shape of these is sort of curved up here and then very linear. So the middle of the hogback hasn't felt this sort of cross cutting channel. So I think there is probably an interesting dynamic in there and I do plan to do that. So that was a great talk and you definitely convinced me that you guys have that whole phenomenon, well constrained and understood. As far as the actual why it matters, could you like put some sort of constraints around what the like compare it to the null hypothesis as if all of the slopes are those Gilbert type convex ones. What are these blocky slopes doing? Are they arresting the morphology in place, preventing transport of soil down to the valley, et cetera? Yeah, that's a great question. So in steady state, which is what I focused on here, the presence of the blocks significantly increases the relief of the landscape and the persistence of topography. So I don't have any slides here, but if you compare to a control run where you have a resistant layer of rock that weathers more slowly, but it doesn't produce blocks, you end up basically getting rid of all your relief much, much faster than when you have blocks. And they're also important. I focus on layered landscapes here because I like that they're kind of simpler and you have a line source of blocks, but also in the mountains here you have a lot of big chunks of granite and stuff like that. So I think they do definitely cause steepening of the landscape and not in steady state. They can significantly lower erosion. So one more question. Thanks, Rachel. That was a really great talk. It's somebody that grew up just north of Morrison. It's really interesting to see these. It seems like your prediction or what fell out of the model in terms of the size of the blocks decreasing linearly with distance from the crest is really fascinating. That seems like something that with some TLS scanning and some machine learning maybe be tested, is that something that you've looked into or has anybody else actually tried to extract block diameters from laser scanning yet what the actual distribution is and what the ramifications are for the modeling might be? Yeah, I think that's a great thing to do. I haven't done that yet. I have thought about doing sort of drone surveys to measure block size. One thing is that I understand what's happening in the 1D model really well, but the rules for block motion, for example, we really don't know how they move into life. I made up this simple rule that now I can understand. So what we'd have to do is really have a better understanding of the mechanisms for that and then it's pretty easy to sort of redo the math I did with a different rule and see if you could compare that with field data and see if it fits. Okay, let's thanks Rachel for her talk.


Large-scale manufacturing of high-energy Li-ion cells is of paramount importance for developing efficient rechargeable battery systems. Here, the authors report in-depth discussions and evaluations on the use of silicon-containing anodes together with insertion-based cathodes. This article was authored by Gebrekudin Gebrosilassie Eshetu, Hangjom, Zabia Judis, and others.


It was guaranteed, if you come to Kashi, you will attain to Mukti. He established what is called today as Bhairavi Yatana. Last forty seconds, many lifetimes of accumulated karma will play out in fast forward. Karl Bhairav means the dark one, as one aspect of him. It is seen in many different ways. It is a deadly form of Shiva. When he went into a destructive mode, not of destroying this or that, of destroying time, see all physical realities exist within the span of time, isn't it?  So Karl Bhairav means just that. Because most people do not choose to live in a great manner. They have an aspiration, at least they want to die in a great way.  So the last face of their life people came because they did not live gloriously. They have a dream of dying gloriously at least. Hop! Dying gloriously means death leading not just to disposal of body, but death leading to an ultimate liberation. It was guaranteed, if you come to Kashi, you will attain to Mukti.  So all the lousy creatures started coming because they lived badly and they want to die gloriously, only the population of the lousy multiplied. Then Shiva said the place is becoming lousy with so many lousy people. The place itself will become lousy. So he said there needs to be some check. So he established what is called today as Bhairavi Yatana. Know what Yatana means?  He will make it happen to you here. Forty seconds of one's life, one is either conscious or if he's in a consecrated space, this will distinctly happen to every human being for whatever reason one may be dying. Whether one is dying of old age or disease, the last forty seconds, many lifetimes of accumulated karma will play out in fast forward. At that moment, these forty seconds only, if you lived a life of ignorance, if you lived a life of unawareness, lifetimes of unawareness, these forty seconds if you can maintain some sense of awareness, he said all the many accumulated lifetimes of karma, you will drop it, you will go through an intense phase for forty seconds only and you will be clean and you'll dissolve. Essentially spirituality means putting your life in a fast forward. You may suffer much more because everything is happening at a fast pace. What you would have stretched for ten years is happening let's say in one month. So the amount of intensity of suffering that you go through is big. There may be moments of ecstasy and joy but there is so much suffering because things are happening rapidly within you. So at least towards the end of your life you want to hasten the process. So Bhairavi Yatana, all this is because of a powerful consecrated space. Consecrated space means one thing is just this, it's concentrated life. That means life becomes so concentrated that it burns karmic fuel at a tremendous pace. After some time once you get used to it, there is no more Yatana, it just burns. Essentially you are at a higher path. So that is the purpose of every consecrated space. Kashi is significant because of the enormity of the way they built it, the aesthetics, the beauty of it. In those times they say there wasn't another city on the planet which was that beautiful. All these things put together it became a big draw. I mean they created the atmosphere to get the people's focus. So Kashi is not all pleasure and beauty. It is a place where people go into most intense form of suffering because he puts life on such a super fast forward. Lifetimes of things burn in one moment. So those who are aspiring for Mukti, this dimension that we are referring to as Mahakala becomes of paramount importance. The Mahakala temple, it will shake you from the root of your existence.


What's up everybody, it's Jason here for jaspyscasebrakes.com we're giving away six NT football spots away with this 2020 Mosaic football hobby one pack break, number 58 random teams. And again guys, first we're gonna do the break, randomize the customer names and teams to shoot the hits out, then at the end of the break we will take all 32 customer names, randomize them, and the top six names, one through six, we're gonna spot each in the break. We did post up the last filler, which is number 59, that's the last six spots we're giving away, plus six spots straight up. So we're just 12 full spots away. So let's do the break first, let's roll it and six into three, nine times. One, two, three, four, five, six, seven, eight, nine. Matthew down to Terry. Nine times, one, two, three, four, five, six, seven, eight, nine. Dallas Cowboys down to the Houston Texans. All right, and again, stick to what you got guys. So let's quickly alphabetize and I'll give you a quick glance at your team right there. So last one we did guys, we pulled a stained glass. All right, stick to what you got. Warren Sapp, Jerry Judy, very nice. To 99, and overdrive Phillip Lindsey. Van Jefferson and C.D. Lam. All right guys, so the switch scenes and let's give away the spots right there guys. Good luck, top six, get in, let's roll. Two into five, seven times. One, two, three, four, five, six, and seven. Daniel in, Daniel, Matthew, Matthew, Matthew, Matthew. Wow, that definitely paid off. Matthew had a lot of spots right there. So there you go, after seven times, Matthew, Matthew, Matthew, Matthew, Daniel, and Daniel. Congratulations guys, those are in the NT break and the next one's on the website guys, last one. Jaspy's casebricks.com. Also, I don't remember if I said the number in the Jerry Judy, but that was a blue. Number 76 out of 99, just popped into my head right now like if I might have skipped doing that. All right, appreciate it guys.


Okay, so we're starting on time, and this is, let's see if I can do this, multiple cameras. So this is the, can you guess, in this hour, this is the badge clinic. You almost can read that. So what will we talk about in this hour? We'll talk about badges, these things here. Yeah, so we'll probably see what they can, what we can do with this year's badge, because it's kind of a storage device, so we can use it for backup and some other interesting things, because it's an office hour, there is no set agenda. So, we'll probably jump around a bit from different topics, and I will watch the, keep my eyes on the general text and the office text channels in case. In case there are some questions. Okay, so I guess you can see that this year's badge looks a little different than last year's badge. They're about the same size. This year we have no LEDs and no power supply, there's no battery inside this year, in place of that we have a fine leather finish on the back. With a plastic enclosure and full color front overlay. And I'm just curious if audio is okay. I don't know which channel to type to there's all these channels. Okay, so I'm not going to make any changes unless somebody tells me. So, one of the things you can see in this year's badge, even though it does have a front overlay that usually covers all of the parts with color plastic, this PET. So, instead of seeing this, which is a PCB, you see this, which is a cover over a front overlay full color printed. And in order to see these very small chips, which we thought would be interesting for all of the hardware hackers among us. We put it we put in these transparent windows. Alright, so let's take a look under the microscope at these transparent windows. Because I'm curious as well. What this looks like. So this is the raw PCB with a E prom integrated circuit on top there, soldered in. And when we take a look at the color. Color color overlay. Okay, this is going to need focusing and less illumination. Yeah, you can't see too well, can you. I guess because the light needs to be just right. Let's turn the light on again. Okay, so my experiment didn't work that well, but these are the problems that are storing our data this this year. Alright, so take a look at the channels and seems that video and audio is okay. So we'll do a quick demonstration. On how, how we can write to these storage locations. Alright, so that's the, that's with and without the front overlay. And to write to this the antennas on the back. So we're going to need to align the antenna from the back with a reader device, which typically is a smartphone. Alright, in order to use the radio to be able to use NFC, you have to turn the phone on. And it has to be at some accessible screen for the users, right so it can't be turned off. That's the first thing you need to do in order to use the badge over radio. And the last thing you have to ensure that the NFC circuit is turned on. And that's right here. I can turn it off. And you need to have that turned on. Alright, so that those are the two things that you need. And after that, if you have nothing else happening aside from aside from what do we have we have discord and the Chrome browser running on my phone. So, something should happen if I have programmed something to this device. And I align the antenna of the badge device to the phone. So I'm going to push the middle button there. And it brings up a web browser. That's telling me that the data stored on this button which I pushed is a URL. In this case you're curious. This is what the URL is on all of the middle buttons. Alright, so that's reading data off of the device off of the badge this year's electronic badge. Without really doing anything at all this is right out of the box. What does the box look like looks like this. I don't know if this is so interesting but we'll do the unboxing. So actually this is a wrong manual for this box but we have this excellent manual by Andres. And in some part I discovered this just on my own. Let's see if we can. In fact, on the printed manual his name isn't on your oh yes it is in fact there it is. So it's not so. So it's not so anonymous. I'm glad that he put his name on there. So that comes in the box. Obviously the different parts for a do yourself model, you have to put it yourself together. You have to put do it yourself put it together. So the parts that do come assembled are all the very difficult things. That's these. Dome switches which if you if you get three of them and you lose one then you don't have enough. If you don't lose all three you still have to align them perfectly well over the. Over the circuits and then place tape on top without anything moving more than a half millimeter so it's just kind of messy and uncomfortable. On top of everything else we knew that we would have to preassemble some of the parts anyway. Because these problems, which we have already seen under the microscope, they're only two by three millimeters wide. And they're one half millimeter tall also. So they're very, very small. That's why we're pre assembling at least some of the parts. Which come in the do yourself kit. All right, so that's what comes in the box. And after you take that out. You have something like this. You put it together. Put the leather on the back and the color overlay on the front. And then you can start programming and doing just the same thing that I showed before. I will do that just once more in case you didn't completely see it. This time, nothing on the front. Okay, this time I'm going to show the action from the back. I'm going to align it over the over the antenna. I'm going to push down. Did you hear that? So that's how it sounds. And when I look at the front, well, it opened a web browser. Okay. Now I've got a whole bunch of. Yeah, okay, so that's the reading right out of the box. Okay, because we did pre we programmed some of these identifiers onto these devices. We have three, three E prompts. And on each E prom, you have a variety of different slots, depending on how much data because they do have different capacities. These three E prompts, the first two or 512 bytes and the last one is eight kilobytes. So depending on how much is there, you can do quite a lot of things. In fact, let's try using this program called NFC tools. I'm going to add several records. I'll try to do this very fast. Let's do more narrow village. I'm not spelling too well today. All right, we've got more narrow village. I'll put another URL on there for a pop quiz later on more narrow devices. We'll put, we'll put a piece of text. We'll say this is, we'll just say def con def con 28 safe mode. Do you like that? Okay, so we have some texts. What else should we put on there? Somebody give me an idea. Take a look at all of these things. I'll help you choose quite a lot of different types of information, isn't it? Each one of these conforms with the end def standard. So that's what goes on NFC data storage. And every single one has a mime type, which it's hiding from you because it's not a comfortable way to store information. It just tells you, okay, an address. And there's a mime type associated with this. So let's just say Iceland. That's a place, isn't it? I think so. All right, so that's a place. We'll add another one. We'll add a file link. I don't know how I've never done file link. I don't know how that works. So let's do application. The easy one here. Email is really easy. We can do email info at more narrow devices. And object. Okay, this, it seems that that should say subject shouldn't it done subject. I don't know why it says object there. And here we'll just type hello world. So we're putting out entire email. The headers and the body. Hello email, I guess. So we've got all of these different pieces of data. Do you folks see that? I mean, I could keep going, right? I could, what's more options. So I could keep going and we would have 20, 30, 50 pieces of data here, and we can rearrange them. And what I wanted to show is that there are two URLs. So which one do you think will open a website? I mean, it's going to open a website if I, if I write this to a to a village badge, and then let's do that now. Let's, let's write. So now it's saying approach NFC tag. Do you see that? This is all quite self evident, I think. So I'll turn the phone over. I'll put a line the badge onto the onto the phones antenna on the back. I will use the, I will use the star button. Shall I do that? All right. So it's saying approach NFC tag. And now I'm going to click on the star. All right. Maybe you heard that and it does say write complete. So what will happen now if I close this application. I want to close this really, let's see what happens if I don't close it. So we're at the home screen. I suppose you call this. And I will, instead of clicking the second button, the moon there, I will click the star. So it does bring up a website. Monero village.org. Oh, I think it's I think I didn't use encryption. I just wrote HTTP. I think is that what it's complaining about? No, narrow village. What's wrong with this? I don't understand the problem. Okay, so here is a your eye. Maybe it's because the WWW is not correct. The point is that the web browser opened certificate date is invalid. Okay, so it seems that we have some problem with our website. It doesn't matter too much. What's important is that this badge opened automatically a website that we have programmed in by ourselves. On to this device. Right. We can try this again. Looking back at the list of pieces of data. What happens now if I rearrange this, if this your eye replaces the first one, let's do that now, shall we. So I'm going to use the star again, but this is a different badge. So, put that on the back there. So click. Why isn't it working? Could it be that another. So this is not working. Is it. Let's try this one again. Let's try this one. So this time it worked. Not sure what happened with that other badge. And the test is to see what happens now when I use that one button and it will bring up a website. Okay, so that's the correct website now that we looked at that we got before. Right. So that's kind of the workflow of programming these and using them for for day to day data storage. Right. Monero village.com. Is that what AJ is saying. I thought it was.org. Have I been typing the wrong thing. Sorry, I have to do this. This is my screen. And it looks quite good. Oh, but okay, that's German. I'm sorry about that this. Now you're right. So I've been typing org all this, all these days. And you're saying that I have to type calm there. Then do I get a certificate. And it still says it's not secure. All right. So this is not the right time to, to troubleshoot and debug the website. But we did, however, we did just have a demonstration of. Of how to program and use these badges on a day to day basis. So I can show you our application or. Or a homepage, I suppose you could call it for this year's village badge. How do I do that? I have to go back to back to this web browser. And because we were, we were spending most our time on the hardware, the software interface or the website, in other words, it's some of the parts are working and others aren't. So this is. Bob Monero devices.com. This is with a good certificate. Okay, that's German, but it says is there good certificate is fine. So we have two different menus here one at the top that can toggle left to right and one that goes up to down. And we've got some actions. I mean, it's a standard web application. Right. We're not trying to make a whole operating system here. But the tradition of the typical things like the, like the about page, I guess this is good enough. It has all the information that you might expect. We have the welcome page there, which gives you an idea that you can use the badge on Android or iOS. Because those two devices are smartphones with NFC circuits inside and that NFC tools is the application that works. There's a few other things that work as well like the game. I'll just click on game there on the left. It takes a bit to load. So we teamed up Monero village teamed up with the rogues village and a few others as well. And they programmed a game, which works with the, which works with the badge. I haven't gotten that far myself, but you can see there's a few people who have made it to the end. And the one thing that I don't like if you just left click on the play button. So there's a cross side scripting problem, which it's not a problem. It's how the website is intended to work, but they it's called core CRS. All you have to do is click on the right to do a right button click. And then, I mean, you can choose any of these things. I'm just saying if, if I choose this, you won't see it. It's going to a different tab. Right. So what I'm going to do is copy the URL and then put it up here to show you what the game looks like. And this is the rogues adventure games. There's a bunch of things to read about it here, but we will just kind of start playing. And although I haven't made it too far, according to our colleagues at the rogue village. It's about halfway through that you can use your, your electronic badge with this game. So I'll just type some random thing here. And so I'm not going to do this too long, but I'd like to give you some idea of how it works so you can go down the stairs I think there's something to look at here. Look at fossils. You get the idea right. So this is kind of fun. Now how do I go backwards? Oh, I can indeed change the tabs. Right. So that's one of the things that is working. Some other easy to introduce you to implement things are working like the gallery. I mean, this is not very valuable. But if you're interested in what the red one looks like, there it is. These are the different colors and you've got the DIY to do it yourself. That's why there's no plastic enclosures and you've got the different parts that you put together yourself. And this is the wonderful user manual that Andres created for us. It's really nice. And this is kind of our experiment with the packaging which we failed at last year and this year we did pretty well but we went overboard with that. So that's the gallery we've got a file server where you can download the glossy color user manual or that well it's not glossy electric. There's a date that off. It's not printed on paper when you downloaded electronically so there's no gloss or matte finish. Okay, but you can get copies of either one. I'm not sure what happens if I click there if it even works. You see it does work. So there's Andres design and all the illustrations really wonderful work. And you can you can tell that the file server is working. We've got status, which is kind of halfway accurate just says their application is undergoing development, which is true. I've got a top 10 FAQ is how so I explained already why the playing of the game fails when you click on it, which valid villages are participating. So none of this is all too exciting what we actually really want we start at the beginning here again. What we really want is here at the configure. No, I'm sorry, not the configure but at the onboard. This is where it's going to get exciting, because although, although it's not fully implemented to actually write the and def identifiers and pieces of data over radio. So we want to implement those things here and the way it will work. So here, any name at all you could write, you could change the gender and change the geography you can write your one of your some dead person, you could write I am Alfred Nobel. So Alfred Nobel is no longer with us. What I'm just saying is that you can create your a pseudo name here. All right. I have to put that in. We check off the things that you're interested in. So I like it. I like rogues a lot. And, well, that's too many maybe I want bio hacking as well. I won't be able to get them all on there because I'm programming the very small e prompt so I need to take some off you get the idea so I'm just going to be interested in this one round. I'm going to write rogues Monero and bio hacking will click on associate me and these are this is where it starts to not work. So even if I click on there, it's kind of these are not my choices. Yeah, you can see that this is still in prototype mode. So these are not my choices. But eventually we'll be able to write data or cancel. And it will start waiting for you to attach a badge or put a badge next to the antenna on the phone. If I want to do a factory reset, I can do that as well. And that's how this association and onboarding functionality will work. Once you have your identifiers on the e prompts all lined up like you like, you might want red team on the third E prom you might want bio hacking on the second one and crypto privacy and Monero you'll want maybe on the first one whatever it is. You have you line these up and you write them to your badge. You can then use the inner village network. Right. And although this looks okay, actually does look as it like it works. So this says here under development. Please stay tuned. So it's not working yet. Okay. In the end, you can connect to the inner village badge network by clicking on connect. You can do a ping just to test the network connection. If you need to authenticate because for example some of the village rooms or channels or topics are protected. Maybe they would like to know who walks in through their doors. Then you can authenticate and if you don't need to then you just skip that opcode or network code. You can turn on the bridge. I think the bridge will be activated by this command the safe mode which basically means we're going to do a proxy from the MQTT network, which is what we're connected to here. To the DEF CON discord. I mean this is kind of not relevant because they're probably going to turn off the DEF CON discord. So there won't be much time to use it, but that's there just maybe for another day next year. So we can knock on one of the participating villages doors. We can knock on Monero's door. And if we don't get a response we can knock again and maybe on the third knock we're automatically allowed to enter there can be some logic like that. Once we're inside we can tip using the using AJ's tip arrow, but one, two, four units. And once we're inside we can get information about our room. Maybe we're walking in the bio hacking room for the first time. And we didn't realize that there is a device program there medical device program. We'd like to know more about the room that we walked in we click on info. We can leave the room just as easily with the leave command and disconnect from the network with disconnect. All right, so that's kind of the rundown of the web application, which is under development. If we look at status it says that clearly application under development. Okay, anybody who wants to help. Help develop this. Let me see how to write. So what we can. So there is a URL to show I've written it down some other place, but I'll never be able to find it. So I'll just reuse this piece of paper. Everything going okay AJ. So, if you'd like to help to develop all of this web application logic, which is quite challenging. It's just tedious. Lots of troubleshooting fire bug and debugging. You can do a fork of the repository because it's all open source repositories found here. This one is certainly calm I know that because we don't have org. And we have a certificate everything's okay here. SCM stands for source code management. And if you do go there, then you can find all of our source code. Shall we take a look, or are there questions about something else some other topic. Next office text. Don't see questions. So what we'll do, we'll take a look at the source code management system. How do I get back to that. Here it is. Okay, so now we will choose instead of B O B. And the nice thing about SCM is that it takes quite a long, long time to load because it's a very slow. Virtual virtual server. VPS virtual private server. Alright, but in any case we see that there's that something did come up here. So instead of explaining all of these things and clicking through each one which is very slow process, I will just go right to apparatus, which is modern, which is Esperanto for devices. And then we have a list of the different types of devices badges is here. And in the list of badges we should see a few different things and there is Monero rising. Iron Triangle, which is the, which is apparent project of this derivative, the bush of being I think I should rename this but the bush of being is the is the inner village badge. So I just clicked on that. Let's navigate over to where the the web application is found under software. So there's a bit of things to read about here the storyline hardware network. It's not up to date, but I think it's good enough explaining a few things so right here in software that's because it's obviously not hardware graphics and closure documents so if we have a web application is going to be listed under software. So I click there. We've got the website. So we may see other things here under software we may have, you know, Android APK, not the APK itself but the source code that builds the APK and whatever it's called for the Apple. So I'm going to click on website and then most people who are familiar with websites you see the traditional CSS, you know the HTML five and JavaScript CSS arrangement. So we've got documents this is where addresses user manuals are located inside the actual sources. And then we've got a few things I think font awesome is in here as well a few things like that. So here's the index. I don't think anything else is is all that interesting I'll just click on index to see what that looks like. And we're not going to drill down too deep, but this very last level just kind of maybe interesting for some reason. This is all the source code. Oh my and it's just not interesting at all. So you do have some snippets and you can navigate through this SCM source code management on your own because it is public site you can fork poll and fetch sources you can do merge requests. And, and I certainly hope that you do as well, because we could use a help. I mean, there's few of us doing work on this. So that's why we're kind of behind on things like the web application. So AJ says it all is good. I'm happy about that. We have another 20 minutes or so what should I do now. So yesterday what I said, I would demonstrate was the impersonation is going to be a bit difficult but I said I would demonstrate a passive capture. I'm not data theft because these are my own devices. So it's like opening the drawers to your shirt drawer, you know, you're not stealing your shirts when you do that in your own house, right? So that's why I can take my own data and everything is just fine. If you do this without your own data, it's just not okay at all. So what I have here is a very nice box of chocolates. The light was a bit better. I'm going to try to adjust the lights a bit. I'm not sure if that helps. I don't know if that helps. So I've got a nice box of chocolate here. And first thing what I will do is prepare this because I forgot to turn something on. Right. And that's the other camera angle. That's about the size of the box of chocolates. And that's the way a box of chocolate sounds, isn't it? I don't know if you heard that. So either remove this cover, open this up. What do you think is inside? You want to take a guess? No, you don't want to guess? I'll show you. Okay, so that's these chocolates are inside. You know, they're definitely chocolates. Okay, so I've eaten almost all of them. I'm sorry, I didn't leave any for you. So what do you think will happen once we put this lid on the chocolate again? And let me just do that. I should have prepared this beforehand. Sorry about that. All right, so we've got the box of chocolates. I'm now going to place, let me just do this a different way. I'm going to place a library card on the box of chocolates. The contrast is very bad because it's a blue library card and blue chocolates. I'm sorry about that. I couldn't change the colors quickly. All right, so here's a library card and just going to drop that on there. And if you heard that, if you didn't, I will put my microphone next to that box of chocolates. So I think you heard at that time. What I just did is capture data off of my library card. All right, so here I'm looking at the data now because if this wasn't my own data and if it was a credit card instead of your library card or say a passport I'm not sure what types of cards and devices. I just have this kind of circuit inside, but this one as we can see is a my fair. So it's a ISO 14443. This is a RFID standard. And we just captured the data, right? It's the good news is that it's encrypted. You can tell that because it's got an ATQA and an SAK. But the serial number is there and you can certainly see some things, right? So what is this number? ISO 14443. I'm going to do one more thing. How shall I do this? I'm going to capture the data off of my inner village badge now. And I will demonstrate that it's very difficult to trick your inner village badge in the same manner. For one reason, because it has passive data theft protection built in. This is the screen. You can see that it's empty. I'm now going to try to capture the data in the same way and just dropping it on there. It does nothing. It's impossible to capture the data. All right. I'm going to align the antenna. There is no problem. The device is perfectly well aligned on top of the turned on smartphone, which is capturing right now. It's reading. The reason that it does not successfully capture the data passively in this manner would be known as theft is that I have not pushed on one of the three buttons. And once I do that, as long as the screen is still turned on. Once I do that, we should hear it capture. So let me go back here. All right. So I think you heard that it did capture something as I was pushing down on there. Let's see what it captured. So it got all the data off of my inner village badge, that thing. And the good news about that. So it's a different ISO standard if we want to use the ISO 14443 like the library card was and I just need to use a different button. All right, because we have 15693 on these two. And the sun is a 14443 standard, which is my fair. So we can basically copy the data off of this library card onto this badge. All right, it is encrypted, which makes it more difficult, but some some library cards are not encrypted. So some of the things to understand about that it did successfully copy the data or capture it. Right. If this is a box of chocolates that's unopened, you would not know that this is happening and you can do this with a number of daily objects like magazines, newspapers, you can embed a reader into a table itself at a coffee shop. I think you understand the point. So today and tomorrow, yesterday and forever, there are there are people stealing data and we wouldn't know it. And that's what makes it important to have a sense of not a sense to have a technical circuit built in which disconnects the antenna. When you're not pushing on this when a human is not pushing on one of the three buttons, this antenna is not connected to the to the ICs that integrated circuits which are storing the data. And what that means is that it's nearly impossible as it could possible. It might not be impossible. I just don't want to say that but it's very difficult. It's very, very difficult to capture data off of these things unless you're pushing on a button. And what I call that is defense of passive data theft. Is that what you call it to need money? Are you watching? All right, so we just demonstrated the passive data theft protection. And we demonstrated the writing of information. We demonstrated the passive capture of a library card. We demonstrated the difficulty of copying encrypted information. And we saw a nice chocolate box demonstration. And what else do we have? A variety. What I like to experiment with are these types of transit cards are quite often they either have a copper smart card integrated circuit or they have an antenna inside. You can't see it then. And here's one, for example, with an antenna inside. How about this? Let's do another test. I will turn on this smartphone again. So we'll get this working again. And we've got this turned on. Remember, it's always very important to have your screen turned on. Otherwise, the NFC circuit, a lot of the radios don't work. All right, so this is an empty screen. There is no data on the screen. We're now going to passively copy data off of a transit card. Shall we do that? All right, so I'll just drop it on there. And if you heard that, it's already, it's too late. If I was not the owner, then I would have just lost the information. So what we have here, this is an interesting memory model. It's a my fair again. So you would see the 14443 has a serial number. It has memory information. So this is quite interesting on the pro model. It dumps the memory on this one. It doesn't, but in any case, so we just captured the data from a transit card. All right, so that's how that works. What else can we demonstrate? You can take a quick look at what the devices look like from start to finish during the manufacturing. So the manufacturing starts with a etched circuit board like this. A bit better. The lighting is just not very good, but so I'm not happy about that. And then there's a shadow if I do that. Okay, so this is the PCB or printed circuit board. And if you take a quick look, there are no parts on there. You can see the three different footprints. U1, U2, U3. There's no switches on the switch, SW1, SW2, SW3. So that's how we start. The other side needs to be flush and straight. So we don't have parts on there at all, because it needs to be right up against the reader device in some situations. So we begin by populating parts on this side. So I'm going to show a different PCB now. There they are side by side, and the one doesn't have parts, and this one does. Okay, so what does that look like? After we populate the PCB with switches, with e-prongs, with integrated circuits, that's what it looks like then. There we go, focused. So we've got the three switches on there. We've got a piece of capped-on tape on top to keep them in place. And then we've got our e-prongs, two of which are holding data in NDEV type 4. I'm sorry, NDEV type 5. And the last one, which is this one, U3, is holding data in the format of NDEV type 4. That's my fair one. Now, the other side is just the same, because like I said before, in some cases, we need this antenna to be right up against the reading device, and for this reason, we can't put parts there. And the next step in the procedure to populate or to create these devices and assemble them is to place an overlay on the front and a piece of leather on the back for protection. So what does that look like? The overlays look like this. So that's what it's like when... I'll just use one here. So that's what it looks like when we have placed the overlay, which has an adhesive back on it, peeled adhesive back on, and put the overlays on. And you can see that through the overlay, there are transparent windows that show you the parts underneath the small chips. The other side of the badge, because we're going to be... so this is hard to see because it's black, but in this case, it's red. This is where we differentiate the colors in the villages. Whenero obviously has an orange one. And the reason that leather is on there, so that when you put this against the phone, that it's not scratching your lens. Okay, so there is a functional purpose for this leather. Most people think that it's decorational. I mean, it does feel good, but it's actually there to protect the lens of your reading device, which is usually a smartphone. All right, so that's the front and the back. And once we do that, all we need to do to finish the device is to put it inside a enclosure frame. The reason this has two stripes is that they come out of the printer like this. We need supports in between those two protruding pieces of the model. And that's why we put some supports in between. And one problem that we found is that every tenth badge that we assemble, we break the frame on it. So that's one reason we're not enclosing frames with the do-it-yourself models, because we would need to supply two, three, four frames for each badge to make sure to ensure that the person didn't break it. All right, so that frame goes on the edge of the badge, as you can imagine. And it covers part of the leather to keep that on, and the edge is no longer... Well, let me... I mean, this doesn't look good when you don't have that plastic on. You can see the different layers. So that's kind of a decorational thing. I do suppose that if you drop the badge, that the plastic frame does help a bit there as well. So you could call it a protection feature. All right, so that's... I just realized that I forgot to record this. I'm supposed to record... Okay, now it's too late. We're five minutes or ten minutes away from the end. Okay, I forgot, sorry. Right, so this is what happens when you fully create the badge. We have some black ones, which are called... The model number is called black matter. Black matter, more narrow orange. We've got some attack red, red on the back and on the front. We've got defense blue. And the defense blue is quite nice. It's very translucent. You can see right through the plastic in some areas. This is what's so nice about SLA stereolithography. It's much more difficult to get a FDM or fused deposition modeling process translucent. Anyway, so these are all the colors. I think there's a green one as well. And then we have some unique village colors. Let me show a couple of those. Like this one belongs to the rogues village. Colors do not... I don't know if maybe I can... I think it's a lighting problem. In any case, this is blue. You can't tell that it's blue. With a white frame. And they chose this because these are the colors of the rogues village. They chose the symbols as well. We got a lot of help from the rogues village. I really appreciate that. Thanks folks at the rogues village. This is the biohacking color scheme that they chose and reserved for their village. Because in biohacking they have black and green. And so as you can imagine, the front is the same on all of these. Translucent green frame. You can really see through that, can't you? And the back is black. So I don't need to go through all of these because there are five or six different ones. But that's kind of how they look. And so with five minutes left, I would just invite questions. And if there are no questions, then we can either finish early or I can maybe look for some more. Oh, I know what I forgot. I wrote this in the description for this presentation. What I forgot is to show other badge types. So here is a prototype. This is kind of how we were developing before we got far enough to release the design. So we have some wires soldered on there and extra button up here, which is a different tactile strength. Here these are 260 grams. And this one up here is only 130 I think. And then different parts. These are M24 SR LR04 and the back looks very similar. So this is a prototype board. Here is the Monero Rising. This is quite nice. I soldered a header on there for the SAO connection. And basically how these work, it comes with a battery.  And when you turn it on, it lights up obviously because there are a lot of LEDs on here. So let's see what that looks like on the front. Now we'll turn it on. So that flash is a, it's kind of a negotiation. It says I've turned on. It's indicating that the badge is ready for action. So there are three capacitive touch buttons on the bottom here. They're not tactile, they're capacitive touch, which means I just lightly put my finger on the middle one to turn it on and off. So now it's on. I have to be careful when I'm using the buttons because they are very sensitive. So pressing them from the back is possible as well. Let's see if I can do that. Okay, it's not so easy as easy as I thought, but if I push the same button again, it turns it off. You understand how that works? Once turns it on, once turns it off. So that's the on off button. The buttons to the side, left and right, these change the animation. Some of you already know this because we produced quite a lot of these badges and a lot of people took them home last year. So I will move to the second animation. Here's a third animation so I can go back to the first. And in all cases, when I switch the animation, I have to rest my finger on there long enough for it to complete the entire animation cycle. If I just do a quick tap, it will not read. Okay, well, then it did, but you get the idea. Unless I'm touching that button at the very end, it won't register. So that's how the animations work.  So that's how these things work. The one that I like the most, it's the very first one. I think it's starting night or sparkle. I can't remember the name. These, these animations have names. Yeah. I wish MIDI poet was here because he did the firmware design and engineering is called these things with what they look like like this starting night. And we're close to finished with the badge clinic for today, but I hope that some of this information was helpful. Once again, I will turn it over just to show the back in case you're curious. That's how it looks. I could put this under the microscope. But anything larger than this very small part on the end under the microscope it's it doesn't you can't tell it doesn't help because the microscope is too powerful. So this is what this badge looks like it has I think 100, between 120 and 140 parts. I've forgotten the actual number. You turn it on and off with a switch on there on the right here. Be careful with the switch. You don't want to push down while you're. It's good to be careful with it. It has, it has bent off in some situations and you have to bend it back. So I'll just turn it off there. And that's the hardware on off switch. All right, so we're five minutes until the next presentation, which I believe is let's just check that out. Unless AJ wants me to stop or I don't know if we have a next presenter. Let's just check this out. More narrow village dot what or calm I really I don't know I'm going to do org. Okay, so this is not TLS protected, but in this, this moment, I'm not so concerned. So let's see who's doing the next presentation. We have bad clinic is what's happening right now. And so in one half hour. Here from Rumen. Giving competition to Monero by ditching opt in privacy. All right, so this looks very interesting. This appeals to me quite a lot. It's always nice to know what other cryptocurrencies are doing and how that relates and contrasts with our technology here at the Monero village. And we actively welcome all of the cryptocurrencies in the world. Including the one you just made five minutes ago with your Python module. Python library. So, this is what we do in Monero village right anything is blockchain related cryptocurrency, things like that, you're welcome to ask questions about it or just come by and explain your project. We have that with low key mesh as well today. Really interesting stuff and in the next presentation, which is coming in just one half hour. It will be from a Z coin enthusiast and developer I believe. So that sounds that looks really good. So I'm going to say goodbye. And I hope that you liked all of these devices. These these badges there, I think are sold out for the for the do it yourself models. Because people seem to like those quite a lot, but I do have this stack right here plus a few others of the pre assembled model. So, if you're interested in attack red defense blue, you can get that. I'll write the URL here as well just in case you're not sure where to find them with that then we will turn off the stream. So the URL is shop dot Monero devices.com. That's where you can still available. Get your badge. Does that sound good need money. Are you watching now. Are you watching Scott. Who's watching besides myself. All right, so that's, that's all for today. This was the badge clinic, the last badge clinic of the year 2020. Well, you know, we could could be in China for, I'm not sure about that they canceled China but that was the badge clinic for DC 28 and thanks a lot to the AV folks for helping AJS. You did a great job and and just as well. Okay, so I will say goodbye. And that's it for me. My name is Michael MSVB. Have a good one and thanks for listening.


Major news in the Prop 8 case, with new briefs filed before the U.S. Supreme Court. Another survey shows a majority of Americans support the freedom to marry, so why is the Republican Party turning its back on relationship recognition? And challenges to the Defense of Marriage Act were already on the fast track, but now that track could get even faster. At the American Foundation for Equal Rights, I'm Matt Baume, and welcome to Marriage News Watch for August 27th, 2012. Late last week, Afer filed a brief with the U.S. Supreme Court, asking the court to deny the Prop 8 proponents' latest attempt to stop couples from marrying. Two courts have now found Prop 8 to be unconstitutional, and now the proponents are making a last-ditch effort to have those victories overturned by the Supreme Court. Afer's position in its new briefs is that the previous decisions were correct, and don't require any further review. The next step is up to the U.S. Supreme Court. They could decide as soon as late September, whether to rehear our case. If they choose not to take it, the Ninth Circuit victory will go into effect and Prop 8 will be gone for good. And if they do decide to take it, Afer's attorneys are prepared to defend our previous wins before the U.S. Supreme Court. In other news, yet another national poll has shown that a majority of Americans support the freedom to marry. This time it was a Washington Post-Kaiser survey showing 53% support to 42% opposed. This makes the 14th national poll to show our support at over 50%. But despite this undeniable trend in public opinion, the Republican Party is headed towards a platform that doesn't even recognize civil unions. The party's platform committee last week voted down a plank that would have included limited relationship recognition. In response, the group Young Conservatives for the Freedom to Marry has denounced the move as disappointing. They vowed to continue working towards building Republican support for marriage equality. And finally this week, a fourth DOMA case is now awaiting a decision from the U.S. Supreme Court. The case in question is Peterson v. Office of Personnel Management, in which one federal court has already found DOMA to be unconstitutional. Typically, the case would now be re-heard by the Second Circuit Court of Appeals, but the plaintiffs, represented by gay and lesbian advocates and defenders, want to skip the Second Circuit and go directly to the Supreme Court of the United States to settle the matter once and for all. As with the Prop 8 case, the Supreme Court will begin deciding which cases to take in late September, so you can expect major news about the Freedom to Marry then, just a few weeks before the election. Visit AFER.org to learn more about our case to overturn Prop 8 and win full federal marriage equality. At the American Foundation for Equal Rights, I'm Matt Baume, we'll see you next week.