All right. Good morning, everybody. I'm not sure that I've ever seen 9 a.m. at Fostem, so thank you all for coming to talk about every developer's favorite topic I know, licensing. And I have never been able to participate in the JavaScript room here before, so I want to thank the organizers for having me and giving me the opportunity to talk about it. And I didn't know that the opening keynote in advance was going to start this topic going, but that's, as the introduction said, set things up for us to talk here today. I'm the executive director at the Free Software Foundation. I've actually worked at the foundation since 2003 in different capacities. I've been the executive director there since 2011. And as part of that, I work with all the different teams at the FSF, including the technical team with our students' administrators and web developer and our licensing staff as well. So try to help them work together to advance the FSF's interests and freedom for the web and elsewhere. So I've talked about this topic in licensing focus settings before. I've never talked about it in the JavaScript developer focus setting before, so definitely a big part of what I'm here for today is to hear back from you at the end about whether what I'm presenting here makes any sense at all from your perspective. And then if you know possibly other ways where we could accomplish the same goals besides the system that I'm going to present here. So try to save some time at the end for that. And if we don't get to your ideas, then please do follow up with me after we're either by email or I'll be around the conference the rest of the day, of course. So at the Free Software Foundation, our goal is to not just make Free Software better, but to make all Free Software Free Software. So in our perfect world, there's no proprietary software. That's all free. So of course, we have the problem right now that was mentioned in the keynote yesterday. We have now laptops and desktop workstations that run all free software, require no proprietary drivers or proprietary blobs. Even the boot firmware on this laptop is free software. And the FSF has certified machines that meet those criteria under our respects for freedom program. But despite the fact that we might run one of these systems, we're asked to run non-free software. And in fact, our running non-free software still every day. And the main way that happens is by proprietary JavaScript being delivered to the user in the web browser. And so Richard Stallman called this the JavaScript Trap in an article that he published in 2009, which was referring to his 2004 article back when Java was proprietary and it was the Java trap. I don't think I have to tell you all that JavaScript is basically an assumption on the web now. You can't do much of anything if you turn it off or block it. Mozilla in 2013 removed the option that had been there for a long time for users to disable JavaScript. And I wasn't happy about that, but I understood why they did it because users were unchecking that box and then reporting all sorts of bugs that were happening when sites weren't working properly, not realizing that they had disabled JavaScript. But it's just an indication of how required in this theorem JavaScript on the web is. Now, at the FSTF, we don't want to avoid all JavaScript, of course. We only want to avoid proprietary JavaScript. So this isn't necessarily a problem for freedom reasons. People might object to it for accessibility or other reasons, but for freedom reasons, not necessarily a problem as long as the JavaScript that's required is actually free. Unfortunately, JavaScript programs are generally not free. And in particular, they're not free as they're typically distributed to the user. So we know there's all kinds of very popular free software JavaScript frameworks out there where the site operator or the web developer can get a copy of jQuery, it's free software. But the way that these programs are then served to the user in their browser doesn't meet the requirements of free software even if that software is available elsewhere under a free license. So what do I mean by that? The two basic requirements for something to be free software. You have to tell the user it's free software in some fashion because otherwise, around the world, the default copyright is all rights reserved. And so it's proprietary by default if there's no notice to the contrary. And then you also have to provide the complete and corresponding source code. So we know that permissive licenses, like the expat license, allow, commonly called the MIT license, allow people to redistribute that software in binary form if they want to. They're allowed to do that under the license, but if that's how they do it, then that's not free software. It's free software if the source code still comes with it. So the failure to do these two things are the reasons why most JavaScript is non-free. So we know minified JavaScript is not really source code. It's not the preferred form for modification. It's not quite as difficult to work with as a true binary, but it's essentially the same thing. If you are debugging something or trying to make a modification, minified JavaScript is not going to do you any favors. So because people serve JavaScript minified and for all the performance reasons that they typically do, that means they're not normally giving users the source form, which means it's not free software. This hurts users. We shouldn't wait for proprietary software. So we're talking about two different cases here. There should be clear about that. One, I would call kind of the unintentionally non-free case, and these are the cases where people are trying to use a free software JavaScript framework or a free software JavaScript, but they're just not giving users the source and they're not providing clear license notice. That's one category. The other category is JavaScript that's deliberately proprietary. So things like Google Analytics or the JavaScript for Gmail or Google Docs. That JavaScript is intentionally not free. So it's important to keep these two different cases in mind. In the second case, we know from the history of free software versus proprietary software, all the terrible things that can happen to people as a result of proprietary software. The same things can happen as a result of proprietary JavaScript that happened as a result of proprietary C or Python or anything else. We have an unfortunately expanding collection on ganu.org and slash philosophy, slash proprietary of all these examples, not just JavaScript, but other things as well. So if you're ever trying to explain to somebody why proprietary software is harmful, that's a good resource. Run through these quickly because I know you're all familiar with the fact that JavaScript can do these things, we know that JavaScript can modify the copy-paste buffer so the user might think they're copying something and then they paste it into their terminal and it's rm-rf and there you go. Block browser functions like saving images, sort of the poor person's DRM. Record your keystrokes. This is one that a lot of people don't realize. It's gotten a little bit of press. There's kind of a story about how Facebook was recording what users were typing, even if they didn't post it in the end. Also another story recently about how customer service online chat typically actually shows your keystrokes to the representative on the other side without telling you that. And then we know that JavaScript can be used, of course, to deliver malware within the browser and there was one example some years ago that was used to exploit Tor. But it's also the other side, it's not just about avoiding attacks or mistreatment of malware, it's about enabling the power of free software on the web just as we have that power and that dynamic and that culture before JavaScript was such a popular thing on the web on your own system. I know there's, this all kind of started with grease monkey, I think, and then it turned into several different sites repositories where people are sharing JavaScript that can modify the behavior of different popular sites or do different cool things in the browser OpenUserJS is one that I know of and they're actually making like a pretty strong effort to license the job, because all the JavaScript there is actually freely licensed, which was nice to see. But the point is we're trying to not just stop the negative effects of proprietary JavaScript but also trying to sort of move to a new model of the web that embraces user freedom to modify the behavior of how a site acts in their browser with the cooperation of the site operator and everybody involved. So if we're going to do that, we have to meet the basic requirements that we have to provide source. This is the system that the FZF has developed called, we call it JavaScript Web Labels and I'm going to walk through the different components of that. The first is a stylized comment to include in your JavaScript files to point to the source URL. And it's our, we've stated publicly that we believe doing the following things will be in compliance with your GPL's requirement to distribute source code. So we've had a particular challenge with copy left in GPL covered JavaScript because if you read the requirements in a certain way, you might think that you have to distribute a full copy of the GPL with every JavaScript file that you serve to your user. And that can be possibly pretty burdensome. And also how do you properly serve or offer the source code to the user in order to meet the GPL's requirements? So these source code, source comment formats work for that. And then after that, indicate the license of the JavaScript code. And we have a couple of two different ways of doing that. The first way is actually embedding the, or putting the license notice in the file using a comment of that format. Of course, if you're the copyright holder of the JavaScript, you can actually use a license exception to make this even easier for other people. So using GPL v3's additional permission feature, you can distribute non-source. You can add an additional permission worded like this. You may distribute non-source, e.g. minimize or compacted forms of this code without the copy of the GNU GPL normally required by Section 4, provided you include this license notice and a URL through which recipients can access the corresponding source. So if you're the copyright holder of JavaScript that you wrote, then you have the power to add an additional permission to the license. You, of course, can't do that if you're modifying somebody else's JavaScript under a free license because you have to have that permission in order to change the license terms. But this is a clean way to hear the copyright holder because it leaves no doubt about the GPL requirements for providing the copy of the license and the corresponding source. It lets people know that they can... it's okay for them to not distribute the copy of the license as long as they provide a link to the source code. But you're probably not the copyright holder for most of the JavaScript that you're working with. This format was actually announced all the way back in 2012. We're going to talk about how it's doing since then. The full description of it is in slash licenses, JavaScript-labels on gnu.org. The goal of the system is two-fold. First of all, it's to be machine-readable so that it can be read. Licensing information can be read and processed by browser extensions or server tools. But the second thing is it really does need to be human-readable. If you think to the GPL's basic requirement or most free software licenses, the basic requirement that you need to tell the person what they're receiving is free software. You need to inform them of the rights they have over the software. This isn't strictly a machine-readable format. It's something that humans are supposed to be able to read and understand as well. It starts with adding a link somewhere on the site, typically in the photo with other copyright information. This is fsef.org. Link called JavaScript licenses. When you follow that link, sorry, you mark that link with an attribute, REL equals JS license. That's part of the machine-readable automated tool portion. This is part of the approach because it means that any page of the user loads, there's a standard place, a standard link that should lead to the licensing information. That link leads to something that looks like this. It's a simple HTML table in a specific format. You have the file that's being served to the user. For example, the minified version. In the center, you have the license, and at the end, you have the source, the corresponding source. This shows you the format of the table. The table columns are given specific IDs. Again, they facilitate the processing by tooling. I showed you fsef to start with, of course, but it has been adopted by some other organizations and some other sites. We're going to talk more about how that adoption is going in a minute, but just to show an example from Electronic Frontier Foundation. It's pretty cool that they picked it up and started doing it. Free software, obviously, generally for their work, but they went out of their way to make sure that they adopted this as well for the JavaScript that they were using. I think this is a screenshot of their old site, but I confirmed last night that it's still there after they went through their site redesign. They still have it, and in fact, they have a lot of their JavaScript license under the AGPL, which I thought was excellent. Automation, based on this format, you could imagine a number of tools that did interesting things with it, but the one that we focused on is called GnuLiberJS, it's a Gnu project. It's a browser plugin for Mozilla-based browsers that looks for this format and licensing information on sites when you visit them, and if it doesn't find it, it blocks the proprietary JavaScript on the page. It looks for that web-label's information and for any JavaScript that has a corresponding source link and a corresponding license that's free and has a system for recognizing licenses, it will allow that JavaScript through anything else that will block. People don't know a script, right, to generally block all JavaScript, but this is a different, more targeted approach. So, like I said, it happened in 2012 that we started pushing for this. How's it going? I would have to say, not that good. Well, some of the reasons are a bit mundane, so GnuLiberJS as a piece of software for a long period of time was not working very well, and it was hard for us to persuade people to adopt a particular format that has the aims of being machine-readable and useful without any corresponding high-functioning tool to actually use that format, and people that are operating and taking care of big sites with a lot of JavaScript and a lot of pages, you know, you can't give them a tool to go through and test the site, and it becomes quite a bit of work for them to go through and make sure that everything is done properly and according with the format by hand. Then there were the updates to the Mozilla extension system, which broke GnuLiberJS further. So, it took us too long to react to this and catch up to it. The good news is that it was rewritten, and from all reports it's now working pretty well. There were also some performance issues with it. You know, it's trying to go through every JavaScript file and see what the license is, and so it would have to do that for every file before letting the page proceed. There's been a lot of performance improvements. I encourage you to try it out and give us some feedback on it. And there are still further challenges coming. The changes that Google was talking about making to the Chrome extension system, the API will basically make plugins like this almost impossible, maybe impossible, because they're taking away the ability for plugins to modify the content on the page. It's also going to cause problems for NoScript and a lot of other plugins that people have come to rely on. So, I imagine people might be wondering, why didn't you do it some other way? And I'm hoping to hear some of your ideas for how licensing information can be presented that satisfies those two goals, the machine-readable and human-readable. We do not claim this to be the one true method. We didn't go through a big public comment or kind of standards development process in order to come up with this. We wanted to get something out there to start with because this problem even in 2012 was so bad for free software and it's only gotten worse since then. But, you know, plugins like LaborJS could easily support multiple systems, and there's no reason why you can't have multiple systems. There's no reason why we can't experiment with some different ones and settle on another one. I know there's been some proposals using RDF, some using HTTP headers or getting attributes like for licensing tags added to the script elements itself or using custom attributes or I think there's a potential maybe with JavaScript source maps. I saw the great news the other day that Ruby on Rails is going to be turning apps on by default. So, I think there's some potential there. But, you know, we're not going to wait for the perfect system to keep pushing forward ways to help people sort of JavaScript in a free way and help users receive it in a free way. So, let's point to some next steps. LaborJS improvements. I mentioned that a lot of them have happened. It was Georgia, the author of NoScript to help us get that done. But there are more things that need to be done. We all have more wishlist and future requests for it. Mobile devices. You know, the primary way people browse the web now. The good news about this is I'm hoping, you know, fingers crossed that we will have an Android version available within the next few months that it will work with Firefox or iSCAD or any Mozilla-based browser on Android. It won't be on the iPhone because the App Store is not very friendly to resolve for. Then the next step after that for us is to have a command line or automated testing version of LaborJS. So, even for us at the FSF, it's kind of a problem. We work really hard to maintain clear licensing information for our JavaScript, but we also use, you know, upstream platforms. We use Drupal. We use CPCRM. We use MediaWiki. And anytime there's a change or an upgrade, sometimes the web-label system breaks. There's a new JavaScript or something changes. And, you know, we don't necessarily find out about that unless we manually check it or somebody reports a problem to us. But something that people realistically need in order to actually adopt this is an automated way to test it in an easy way without browsing to every individual page on your site. That's the next priority after the mobile version. Something that I'm hoping people in this room might have ideas about or be able to help with is how to modify or make, you know, the right sensible defaults or features in the tool chains and the tooling that are popularly used in the JavaScript community to make a format like this for a minified JavaScript to kind of just happen automatically or, you know, other ways that the tooling could be modified in order to do better at providing licensing information than links to corresponding source code. And then, you know, we can't just demand that upstream projects make changes in order to, you know, fix licensing information. If we want that, we want to help them. And that's something that we have done at the FSF. We've sent some patches upstream to, I think, Etherpad and some other projects to help the LibreJS or, sorry, Rails and JavaScript licensing information get upstream. You know, you can imagine there's a lot of projects that if they started doing that, they're in such wide use that it would make just a huge difference on so many different sites where those frameworks or those platforms are being used, they would be properly free right out of the box. And then we need on the user side, we need awareness campaigns, you know, on both sides, user and the site operator side. We need awareness campaigns in a friendly way, especially because when I mentioned those two problem areas, the, you know, but also the unintentionally non-free, especially in that case with unintentional, we need to take a very friendly approach and a constructive approach, but emphasize the importance of this, that this is software that's running on our local machine and needs to be free just like any other software that we run locally. So I would love to hear your feedback, your ideas, your comments about this. Has anybody in the room tried adding web labels to their site before? We got one. Yeah. A lot of people think about that method of providing license information. So what a link to the standard license suffice instead of putting a lot of text and a comment. The only text that we're recommending, so two things, you don't need the comment in the file if you're using the web label system. So if you have that separate table that provides the correspondence between the file, the license, and the source code, then you don't need to add anything else to the file. You only need to comment in the file if you're not doing the full web label system. But even if you're putting the comment in the file, what we're encouraging people to do is just to put that basic statement about the license in the file, the short version of the GPL boilerplate, for example, that you typically see in a source file because link to the license isn't really doing a great job of telling the user at least the summary that this is free software and you can freely copy it and share it and modify it. So that's nice to have there. But you don't need to worry about it all if you do the web labels.


