time of year where hundreds of disabled veterans are going to ascend to Snowmass, Colorado for the National Disabled Veterans Winter Sports Clinic. This is a partnership between the VA and DV, stretching back nearly 40 years. And it couldn't happen without, certainly the participants, the volunteers, but also couldn't happen without the sponsors. And here I have Anthony Klossin, CEO of Colossal Contracting. Anthony, tell us a little bit what drew you to this event. Sure, so the energy, the love, everything draws me to this event. When you get here, you're greeted by the honor guard and veterans stepping off the plane. They were saluting our veterans as they came in. This whole scene is fixed and full of energy and love for our veterans. I was gracious enough to come two years ago and my friend Ron from DAV took me down to the boot loading, right? And that is where the veterans are flying down the hill.  The love that they have and the energy that they have and that they deserve is all here. And the DAV does an amazing job. And for companies like mine, this is a great opportunity to show the veteran community and show the world how much we love them, right? And the DAV has set up something amazing here, right? The atmosphere, the food, the drinks, the events for the veterans, you know, they have a big kickoff dinner tonight. It is just amazing and I'm just so thankful to be part of it. I can tell the passion in your voice and I can see the electricity in this room and it's all over the village here. What are some of the events you're looking forward to participating in or maybe observing? Yeah, all of them. All of them, I mean, there's not a bad event here. I mean, all of them are filled with amazing athletes. That's the thing is, you know, these veterans, disabled or not, are the same people that they were when they signed on the dotted line for this country and seeing them tear it up on these events and they're true athletes. I'm talking, these athletes are amazing. I'm seeing stuff out there that will strike in your mind forever. But seeing the smiles on their face and being able to be competitive, veterans naturally, we're competitive, we wanna get after it. And DAV has like gave them that opportunity to go out there and tear it up and be competitive. It's motivating for sure. Tell us a little bit about, and you're an Air Force veteran yourself, tell us a little bit about Colossal Contracting. Sure, so Colossal Contracting is a service disabled veteran owned small business. We're an IT value-added reseller. So we build networks for the government. We support all the agencies, the VA. You know, what we do is we make the customer's mission our mission.  We do complex IT solutions for just about every agency in the government.  That's got to hit on a different level too, right? It does. And that's why being here is special. And I really charge all the companies out there, especially in GovCon, get involved, right? This is a community you want to be a part of. It's a brotherhood, it's a sisterhood, it's everything.   Excellent example of what other companies might be able to do in future years here. And all the events, you know, adaptive skiing, snowboarding, scuba diving, fly fishing, rock wall, I'm throwing a snowblow, snowmobiling. I mean, you know, the options, they're not endless, but they're certainly a lot of events to take part here. And make sure you're following along at winnersportsclinic.org for all the coverage. Thanks.


Hello everybody, my name is Fausta Baglisi again from Cybertrain Diversity. I'd like to thank you for joining me again, watching the features of the Thinkorswim platform that we're featuring of something that we call Level 4. Now, if you watched some of my previous videos on this platform, which if you haven't done it, make sure you like us and friend us and be able to watch them. But I want to explain to you the great features of how to stop reading the past, but focus on the future. Now, what we're focusing on right now is something called iceberg orders. What is an iceberg order? It's a big block order. Now, if you're a day trader, a swing trader or an investor, you could use this platform for any type of style of trading. The big thing that you have to learn to be a very good trader is you have to know how to read the future and not the past when everyone keeps thinking. A lot of you always focus on where's the support? Where's the resistance levels? Well, just think about for a second. The past is not indicative of the future. Here at Cybertrain University, the way I was trained being a market maker over the years, is that you need to know where the big boys are. Like I said, where the institutions are, the high-frequency trades, the dark pools, those are the people you have to look for. What we're looking at right now is looking at a stock symbol, which everyone's very familiar with, which is called Microsoft. Now, what we're looking at it as a very big scale as a swing trader. As a swing trader, we always want to know, okay, do I take a profit? Do I get out? Do I get in wherever it is?  You'd think that they are out there, but now's your chance to see it. Now, here what we're looking at right here is, I'm going to get my little pointer, so you guys fellow traders could follow along. Actually, I'm going to get my little pencil right here. There we go. All right. So if you notice right here, we have these big orange lines. Okay. Now, these lines that you're seeing right here, fellow traders, these are orders that have been out there when the market opened up. And as you work your way across that line, you'll see that there is a 72,000 share seller out there that wants to get out of Microsoft at 320. Major resistance levels, but before that, you'll notice that we have another big seller at 315 for 58,000 shares. Now, let me repeat that. This ain't chump change. 58,000 times $300 stock is no $300, okay? We're talking millions and millions and millions of dollars. Now, all those orders are aggregated. Once again, watch some of my older videos that I have that go into detail about that, but the big thing is you want to have that game plan. Some of you said, do I set my limmer stops and exits? Well, here you have. You have the facts right in front of you so you could have that game plan. Now, obviously you could see Microsoft is really like kind of trading in this range over the course of the day. And let's say you're away, you want to have a game plan, you want to get out. Where you obviously want to know where the next big buyers are. And you could see right here that you have another 50,000 share buyers right around 300. And then you got 73,000 at 95 and another 75 at 290. Do you notice a pattern there? That this stock realistically is moving in $5 intervals. So if you want to know where the next support resistance levels are, all you got to do is look at the book map, see if they're out there. Now, is that people say, oh, that's common sense. That's normal. No, it's not. No, it's not. Sometimes they're not out there. Sometimes you think they're out there, but they're not. And that's where people make this mistake. So there are going to be bigger ones than others. And as I zoom out, and let me just clear this out, and as I go over the years, you could see that there's 100,000 share buyers at 280. Okay, there is 118,000 shares at 350. So these orders have been out there. So if you're an option trader and you want to do, let's say you want to do a leap or whatever you want to do a short-term trade, you want to do any type of option strategy that you have, this is a way of using book map to have that game plan. So regardless of how you're using indicators all the time, just remember the problem with indicators, they do not predict the future. The future is where the orders are out there because those indicators are laggers.  And the leader is you have to know where the buyers are and the book map is going to show you that on the Thinkorswim. So anyway, if you liked this video, please like us, friend us. We'll have a lot more of these on the book map on Thinkorswim. And also you can always join us in our professional trading room. We'll show you live in the market, which you could see it live and not only on stocks like Microsoft or Intel, we can look at other stocks. Remember there are 25,000 stocks out there you could trade. So the point is, if you want to try them and you want to see what's happening in your stock today, here's your chance. Thanks for watching. We'll see you in upcoming videos.


