 get something in your life. Hi, I'm Dazza Grimoire, a scientist at MIT Media Lab. And in New York, we're jumping in with Beth McCarthy at Starfish Mission, who's leading a mechanism design, a regular Tuesday workshop. And Beth was just going to kind of help us understand how mechanism design could be applied to this open media initiative and part of that distributed event series. And I don't know, maybe Beth, you could also continue. You were just starting to do a little kind of recap on what we've done in San Francisco before, so we're live. So yeah, what we did on Thursday, which was this legal.io event for us. If watching week about governance and public policy and legal components and how it impacts what can in general, we started talking about the specific problem that's posed by the open media legal hackathon, which is looking at identity mechanisms for right-tolders and creatives to control works and also, I guess, get equitable payments and just basically having a creator-centric ecosystem that also is viable and incentive-compatible, et cetera. So this has been a super useful example, I think, in general for looking at this really complex ecosystem that isn't working currently, but also is impacted by certain legal frameworks that are playing out right now. Like, there's the Music Modernization Act. So that's like this law that was just passed. And yeah, maybe you could say a few words about that since the person who's joining us today, it wasn't here on Thursday. And grounding that a little bit, because you have a better explanation. And so looking at the legal business and computational technical issues that impact creating mechanisms that actually are effective from powering creators. So there's these two separate things that we're mapping out. So before we mapped out the incentives for these different parts of the ecosystem I mentioned, so creators, consumers, and distributors. And then today we'll take what we started understanding about the different incentives and pain points for each of those groups and actually testing some different models that might work that you have. Like something that you're sitting like mapping out, does, well, these mechanisms actually work? Do they need a token, et cetera? So yeah, but yeah, if you could say a few words about the Music Modernization Act, I think that would be, and just kind of the hackathon in general, I think that would be super helpful. Sure, yeah, I'd be happy to. Well, first of all, you can kind of get all the details at legalhackathon.org and at a high level, this is part of a collaboration between Berkeley College of Music and MIT to have a distributed series of creative events with legal hackers, a global meetup of attorneys and creatives to try to rapid prototype and generate some new innovative ideas that can help put musicians and other artists and composers as well as performing artists and others more in a position of ownership and control of their works, digital markets and ecologies. And the Music Modernization Act that Beth mentioned is important just a few days ago, Congress enacted a new law that was years in the making and it creates some interesting opportunities for some creative solutions just now. The main thing it does is simplify and streamline how royalties can be paid to individual musicians and performing artists, creates an industry collective called the Mechanical Licensing Collective which has some representation from distributors and producers and composers and others. They're empowered to collect money from people that wanna use music and then they're responsible for finding a way to get that money to the people that are owed royalties. Right now that's very difficult to do. So our thinking was that this might be a perfect time to come up with some interesting ways to have new business models and legal frameworks and technical architectures to simplify and streamline all that, maybe get ahead of the law a little bit. The mechanism design method seems like a really good way to surface some of the opportunities. So that's some kind of what we're doing. Can I start applying the Mechanical Licensing Act so I'm gonna add on to yours? So like currently it's like this act and like do we just like that? Like this, we just call it right? We've never had this particular model of like tying into what we're doing elsewhere. So I don't know, yeah, I think we could ever please. No, like it's like, the way you define is like, you're like the sound, the goal sounds like we're just trying to upgrade your current system but what mechanism design does is that like tries to understand what kind of assumptions we're making for a particular system and then trying to like meet up all those assumptions and come up with the core of it and then start building on top of that core. So like when we say, okay, like this app is happening and stuff, it's like totally out of the corner. Cause like think about it, like with this, like if it only works in US, it's not gonna make sense. Like the way we think about this stuff should be like, how can we make a network or like how can we make a like pure, pure, whatever open source that is not for like US but for everyone and like without keeping our assumptions about like what is a digital right and like the creator and stuff, we can also apply like agency, agency and business and like come up with other stuff. So like let me define the mission like that. I'm like, why are we doing this? Yeah, you can find the mission defined through around the world at legal hackathon.org and we're collaborating now to apply this mechanism design method to it. So take it away, Beth, lead us. Yeah, so we don't usually talk about like little compliance in this workshop it just so happens right now I think it's a hackathon like gone by schools. So this particular workshop is a hackathon like where the problem space is defined by it's America within the program New York Music Modernization Act. Got it, but then- So those are design constraints for this particular hackathon. Okay, okay. Yeah, it's like it becomes like loopy because like if you're like, if we are trying to apply this mechanism design, design thinking and stuff, it's kind of like- Obscusing stuff. Okay, so maybe we should terminate the broadcast at this point. If you can maybe just do a quick recap of kind of what happened on last time and then you can go into more of this broader scope after we've shut off the broadcast, okay? Okay, yeah, so wait. So I guess, yeah, last time we set out, yeah, this figuring out who the actors were I guess and on Saturday I'll be in New York to the New York section of the hackathon. So we can go more into who the actors are in the ecosystem and talk about that and also talk through this specific legal compliance issues how it plays into the computational issues that face us and just mapping out the entire system like within this legal framework that the hackathon is based but I would say, you know, today since the focus is less on like tying into the legal hackathon specifically then we'll probably in there. But yeah, look forward to meeting a lot of you guys to play on Saturday, so. Definitely, this Saturday in New York City at the Bushwick Collective and the following Sunday at MIT Media Lab and like at, you know, 10 locations in between you can find all of those at legal hackathon.org Come hack with us. Thanks Beth. Bye bye.