So we're here at the Mara Connect, and who are you? Hi, I'm Adon Lachinsky from Gang concept in Germany, and we're here presenting with a lecture bit this automotive demonstration. So what are you showing here? Can you come close to the mic? Now for the presentation of the mic. This is a standard Ramazaz R3 development board, but this is very similar to what is actually being used in production. And what we're running here is our FROV hypervisor, which is running 2PM. And 1PM is running cluster system, and the other one is running the IVI system. And they're both running in the same system here. The hypervisor ensures that the voice are isolated, and that they are basically running independently of each other, but on the same hardware, which gives a benefit in the sense that you just need one system, and instead of two, as previously. So what is this, Ramazaz R3 car 3H3 platform? Well, this is our arm raised cluster system. Can you come closer? There are eight courses in there, so four A53s and four A57s, and there's an additional two analog step R7 board in here. So the R7 is typically used for all these safety related things. You run your RTOS on, and on the Cortex-A, you run the hypervisor, and the Linux or the virtual machines you need for your setup. So it's a CPU-GPU virtualization. Which part of the Naro do you work with? So regarding graphic virtualization, there's also imagination for the art graphics in here, and that supports hardware virtualization, or hardware-based graphics virtualization, and that's what we're using here, so that both VMs have access to the graphics card and can do a very performant graphics output. And are you based in Germany? We are both based in Germany, yeah. So ElectroBit is a German company, and we as well.