Hey Eddie. How are you? I am doing well. How are you doing? Well They changed up the zoom link on us and I'm wondering if people are still looking for the new one I've tried to post it as broadly as I can but People may need a couple extra minutes to join here today No worries. All right here they come Hey folks glad you were able to get the new meeting link Thanks. Yeah, we clicked on the meeting invite. I think there's a few people in the other one Well, I'm Andrew and the guy called pass is on there. So I'm I'm just gonna paste this link into the chat on the wrong one Perfect. Yeah, I only found out about the change yesterday. I've tried to Circulate it as widely as I could but I think if it was stuck on their calendar already, I don't have a way to Update that But Matthew should we give those folks a few more minutes to pop over to this call? Go for it. Yeah. Sorry, Anika. Yeah, so I did post it in the everyone chat on the on the other link. So I think it looks even like some people are coming across now Okay, great. Perfect. Yep. I see some more folks joining Okay. Well, we are a few minutes after but I think we can probably go ahead and get started Now welcome everyone to today's firefly community call This call is being recorded as you were probably notified when you joined so just wanted to point that out just a couple quick housekeeping things as a Public hyperledger community call this the recording of this call will be posted afterward And we also need to abide by the Linux Foundation antitrust policy and code of conduct Which are both linked in should be on your screen right now and both linked in today's agenda So if you have any questions about those you haven't had a chance to read them before please go check that out and With that we can jump into today's agenda So the the first item on the agenda for today is a As a proposal for new maintainers, which I'm really excited about I want to introduce to the I'm sure you probably had a chance to meet or have interactions with Both Matthew Whitehead and Chen and they have both been making fantastic contribute contributions to a variety of places in the the firefly project, but primarily in the EVM connect connector, which is one of the One of the more foundational one of the lower level layers of the stack and a really important piece of the project so Matt and chime have have demonstrated significant thought leadership in in the future in the direction of the blockchain connector and Have just been making fantastic contributions to the project I want to bring them on as maintainers so they can move to actually approving pull requests as well Which they have been actively participating in already And so so the way the process works is I'm I'm proposing I'm sponsoring them as the existing maintainer and at the next community call We will have a vote if existing maintainers are not able to attend the call They will be able to vote via email as well, which I will I will send out an email to coordinate that amongst the maintainers and then after the next community call they will I'm assuming that the votes will all be unanimously in favor, but They will be brought on as official maintainers and added to code owners at that point and the appropriate github user groups, so Um, yeah, I just wanted to briefly introduce Matthew and chung I don't know if you just want to say hi to the group here But thank you guys so much for all that you've been doing in the project and I look forward to continue to working with you as potential maintainers going forward Yeah, great. Thank you very much. Nico for very generous introduction yet. I'm nothing particularly tired at this for this point, but Thanks, Nico. Yeah We'll wait for the next call Thank you guys. All right. Now moving on through the agenda So one of the things that we wanted to talk about today is Some of the things that are interesting and exciting coming up in firefly 1.3 So some of those we're just going to talk about and just briefly touch on in the bullet points But one of them in particular Enrique has offered to actually do a little demo of So to most of these things that are on this list are things that are with the exception of the last one Are things that are already merged into main and are there and if if you like Bleeding edge software you can go check them out today They have not been in an official feature release of firefly yet though So that's just kind of where most of these changes currently stand But with with no further ado, I will turn it over to Enrique to demo one of the new upcoming features in firefly 1.3 Sounds good. Let me share my screen All right So yeah, so as as Nico mentioned, we did a lot of MTLS work and recently one of the big change that went in is the ability to configure MTLS for webhooks As I think most of you are aware there's ability for you to listen to certain events through webhooks And now we've made it to be able to configurable The configure a different TLS configuration per subscription Um, so now when you create a name space, um, or when you specify in your Configuration YAML you can specify a set of an assuring a second a set of TLS Um certificates or PEM files That then you can reference when you create a subscription Um, so if we quickly look at the, um Docs so under each of the namespaces that you are predefined you can add a TLS configuration where you can give it A name, um For that TLS configuration that you reference afterwards, you'll have a path to a CA file A path to a certificate, a path to a client auth in the case where you're doing MTLS So this is TLS or MTLS If you want to enable it and you can also do some verification checks as well You also need your your key file as well because that'll be your private key for the MTLS communication And that will allow you to then use that as part of the subscription So we take a quick look at the API And I'll show you one that I just pre-created So I have a little sample express.js Server running locally, which is secured with MTLS So it has a server key a server cert the client CA cert that it trusts And then it's requesting That The client provides a certificate and it rejects one size unauthorized Has a sample one that says hello and has a one that just console logs events from firefly So here all my testing that did earlier. So when and it's not filtering So at the moment, it's whatever event that comes out of firefly. We're able to just log it to the console At the same time, I have using the firefly cli Run a stack With two members in it And and its own chain And I've specified a TLS config for my predefined default namespace. Hopefully that's big enough. Let me know if you want me to zoom in And there is a TLS config here Which specifies a path to those certificates that generated. So that'll be the CA for the server The client certificate and the client key So if we go back to the API, you can see that I create a subscription To my local 3000. That's where my express app is running I want the data to see the events and here I've referenced the TLS config name that was in my Firefly configuration. So when an event Is produced in in firefly that I'm interested in at the moment, as I said, no future. So any events really I will be able to use it will use firefly will use those TLS certificates to call my workbook endpoint So if we Quickly check that. So I have a sample contract that I deploy this part of testing And I'm just going to invoke one of the functions, which is just the owner function And if I execute that and I go back to my terminal You should see a series of events have just occurred. So there's a little bit of debugging here That I put in express that tells you that there's been an effective a TLS handshake that's happened Um And you can also see another TLS. So first you get the was I submitted and then you get the operation succeeded So yeah, that's a quick demo on How and you can configure your namespace with a set of TLS certificates and keys and then use that as part of subscriptions for webbooks today Um, yeah, that's that's mostly what I had to show. Um, let me know if you have any questions or if you try out Let me know I guess Thanks, Enrique. I really appreciate that great demo fantastic new functionality there building on on what's been there and Thank you for the demo any any questions on the What Enrique has shown here before we move on to just chat about some of the other upcoming features Okay, cool. I'll go ahead and share screen again so we can Pull up the agenda here Yeah, so just I really quickly wanted to just touch on a couple of the the things that are in the new In the upcoming release of firefly again Most of these are merged into main and I'll touch on the ones that are still in active development here um, one of the the the really exciting things and Maybe Andrew can chime in and correct me if I'm wrong, but I think this one is is mostly in main, but there may be a few smaller sub work items that are still outstanding on this one, but So firefly has long had Really powerful messaging features and functionality In uh, what I think from what the earliest versions of firefly one of the really compelling features was to be able to attach a message or associate a message with a A token operation whether that was a token mentor token transfer And it sort of allowed you to associate extra data with the transfer as well as having a link on chain that Says that they go together and to be able to prove that on chain While keeping the payload of all this extra data, whether it was metadata or or even another image or whatever it is off chain as well And so so this is a really powerful feature of firefly. We are extending firefly's apis to now allow you to To do the same type of thing with custom smart contracts and not just through the tokens apis so there there will be an ability to Basically in your contract if you add another parameter a data Parameter which or argument which is the the last argument of your function of type bytes It will allow Well, it's for for solidity in ethereum contracts. It's type bytes. I believe for fabric. It's just a string It will allow firefly to associate a firefly message with that contract invocation as well Um, I think andrew is on on this community call. I don't know. I know he's done a bunch of work on this as well I don't know if he had any details that you want to chime in on there or anything else you want to add or maybe correct me If I could miss folk there in a way Yeah, yeah, I definitely can can you hear me all right? Yep um Yeah, so I think you covered sort of the basics Um, I do you want me to share the the fire and just kind of the overview for people to reference it? I steal the screen share for just a minute. Yeah, if you want to All right, I'll let it play on the spot here. I didn't check with you if you wanted to Yeah, no worries. So this is um, if anyone wants to go see it um in the the firefly fire repo number 17 It's an open pr still um because like nico said the major functionality has been merged um, but there's still a lot of sort of edge cases And basically this this opens up some more of the core firefly functionality in terms of how on and off-chain coordination works So it essentially gives you a lot more ways to shoot yourself in the foot if you use it in the wrong way So I think there's still some work to be done here before we can consider it ready and shipable but uh fire 17 is pretty fleshed out at this point has gone through a few cycles of review and amendment um, and and like nico was saying essentially if you've used the firefly invoke apis at all This should look very similar right um, I can say You know, I'm going to invoke an interface uh at this address I'm going to invoke this method with these inputs and then there's this new bit. It's been added Which looks very similar to when you're sending a broadcast or a private or potentially a token transfer with messages We're thinking that this might even become the main way to send messages with some other Firefly transaction whether it is a token transport or just some custom method that you've defined You do have to Add some parameters right you if it's a an ethereum method. You have to have a bytes parameter on the end Where some data can get packed if it's a fabric method You have to have a string parameter on the end of your signature And basically firefly is going to pack this message. It's going to assemble a message the same way it does Um in the normal messaging queue And send that message offline and then it's going to pack depending data about that message in a predictable way That if you follow these instructions, you can unpack it and basically do a batch pin Yourself in a custom contract in either ethereum or fabric. So definitely a more advanced Feature um for for those who they're you know comfortable with the sort of basic API invocation and the basic messaging capabilities But I think this opens up a lot of really powerful ways Um to actually do custom on and off-chain coordination. So that's all I'll say about it here I think we have discussed this in an earlier form on a community call So happy to continue discussion on the fire or on discord And definitely look out for this pr to get updated as the remaining pieces get merged And hopefully is you know fully baked and available feature in 1.3 down the road Awesome. Thank you, Andrew Yeah, any questions on that on uh Associated messages. Yeah. I know this came up on a previous call, Andrew Um, and so would it would an accurate summary of this be that you you now have a way of invoking a batch pin from a contract Rather than directly from firefly. Have I understood that correctly? Exactly It's it's taking what firefly sort of codified has really the only Opinionated smart contract that firefly provides this very simple batch pin And it's exposing that in a predictable on-chain way So you can invoke it from another piece of on-chain logic And then tell firefly, you know how to get off-chain stuff into your contract and have it pop back out Um with a coordination message on the batch pin contract So, okay. Thanks. Yeah. Cheers Awesome. Yeah. Good good question. Matthew. Thank you Um any other questions on that one? Cool. Okay. Uh, I'm gonna probably go through these next few a little bit more quickly. Um, that was Yeah, I think we've kind of touched on some of the most exciting things that are in 1.3 Um Well, there's a couple other ones on here. Um Yeah, so I think in 1.2 Maybe we introduced an API that allows you to delete local data, uh, which can be really useful for if you have You know data retention policies and things like that It can allow you to purge data from your local database and from your local blob store in data exchange as well Continuing on that theme 1.3 will include additional API methods for deleting other resources like token pools, contract interfaces And then there will also be this A distinction between I'm just creating something and That's Can be a separate Operation from Actually publishing that thing to the network if you're in a multi-party network. So For example, you could create a 1.3 will have the ability to create a contract API and not publish it To the rest of the members of the network In in prior in the current version of firefly and prior versions in a multi-party network as soon as you create a A contract definition or contract API or or a data definition Those things are immediately broadcast to all the members of the network Um, that that made deleting them more complicated and so so there's some some Features that kind of work in parallel here Giving you more flexibility more control over where data goes and the ability to remove it when necessary Um, and rikki has has already demoed a portion of the next bullet point But there's configurable mtls across all of the different firefly microservices that use fire there's a common htdb request library that's used by Not only firefly core, but some of the other services as well And so anytime firefly makes htdb requests out It uses this library. And so there's a common set of configuration that can be applied to All of the different plugins that utilize this within firefly core For enabling a secure service to service authentication and encryption Um, another new exciting feature that's in active development right now is postgres support for evm connect persistence right now it uses level db and you'll be able to select between level db and postgres for Storing events and receipts and event streams and all that good stuff So that that should Probably come with some noticeable performance benefits as well. And so that's that's an upcoming change Um There's there's have been some improvements to the erc 1155 connector I believe this one's already merged that allow it to work with a wider variety of It's more flexible in the contracts that it works with In terms of different flavors of 1155 There are numerous performance improvements in transaction throughput Throughout the different layers of the stack If that could be a whole other community call is to all the all the places that We've we've improved small things here and there but Yeah, I just wanted to just briefly touch on that don't have time to go into all the the nitty gritty details there And although the last but not least is a new area of this will be the biggest Or one of the biggest That the first bullet point we touched on Is associating messages with with custom contracts is a pretty significant architectural change and improvement But but the other one that's coming in this release is Active active high availability as well. This is currently in the design phase There has done a little bit of coding on it But still a lot of design and just sort of figuring out the architecture side of things There is an issue on github that Has all of the the running list of work items that are related to it That is up there if you're curious as to what it all entails but the idea is that The goal is to be able to run multiple instances of firefly core simultaneously and Each instance of firefly core will use leader election to determine Which runtime is responsible for the critical threads That need to be sequenced and so so one of the the really core important principles of A blockchain and a firefly is sequencing and so anytime that there is a a Deterministic or distinct sequence that needs to be established the firefly core nodes will coordinate to elect a runtime to be the the leader for that particular threat and so Specifically that that comes in a couple of places One is the event aggregator So per name space there will be A runtime that is designated as the leader for the event aggregator And the other place that that is important is on a subscription. So When a web socket client connects to firefly core node and Begins listening on a subscription. There will be one runtime that becomes sort of the the leader for for driving That event subscription and delivering events to to their So lots of lots of work still to be done on this one, but it is in the early phases and really looking forward to to seeing the Just the maturity of the product In this area and I think it's going to be a pretty exciting one That is it for kind of the areas that I wanted to highlight I guess any questions on on the the 1.3 roadmap or anything that we've touched on thus far Hey, Nico, um, do we have a sort of a timeline in mind for 1.3? Do you have a sort of a finger in the air timeline for when when we might get out? Soon Nice Yeah, so I I think most of these are Close to ready with the exception of of active active. Um, I suppose there's possibility that we might That if active active continues to get pushed out, um, we there's enough other interesting things that we might cut a 1.3 and active active might slip to the next feature release, but Uh, I I think I think a 1.3 is is due at some point. I would say in the next month Or two at the most Okay, cool. Yeah, it sounds about right I know this is being recorded, but that's not a commitment just to be clear to to everyone else who might be looking at this Yeah, good question. Any any other questions? Hi, Nick. What are the other contracts? This is my first call. I'm ball. So what are the other contracts that you are trying to implement for erc one fund five five because that is that's what Well, hey, ball. Nice to meet you and welcome to your first community call. Um, yeah, great question Uh, I don't know Andrew is that one that uh that you could take there? Um, you may know more of the specifics of New things that it supports now that it didn't before Yeah, definitely. Um, essentially We started out with a pretty opinionated A set of erc 1155 that we supported right um because What we've kind of come to embrace I guess is that 1155 is a really really open-ended standard It's not even as opinionated as some others like erc 20 and erc 721 um, so we wanted to kind of get the best of both worlds in terms of Making it useful to do things that you want to do with tokens, but also making it flexible um, so when we started out we defined our own extension on top of uh, erc 1155 that had some constructs for defining what would be a fungible token versus a non fungible token and Defining a very specific way of partitioning the whole contract into different tools of tokens Which are are two common things that you can do with 1155. You don't have to do either But we wanted to specifically support a sort of opinionated notion of fungibility and of partitions um, and so what we've done kind of this past month or so is go back and adjust the connector to not only support that opinionated extension 1155 But to let you specify a little bit more how you would use it So basically there's more input parameters when you create a token pool that's backed by an 1155 contract So you can specify if it has a factory or not, you know, and if it allows you to create a partition Or if you're just using an existing contract you can use the whole contract as a single token pool Or you can use a partition of the token id space by saying a start id and an end id and say, okay, you know all tokens from zero to zero x f f are Going to be representative of a fungible pool, right? So just a lot more parameters to hopefully support a wider variety of custom 1155s out there So definitely looking for people, you know, kind of sponsored use that Because because you know, I've mostly used the sample that that we came up with But but trying to support other flavors and looking for people to help Make sure that we're addressing those Yep, thank you. I will try it out. So thank you then that would be great Cool. Great question ball out and thank you, Andrew for the added detail there. I appreciate that All right. Yeah at this point, uh, happy to open it up to general discussion on any firefly related topic whether it's about Things that we've discussed on the agenda for today or just kind of general Conversation the folks want to have or questions that you have about the project. The floor is now open So if anyone has topics that they'd like to discuss We've got a number of maintainers on today and we would be happy to chat about them Um, I'm going to throw one other plug out from the maintainer side. Um that we in addition to 1.3 We are trying to get a 1.1. No 1.2.1 a new patch release on top of 1.2 um I opened a pr with some backports that I think are needed for that Enrique, I know you had tagged some changes that you might Have wanted to you might you know have thought are necessary for a patch release. So just kind of a Bump for maintainers and contributors that are on the call. Um, I would love to tie that off Sometimes soon because I think there's some really important fixes. I started a thread on discord a while back I can kind of bump it back up. Um But yeah, we'd love to get those fixes out to everyone because I think there's some known deficiencies in 1.2.0 Yeah, it's a great call out. Thank you Any other topics that folks want to discuss today? Well, if not, I'm happy to give people the time back Thank you, Nick. Yep. All right Thank you everyone. Thanks for coming out. Uh, looking forward to Uh, the the vote to bring, uh, Matthew and Chung on for uh, as maintainers The next time and uh, yeah, thank you all. I hope you have a great rest of your day and we'll talk to you later Bye-bye