Call all hands speak to quarters But better one broadside into it. You please Captain Bush point us on target Lin stops really Bad CS foresters indomitable man of the sea a ratio hornblower to imitate me in in every gesture and speed But I I had other things on my mind Bonaparte's forces were laying siege to the Russian defenders outside the city of Riga Immutation well the art of war seems to be that of imitation Well, it definitely was so in the belief of Frank Kaiser it's a Prussian colonel who had deserted Bonaparte in order to oppose him And who was showing me the Russian earthworks and the lines You will observe from a door hornblower From this vantage point up here on the gallery of the church tower We can see spread out before us the whole operation Maiden is attempting to move up his heavy guns Cleftic method now from the line of the river Diagonally up to the pine boots. It's dug a trench. It is protected with best works Huge baskets later fit with the classic method. I see then from the pine woods another diagonal trench Yes, and so on the zigzag Each captain closer to our lines and clearly has solid breath works behind which to impenoy. He's heavy up to you Yes, but how long before they're in range? She'll judge two weeks Two weeks. It has been done this way since the days of Caesar Well, nobody will deny that Bonaparte wants to be another Caesar But you know guns heavy enough to batter down those breastworks. It is most difficult I've got mortars aboard my bomb catches if we could we we could level them no time No, and why not do so Commodore? I said if we could but that river isn't deep enough Sandbars shallows quick sands. No. No, we'd run aground before we got within range. I see So we must carry on the fight our say Betty telephone close of it. There are some things that even the British Navy cannot do. I Understood nothing was impossible to the British Navy Apologize Commodore To my lips good will even between allies is sometimes a frail matter Earlier we'd been warm friends, but now that the French approaches were moving towards Riga I was asking why the Russian guns couldn't stop the enemy and they were asking why my ship's guns couldn't do the same I Had it back to Riga and they're on the waterfront. I I ran across lift till it mound Oh Dusty earbuds. I thought this is dry as a camel. Oh, Mr. Mound if you completed your business I have a moment before going back aboard the non-subtractor. Okay, sir There's an Indian over there. Perhaps you'd join me in a glass of this odd beverage.  I think of home There's honeysuckle outside my face and Hampshire Comes in the window sweet and strong as perfume. You're married man Yes, sir long little more than years. I'm children. We're expecting one sir. Oh, yeah Any day now, we're both hoping for a son I sent a letter to my wife the cam carried it on her boy's back. I'd be there by now. I Wrote her that if it's a boy Yeah, I Told us name him Horatio. Oh Did that if you've no objections? Oh, there's no reason to consult me. Mr. Mound. It's a common enough man Yeah, listen Listen to that gunfire Well, Mound it seems we're not back in England among the honeysuckle On board the nuns such I was both touched and irritated by months here What glorified me in his eyes, I certainly couldn't imagine not one nice ship stood idle in the midst of battle line of trenches here a Battery here their main flank and stores are behind a dyke here called water is close enough to spit on them Oh, come look at the chart show water bush. I too shallow for us. I mentioned that to plaza. It's he was not impressed land soldiers Well, at least you understood it and Mound understood well, it's a good young officer Yes, he is he's a fine future too. You know, I find I've quite an affection for young Mound Lived in Hampshire. He says as a home there wife and a child on the way. How's he now? Oh, I never even knew he was married. No, I never thought to inquire not before today. I had a drink with him today Good officer. Yes I'd only just come in from the breastworks dusty road from there to Regan. I float was as dry as a Camel what's that sir as a Camel By heaven boss, I didn't I think of that before what's a whole gathering sentimental talk about home and all that nonsense Bush a man should keep his mind on his business and our business is war. Where's the messenger? My compliments to the officer of the watch. Would he please make signal to the bomb catch Harvey for mr. Mound to meet me on shore at once Oh Exactly Camel from place of its and the general is now fifth left in a mountain. I may have your ear also Please you're coming out. However, I believe it is a fool's errand on which you're right here in such haste Why you see you will use camels. We have no camels. This is not the Sahara desert Yes, but that's not the commodore is an expert on ships Perhaps these cameras are called ships of the desert. He's an expert on them Oh, it's a can of unclassified. Shall we get down to business? I make no offense. Well, I hope not the allies in the center Exactly generalist while we talk the Frenchman move ever closer and closer Well in this instance gentlemen a camel is unable term mr. Mound Will you introduce these gentlemen to the meaning of the word Camel? Yes, a camel is a method of reducing the draft of a ship What kind of cabbie as the Commodore has already pointed out the water in the river is very shallow Too shallow for our bomb catches to come within range of the ms. Yes. Yes. I've been told it over and over Oh, no receipt mr. Mound So if two loaded vessels are lash tightly one on each side of the bomb catch and are then emptied of their loads It will lighten all three and raise them farther out of the water They're out of the water. I do not yet comprehend. Generally. Oh, you have some barges in rigor. Yes Barges don't know more than a couple of feet of water when empty. We will load them with sand then empty out the sand The bomb catch could be lifted keen out of the water And get we get close enough to bring the guns to bear exactly general we may commandeer two barges big ones That's one scum. Oh, good. Oh, man. That's there's only one problem. Yes, sir Are you going to steer them all drawing less than two feet of water? They'll be almost unmanageable. That's true, sir They'll drift at the mercy of the winter unless mr. Mound by George a Daniel brother Generally not that's a very large auxiliary rudder set well behind the ships It's big enough. It will compensate for the lack of bottom to the key Man you'd also better pierce the sides of the barges and use oars as well. Yes, sir Good. Well, we'll proceed at once. How long do you estimate Mound? I'd say by tomorrow noon Tomorrow noon you disagree if I'm glad to return it's come with a hornblower I did not follow you and your cameras. I didn't understand about them But these past few minutes I have been observing the activities of the enemy. Please take the telescope and see for yourself They're beginning to move out of the big guns. What by tomorrow at noon. It's well, it may be too late So the art of war is not entirely immediate after all just as we had refused to accept the inevitable Exactly so had the French Marshal made on tried to hasten his time table Work on the camels progressed with border layer phantic speed The barges were brought out from Riga. The Harvey was last between them Torches reddened the darkness as the men labored to quicken the task to be done by dawn Defton and Mound was able to start toward the river Like three giant water bugs fastened together the barges and the bum catch began to move I know sir We're not deep enough in the water to get any bite against the current or the wind the Daniel rudder doesn't compensate even though Right, sir. We need a stronger pull and we haven't got it. You better drop anchor, but the French guns are moving up It'll do is no good to go on like this our draft may be shallow But we'll we'll only pile up in the soul water pile up and sit there on the soul watching the French batteries pound our allies There must be some solution. Let's hope we find it. Well, we must find it Well, thank you, Mr. eyes up My promises we seemed unable to give aid to our allies we'd raised the Harvey by lashing her between two emptied barges, but Wind and current for proving too much for us to handle There's an hour after dawn On the deck of the hubby the young face of left in and mine was gray with fatigue and helplessness We've got much time left. So have we Only the wind would change if it would back around behind us instead of being off the starboard Besides the French guns will be in position by noon. Yes If the wind shifted we'd be in position to in shallow water right on Boney's plank 13 inch shells loaded with the explosive fire from that motion Must be some replacement for a rudder, sir. I trust there is Heading for the church tower I took with me a warm feeling for young man And also took a signalman summers to rig a pole so that we could let the bomb catch know the effect of its mortar fire Colonel von Klasiewicz watched these operations with me Signals ready for boys very good summers stand by It's the French siege guns are in position Any moment they should open fire Moving up river now Colonel. Yeah. Oh, yes. It moves. It's an awkward craft It moves as fast as it can the French siege guns will be sheltered behind those brass works You see they are piercing holes in the best way to allow the muscles to project I can see our battle is a useless against best words of the Harvey carries a mortar. Oh, yes Yes, very I once in position the shells will drop down as it from the sky I think see you also general asthma will be here at any moment observe personally good Good governor general of Riga for silent thunder. He will be very disappointed should your plan fail I also should be very disappointed Summers, there's the ready flag going up on Harvey.  Please do describe to me. I will sir The mortars being loaded. It's aimed by pointing the entire ship like an arrow at the target Summers make signal to Harvey on target fire at will Yes, one has been fired without delay That's what the best works, huh? They've been novel a siege gun destroyed look the muscle is picked wide open The French wallstone battery on the move that you see that summer's coming up from the real son You're singing runs right from a door. They're heading to take up a position on that point of land below your body Bring the guns to bear very soon. I think we'll break off more actions. I have a moment if you please Commodore cornblower. We should be beat if your mortar fire should continue as long as possible It is doing much better. Well, very well general. It shall be continued Summers keep an eye on that horse to on battery Catches being fired up on Nelson. Yes, I can see that French cannonball dropping all around it That last ball to raise the fountain of water very close that's close enough someone signal to the Harvey discontinue the action She's got it sir, they've sent the anchor and out for the oars Sales up Oh come boy She remains within range still yes the wind would drop now So much smoke she's moving Fast enough summer's Faster faster she's reaching for deeper water now sir, but she's still within range the French is a No, sir, they're not tied together any longer The tenant mind has cut the barges loose summers Once out of show water the Harvey can no move faster Notice the silence gentlemen French batteries stopped firing. She's out of range. Yes Very close call Commodore very close, but the world it's another that's not Where's worth it? Commodore hornblower Thanks to you. I should estimate the progress of the siege has been delayed by Oh, I should estimate a bike by four days For days. I should estimate Four days four days is excellent It is by such little delays that a final victory will be one in return and I'm here for what days I felt inexpressibly tired and worn out The main army of the talent blown apart was marching into Russia and all we could accomplish at this outpost was for days delay sir Mr. Wilson is second in command on board the RV with your permission. I shall signal him Signal Wilson. Yes, sir Now and Now and was killed. Yes, sir. What are the last shots from the shore? I see I delayed signaling to discontinue the action. I Delayed till the last moment. I he was a fine officer. Yes Only I was he he wrote his wife if his child is a boy. She's to name him out to me if only I Only I'd not delayed a fine officer, sir was Mr. Mound So shall I signal for mr. Wilson? What's it? Yes, Captain Bush signal mr. Wilson, if you please Joe Hornblower starring Michael Redgrave is based on the novels by C. S. Forester Music composed and conducted by Sydney Torch produced by Harry Alan towers You


This is stock number 9T404A, we are here at Summit Automotive in Fond du Lac, Wisconsin, your new and used Ram and light duty truck headquarters. Today we are checking out this super clean 2018 Ram 1500 Quad Cab Short Box. This truck has the award winning 3.6 liter Pentastar V6 motor and it has been fully safe to get inspected by our service shop as a fresh oil and filter change, all the fluids have been checked and tapped off and this truck is 100% ready to go. Maximum steel metallic is the color we shoot all of our videos in 1080p 60 frames per second so if you have HD capabilities on your computer tablet or smartphone device turn them on right now because it is like you're right here looking at the truck with me and definitely your best way to check out the vehicle quality and condition wise before seeing it in person. If you want to check out more photos in the upper right hand part of your screen is a link right to our website, it comes with the Goodyear Wrangler SRA 27560R20 tires with about I'd say 60 to 70% of the tread left, maybe even 80. Has the 20 inch factory alloy rims with the chrome covers, didn't see any dents or dings on that front fender, headlight lenses are nice and clear, the express package gives you the painted front bumper, no dents, dings, scuffs or scrapes on that and you do get factory fog lights with that express package, passenger side fender, no dents or dings on that and as you go down this side of the truck you can see just how clean that body is, how reflective and mirror like that paint is, we take these HD videos so if you are far away or even if you're close by and just can't make the trip down but you're still interested in purchasing the truck you can still see the truck here, the truck and have confidence in the vehicle that you're looking at so that you can make a smart buying decision from the comfort of your own home. In fact we offer a Summit Auto Fastpass in the upper right hand part of your screen link right to our website where you can apply for financing on this truck, get pre-approved, get a payment quote, even appraise the trade if you have one, all from the comfort of your own home and that's the Summit Fastpass option you can see the frame and under body is like new and the lower rockers are in excellent shape as well, these back tires have just as much tread as the front tires and the back rim here is in excellent shape. We want to make sure that when you get here there's no surprises so you can be ready to go and have your whole deal done with that Summit Fastpass and just take out some of the time that's usually involved with buying a new vehicle. Spraying bed liner, excellent shape, the bed is in excellent shape, has a locking tailgate, backup camera, full towing package which includes the receiver hitch four pin and seven pin wiring and on this side the truck just as clean as that passenger side, no dents or dings in the box and for full disclosure this back rim excellent shape too. It does come with the heated power mirrors and as we hop inside the truck here you can see the express package gives you the gray cloth interior, there are no ribs, there are no tears on the seats, excellent shape, has factory floor mats throughout, power windows, power locks, power mirrors, auto headlamps and as we hop inside the truck here you can see that this one has only 8,298 miles you get the digital speedometer, you can change that to miles per hour or kilometers per hour, put the lights on and turn that down so we can see a little bit better. Digital speedometer, outside temp and compass display, the steering wheel is in excellent shape, got cruise controls on the right with the gear selector, Bluetooth and information center controls on the left comes with the 5-inch touchscreen radio, AM FM and Sirius XM radio capabilities, this is also where your backup camera shows up. Climate controls down here you got your 8-speed automatic transmission, push button four-wheel drive including four-wheel drive, low M lock, stability control and a tow-haul mode, you do get a power point there and a USB on that side, carpeting and floor mat is in excellent shape, pass new side seat, no rips or tears on that, this truck's never been smoked in, smells like new inside, headliner is absolutely perfect, you get map lights up here and we'll take a quick look at the back seats.  Power windows in back, also the child safety locks on the back doors and we will take a quick look under the hood, I would personally like to thank you for checking out the video today and hopefully from this HD video you will have been able to tell just how clean this truck is all the way around inside and out under the hood, we have the 3.6 liter Pentastar V6 motor and Jimé is very clean, runs very smooth, this truck has been fully safe and inspected by our service shop, has a fresh oil and filter change, all the fluids have been checked and tapped off and this truck is 100% ready to go. To see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, half-tons, three-quarter-tons, one-tons, you name it we got it go to our website www.summitauto.com full pictures and descriptions of every single vehicle from two locations all at summitauto.com and if you'd like to check out more HD videos you can go to youtube.com slash summit auto remember to like, subscribe and share on this video and all the videos that you see there in fact in a second you will see links to subscribe to our YouTube channel on your left it links more half-ton truck videos like this one on your right if you have not been to our website on the bottom link to this vehicle on our website click those check us out and we really look forward to help you with this super clean 2018 Ram 1500 quad cab short box with these six four or I'm sorry the 3.6 liter V6 motor and maximum steel metallic thanks again