It has always been difficult for astronomers to determine where one supercluster ends and another begins. But now a team of astronomers have collected data on thousands of galaxies around us. To understand their peculiar motion, the peculiar motion of an object is its motion less that part of its motion associated with the Hubble flow due to the expanding universe. They use this data to identify which galaxies are moving towards us, shown in blue, and which galaxies are moving away from us, shown in red. With this data, they were able to create a map of the paths galaxies are migrating along. These paths are called cosmic flows. Using this motion, they came up with a new way to map the distribution of matter in the universe. In our segment on the Virgo supercluster, we counted the Virgo galaxy cluster and a few hundred others as our local supercluster. But using this new technique, we see that the Virgo supercluster is part of a much larger structure that is 100 times larger and more massive. The astronomers who made this discovery have named the new supercluster Laniakea, a lion for immeasurable heaven. Here is an illustration of Laniakea, along with Perseus Pisces and adjacent supercluster. The boundary is where the supercluster objects are shearing apart. Like the North American Great Divide separates water flowing to the Atlantic Ocean from water flowing to the Pacific Ocean. In this view, the red dot shows our Milky Way's location in Laniakea. Now let's take a look at a few more galaxies found in our local superclusters.


Hi, I'm Vagarin Cascadian. I do a small consulting business called Aikidov LLC. And I'm going to be talking a bit about how to use Debian on embedded systems and best practices to maximize your long-term viability with using Debian. I'll probably talk a little bit about some of the history of Debian. I'll be getting into some of the norms in Debian and some of the infrastructure in Debian to help kind of give you some pointers. I'll talk about some devices that I've kind of worked with getting Debian working on and kind of the successes, failings, and challenges there. And I'll be talking about ways in which Debian can be the ideal view of how you should be doing this. And then I'll talk about some compromises that you might want to make along the way that might make your ideal view fit a little better with some of the practical realities when people are making some hardware decisions. So when I started writing this talk, I realized I've been doing this stuff for 20 years, which was kind of a surprise to me. I've been involved in Debian in some semi-official capacity for about 14 years. Somewhere along the way, I got stuck with UBoot just because I asked to enable a board. And I've been doing all of the uploads for Debian ever since. And I've been working a lot on the reproducible builds, farm running a bunch of arm boards to rebuild all of Debian. And just a couple of years ago, I got my black belt and aikido. That may not seem relevant now, but I'll work it in. So Debian started almost 25 years ago from counting it. I think it was later in the year. So it has a huge repository of packages available from which you can just basically, if you can run Debian on your system, you have access to a huge amount of available software in the free software world. Not everything, but a lot of things. It also gets regular security updates for the stable releases. And it supports quite a few architectures, including many of the architectures typically used for embedded systems. So as embedded hardware is kind of edged beyond the microcontroller era and on to general purpose computers, Debian becomes a lot more viable for systems for a lot of these strong reasons. One thing that kind of sets Debian apart. Oh, you can't see the top. All right. Well, there's a Debian social contract. It kind of guarantees some things to the users. And these things, typically, it's going to remain free. You can use it, modify it, redistribute it, and we'll get to that a little bit more later. Debian tries to give back to the community, tries to do so in a transparent way. And we love our users. And there was a pragmatic, somewhat controversial compromise in Debian where, officially, everything in Debian is free software. But there's this little section we tend to shunt off to the side and kind of support it that includes some components that wouldn't fully meet Debian's typical freedom guidelines. So the social contract, not every distribution has a contract kind of like that. So they basically just say to you, this is what we're doing. This is why we're doing it. The Debian free software guidelines kind of spell out what we mean by free software. It includes things like using, modifying, redistributing the software. And this stuff can really help avoid vendor lock-in, which to clients, sometimes, that's really a valuable, valuable feature. And it gets into some more details. And the Debian free software guidelines were used as the basis for the open source definition. So they're very similar with a slightly different angle. But one of the things that really sets Debian apart from a lot of distributions is they have a very strong policy. So it has the Debian policy, which really describes mandatory requirements in order for a package to be in Debian, and also best practices, which are kind of optional, but strongly recommended for it's suggested practices you should do.  And if it's not behaving that way, it's a bug. It's not some feature, or it's not some, well, I wanted it to do that way. So things like packages can't overwrite the configuration of other packages. You install a package, and it shouldn't break some other random package on the system. That's a bug. Not every distribution really sees things that way, and it has some pluses and downsides to that kind of an approach. But the policy really gives you a somewhat of a guarantee of how the system is supposed to operate as a whole, which you don't necessarily see in a lot of other distributions. The release cycle has a number of kind of stable and stabilizing phases. So packages typically get uploaded to the unstable distribution, which is kind of a staging area where they migrate to testing. And then testing is basically a work in progress towards the next stable release. And once all of the release critical bugs are sorted out in a testing release, it'll typically be released as a stable release. And then it gets roughly a two-year support cycle and their efforts to extend that for I believe up to five years and maybe even beyond that. And then there's the old stable release, which was the previous stable release. They typically have code names based on Toy Story characters and they have numbers, which within the Debian community aren't really used a lot. So having to learn all of these Toy Story names may be a little odd, but that's how it works. There are a huge number of derivatives and or projects working within Debian as well, such as the Freedom Box. But they're basically, Debian has formed this basis that can be reused for other projects that maybe have a slightly different goal than Debian, but the guarantees that Debian provides allow it to be a really useful framework for other projects of note, since this is the Embedded Linux conference. Armbian is a really interesting one. For the most part, it's just straight Debian with possibly a different boot loader and a different kernel. So that's basically some of the approaches we'll probably talk about in a little bit. Reproducible builds is something I've been really involved in. This kind of is recently added to the Debian policy and this can ensure that a given package will actually, it gives you a trust path to figure out when you're building this source code, it results in this binary, and it does that by having arbitrary independent people able to rebuild it and come up with a bit-for-bit identical package. So that's something that more and more distros are working on and that's really exciting, but they're not really there yet. And neither is Debian, but we're working on it and we've come a long way. So in Debian, related to embedded systems, a really important package is the Linux package. So Linux, there's a tracker URL, tracker.debian.org, and that will take you to a webpage which kind of gives you an overview of the status of Linux in Debian. Typically, the versions of Linux in Debian are for the most part taken straight from upstream and then they remove some binary blobs and there are a few other Debian-specific patches, but for the most part, it's straight from upstream and if you want to get any new features into it first, you have to get them into an existing branch of the Linux kernel. I'm pretty much the only current UBoot maintainer in Debian. So similarly, we usually backport patches from upstream, but I have taken the liberty of occasionally testing patches out in Debian first and then submitting them upstream, but typically we really like to only deal with backports and not implement new features. Arm-trusted firmware has started to become a bit of a thorn in our side in Debian. Not because of anything inherent, the licensing actually looks pretty reasonable, but I haven't found many boards that actually work with the mainline Arm-trusted firmware. And there are countless vendor forks of this project and ironically, the first Arm-trusted firmware that actually got into Debian is one of the all-winner forks of it. And this is really needed for just about all Arm64 systems. So that's a work in progress. Would really love to see more work towards getting boards supported on mainline Arm-trusted firmware that would really make the world an easier place for Debian. So another thing that, because Debian strips out a lot of the driver firmware, binary blobs without source code, there may be incompatible licensing. Some of these will be integrated into the non-free components of Debian, but some of them aren't or aren't yet or they're not readily available. So these things, how you install Debian is basically like many distributions, you can network boot it or boot it off an ISO in the Arm world, in the embedded world, maybe USB boot or off of a microSD. We've got images for netbooting, netbooting or SD card images for the Arm-HF architecture. And really, we get down to the key things of it needs to be supported in mainline Linux. It needs to have a free bootloader and it needs to have system or driver firmware available. So that's kind of the ideal world. We want all of these things merged upstream. So I'm going to talk about a few kind of case examples. In fact, this device I really enjoyed working with a long time, it's got a great keyboard, it's got these little mouse controllers and it really everything just fits at least my fingers quite nicely, but I kind of got stuck in this cycle for a number of years where it was based on a Linux 3.2 kernel and at the time that was the current Debian stable kernel. So I thought, okay, it's got a few patches but they're working on doing the right thing. So a security update would come out. I would rebase the patches against the security update. I would build it, I would test it, maybe something wouldn't work and then I'd have to do it again maybe just two days later and this started to wear on me but eventually the SD card on which I was running Debian, it just failed and I said, okay, I see that there's some stuff in mainline for the Open Pandora.  It ceased to be a recent kernel. So the upstream support on the Open Pandora, well, because it is a small keyboard, it's got a function key to be able to get to a lot of keys and that didn't work. The mouse knobs, I couldn't get those to work. The Wi-Fi didn't work, that's kind of hard to live with because it's not like there's an ethernet jack on this thing and USB still didn't work. I've never really had USB working on this thing even with the image that it came with and the U-Boot support, all you really had was serial console output which you have to plug in an adapter so if I need to, if I do the kernel update, I need to make sure, oh, I've got another computer on hand so I can do a serial update but I've taken this thing traveling without having to deal with a laptop and I've done development work. I've uploaded packages to Debian that while doing development on this thing, I mean, it's really a nice piece of hardware. I was really sad to give up on it but that's basically what I did. Another board I started getting involved with was the Beaglebone Black. A number of years ago, it used to run an Anxtrum-based distribution and for whatever reason, the main person maintaining that disappeared and they're like, we should give Demi a try and so somehow I got involved in this and they said, well, we've got patches based on the 3.2 kernel and I'm thinking, oh, I've been doing that for my Open Pandora, that should be easy and turned out they were for a different variant of the Beaglebone. I think it was the Beaglebone White. They had their own Benderfork of Uboot. Then I saw that Uboot was supported in Mainline Uboot but the version of Uboot in Debian was several years old so I was like, hey, can you enable this? And that's how I ended up maintaining Uboot for the next few years. But now the support from Beaglebone Black is pretty good in Debian. They've got most of the drivers working. Uboot support is reasonably well supported but the Beagleboard.org foundation is still shipping their own image with a custom kernel and a custom Uboot with a bunch of patches which they've just recently tried to push some of upstream again. So the Beaglebone Black is actually turning out to be reasonably well supported in the end. Didn't look great at first but they were doing the right thing and that's great. I also got a few of the little chip computers which I don't know if you ever tried to do a search online for chip but wow, that's hard to find. So that was kind of unfortunate although pocket chip was a little easier to search for but on the early models which are the ones I got because I got all excited and got on whatever crowdfunding platform it was and supported it but the NAND is not really supported on Mainline Linux and it doesn't look like it ever will be. I would love to be proven wrong there. The vendor bootloader doesn't boot a kernel with a raw NITRD which some of the distributions tend to like that feature enabled and this is a common thing in vendor Uboots is they won't, they'll enable just the features necessary to boot their particular variant of the operating system and then I don't think the Mainline Uboot supports the NAND on board and there's not really, it doesn't actually even have a microSD card or anything so you can boot over USB and then the only file system you can get access to is like a USB stick or something which makes it kind of hard to be a mobile device but so this device, I don't know maybe someday it'll improve. There are a few of them out there but these are kind of some of the stories that they didn't quite work out or they worked out to some degree or eventually they work out. So you get to a situation when you're developing when you're developing software for a particular board or a particular system you kind of get to a point where you have a choice. It's like you can either engage the community but that might involve some sort of conflict, right? Like you're like, well, we need these features enabled, we need that but what people usually do, what projects often do is they just run away and they kind of go do their own thing in a corner somewhere but this has some drawbacks. I mean I'm glad people aren't like getting, you know, getting ready to do fisticuffs over like getting their support for their board, you know, fighting on the mailing list and creating lots of flame moors but running away has its problems too.  So I would like to propose some kind of middle road approaches that can help prevent a long term problems that we've seen from innumerable boards, I just mentioned three boards but, so the kernel is a really key component. I mean, basically if you can boot a kernel on your board and you have Debian as a user space, you can run just about any kind of board on that as long as it's supported in, as long as it's an RMV7 board or if you use the really old Debian ports, the RMV5 port but a nice middle road is to basically take the Debian stable kernel and then backport patches from mainline to get it supported and there was a talk earlier where they actually talked about how you, that actually optimized and improved their driver code by basically pushing everything mainline and then backporting the features and that's a really excellent way to approach it and then you can kind of have a stable baseline from which to work from or do a custom kernel but continually have a plan for how to keep stuff working in mainline so that you never get stuck on an old version. Similarly, the bootloader, it's the same kind of thing. There are countless forks of U-boot for tons of different boards but in the end that version, every once in a while we'll get somebody, we've been, I think U-boot's been using date-based versioning since 2010, 2009, I'm not sure. A while now and every once in a while we'll get somebody who comes into the IRC channel with like a version 1.1 something, right. Well that's old and then with the date-based version you can see, well, it's exactly that old, you know. So we see even really new boards getting released with like versions of U-boot from 2010. So this stuff isn't sustainable in the long term. Would really like to see people focus on pushing things upstream. I've been involved in some of that and then in the x86 world, a lot of people don't really even think about the firmware. They don't even have a choice really. They've got this BIOS on their machine and maybe the vendor provides updates, maybe they don't but it's a little different in some of these embedded systems where you actually do get the source code to actually replace your boot firmware and we should keep that current so that when unforeseen security issues come up we can actually, that require something at the boot loader or firmware level we can actually address those issues. Another thing, a complaint I've heard about Debian is sometimes the packages are a bit old or a bit out of date or maybe not in Debian but you can follow the stable distribution with selected versions of packages that are relevant to your particular use case or you can include just the selected subset of packages that aren't yet in Debian and that way you can focus on maintaining the actually value added part of the product, whatever it is you're working on and that'll give you a pretty good approach to not over commit yourself. A lot of these projects don't really need to maintain a whole operating system. There are lots of operating systems out there already and I'm talking about Debian mostly because I know Debian but there are other choices and really focus on what is your particular projects specialty so by doing some of these approaches you can really bring that out. I'll talk a bit about the Debian community. There are over a thousand developers in some official capacity depending on what exactly criteria you're looking at and then thousands of additional contributors above and beyond that. For the most part individual packages are maintained by an individual or by a team but it's not an absolute. They're not the only people who can upload that. Any Debian developer can upload any package in the archive technically. There are some social guidelines around not doing that for anything, for any random reason. You kind of need a reason to do that but in general it allows some flexibility between targeted maintainership and the broader realm where if somebody's on vacation we can still get a critical security update out. There are of course online resources available mailing lists which have historically had some reputation for being a massive flame wars but I think in the recent years that I've been involved it's been less so given a few exceptions but IRC is also a great place for more real time communications. They're irc.offc.net or irc.debian.org which is just the C name for irc.offc.net but there are a number of Debian based channels on IRC and then of course a wiki which as many wikis go it's not necessarily well curated. There's a lot of stuff that's quite out of date. Some pages are really well maintained so that's also one way that other people can get involved is if you see stuff that's out of date fix it. That's a huge ethic actually in the Debian community is it's an ethic of duocracy and that's also something that can really if you're an outsider it's not that hard to become an insider and guide Debian in the direction that's useful to whatever your project is. So there are numerous events every year there's a Debian conference and typically hosted in a different city every year. A few years ago we hosted it in Portland this coming year will be in Taiwan and then numerous smaller mini conferences some of the mini conferences like in India are as large as the official conferences but and then we'll have bug-scrushing parties where we might try and get a release out the door or trying to move some new feature over that's been lagging. So I kind of referenced this tracker I just wanted to give you an idea of the kind of information you might be able to see like by going to that page. So this is for example the Linux package and it'll basically show you the versions of the package currently in Debian gives you links to the bugs, build logs numerous other kind of quality assurance checks. So this is a really great URL to know if you're trying to if you are using Debian and you've got a particular piece of software in Debian you can pretty much go tracker.debian.org slash package name and it'll get you to a summary of information about that package. The web interface to the Debian bug tracker is actually read-only, which you know this thing, I'm not sure how old it is exactly but it was kind of around before this whole web 2.0 thing happened and so basically you can browse the bugs and do all that sort of stuff but really when you get down to it it's an email-based system which for my workflow actually works really well I can do things offline, I can queue up mails I can develop bug reports I can download all my latest bugs to annoy me and then read them on a train or a plane or something so you can actually do quite a lot offline and it's a pretty simple format I mean you just email submit at bugs.debian.org make sure there's a package colon and name a package in the body of the message ideally a version and then there are numerous other kind of tags and flags you can set but so for some of you this may seem like an antiquated system but it still has a lot of merits and this is how you get information into the bug tracking system so I've been suggesting that there are ways you can get involved in Debian of course you can report on features or bug reports that's a pretty good entry level that's certainly where I got started some innumerable years ago and it's really not that hard to become a maintainer or developer of a project within Debian if there's a piece of Debian that is useful to whatever other project you're using Debian with typically people are pretty happy to have help and as I said earlier it's a bit of a duocracy so those doing the work define what happens I mean so if you need something done in Debian in many cases you can typically jump in and do it so there are and if you've got a reasonable coding skills background or whatever if you're familiar with revision control systems and at least one programming language you can typically jump in on some project and make a really useful contribution there are also other ways for non-uploading contributors people who help with editing the website or planning conferences there are numerous ways to get involved but given that this is an embedded Linux conference I figured it was maybe targeted a little more towards the technical end and so if you already have a lot of those technical skills the process has been pretty streamlined to help get people engaged so I think this talk was used in one of the slides or one of the this slide was used in one of the talks I mentioned earlier so thank you Wikipedia but this is actually salmon in the Willamette River just like a few blocks from here and the salmon in this region there's a long history thousands of years of salmon swimming upstream they actually contribute oceanic nitrogen deep into the inland country the forests of this region are basically there because partially because the salmon kept swimming upstream and they would they grow up in the tiny little streams and then they swim out to the world and they do their interesting things eating other ocean fish then they swim back upstream die and contribute everything back to the place where they were born I think we should be doing this in technical projects as well you know maybe you need to go off and do something that's not quite appropriate for within Debian but if you bring it back in I think we'll have a whole cycle that really can avoid some of the problems that we've been seeing so I'd really like to thank Linux Foundation for hosting this conference they also sponsored the Core Infrastructure Initiative which funded me for a lot of work on the reproducible builds project which is sort of related to this and Debian of course and there are so many people pushing things upstream and I want to just say thank you that makes as a Debian developer that makes a lot of my work a lot easier so let's see obligatory licensing and questions how does this work I didn't know I was gonna get a microphone this is pretty cool so you talked about some of the boards that were not working out so well do you have any favorite boards that you like running Debian on? I've been really happy with the WAN board series they've just been on the reproducible builds farm they're not the fastest of boards we have but they've been really stable so that's one of my favorites for a somewhat newer board I just recently got a dev board from Thio Brahma Systems it's the Puma RK3399 and I haven't spent a lot of time actually working on it but the board is really nicely labeled with like switches instead of random jumpers or having to short like connectors which I've had to do with some boards just to get them to boot correctly so but probably the one that comes to mind first is the WAN board for something nice and stable it doesn't really require much external firmware or anything which is nice and it works reasonably well out of the box on Debian how many people have worked on a project using Debian? okay I guess the title of the talk might have biased the audience a bit there cool yeah yeah any any war stories from a project you're using Debian on or I see a hand back there hey um so I felt this talk was mostly about evangelism for Debian but I was hoping if you had like some concrete points about best practices for Debian on embedded systems okay like what are some of the takeaway messages real takeaway is get your stuff upstream I mean that's really to a large extent on Debian if you have upstream support in the Linux kernel if you have upstream support in Uboot if you have your boot for boot firmware available upstream Debian basically just works so in that sense yeah I don't have a lot more to say it's kind of stressing that point and there have been a couple other talks talking in a similar vein throughout the conference so yeah okay thanks so if I want to use newer stuff in Debian stable there is something called backports.org can you speak about that a little sure yeah I'm glad you brought that up that's kind of like an in-between place between testing and stable so backports there's backports.debian.org is a site where basically they'll take newer versions from the in-development release of Debian the in-progress release and rebuild it so that it's compatible with Debian stable so I think even I should have mentioned that more explicitly yeah so basically yes I should have included a reference to backports.debian.org on this slide that's a really great service you don't get quite the same security guarantees with backports but in general you get a pretty good process and contributing to backports.debian.org is something you can really a way to really help get all of your stuff integrated if you do need newer versions of software there's also a site called mentors.debian.net or is it .org I'm not sure off the top of my head that allows you to upload packages and then request sponsorship for not just backports but any part of Debian so you don't actually have to become a developer in order to get things into Debian but backports is a great starting place where you can if you need to learn the particulars of Debian packaging that's a nice easy way to sort of contribute yeah thanks that was a great question I should have included it in the first place last call all right what can you say about how to formulate this it can be frustrating to work with a lot of packages because the packaging format as it's always been is tar balls plus patches I know there's been there was a a Git variant of source packages for a time that seems to have stayed experimental or died right I know that a lot of Debian developers use Git repositories and this new GitLab infrastructures coming in place um what's going on in the community these days when it comes to source package formats and is there ever you think we'll ever see a time when the official source package format is a real Git repository like everything else in the world and not something that's you know ultimately gets converted to tar balls plus patches which are right kind of hard to work with yeah there is an interesting project called DeGit I don't know if you've heard of that but that basically allows you to kind of do that kind of a workflow and then the packages that get uploaded as a result of that are are then imported as like I don't know if it's a commit or a tag in your Git branch but it basically is a workflow where you can basically just commit to your Git commit and then you just you use the DeGit tool to upload and then it'll prepare the source package and it'll prepare all those artifacts that you don't kind of want to deal with um so there are people working on other approaches but yeah the DeGit source or the Git source format as far as I'm aware nobody's actively working on it and like I said Debian is very much a bureaucracy and it's also thousands of individual interests all kind of working together but also kind of working independently which is both a strength and a weakness of Debian so I can't really promise you anything any sort of timeline or anything I haven't heard of anything in the works to really change that angle of Debian but have you seen anyone try has it been a discussion that resolved in some not in recent years we have this general philosophy about it and yeah and I haven't seen any recent activity on that um but yeah uh I mean the biggest change right now is we we're basically the only official hosted infrastructure is all going to be Git based we used people can still use whatever revision control they want but the the provided hosting infrastructure is just going to be Git based from now on and it was the vast majority of packages already simply using Git so so sorry to not give you better news but don't think that's the status of it thanks oh uh somebody mentioned Git build package yeah there there are a handful of tools there's Git build package there's Git DPM there's D Git and they all basically serve as a way to generate the tarball plus patches that we then upload to the archive and then the build machines go and rebuild all the packages I've been given this microphone but I think the speaker just went over what I was saying so thank you okay any other questions or comments or hopes for the future all right I have a general question since I'm already holding this which is do you think um especially given the slower release cycle of Debian as compared with many other distributions I haven't gotten the impression that the community as a whole particularly values supporting embedded platforms which is just because the landscape changes a lot faster in the embedded world do you think that understanding is accurate or do you think it's changing or so on well what's really interesting about Debian's workflow is we produce the stable release but the majority of developers are on a rolling release you know so we kind of have a bit of both which actually I think can actually be a positive thing it gives us the time to like really go over and make sure everything's complying with policy you know having those releases I'm very partial to a stable release I kind of have a bit of a system administrator background but I do think Debian actually has a nice blend of the rolling release and stable release kind of format because packages are constantly rolling into testing you know it's it's maybe not technically a rolling release or whatever but it has a lot of the same properties so so yeah that that that's a whole another approach I was definitely recommending targeting stable and then basing your stuff on that just to give you so that the rug doesn't get pulled out from under you in the middle of your you know development process but if you would rather go with newer stuff definitely targeting testing or even unstable in some cases may make a lot of sense just as a response to the earlier question about Git I know of two arguments against one is that the cryptographic provenance checking for current tarball based Debian packages is considerably stronger than that is that's used for Git and second is that when dealing with several layers of derivatives out of Debian it is sometimes easier to rebase by having separate patches in Quilt than doing it in Git thanks for coming everyone and I hope you got something good out of it