Oh, hi there. Welcome to TomorrowOrbit.12.13. My name is Jade Kim, this here is Jared Head, and today we have the exquisite honor of sitting down with Brittany Zimmerman of the Paragon Space Development Corporation. It's an innovative, world-class aerospace company that specializes in life support and thermal control in extreme environments. Hello, Brittany. Can you explain anything that I just said about Paragon? Yes, I can do that for you. So what our company does is life support systems. So that is keeping people alive, not like a doctor, but in equipment, essentially, onboard spacecrafts, habitats for planetary surface operations, spacesuits, and we do it in extreme environments. So our primary area is in space applications, but we also do terrestrial applications as well. Very neat. So can you explain a little bit more about the aspect of life support? So like you said, not like a doctor, but in that basically just having people survive. So can you explain a little bit about what goes into that? Yeah, for sure. There are a lot of portions that go into keeping people alive in space. So one of the things that we specialize in is water reclamation because water is obviously an important substance to have during any mission for life. We do air revitalization. We do radiation protection. We do thermal control systems. So basically, if you think about a mission going out into space that would only utilize robotics, that is not something we probably specialize in. As soon as you add human exploration into any of your missions, that's kind of where we come in. So it's temperature control, nutrients, water, air, making sure that pressure control is correct. We do humidity condensate, so making sure that the correct amount of moisture is in the air and not condensing on any of your instrumentation. We do all radiators, for example, as well. So we have a lot of stuff going on. Very cool. So then, with what you guys have developed thus far, what kind of applications can be made in terms of... I guess what I'm asking is how extreme of an environment can these systems acclimate to? Some pretty extreme. Obviously, space is not made for human life to exist easily. So we can operate in vacuum. We do a lot of stuff trustingly as well. So we do a dive suit, so high pressure applications, as well as vacuum applications. We do some stuff for the mining industry in the past. We've done that. So I can't think of many environments in which we wouldn't be able to operate maybe high acidity environments. I don't think we've jumped into that. Other than that, I think we've done it all. Very cool. And Brittany, I'm sure you guys work in things like vacuum and high and low temperatures and other things like that. And Wicked is asking in our chat room, does your work include MMOD shields, which is micrometeoroid shields? It keeps yourself free of extra holes. Seems like a fairly important part of keeping someone alive in space, which is a pretty good point that they bring up. Yeah, certainly. So MMOD is something that we take into consideration, but we don't necessarily make shields for it. So the structural component of a spacecraft is usually designed by another company. But what we are responsible for is being able to continue life support if some sort of breach of the barrier were to occur. So we have leak rates associated with different MMODs that were, if they were to break through the shell of a spacecraft, how much oxygen, nitrogen, what kind of pressures would we need to be able to pump into the environment to keep astronauts alive for a required period of time with certain requirements from whichever spacecraft we're working on at the time to ensure that the crew would have an appropriate amount of time to fix that problem and still be maintained. Got it. And kind of going off of that, a question I had as well as Travis Neal from the chat asked, didn't Paragon do the life support assessment for Mars 1 or did they refute it? No, Paragon, that was before my time with Paragon, but Paragon, I believe they did Inspiration Mars and I'd have to ask Barry if we did Mars 1 or not, but I think that we definitely looked into it, what the conclusions were on that, I'm not exactly sure. Yeah, so interesting stuff about that, them. So just to kind of, you know, talk a little bit about how Paragon themselves work. Distractor 1701 is asking sort of like, what's the mode of operation for Paragon? Are you a manufacturing hardware? Do you consult subcontracting on design work or do you do a mix of both of those? So we do a lot of stuff. I think it makes for a healthy business model, of course. So we do a lot of, we do some manufacturing in house. So we do have our own manufacturing department, but it's mostly utilized for a few programs. We do a little bit of outsourcing for manufacturing work, but a lot of the engineers utilize our manufacturing departments in order to fabricate prototypes and things like that because we do a lot of research and development. So we do a lot of SBIR contracts and we do do subcontracting and we use our manufacturing department a lot in order to, you know, proof of concept or feasibility studies on some of our lower phase SBIRs or STTRs. We do a lot of government contracts, but we also do private contracts. So we're kind of all over the board and I think that's really nice because as things add and flow in the industry, as we all know they do, we kind of always have something that we're looking at working on. So I think it also gives a lot of the engineers a wide spectrum of things that they can become experts on or things that they are familiar with and are working on. So if you're kind of bored of something one day, you can work on something else the other day. So I mean, we have contracts right now, we get to work on the dream chaser. We are actually designing the radiators for the dream chaser space vehicle. We're doing the humidity control subsystem for the CST 100. Yep, there she is. And so we have larger contracts like that on top of our, you know, we have our NASA contracts and SBIRs associated. Very nice. So it sounds like you folks are plenty busy, but I have a question for you personally. So what ultimately inspired you to even get into this industry and specifically in life support systems? Life support systems. So I think I've always been infatuated with space since I was a little girl. So I always knew that I wanted to be an engineer and I went and got my mechanical engineering degree. And I started my career in aerospace, actually. So I actually worked on aircrafts before I moved into the space industry. But I had an astronomy professor in my undergraduates program. His name was A. James Mahman. And he's, I think, really one of the people who pushed me into my, I already knew that I love space, but making me think about space as a career option instead of as just something that I enjoyed as a hobby. And while I was working at Rockwell, I heard about the University of North Dakota space program. I was Googling and I was like, what is the best space programs in the world? And it's a program up at the University of North Dakota. And they, it was a help actually Buzz Aldrin helped found it. And they have such an amazing curriculum there. I applied to see if I could do it kind of as an online option while I was working full time as an aerospace engineer. And when I went up for orientation after I had been an online student for a while, I got to see some of the laboratories that they worked in and the things that I could have been a part of if I went there full time and I couldn't say no. So I got the choice essentially of different programs or projects that I wanted to work on. And I just fell in love with life support, specifically bio regenerative physical, chemical, hybrid life support systems. So that's utilizing living organisms, higher plants, algae, bacteria and things of that nature in order to provide life support in extreme environments. So I got to help develop the greenhouse module for the inflatable lunar Martian habitat. It's a NASA funded program at the University of North Dakota. The same habitat that I actually got to do my first analog mission in. So I guess that was kind of my introduction into analog missions as well. And there's something that just makes you want to get up in the morning and go to work. And when I was an aerospace engineer and I worked on aircrafts, it was interesting. Don't get me wrong. But I mean, I would have mornings where I'd hit the alarm button four or five times before I'd get up. Now it's not like that anymore. Now I dream about my job. I think about it in the shower. I think about it all the time. It's a new sense of fulfillment that I am really excited to have in my life. And that is so fascinating because it really does say something when, you know, you can literally spring out of bed. And as you said, feel fulfilled. What aspect of it makes you feel fulfilled? I mean, is it the fact that you're developing things that are going to further humanity's reach in space, which is a huge thing unto itself? But can you kind of dive more into that? Like what what that passion is? Yeah, for sure. I think one of the issues that I've had in a lot of my previous roles internally was that I just I would get I get bored doing the same thing over and over again. So in this specific role, you're not only working on programs that get to keep astronauts alive in space, you're adding to our scientific discovery as a race, you know, as a human race. You get to continually learn and education is just fundamentally part of me. Like I love learning new things. I love bettering my understanding of the things around me and how everything around us is and why and how we can, you know, develop more knowledge about these things. Because I think the more that I learn, the more I realize I don't know anything is about the problem with education and with every answer you get, you get 30 more questions. And then on top of that, to I have such a great crew of people that I work with. So that is also just a major bonus. We have a pretty small group, we're less than 50 people in our company. But the talent that is there is outstanding and the passion for space is absolutely ingrained in every single person that I work with. So it doesn't feel like a chore even when we're like working long hours, because you can just, you can feel the excitement, I think, between me and a lot of the other people that are in our company. And being able to do that. And then on top of that, working so many different programs at the same time and having your hand. And like, we're not providing small bits to the programs.  And that, you know, that pride that goes with knowing that you did something, I remember my very first program was assigned to me. I like looked at myself after taking my job. And I was like, Oh, my God, I don't know if I can do that. I'm going to be fired immediately. This is difficult. And I remember I picked up a bunch of my textbooks, I started learning one of my co workers, Thomas Kenyatta. He really helped me out and kind of pushed me in the direction because it was, it was a highly thermal and fluids problem. And I hadn't, I hadn't done thermal in a very long time since I had been in college. So I had to write this mathematical model and something else I had not ever really done. And the guidance and the, the sense of pride I had when I finished that, and it was a fully functioning model to sit back and be like, Holy mackerel, like, I just made this and this can predict things that are going to happen in space. This is going to influence the way that we design our machinery here so that it functions correctly, both on our test floor down here. And then once it's launched, I mean, that's a feeling that I don't know if I could get, you know, socially or elsewhere. So it's, it's special. And a lot of people in our chat room are, are absolutely enthused of your infectious and enthusiast, enthusiast of your enthusiasm with that. And a lot of them are, I mean, multiple people have asked like, what are your favorite projects that you've worked on in like the entirety of your career so far? Oh, okay. So the program that's nearest and dearest to my heart is a program called Ira. So that's an, a water processor and essentially. So it, it uses a hybrid approach, which I was telling you earlier is kind of my thing. So essentially what happens is on a Martian surface, it doesn't have to be Mars, I suppose it can be any celestial body. I mean, heck, it could be Earth too, it could be anywhere. But let's, let's use Mars as an analog here. So in a habitat, all of the water that is used from the crew would be, is collected. So that's urine, that's, you know, wastewater, that's runoff, that's condensation collection, that's water runoff from your greenhouse, it's a hand washing water, it's a shower or laundry water. And all of this is collected and pumped into something. It's a bioreactor that's been developed by Texas Tech University run by a man named Andrew Jackson and he's our technical partner on this program. And essentially they use microbes to, to treat this, this your, this gray water essentially, and it studies the pH. So at that point in time, we pump that now pH study effluent into a system, which is where I kind of take over me and we have a team of about two or three people. And we have designed essentially a way to reclaim that water. So we use a distillation process and a few other things I'm not sure I'm allowed to talk about in order to regenerate that water into being potable. So we're essentially taking that water that would be discarded and making it drinkable again so that we can close the loop on board. I guess hopefully I want it to work on board microgravity conditions, but right now it's designed for gravity environments. So celestial body. Dare I ask, do you know what the efficiency of that system is? Is that something you can, or is that sort of the quiet things you can't talk about? Yeah, well the efficiency, we're actually in phase two right now. So for anybody who doesn't know how the phases of development work, there's a phase one essentially, and that's more mathematical development, it's proof of concept sort of stuff, more paper studies, maybe small development testing. And then there's a down selection at that point as you move into phase two. And at phase two is kind of fun because you start to get, you get to make your prototypes. So you get to make these full functioning systems. They don't necessarily have to be flight hardware because you're doing ground-based testing on it. And you're doing characterization of your system essentially and you're learning about what your designs are capable of actually producing. So it's moving from that theoretical into that practical or actual testing phase. And we, it's a two-year portion that we're in there. And then from there, there's a final down selection out of phase two. And then phase three is typically the system that goes into like experimental space testing. So we are nearing the last probably quarter of our phase two effort. So we've gotten actually a full functioning system up and running. And we were doing stand-alone testing here for a while. And the fun thing about that is there's specific funding that is available to phase two. So you're not allowed to spend more than a certain amount of money. So the way that you would actually design it in space is slightly different because you're going to take into consideration things like efficiency, especially thermal and electrical efficiency. You're going to take that into account much more in final fabrication in our design. So we kind of take a garage approach for some of those things that aren't necessary for full functionality. So it's hard to say right now exactly what the efficiency of the system would be, but it's pretty impressive the way that it is even though it's not in flight condition yet.  What are some things that in learning and developing life support systems or just anything in what you've developed that really surprised you? Like you were completely not expecting this to become an issue. And that is something that's kind of blew you away that you had to consider that. I think that one of the coolest things in my education was A, learning about how space truly affects the human body. And also just the, I think maybe the thing that I find most interesting is hypoxia, actually, if we're going to be honest, and that would be the body's reaction to having a lack of oxygen. And they've done a ton of testing on this and it's super interesting. I mean, it's something that even after I've finished my education on and I've learned about it's something I still like to do some research on on my own because I just find it so incredibly curious. So hypoxia is something that a lot of high altitude pilots also face. But essentially the pressure inside of your cabin typically stays the same. So you don't feel a difference in physical pressure, but the partial pressure of oxygen, meaning the amount of oxygen in that same volume is less. So you could have maybe more nitrogen or more something else. But it's not something that your body is actually utilizing, right? Because nitrogen is kind of a dead gas to us. So as that partial pressure of oxygen decreases, and you're breathing in and consuming less oxygen, your body starts to do some pretty amazing and crazy things. So there are a couple of, there are a couple of chambers throughout the United States in which some of the military pilots are trained for high altitude considerations. And a lot of astronauts are also trained to recognize their own signs of hypoxia because they're very different for each person. But essentially they've had a lot of demonstrations in which you'll have an astronaut or a pilot sitting there and they'll have their mask off. And you can't really recognize yourself when you're beginning to become hypoxic. And one of the major side effects of hypoxia is actually euphoria. So it's something that most people, once they begin experiencing hypoxia, which is a lack of oxygen to your brain and your brain sort of starts functioning. In fact, I was lucky enough to be able to do some of the hypoxia training myself when I was up at the University of North Dakota. And a lot of very interesting things happen. You become, you're very sure of yourself throughout the entire process of oxygen depletion essentially.  And you're like, well, it's eight, you know? But as time goes on, they're still asking you these easy questions and you're still sure of yourself, but you're actually incorrect. So it's like, what's four plus three? And you're like, eight.  And you're like, it's eight. And you know it, you know for certain that you are correct and that the answer is eight. And they'll have you write your name on these lines as time goes on. And you can look at the papers afterwards as it just becomes essentially nothing. They have you put these blocks that are just shapes into matching shapes, you know, like the kids toys, or you have to put the star and the star and the triangle and the triangle and such of that becomes increasingly difficult. And maybe the most impressive thing I think is you start losing your ability to see color, but you don't recognize that you're not seeing color. So they actually have you look at a sheet when they return oxygen to your body and all of a sudden the entire world becomes bright. And you have never realized that it had gone dark in the first place. And it's kind of a scary thing because they've done a lot of this testing with pilots and they'll yell at pilots and they'll say, your entire crew is going to die if you don't put your mask back on right now. And such a tiny percentage, almost zero percent of the pilots actually return the mask to their own face. They have to have somebody in their all times to put it on because the euphoria is so great that they choose not to. Wow. Yeah, I was about to say, you know, going up mountains frequently, which you have a lot of experience with. Yeah, people at altitude become belligerent. Do you? No. Because you can, you actually can, at least when you're going up mountains, it's not as drastic as you can in an altitude chamber with that. So you can kind of, you can kind of teach yourself to remove some of that from yourself. But yeah, things like that really do happen. You get euphoric and you sort of get like, I know when I get above 10,000 feet, I kind of get this tunnel vision kind of thing going. Yeah. And then also really too, altitude sickness, or altitude affects everybody differently. Some people will become, some people will be incredibly fit, but completely crippled by altitude sickness. And then there'll be people who are like, not fit at all. This is like their first time going up at altitude and they're like, please and past everybody super fast. Some people get headaches. Some people start doing other body processes. I will not throw on everybody. But yeah, it's just, I gotta agree, hypoxia is amazing if for all the wrong reasons. Yeah, I was gonna say. So essentially, at first I was going to compare hypoxia to having one too many drinks, because that whole just overly confident four plus three is eight thing, like we've all been there. But then when you started getting into the more like, the more abstract, like you can't see colors and all of this, it's like, okay, this is beyond just a few drinks. This is like brain chemistry messing around stuff. Yeah, well actually drinking alcohol starts a process that's very similar to hypoxia.  So next time you're walking down the street and somebody tries to ask you what's wrong, you can tell them you're hypoxic.  They're gonna be like, do you need me? Yeah, I'm not sure. I'm gonna hypoxic. Yeah, exactly. So is that contagious? Yeah, if you want to double whammy, drink alcohol at altitude. Wow. Which I don't recommend. I don't think that's a great idea. Nobody is recommending that. Nobody is recommending that. Don't do it. It's terrible. So I guess, and I've seen a couple of questions in the chat that are related to this, but a question I have is, so you have these suits and these systems that are to accommodate for and kind of diminish the crazy environment of space, but how do you go about testing these suits?  For sure. So actually, I don't know if you guys know this, but in 2014, Paragon broke a world record by sending Alan Eustatius to about 100, just shy of 136,000 feet, where he successfully completed the highest space dive on record. So essentially a gondola balloon inflates as it goes up into the atmosphere and took Alan with him. And then he releases himself from that and fell back to earth essentially in a super high altitude space jump. So Paragon was the company who got to design his suit. And actually, we designed basically every component of that other than I think the balloon itself. And we actually got a system in house, it's called the EHF, and it's a chamber, it's a vacuum chamber essentially that is human rated. So you can put, we've tested several spacesuits actually also inside of this, and we can control everything between the makeup of gases in there, we can pull a vacuum, we can incorporate condensation or humidity. So we get to change the environment however we want to, and we can put any kind of sensors that we want into the system. And we just make sure that it's at a place that is safe to maintain life before we ever try anything with a human. Yeah, awesome. So I gotta say jumping from 136,000 feet sounds awesome. I'm down. Of course you are. Let's do it. I'd sign up. Okay, yeah. All right. So this perfectly goes into my next question, which was actually asked by Graham from YouTube. They asked, would you consider going to space if the opportunity arises? And I think this is a very unique question for you specifically, since you have firsthand experience working with the system that is ultimately going to keep you alive.  I would actually. And this answer I think has changed for me throughout time. And if what I go to space, certainly, would I take a trip that had a one-way ticket to Mars, for example, to never come back? I don't think so. As much as I love space, I also love the comforts of, I don't know, I like trees and birds and going for hikes and breathing in as much oxygen as I want to. So eventually I would like a return ticket. But if the opportunity came up where I was offered a trip to Mars or anywhere else in the solar system, and I had a paragon life support systems on board, I would be very confident in taking that trip. And yeah, I'm excited. So if there's anybody out there that wants to fund my trip to Mars, let me know.  I'm on board. And that's like the ultimate endorsement. I have so much trust in these suits that I would use them and go up in space in them. So nice. All right, Brittany, I believe you. So I just want to kind of get a question from Rebel in our IRC chat room. Because you talked about Paragon making the pressure suit for Alan to do his super high skydive. And Rebel is asking, how long does it take to create a suit from development to usage? And will this increase in speed and lower costs much with the commercial and tourist future? Plus, you know, a lot of sizes and use cases because obviously, you know, a couple of weeks ago, still kind of trailing with that space suit issues on the space station. So kind of how long does it take and what's that looking like? I think that this space, I mean, the StratX program went pretty fast. It only took a couple of years. But I think to develop a line of spacesuits that was applicable for, you know, to accommodate all different types of astronauts, which of course anybody would want to do, it would take a great deal of time longer than that. I know that they've been working on, I think the NDX series of spacesuits up at the University of North Dakota under Pablo de Leon for quite a few years. And that's a testament to he is such a hard worker and intelligent such a good team around him also. But it takes a lot of time to make sure these things are right. And in my opinion, it's something that you need to take the time to do because, you know, a public opinion plays into how much funding we get in our industry quite a bit. And they don't take well to you making a mistake once or twice. It's one of those industries where you succeed or, you know, the first time around or you're out. When you're when you have people's lives in your hands, it's not really something that you get to rush. It's not something that you get to take corners on. And of course, you want to develop things as quickly as you can. But you also have to make sure that you're you're stopping and taking the time to check every single thing that needs to be checked. And you have somebody that you trust looking over your shoulder. And you're going through the correct phases of develop development with the correct people to make sure that these things are done in an appropriate manner because because it matters. And so time wise, I think it would depend. And I don't know if you guys know this, but the development of spaces, it's not like you get to design one spacesuit that is applicable for all applications. A lunar spacesuit is extremely different than a Martian spacesuit, which is extremely different from an intervehicle spacesuit, which is extremely different from a microgravity EVA suit. And a lot of that has to do with, yes, the environments and the pressurization of those environments. But also something I think a lot of people don't know is that the regolith on these different celestial bodies are incredibly different. So here we're used to our sand being very rounded because we have all of these natural processes, and we have this pressure that's on us. And we have the we have our natural modes of essentially a rubbing down created by the pressures both under sea and the pressures that are put upon us by by our just, you know, just the atmosphere essentially. So these processes are lessened once you're on Mars. And then even further lessened when you're in somewhere like the lunar surface. So the lunar surface actually has regolith that is not rounded down at all. They're very sharp. If you look at it under a microscope, and we've gotten a lot of regolith back from some of our earlier missions, you can see that it's essentially little daggers. So we had some issues in the first line of development of our spacesuits that actually went up to the moon because we were getting micro abrasions and tears in our spacesuits from conditions that we weren't quite ready for. So it's not like you can make just a one suit fits all or a one suit goes on any mission sort of deal. So you kind of have to end up with, you know, a lot of things are specifically developed suits for the conditions that you're you're trying to, you know, use them in. Well, yeah. And it's quite a multitude of those two. And to kind of go with that, Karth Naran from our YouTube chat is asking, how effective is it to create a spacesuit from carbon fiber from multi planetary environments? I guess kind of what are like, what are the materials that you have to use in order to make a space suit? Oh, man, I'm not really that familiar with it. Most of my programs are in the life support systems for spacecraft applications and for habitation. But I don't know if I've ever seen a space suit made from carbon fiber. I would think that, you know, we have a lot of issues, essentially, you're always pressurizing and depressurizing spacesuits. I think that carbon fibers, especially maybe a bit, you know, they're not very flexible. I think that will cause a lot of issues in the fabrication of a space suit. So durability, I think, is one of the things that we care a lot about. Like you do have a lot of things that will rub up in high lifetime cycles, essentially, that'll be used for a space suit. So you're looking for durability. You're also looking for like breathability, right? We have lots of different layers. It's not like one material makes up a space suit. It's not like our clothes where we just weave one thing together. There are different layers of a space suit that perform different functions for the environments that we're planning to work on. And so I think that question would be better suited to specific layers of a space suit, rather than just the material of a space suit. A space suit is made of lots of materials. I would hope so. I would hope it's not just like something that you can slap together and go to space. And it's like, I can't imagine how immensely complex it is and for good reason. And there's a really great question from Destructor 1701 from YouTube. And this is kind of a look into the future. And they ask, does Paragon have a strategy in mind for serving the potential space boom over the next decade? I'm thinking end user space suits, plug and play, life support for HABS, et cetera. Yeah, definitely. So I think that we actually have a system that we've already designed that is super cool down in kind of like our museum. And essentially, we have already developed a kind of plug and play life support system, essentially. It houses a TCCA, a trace contaminant control assembly, which is responsible for taking out any particles that are in the environment. If there were to ever be a fire, it's a fire particle mitigation system. It works to pull humidity out of the cabin air. It does carbon dioxide scrubbing, so sort of like your air revitalization. It has all of these components that are necessary, essentially, to maintain the cabin environment. And we originally designed it to be usable for seven crew. And it's not a very big unit. So they have these little dials, too, where you can essentially dial in and out the function of each of these individual components of the life support system to hone in on how many crew members you have. So if you only have four, you can kind of move the dial before, right? I mean, there's not a dial that says four, but that's essentially the idea. And we have this entire unit that is capable of adapting to different crew sizes instead of continually redesigning the life support system every time that the mission plan changes. And you have a different number of crew that is planned to go on these, especially for long-term, long-duration space flights. And I think that we're actually a little bit ahead of our industry. I think that one day this is going to be something that is insanely useful. And we're just kind of waiting for the rest of the industry to catch up. Wow. So you're talking about like a modular life support system for a hab? Yes, I am. That is so cool. And actually, to kind of go into that a little bit, Blackbox Camera Calm on YouTube is asking, what is the longest duration that a spacecraft life support system is able to operate for without resupply? And I kind of want to throw a little bit on there too. Because if you go to Mars and you do a mission that returns, that's at best case, shortest duration three years. So that means your life support system has to work effectively for three years continuously, minimum. What are the challenges of developing a system like that? What are the huge problems? What are those hurdles? Oh my gosh, there are many. But I guess I'll start on my kind of bioregenerative spiel here, because that's very near and dear to my heart. But currently we have three different approaches for maintaining essentially life support for these missions.  Like you mentioned, we're constantly sending goods out. And then we have a bioregenerative approach. And that is the approach that I care about that is like nearest and dearest to my heart. And that is essentially using, like I said before, living organisms to provide a portion of your life support. Because I mean, we have microbes or bacteria or higher plants, this thing right here, am I pointing there? They're my plant. Naturally, it's a natural CO2 scrubber. It takes CO2 out of the environment and it pumps oxygen in. That's exactly what half of our physical chemical systems do, which is the third approach by the way is physical chemical. It's essentially using filters, chemicals, mechanical processes to provide life support. And it's a very interesting thing because bioregenerative approaches also have the ability to provide us nutrients. They clean water. We can pour dirty water essentially in the base of plants and we can transpire clean water out of the leaves of the plants and then condense that later and collect it. This plant is doing three or four of the jobs that I've been working for a very long time trying to design in a mechanical sense. So there's an interesting dichotomy I would say that exists because a lot of engineers don't really appreciate the science behind biology because the stability of it is concerning. It's hard to predict and engineers like to be able to predict everything that's going to happen. And then you have these systems that are plausibly autonomous. Once you get them started, they could last for a long time, hundreds of years. I would suspect if you had the right approaches to it, down side of that being the nutrient cycle, which we're still looking into, but it is long periods of time. And the difference here is way back when we were starting essentially this space race, we had these ideas. NASA was doing research on algae and higher plants in order to pursue a bioregenitive approach to life support. But when you're just going to the moon and back or when you're just going to Leo, that's not necessary. You can get there so quickly and back that it almost makes sense to perform resupply as your approach. But as you're moving further and further out into our solar system for extended times, when you're moving into long duration spaceflight, you can't have rendezvous missions that are expected to hurry up and get there and resupply these things. So now you get to a place where you're really in need of autonomous systems and bioregenitive is really peaking its head. And the engineers are correct in seeing that we do have some issues in stability. I mean, we don't exactly understand what could happen in radiation conditions that change the makeup of certain microbes that are in the soils or are internally to plants and how that might change things. What if we have one certain thing that wipes out a bunch of our plants? We have ways of companion planting and doing things that ensure that that is much less likely. I think that the real approach for future duration is a hybrid approach. So it's pairing bioregenitive approaches with physical chemical approaches. So it's kind of a buddy system. And we have progressed down the physical chemical road because of, you know, NASA's push during the space race essentially, we knew so much more about chemical systems by the time we were kind of in that race to the moon that it both made sense logistically and, you know, and in a sense of research and what we had still to learn. So how long can we support people if we take bioregenitive physical chemical approaches? A long time. Way longer than three years. That's good to know. So as we wind down before we say goodbye, I really want to address the elephant in the room, which takes form as a hole in the wall. And a lot of folks in our chat, including Jared and I are really concerned because I don't know if you know this, but right behind you, there is a hole in the wall that basically is exposing you to the vacuum of space. And we're really worried because you seem to be fine. Don't look now. Oh, just kidding. And so can you just please explain, explain that because we're all quite worried that you just have the vacuum of space like right there and you're still lovely and healthy, but you know, it's, it's, it's a paradigm, you know, I don't know what's going on. I'm really into space decor. And I'm also really into Doctor Who. So this kind of reminded me of kind of like the crack in the universe. Yes, the timelords are trying to bust through my wall. So I just like to surround my things, self and things that make me happy. And this is one of them. Nice. Well, it's spectacular. And it really does serve as kind of like the perfect backdrop for this entire interview. So I think anywhere in my house would Oh, nice. Well, Brittany, thank you so much for talking with us today. We're really excited to see the evolution of life support systems because that is basically what is going to enable humankind to progress further and further into space. So thank you for the work that you do. And thank you for inspiring so many others, whether you know it or not. So if our viewers would like to learn more, where can we send them? You can check out, I think Paragon has a Twitter account at Paragon SDC. We'd love to answer any of your questions. Also, you can find me either on Facebook or on Instagram. And I would love to talk space. I can talk space all day long. If you have any questions, Brittany Zimmerman on both of them on Instagram, I'm at astronaut.brittany.c Wonderful. Well, thanks again. Thank you for joining us. And we hope you have a wonderful weekend. But before we say goodbye, we would like to give a very thoughtful acknowledgement to our citizens of tomorrow. These folks, all of them, they all essentially help make this show happen and give us meaning and purpose. As you can see, there are several names up there as we go on through the different echelons. All of these folks contribute a certain amount of money per month. And if you would like to become one, you can head on over to patreon.com slash tmro. Look at that beautiful, beautiful wall of text. Actually, my name's on there now. I am now a supporter of my own dreams. And also, you don't have to financially support us as well. You can head over to community.tmro.tv and actually help us out in whatever ways that you can. Can you code? Can you do really cool graphic designs? Can you subscribe to us? Can you like us? Can you ring the bell? Can you put it on your Facebook or whatever you got? So just share it around and show us, show us to everybody that you please. And if you can't make it rain monetarily, make it rain emotionally. Share us with your friends and family. Get the word out about space. Just be you. And on that note, thank you so much for joining us. This was Tomorrow Space Orbit 12.13. And we will see you folks next week. Good.