What they gonna do with me now? I'm still a twerk of the town Holding the sisters, I'm hooking them down Reaching the smiles and the frowns Gang hop out, then we clearing the quiet In front of the changes, I got her nigga Tennessee No vibe, she don't love me, she just feeling me They don't have to spend a lot of money So, guys, is it Lil Rik or Lil Rik?  Yeah, Tariq Everybody think it's Tariq But my name Tariq You watch Hawa? No Tell me your name Tariq I know who it is, though Okay, so tell us how you got into music The same person that gave me my name Tell you shit like that He, yeah, got locked up And I used to go to the studio at home But one time, this girl I know Used to just tell me all the time She used to be dumb and annoying And telling me, like, you like a rapper You like a singer You like you could be a singer And I used to be like, bro, stop telling me that So then one day, my cousin took and hit me up Like, yo, come to the studio I went to the studio with him, the engineer He told me the same thing He like, yo, you look like you could be somebody He like, get in the booth I get in the booth, I wasn't doing I ain't, you see what I'm saying I wasn't feeling it So I'm like, no Then I started doing it again Once he came home from jail Okay, so he definitely got you in the studio again Once he came home? No Or you would just practice him or?  So what was your dream? Like, if he was not music What do you think he was gonna do? Or what do you think he was gonna be?   I got locked up and I came home and then, you know. You got locked up? Yeah, we don't want to talk about that too much though. So what's like people go with it?  Everything big, so um, so you just shrunk your project. Only one feature on there. Yeah, one feature, I mean, Doug on that, that's it, you know. Why all the other tactics with that? Like why you like that? It's just like a thing where you see what I'm saying, I want people to know I don't need a whole bunch of features on my mixed tapes and albums and all that for somebody to know that I'm nice or somebody to intrigue my music, you see what I'm saying? Because that's why a lot of other people music gets even played, you see what I'm saying?  But you're not into any features but you wanted to make this project more about you.  A couple new work features, a couple, I don't know how many, I know the young cowboy. I made a lot of money, I made a lot of money off of features. Well, we know you're charging for features. I made a lot of money off features. Even still, you do a feature with it, maybe you saw that at the end when you saw that program. You have to check it out. So like, I'm sure you're kind of selective on who you do features with for sure. So is it like you slowing down the features or you want to focus more on yourself now? Yeah, right now I'm slowing down now.  Getting the cheese, stacking the cheese up and I was like, I'm doing, I dropped my teeth. I'm about to be busy for a minute. So now I was like, you see what I'm saying? I got to get active myself. So let's just, you see what I'm saying?  Got you. But you was looking for a couple of trials.  You are a high bridge right now. Yeah, for sure. So you are high bridge. How did that meet? Can they choose from Philly? Yeah. So how do you and high bridges click up? Click up, click up. They QP texted me on Instagram. And Don texted me on Instagram. What song was it that you think they hit you up? What do you think it was? Your song was spreading. I only had one song go. It was called Proud of You. And they only had like 82,000 views. And it was out for like eight months. And they reached out to me like pulled up from high bridge. I got on the train by myself, so it went down. So you were really familiar with high bridge being from Philly, of course. Yeah, sure. So what was it about them that made you like lock in with them? It was just like when I pulled up on them. You know what I'm saying? When I pulled up on them. I don't need nobody with me all the time. You know what I'm saying? I pulled up on them. I'm talking to them. We having conversations like we wasn't even doing music. We wasn't talking about music. We just having conversations. So it's like, all right, copy. I understood where they was coming from. And then on top of that, when I come from, I don't get an opportunity. A lot of people don't get opportunities at all in life to even change their life. You see what I'm saying? Some people miss their opportunity. So it was like, a lot of people don't know. We were like family. We locked in for them. So what was the obstacle you had to like, I guess, overcome? Or what was something that they, I guess, a lesson that they taught you, especially when coming into the music game, coming into the industry and meeting different people? What are some lessons that you could like, you know? In this business, I learned, they taught me, in this business, you see what I'm saying? It's cool to build relationships with people and understand certain things, but you got to always understand that it's business at the end of the day. You see what I'm saying? As cool as it might get, as friendly as it might be, you know, God is business, you see what I'm saying? So it's like, that's a big lesson I learned from them that they taught me. You see what I'm saying? Business is business. That's what I'm saying. That's what I'll be on business time. I ain't trying to kick it with all the rappers. I ain't trying to be with them. Do you think kicking them with rappers play a major part? Yeah, for sure, but I ain't trying to be like, you see what I'm saying? I'm trying to do it just because the next person is trying to do it. You see what I'm saying? You understand what I'm saying? They understand what I'm saying. So you're red selective on who you're building relationships. So was there ever a time when you had to remind people, you know, like, this is business, like, you got to... Yeah, a lot of times, because people... Yeah, I'm a genuine type of person, you see what I'm saying? Like, I don't care how... what somebody really got going on. But if you believe in yourself and your team, believe in you and all that, and y'all got something going, you see what I'm saying? Y'all come around me with that energy. I know how it feel like to be down there, you see what I'm saying? So it's being cool here, but still remember I'm handling business.   No, I'm not. So what was some adjustments you had to get used to?  What was some adjustments you had to get used to? A lot, a lot, a lot. The way the girls I talk to, the people I kick you with... It's dead. Yeah, you know... Come on, you know that. I'm saying... So what is it that you're, I guess, looking for in a girl or you trying to, like, just focus on music? I'm on music timing right now, I ain't focusing on no girl right now. See what I'm saying? I got somebody in my mind, but, you know, I got somebody in my mind for sure. You got a girl in my mind? I got a girl in my mind for sure. For sure. But we're going to keep that between me and you. See what I'm saying? Me? All right. I don't have a girl in my mind, but you're still open to whatever happens. Yeah, for sure. Maybe not? Yeah, man, for sure, for sure. Whatever hit the fan. So what are some qualities a female got to have? Like, what you not with? Like, what's the super red flag? Let them know what the red flag is.  They don't want to. They just want the friend potatoes. You see what I'm saying? They just want to sit around. They just want to see what's going on. Yeah, sponges. I hate that. They can't come with more than three friends. Give us one more red flag. More than three? No more than three. One more than three? Because you got three homies. You got two other homies. Yeah, you see my, you see my, you see how they got seen, like, they over there. They over there. No more than that? Nah, no more. It's two right now, so two. So yeah. And then what's one more red flag? What's one more? Living a life off of Instagram. So you hate a girl that posts everything? No, just, just like, everything that happens, you got to be, be in it on Instagram, post it, basically post everything.  Throwing subs? You see what I'm saying? Or somebody make you feel something. You go on Instagram like, bro, I don't got time for that. People screenshot it and send it. You know, there's a different type of vibe now. So you see what I'm saying? Seven hundred people are my followers. Like, screenshot it and send it to you. I don't got time for that. Okay, so how do you, so how do you keep your life private, being an artist? You just re-select it? You low-key? You go live here in Nama. I don't feel like you're going too much. Yeah, I be, I be outside. You be outside? Yeah, I be outside.  I be everywhere until there ain't no where I won't go. You see what I'm saying? I be outside. It just, that's just me. You see what I'm saying? But like when you were chilling, we was chilling till the music came out. The music got loud. And I'm back outside, you know. Okay, you back outside? You know I be outside, but we ain't even gonna talk about that. You know. So what should we look forward to 2022? The year just started. You just dropped your project, top of the age, started first quarter strong. Played two Doug feature. Still rockin' on hybrids. You know. What can we look forward to? Like healthy, healthy food. Listen, I dropped the 1-1-2. Upgraded to ice? How much is up with that? Man, you want enough for real? Not for real. Like, because you know, people say they got ice. 40 and 40 for this, 40 for that. Okay. What was the congratulations gift? What made you want to cash out one time? This was a, this was a, like, you know what I'm saying? When you build it up, you gotta get your own, like everything gotta be yours, you know what I'm saying? Like, a lot of people don't gotta change with their names, you know what I'm saying?  You put your name in diamonds, you know what I'm saying?  Like, earlier, I ain't goin' live. We just was in Walmart. I tried to get my money from Walmart to Walmart from, from, from, from users, you know what I'm saying? I'm tryin' to get the money to do, he tellin' me my ID, my stuff. I tell him, he tried to explain, I tell him, bro, my chain, see my name right here, so the lady, she get my ID, she look at it, and she look at my chain, and she say, no, you good, you good. You know what I'm saying? It just means something. You know what I'm saying? It means something to the people. Yeah, to people who just, you know what I'm saying? Does it really matter to you or you just feel like, you kinda gotta do it as an artist? Yeah, it don't really matter. Like, I like jewelry now. You know what I'm saying? I had a plenty of time I never cared about it, but now, like, I really like jewelry. Okay. So we'll be in the next piece you get goin' still on the cop right now. What's the next piece? You want a little watch? You want a bracelet?  Okay, okay. How do you, so apps like Youtube and New York scene, I feel like, What's the difference in things like Philly in New York? What's the difference? New York? On a music tip. New York way different. You see what I'm saying, the Philly that everybody read the scene, but you know, it's just like I heard everybody do the drill. Everybody do the drill, but out there it's a different type of rec. Like, it's like a Philly drill type. Like, they got the own sound. I feel like they're trying to have me on the bars. They got to have, not right now, everybody. They're trying to do drill now. They got to feel it be true, you know what I'm saying? Everybody wants to have you. That's not your boss. No, I don't be doing that a lot. You know what I'm saying? I don't do that a lot. All right, so you fuckin' with the New York scene? And you already fuckin' with it? Yeah, sure, sure. Fuckin' with any artists out here? Yeah, I fuckin' with a lot. I fuckin' with a lot of artists, but you know. How do you feel about New York being super political? You think that's a bad thing? You just want to stay out of that drama? What's your thoughts on that? I don't be carein' about nothin' before or whatever. Come up, you see what I'm sayin'? You know, my God's my God, you know what I'm sayin'? You know what I'm sayin'? Whatever, come with it, whatever, come with it, whatever. You know? But those, that's the family. Yeah, so it's like whatever. It's the family, it's the family, my brother, so. I ain't know like stay out of it, stay in it, but I don't try to chase it, so. Yeah, like if it happens.  Yeah, I'll go to New York.  Cause I like that you don't really try to make drill songs. I feel like you stay in here, Lane. Yeah. I feel like you can tap in there, but you don't want to get in there, or? Yeah, I can, I got drill songs. I just don't, see what I'm sayin'? And that's not me. When you think a little rick, you don't think of. I know. You don't think of, oh yeah. You got a drill song coming out, I gotta listen to this. See what I'm sayin'?  You look for me. You feel like that? You see what I'm sayin'? They have vibes. Dangerous. Loads vibes, you know what I'm sayin'? So like how, so like according to music videos, things like that, you have full theater control. Yeah. Like you don't need a team like sit and plan out vids, or how does that go? My team really let me like, I get to plan out everything from room to room, but then we come to the table as one, you know what I'm sayin'?   Like they, it's a team thing, so you know what I'm sayin'? Okay. How many songs do you say you got it tough though? I know you should drop this project. But you got a lot of stuff to talk about. You be in the studio a lot. I couldn't even give you a number, it's too many, way too many, way too many, way too many. I'm in the studio and you got... Do you have like a favorite producer? Can't remember, that's okay. I got a couple of producers by a legacy, last, last, the producer. And I got a couple of other ones, from Gucci, like I said. Yeah, it was good. It's a whole of you, but it's allowed to be different. Yeah, and then you probably get sent to your email, I should probably give you a number. So what's your say, what's your biggest accomplishment so far? Made it for a month. She came for a month, she came for a month. She came for a month, and one year. She came for a month, we did all of this in one year. She came for a month. So you started rapping in 2018? 2019, I started rapping. You take the series, 2019? Yeah, 2019, I started rapping. So one year, I should create a label or everything. Everything, you know what I'm saying? That was smooth. So what's on your bucket list so far right now? So you made it after mother's course, but what are you looking forward to? What do you want to accomplish as an artist? I'm trying to be on the billboards, like top 10, you know what I'm saying? Top 10? Like we trying to hit rap, can't be your type, you know what I'm saying? I'm trying, yeah. So how do you feel like you're improved as an artist from then to now? Experience, it's developing, it's sound, like what do you do with yourself? I know how to, now, you see what I'm saying? Before I was an artist, but I wasn't like a true artist, you see what I'm saying? Now I know the craft for real for real, and I know what you gotta do, you see what I'm saying? To who do you like become the person you want to be, you see what I'm saying? If you want to stand where I want to be, see what I'm saying? Yeah, so when people hear Lil Reep, what do you want them to think about? Like what legacy do you want to leave when it's music and the show? Or you ain't think that deep yet? I thought that deep, they just asked me that the other day without, I ain't gonna lie, I forgot that. So tell us more, Anto, what legacy do you want to leave on this music show? Now when I leave, you see what I'm saying? I just want everybody to know like you see what I'm saying?  It was genuine, you see what I'm saying? Nothing was ever for just me, you see what I'm saying? I like to really take care of my mom and do everything, you see what I'm saying? That's a stop.  I want people to know that we was really been doing this, you see what I'm saying? For a long time, you see what I'm saying? Even though it might feel like a short amount of time, though days was long, you know, we're going to take care of each other. That's a stop. So tell the people what we should look forward to, 2022 just started. What comes before the 2022 project? I'm like now we'll stream that, we'll tap in 12 songs, you know what I'm saying?  Listen, 2022, I'm dropping. Who, but I'll probably drop two more cheaps, you see what I'm saying? Turning up, we ain't stopping, you see what I'm saying? We go out on more jewelry. You see what I'm saying? More fast cars, you see what I'm saying? More craps, you see what I'm saying?  You see what I'm saying? They can't, they can't go over. You see what I'm saying? We still flexing, we still going hard. You see what I'm saying? We ain't climbing out yet, you see what I'm saying? But listen, man, I just want y'all to know. Tell me who to find, who to find music. Man, y'all know, it's Lil Reed, man. L-I-N-L-E-K, Kelly, man. Find me on everything at that, man. The biggest high bridge, niggas, man, y'all know, we come out strong, man.


Hi everyone, Joe for JaspysCaseBreaks.com coming at you with 2020-2021 Panini Mosaic Basketball Cellopack Break number two. The last filler, the only filler we had to do to fill up that team random. So this gives away spot in that where you'll be assigned a team and ultimately will unlock that. So big thanks to everyone here for making that happen. Thank you. There's all the teams right there. So we'll do the break first with the first ice roll, second ice roll will be the giveaway part. But for the break, five and four, nine times, one, two, three, four, and ninth and final time. Got Michael down to a few Japs after nine, five and four, nine times for the teams. One, two, and ninth and final time, after nine we got the calves down to the hornets. So there's the first half of the list right here and here's the second half of the list right over there. No trade windows and filler breaks. Let's just print this out and rip open that pack. Could there be some surprises in this pack? Yes. We've seen some silver parallels of the top rookies before. Can happen. They're pretty rare wrecks. I don't recall him signing very many when they were out. They must be worth $1,000 now, maybe more. All right. Thanks everybody once again for making this happen. I appreciate it. There it is. Mose. First pack. There's a Lamello ball, nice. National pride. Lamello ball that'll go to Jeff and the Hornets. The pink camos that are exclusive to these cello packs. We've got a rookie Sadiq Bay, S-A-Double-D-I-Q, getting involved. That's for the piston. That's also for Jeff. All right. Now, let's flip back to this list here. Let's gather everybody's names. New dice, new list, and it'll be the top nine after five, three into two, five times. Good luck. Top nine after five, one, two, three, four, and fifth and final time. After five, so from ten on down, it's only the top nine. That time, sorry, Sean, but I appreciate you and everyone getting in. Top nine though, happy times because you're in the next randomizer. Raymond is happy. So is Jeff, Johnny, Sean Y, Jeff, Canard, Robert, Jeff, and Kevin. Congrats to top nine. We'll see you in that team random randomizer. Jaspy's casebricks.com. Bye-bye.