What a great show, isn't it? I just love Slush, so I'm really pleased to be here. Nearly 20 years ago, I co-founded my first startup based in the UK and Belgium. We grew our team to 75 people, and we built chips and software for broadband to the home. I must admit, we worked like dogs, but we loved it as well. In my first year, I did 26 trips from Europe to the US, where our first customers were found. We made the company globally significant, and we sold the company to Broadcom for a total of $640 million, having raised only $13 million of venture capital. So, not surprisingly, I wanted to repeat it, and co-founded a second company which I led this time in the UK and France, and we grew that company to over 300 people, and that company focused on building cellular modem chips. So, that company was bought by NVIDIA for $430 million. Over a billion dollars in just two companies proves beyond doubt that Europe has got the awesome talent pool needed to build really important companies, and we can actually build some good companies, and we can make some good money for investors in doing so. But the question I'd like to ask is, were they great? And actually, is that what we should be doing? Building companies to feed US tech titans? Or should we be doing something different? So, just hold that thought for just a minute. So, you can't tell by my accent, but actually, I was born in Scotland in a small mill town, and nobody in my family owned a car, so we walked everywhere. Later, we moved to a city in England, and it was so big, we couldn't walk everywhere, so we used the bus. But I remember the day my dad got his first car, and his really cool wheels looked like this. If you recognise that, that looks like the Harry Potter car, it's because it is. Suddenly, our world opened up, and we found that we could go everywhere, the roads were empty. It was cheap, and we just had this amazing ability to travel across the city. But bit by bit, that dream has disappeared, and with the densities that we now live in, that's not going to return any time soon. In fact, our European cities were really designed around the horse, not the car. And in a city like London, we're going to add a million more people in the next 12 years. And what that means is that we're spending the world's resources building cars and vans and trucks, and then we're polluting the environment, and then we're reducing the quality of life in our cities. Later in old age, my dad had to give up his car, and my mother never drove, and the net result was that they found it very difficult to get around. And it's not just the old that find it difficult to get around, it's also the young, and it's also the less able, and even people that just happen not to live in the right part of town find it very, very difficult to get around our cities. But it's not just the socially excluded we should worry about. If I were to give you an extra 230 hours a year, what would you do with it? Well, I suppose you wouldn't spend it slumped behind a wheel in a car driving to work. But in fact, that is what over two thirds of European workers do every single day on their commute to the office.  We need a new paradigm. You see, I believe in a future where everyone can travel across our cities without having to drive, and without any delay, and I believe we should do that at the lowest cost to our planet. It's why we founded 5AI, and it drives everything we do in the company. So what does that mean? How do we achieve that? Well, it means we build a transport capability that really is suitable for everyone, young, old, able, not able, rich, poor. We build a capability that delivers that using shared electric vehicles across our cities. We have to make this autonomous because we need to reduce the strain and frustration of driving in our cities, and of course the cost of doing that, and we've got to be able to operate in really quite complicated, difficult environments. And so what we're doing is we're building autonomous shared personal EV mobility for urban environments. So that's the how in terms of how we're doing it. So self-driving leadership is really in the hands of technology companies and predominantly American technology companies. But we're determined to do this here in Europe, and that's because we Europeans have a very different perspective to American and Chinese companies. We know that any solution has to be fully inclusive. We also know that it has to link to public transport. It has to meet the city's objectives. And we know that our cities differ from one another. I mean not just in the topologies and objects and densities and markings and lighting and signage, but in the human behaviors. We know that Helsinki is very different to say Naples. But there's another reason, and it's because it's time. It is time for Europe to build a truly great deep technology company, and that means building a company that goes from deep technology all the way through to the consumer. It's a full-stack solution. And that company's got to be confident enough to learn from that American example. It's also got to be confident enough to drive custom acquisition and confident enough to attract the capital and to attract the talent to do that. And that company is 5AI. That is what we're doing and everything we do flows from that. So having thought that's what we're going to do, one of the key challenges is the channel to market. How are we going to build this technology and get this technology to market? Last year we heard Steve Yervitsen, who's here this year actually. We saw Steve Yervitsen talk about Zooks. And Zooks' idea was that they're going to build a car, and their route to the consumer is build a technology and put it in a car, sell to consumers. Well, we're not going to do that. Instead, what we're going to do is we're going to build an integrated technology and operational layers into an autonomous consumer service. That is the most direct route to the customer, and that will allow us then to iterate our solution to meet the safety and functionality requirements of the future. Solving the perception, prediction, simulation and validation challenges that we see in this problem really represents the holy grail of autonomous driving. And actually, nobody in the world can do this today. Uber can't do it, Waymo can't do it.  Europe's secret for doing this is very much its talent, and that talent centers around our universities. And those universities, we're able to recruit staff from, provided we got the capital and we got the will to do it. In 5AI, we've raised our first $30 million of capital, and since we started our recruitment at the beginning of last year, we've seen 3,000 people apply to the company, 61 people have joined our team already, and we're working on all the key sciences that are needed. The visual geometry, the Bayesian inference, the deep neural networks, the reinforcement learning, the behavioral typing, the game theoretics and the control systems needed to build a safe vehicle. And our team is awesome, and I'm going to show you a quick video of some of our people talking about their work. At 5AI, I'm involved in developing such computers that can understand their environment as good as humans do. This is critical in making vehicles drive safely around us without any human intervention. Figuring out how we can apply this academic knowledge to address real world problems, that's what makes 5AI such an interesting company. And 5AI has the resources, and more importantly the attitude that says, you know, let's solve this, whatever it takes. Here at 5AI, we employ the best computer scientists, mathematicians and physicists in the world. We give them the resources they need to address these challenges and we wrap their research in engineering expertise and rigor so that what we deliver will be a safe, reliable and world-changing solution. Within the next few weeks, we're going to have five vehicles on the streets of London. In second quarter, those vehicles will be self-driving on public roads. And over the next two years, we're going to add increasing amounts of functionality to the point where our vehicles can drive safely in our dense urban cities, dealing with all the challenges that that requires. That is phase one of our plan to get to that point. Phase two is about building the consumer service offer on top, solving the relationships with OEMs, the regulation, the service layers and so on. And phase three is about achieving our goal as a company. That goal is our future, a future we can all participate in, a city that functions, human potential that is realized, a world where we do not squander our resources, a world that we're proud to hand to our kids and to their kids. We believe in that dream. We believe in 5AI.