I turn now to Monsieur Véran. You have the floor, my dear. Please. Thank you very much, and a particular thanks to the World Policy Conference, and especially Thierry and Sangne, for including me. It's a particular privilege for me to be in this panel under the chairmanship of Jean-Claude Trichet, who is also the honorary chairman of Bruegel. You mentioned my affiliation there, Jean-Claude. I also want to apologize for being another male panelist in an old male panel, and I'm conscious of participating in a clearly suboptimal outcome here. But here we are. The question is, is the international economic order collapsing? And I will, again, give another attempt to answer this, and the answer is no. With every reason to be concerned these days, I think we all have them in mind, and they have been analyzed already by a number of participants. There is massive uncertainty. I think this is a dominant characteristic of the current movement, that we don't know a number of fundamental things, even in the very short term. And what happened in China in the last few weeks was a reminder of that. There are some very basic premises of how we look at the world that we cannot be completely sure of.  We're losing the race against time in addressing it. So I'm not advocating complacency here, let me be very clear. But we don't see a collapse in sight of the order. I think the international economic order actually is surprisingly resilient. What happened this year? I was at the World Policy Conference last year. I was privileged to be also here in Abu Dhabi, the other side of town. And since then extraordinary events have been happening. Russia has invaded Ukraine. The consequence has been Russia being isolated in the international system and, to a large extent, taken out of it. So a ring fence from the international economic system as opposed to this conflict leading to a collapse of the system. I think nobody puts the gist of what happened more eloquently than actually two days before the invasion, the Kenyan ambassador to the United Nations, Martin Kimani, who, as probably many of you remember, made that point that what Russia was at the time threatening to do, the invasion of Ukraine, was an absolutely fundamental challenge to all the norms that bind us together on this planet. And so the response in terms of international economic institutions has been forceful, but I would say proportionate in terms of the extraordinary violation of norms that we have seen and an extraordinarily forceful response. So let's look at what I mean by resilience very quickly. The WTO, Mr. Paul Gam, reminded us that it's still there and running even after the aggression of the Trump administration. The G20, we had, to my mind, a very successful summit in Bali, which kind of illustrates what I'm talking about, including some strong wording in the final declaration compared to what I think everybody was expecting. And I think the Indonesian presidency of the G20 deserves a lot of credit for that. The Bretton Woods institutions, Jan Lebsky reminded us of the challenges and the need for the common framework to make progress. That's, we're getting a little bit into the weeds here, but I think if you look at, for example, the restructuring of, the announcement restructuring of the debt of Zambia, we see a possibility of some constructive evolution, especially in the main challenge to the IMF these days, which is the interplay between Chinese lending to a number of developing and emerging countries and the traditional framework embodied by the Paris Club. So I'm not saying the problem is resolved here. I'm just saying that the worst-case scenarios are not materializing. The World Bank, it has been mentioned by somebody in the audience, it's still led by somebody who has taken positions close to climate change denial, but it remains a strong institution. Let's talk about finance, because that's the area I specialize in most. The Basel III Accord on Banking, capital requirements, leverage, liquidity, and stress testing has been an extraordinary international success. It's been implemented in a more globally consistent way than the previous Accord of Basel II. Sadly, the European Union is still not compliant, but most other jurisdictions are, and I think that has led to great resilience in the financial system, in the banking system, as we have seen with the COVID-19 shock and with the shock of the Ukrainian war. The Bank for International Settlements has echoing what I was saying about the violation by Russia of international norms for the first time that I'm aware of applied international sanctions on Russia, one of its members, one of the members also of the Financial Stability Board, showing the effectiveness of collective discipline in the system, I would argue. I'm not aware that the BIS had ever participated in international sanctions before, with the possible exception of freezing the assets of the Central Bank of Yugoslavia, but that was after Yugoslavia no longer existed. We also have seen that challenges to the international, economic and financial orders have not been very successful. I'm not going to expand on crypto these days. We don't see either from Russia or China in very different environments, attempts to, we don't see successful attempts to replace the basic infrastructure of the global financial system, agreements, messaging, SWIFT, the international transaction settlement through CLS group and infrastructures of the same nature. And finally, as Gabrielle has mentioned, we even have unprecedented progress, unfinished of course, in an area which until now had been completely immune to that kind of collective cooperation which is taxation with the efforts of the OECD, I can't finish business to say the least, but the fact that this has even been possible to initiate, I think, has to be taken as a step forward that has happened under difficult circumstances. And of course, the EU, the European Union, which I come from and which is the most advanced exercise in supranational economic and political cooperation, has been built on rejection of economic nationalism with coal and steel in the first place. Well, it has faced an existential crisis, but it has overcome it. Certainly, it has lost an important member, the United Kingdom, but on many parameters, it's now stronger than ever, and we've seen that with the next generation EU, a program of borrowing and spending, which is the first time on this scale that the EU has been able to finance itself on its own at the European level with redistribution among its countries. So, as I said, no complacency. We don't need to replace this system, and I think that echoes what Chaoyi just said. China is not asking for the replacement of the system. It's asking rightly for its reform and transformation. I'm talking about the official discourse of China here. One thing I will say, there have been many ideas already put forward for reform, and I'm not going to repeat things that have already been said. I will just say, as a European, I think Europeans have to be proactive in creating space for other jurisdictions in a changing world, maybe echoing what Aminata Tore was saying in the first panel. When you look at the things I focus most on, the BIS, the Basel Committee, the Financial Stability Board, Europeans are clearly massively overrepresented in that infrastructure. There's absolutely no reason that in the Basel Committee you would have seven individual countries of the eurozone represented individually together with the ECB. So that has to change. Europeans need to take the initiative and provide for more balanced representation, particularly of East Asia, but also of the Middle East, Africa, and Latin America. Let me conclude on that. Thank you very much for this strong plea for the European to be less numerous, but as influential as they are, but less numerous in many of these groupings.