Podcasts about lgpl

First up in the news: Linux Mint 22.1 “Xia” released, Parallels can finally run x86 versions of Linux on Apple Silicon, German router maker is latest company to inadvertently clarify the LGPL license, Google and Linux Foundation form Chromium love club In security and privacy: Microsoft patches Windows to eliminate Secure Boot bypass threat, Then in our Wanderings: Joe enjoys prepares his rack , Dale does routing , and Eric shares 80s kid culture with his kid.

This week we talk browsers, with coverage of the Servo updates and the new Supporters of Chromium group in the Linux Foundation. The Raspberry Pi has a 16Gb model of the Pi 5, and not everyone is happy about it. KDE Plasma 6.3 has a public beta, Flatpack has released version 1.16, and Mint is on the cusp of releasing version 22.1. For tips we have kshift for quick or automated KDE re-theming, php -S for local php site testing, a quick tar howto, and pipewire-pulse for more pipewire and oulse audio fun. You can find the show notes at https://bit.ly/3BUzLqV Enjoy! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Ken McDonald, and Jeff Massie Want access to the video version and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Insbesondere in den letzten Jahren waren sie in aller Munde: Open Source-Lizenzen. Doch welche gibt es und worin unterscheiden sie sich? Welche sind kompatibel zueinander? Welche Implikationen haben sie auf Forks? Diesen Fragen gehen wir zusammen mit Jurist Udo Meisen auf den Grund.

Pablos: So what happens right now in scientific research is, if you're going to do a research study on something, like "are M&Ms is bad for you?" It's impossible to do that study. You have to be very specific and ask a much more fine grained questions like " how many M&Ms does it take to, Kill a mouse?" or to cause a mouse to vomit. You just have to be very specific cause that's something testable. You could test that, you can get multiple mice, you can feed them enough M&M's that they eventually vomit. The whole research study can be done that way. And so when you read scientific research studies, that's typically what you're looking at is some very narrowly defined thing that they believe is correlated to a much more significant or bigger effect, but you can't test the whole thing. You can't ask questions like, "does this thing cause cancer?" You can ask questions like, " does this amount of exposure to this thing over this much time cause this specific, type of cancer in this type of rat?" Things like that. So that's great and all because it means, we're structuring, tests that we can actually perform, but the downside is that for most people, what they would actually like to know is " do M&Ms cause cancer or how many of them is too much, things like that. Getting those answers is often not straightforward from scientific literature. And so the way that we. usually try to compensate for that is to do what's called a meta analysis. And a meta analysis is where somebody will go and dig up all of the studies on a given topic, combine them and try to say, "across a hundred studies involving M&Ms and cancer, this is kind of what happened" and, to just sort of give you a general sense of whether or not, the effect you're interested in is happening. Good examples of this are like, chiropraction is largely, debunked. A lot of people get pissed off at me talking about it because it can be a deluxe placebo, but in clinical trials, very few clinical trials are performed. It's hard to do them. Different practitioners have, different effectivity levels anyway. And so the problem is it's hard to run those studies, but even if you do, you can't find any indication that chiropraction actually cures anything. So this is a case where we don't have good research and the only way to try and get to the bottom of it is with a meta analysis where you find the studies that have been done and you sort of combine their results and try to say whether or not chiropraction works. People, there's no point arguing with me if you're listening and you think chiropractic is great. Go nuts. I encourage you not to do that, but, whatever, do your own thing. But the point is the only way you could get a reasonable answer is with this kind of meta analysis. Now meta analysis is very time consuming and difficult to perform and often isn't getting done, but what it really involves is just go read a bunch of studies. Well, it turns out that's what an LLM is really fucking good at. So you, so right now we're in a stunted position because one of the big problems with OpenAI and ChatGPT is they've crippled ChatGPT. It doesn't read scientific literature and even if it does, it's not really allowed to comment on it. So they've crippled the thing to keep you from talking to it about anything that might be health related and stuff like that. What you would really want an LLM to do, and one of the things that would be really good at is doing ad hoc meta analysis. So you could just say, "Hey, I feel like I'm getting a cold, should I take zinc?" There's people marketing zinc for that purpose. We've all been told to take zinc, but I don't fucking know if that's an old wives tale, Ash: It's like echinacea, zinc, doesn't matter, it's all those things. Pablos: I don't have time to go read every scientific research study, but I bet you collectively we have that answer, and so if I could just ask an LLM. Ash: Wasn't wasn't IBM's Watson at some point pretty good? Watson Health actually had all this. Pablos: That's probably what they were trying to do. Ash: They were doing it and they were doing pretty well. They weren't they weren't using a full LLM model. That's that was the whole breakthrough. Pablos: They were kind of in the pre LLM days. It was LM. It was just LM. It wasn't LLM. Ash: Just language models. And they were taking huge amounts of data. But what they had is they had their own normalized structures underneath. So that was the difference, right? They didn't let the structure form itself. But what you're saying is true. Pablos: You're right, and we could probably build like a Watson for health in a weekend now using, Stable Diffusion or something. It would be way better. You would just basically load it up with all the research and let it go nuts and then let people ask questions like, " Hey, should I be taking zinc?" Ash: The problem is reliability score. Pablos: Oh no, it'd be terrible, but it's already horrific. Right now, we're just going off superstition. I mean, literally that question of, should I take zinc? You're gonna get as many answers as people you ask because somebody's Chinese grandmother said You should be, taking echinacea instead. Ash: You should listen to my first class. The first part we were talking about is what is known as "triangulation of information truth." What is provenance for data. Then you have to figure out, how do you weigh it? LLMs are fantastic, like you said, because they can take all your source inputs. So if you go back to, to signal analysis, or analytics for like intelligence again. We'll just lean on that for a moment. Truth is great if you're playing with mathematics. You get QED and you call it a day for the most part. But for other things, truth, zinc, for example, like your zinc example. There's some balance between like how much did it really? Was it an emotional support protocol? Did it help you because you were convinced that, your grandmother was right or whatever's happening to, to actual physical actions internally, right? We can be scientific about it, but it comes back to source and information. If you pick a really, really dangerous topic and we won't go there, but let's just pick Gaza for one second. How do you find what's really happening? Well, you hear a lot and someone's like, "well, I read it in the Wall Street Journal." I read it here. I heard it there. I took Al Jazeera. I did Briebert. Whatever you picked. The question was, did you do it in all the languages? Did you listen to a local radio station? Did you find someone's signal data from nearby? What was happening? Did the bomb go off or did this happen? If you look at information, just like you're looking at these scientific papers, the question becomes the weighting factor. We as humans, I think one of the things we know how to maybe do, at least a good analyst should be able to do, is try to give weighting based on time and location and stuff. And I think the large language models have to start to put in context again. I think they have to add one more dimension. Pablos: For sure. And I think that you touched on the other thing, which is that right now, all this information is like floating around without, tracking provenance, and so, interestingly, like in scientific research, you at least have citations. which is a lightweight form of provenance. It's a start, but ultimately, the way these things all need to be built, not only , the LLMs for doing meta analysis, but really every knowledge graph needs to be built off of assertions that are tracked. You keep track of provenance, okay the sky is blue, well, who said the sky is blue? Where did you get that from? And that way, whenever you're ingesting some knowledge, it's coming with a track record. That's how we're going to solve news online, eventually. Ash: Kind of like, the Google Scholar score or whatever. I go back to my partner, to Palle, right? So Palé actually has a patent. It's probably expiring soon, so for those of you who want to do this, we should go do it. He owns webprovenance.com. And he owns the patent on how you check provenance. One of the things that came out of the BlackDuck software stuff was that at BlackDuck, we needed to know who created something. So do you remember the Sun Microsystems, IBM, lawsuit, Java? If you're a compiler theorist, then you know that, just because West Side Story takes place in New York, You could probably say, well, doesn't it sound exactly like, Romeo and Juliet? So maybe you change the variables, but it's the same stuff. And the idea was that when we were looking at, open source, with open source, the interesting thing is you're trying to figure out, where did this little rogue piece of code, this little GPL or LGPL infection come from? You need to find it. So it's one thing to talk about the combinatorials, but the other was to find it. And then Palle was like, well, I can do something cooler., He said, if Brewster Kahle's Way Back Machine, remember the original Alexa project? So If you could go in and take all that data, he's like, I could pretty much tell you like who killed JFK. You can find the provenance of almost any information. He wrote this wild algorithm for it. I'd love to see some of that incorporated into the LLM stuff because that algorithm, and again, we would happily, anyone out there if you're willing, this has been a project we've been looking at for the better part of 15 years. Pablos: Well Stability might pick it up. They love that kind of stuff, that would be a huge coup for them. Ash: Well, we should, we should have this conversation offline, but it's a, it's interesting. It's an incredibly cool algorithm. He was a compiler theorist anyway, an algorithmist, at Thinking Machines. So, he always wondered where the info came from. And I sat there and said, hey, we should find a way. And I remember the stunt I wanted was like, to figure out if they were aliens. And he's like, what do you mean? It's like, well, who started that rumor? Like, where did it happen? Right? So, imagine you could take any rumor, and I can tell you how it started. Pablos: That's so cool. Ash: Wouldn't that be the coolest thing ever? Pablos: So important. Ash: Yeah, and we need that. Pablos: That is super important. I've seen somewhere, a map that somebody made of where are all the UFO sightings reported? And like 98 percent of them are in the United States. I think the rest of the world doesn't even have UFO as like a notion. it's not even a, thing for them. Ash: It's cause we have no healthcare. Look, all I know is, years ago, we just didn't have enough data. Years ago, we couldn't. We were like, looking at the Wayback Machine, and we were like, I was like, well, who can we go to to get all the data? Can we get the entire web? Today, large language models have already stolen all the data. They already have it. So if you have enough of the data, we could definitely help you figure out the algorithm to go backwards and it's complicated. Pablos: That's super exciting. Ash: He actually patented it himself because he was trying to figure out if he didn't need a patent attorney. So that was his project, can I make a patent? And his patents on provenance. So I think it's a big coup if they could pull it off. Can you imagine you could just type in who started, where did this first start? Pablos: Dude, that's crazy cool. Ash: It's super cool. Pablos: I'm kind of always on a rant about this, but we need a variety of models. Like LLM is the beginning, not It's a thing that you need, like the way we're doing it now actually kind of sucks and requires a lot of brute force, but there's so many things that it's not good for. Ash: And it's so susceptible to the thing that, what did I do in my life? Psych warfare is all about information corruption. Dude, you corrupt a large language model, that thing is convinced that the sky is red at that point. Pablos: Exactly, well, I've been thinking about that. Why don't I just.. Ash: Corrupt it?. We're bad hackers. Pablos: I can fire up, 100,000, blogs written by an LLM that all just talk about my, prowess with the ladies. Ash: Exactly. Pablos: And the next thing you know, all the future LLMs will be trained on a massive amount of data that indicates that, Pablos is the man. Why wouldn't we do that? Ash: At the end of the day, the LLMs are basically superstition. There you go. I've just said it. Pablos: Right. They're superstition. There you go. Ash: LLMs are superstition. They're based on some concept of something that it derived because it took a whole lot of information from a lot of grandmothers. Pablos: And that's the thing, Like what's posted on the internet is all that they know. It's driving me crazy. Ash: Worse, it's only the people who have given them permission, so the quality sources are going to start cutting them off. So, all they've got, all you've got are the people who are generating rumors that they've seen UFOs. Pablos: Well, that's all true for the LLMs made in America. Ash: Yeah, so the American LLMs know where the UFOs are. Pablos: Japan decided that copyright doesn't apply to training LLMs. So the most powerful LLMs, for now, are gonna be in Japan. Sign me up. Ash: Even better, that means Japanese information... Pablos: That's probably true, learn Japanese. Ash: Which, think of it, if I wanted to build, my 100,000 LLMs generating your prowess, I'm gonna do it all in Japanese. I'll do kanji, hiragana, and katakana. I'll give it to them in all three formats. You could crush it. I I would love to see any of these. I think that's, that should be our ask for everyone. Pablos: Yeah. Ash: if someone, someone wants to run with it, go build it. Pablos: Yeah, people, build this shit. Ash: Tell us. We can help you commercialize. We will find you.

Pablos: There's this idea that was just published that you could produce concrete and make it stronger by adding charred coffee grounds to the mix. And this is some research out of Australia. So concrete, if it's not obvious, is like the most used material on the entire planet, aside from oil, which we burn. Cement, is in everything, and it's this like staggering scale problem. Partly because of its contribution to greenhouse gases, right? So when you make cement, you're burning some shit to make a bunch of heat to make the cement and you need that heat and there are ideas to decarbonize cement by electrifying cement plants. But then there's this chemical process going on, which is the bulk of the carbon emissions. And there's just no way to get rid of that. So that's kind of the lay of the land. Interestingly, about half of all the cement in the entire world is made in China. That country is basically made of cement. This is one of the major targets for trying to do reductions of carbon emissions. And these guys figured out how to use coffee grounds. It's not totally clear to me that they're using, uh, used coffee grounds, I presume that's the case, because there's 10 billion Kilograms of used coffee waste every year that mostly ends up as biomass rotting in landfills. So this is worth solving. I thought this was kind of interesting. You can't just take the coffee and throw it in the cement because the oils and stuff in it will seep out and actually make the cement fall apart. They invented this pyrolyzing process where you basically heat up the coffee grounds to a specific, pretty high target temperature, around 500 C, I guess. That'll get rid of the oils presumably, and makes it into an additive you can just throw into the cement mix and it makes it 30 percent stronger. So I got two things that are kind of interesting, related to this. We Have a company our fund backed called DMAT, and these guys figured out how to make cement that's lower carbon, but the way they do it, is they solved this 2000 year old mystery in material science, which is, how did the Romans make cement? Ash: I was going to bring that up. Pablos: Yeah. Cause they made the, the Pantheon to like two millennia ago and it's still there. It's unreinforced concrete in a seismic zone. And then they, somehow got busy, watching Netflix or something and got bored and forgot all about how to make cement. And then nobody's been able to figure it out ever since. Ash: They were just looking at the colosseum. They were like, Hey, I'd rather look at the lion. Maximus Aurelius or whomever. And then that's it. They're like, forget it. Pablos: Look at the cool lion. Oh shit. The lion ate the guy who knows how to make the cement. Ash: Literally probably what happened. Pablos: That is literally probably what happened. So anyway, I got this team at MIT that figured it out. Ash: It was self healing, right? Pablos: We figured that out a little while ago. It's self healing because what happens with cement is it fractures, water seeps into the cracks and then destroys the cement from the inside out. And that's what's happening to our bridges and everything else we made. And so to make it stronger and handle that, we load it up with steel rebar. So it's steel reinforced, and then it still only lasts 50 years. The Roman cements, apparently lasting at least 2000 years. And what happens is it just gets stronger because when it cracks, water seeps into the cracks and it activates these lime deposits that are trapped in there. And so then the lime fills the crack and seals it up and heals the cement. Presumably the colosseum is just getting stronger over time. Now we know how to do that. So we can make cement that lasts virtually forever, use less of it, use less steel, and the kicker is, it's about 20 percent less CO2, out of the box without even trying. That's pretty dramatic considering the, the scale of the problem and the lack of other practical ways of decarbonizing. So these might be compatible, right? You might be able to also use this coffee additive. What I like about this is that cement is such a big thing. Most people just take it for granted. They don't know how. Intensive this is from a carbon emissions standpoint and the scale of it. this. You know like we can actually make things way, way better. with some of these ideas. Ash: And the way they were doing it, the Romans had volcanic rocks, so they had this ability to automatically have the little bubbles in it. But I think what's interesting is that, some people are like, oh, can we put plastic? Isn't that where we just got in trouble with microplastics? Let's solve one problem and then really screw up something else. The idea I was thinking is maybe this is where the coffee ground becomes like the aeration, right? Cause the whole structure was that as the bubbles popped, that was how the lime. Seeped back in, right? The water combined. Pablos: I think that was one of the theories that was debunked. I'm not positive, but I think that was the, like the prevailing idea, or it was kind of a half baked idea of like how this happened. And I think that is not what actually, it's nothing to do with the volcanic rock after all. Ash: It wasn't the volcanic, right? They had a couple , right? One was like some guy was trying to do bacteria. five, six years ago. That was the other crazy one, which was like, we will just have a living organism inside. The other question is, during production, can you trap, can you use it to just trap the stuff? Like, if you look at, was it clean, right? If you look at those guys, Pablos: So that's what DMAT solved. And they do it with this process called hot mixing. Which apparently was considered dumb for, I don't know, centuries or something. And so nobody tried it. Apparently using hot mixing they can get the lime deposits optimally trapped in the cement. I don't know all the details. Ash: I like it. Pablos: Yeah, so we'll get them on the podcast sometime and have them explain all the all the ins and outs. But yeah, pretty cool stuff. Ash: The challenge with almost all of these carbon reduction technologies is scale. Oh, hey, we're going to take carbon out of the sky. And it's like, okay, what did, what was the impact? Well, it's like half a car. Pablos: Right because the sky is like the most entropic source of carbon there is. Literally, the number 400 parts per million. Well, let's see. If you had a haystack, and you had, 400 needles and, a million pieces of straw, good luck finding a needle. It's literally, the hardest possible place to get carbon. If you want to, sequester carbon, the thing to do would be to just, leave the fucking coal in the ground. Where it's, the highest density of carbon you could find. So yeah, it's, it's kind of idiotic. Most of these things kind of solve themselves if you solve energy. If you had like a shit ton of free energy, then yeah, you could go do carbon capture from the atmosphere, but, otherwise it's pretty painful. Ash: The problem is, yeah, like you said, unless you can turn it back into like a diamond or something, like you said, put it back into coal. These magma guys are, are cranking. Maybe we can use those guys. You've heard of the magma guys? Pablos: What's the magma guys? Ash: These guys were doing the near magma experiment. They're like, we're just going to go 6, 000 feet, like just a little over a mile. What's a mile? 5,280 feet? So you just go a little bit into the mantle. Just tap into that hyper geothermal. Pablos: I don't know what you're talking about. Ash: Oh, so there's a project, just came out a couple of days ago that they revealed that they have a timeline on 2025. They're going to do two. One is an open magma bubble, it's in Iceland and then they're going to do another one on top of it. They're going to build like a little station and they're going to go straight down. This is poking the bear, I would say. Pablos: So they're basically trying to do a man made volcano. Ash: Yes, yes, that's the, that's the way to think of it. Pablos: Iceland doesn't have enough volcanoes. Ash: There's not enough problems where you could just suddenly drill a hole and burst the pimple of God, right? I don't Pablos: People are worried about AI, and here we are trying to make a cousin for Eyjafjallajökull. Ash: I like it because someone's like, "there's infinite heat." And I'm like, "yeah, but it's kind of down there for a reason." Didn't work out too well for a lot of people, right? Pablos: I don't understand, I guess if you succeeded at drilling that hole, then I think you would have basically the same thing as the makings of a volcano. Ash: Yeah, but they're trying to contain it, right? They somehow feel like, like they could drill in a place... Pablos: You're going to have to cycle it because if it cools, even if the magma comes up and cools, it's just going to plug your hole. Ash: So the point is that they have to get a turbine to magma, magma rotating. It's wild. It's going to be interesting. just liked the idea that, that someone's literally poking the bear. Pablos: Oh, they definitely should try. Ash: Cause you know, we talk about fusion being risky, but this one I just feel has a lot more problems. Pablos: Yeah, I think they're just gonna, the magma is just gonna plug the hole. Ash: No, they've got, they've got, some ideas. Yeah, well, it is pressure. It's under pressure. That's why I keep calling it a pimple. Pablos: Yeah, that's why volcanoes get made, right? Ash: That's why they gotta go to Iceland. But, the interesting thing is, if you could technically, if you could maintain pressurization all the way up to the top, right, then it can stay magmatic and you could technically build some sort of, high velocity magma drive. That's, what they're thinking of. And that will just keep cycling. Cooling, but just spinning this turbine. Pablos: What do you do with the magma that comes up hot? Ash: It becomes like a, a river. Pablos: You run the turbine, but then where does it go? You gonna pump it back down? Ash: Yeah, it's as if you were in a magma flow, right? So magma continues to move. It continues, it has a lot of movement, which people don't realize. Look, the minute I heard drill 6,000 feet into a thin crust lava magma I sort of went, Hmm, this cannot end well. That's, that's the way I looked at it. But who knows? Pablos: But it's just Iceland, so you know, there's only like 130,000 people there. They're tough though. If anybody can handle it... Ash: Don't you remember? Didn't, they stop all transatlantic flights? You remember right? There's like a little Ash: cloud and, so just Iceland, but it's, it's literally on the jet stream. We Have a few airplanes crossing right over Iceland. No more going to Europe or vice versa. Pablos: Yeah, well, we overdid it anyway. Europe is basically just like a suburb of the U.S. now. Ash: And Brexit. So, you know, Pablos: There's a lot of people who are trying to figure out how to decarbonize cement and it stalls out in part because there's like four or five thousand cement plants around the world, and they all cost $100 million to build in the first place. A lot of the ideas for decarbonizing cement require building a new plant. And even if you could build one, you're not going to build 4,000 of them. They're Just non starters. And that's part of why I like DMAT is that they can integrate in any cement plant with basically zero capex. You can just go in and upgrade, turn some knobs, and make a new formula. So, that's super cool, and hopefully this coffee based additive would have that property as well. Ash: I think what's interesting is just the coffee part of all this conversation. Pablos: If I go back to that article, it says that there's, 10 billion kilograms, which is 22 billion pounds of coffee waste a year. I presume this is post consumer grounds. Ash: This is probably commercial coffee grounds that they can track using, like, Starbucks. It doesn't include what we take home. Pablos: So it's at least something like three pounds of coffee grounds per human, for every man, woman, and child on Earth. I don't even drink coffee. So somebody else is doing double. The other one that we, got excited about and backed is this, startup called Marvel Labs. What's exciting there is they figured out how to use the used coffee grounds as an input material for 3D printers. That sounds like kind of a cute thing, but the truth is it's staggering implications. And it's because 3D printers, they're called rapid prototypers because we used them in labs and they were very expensive and impractical for a long time. And then in 2007, one of my buddies helped start MakerBot, and I was an advisor for MakerBot, which was the first consumer 3D printer. And so we thought we were gonna eventually build farms of these things like AWS, you'd just have a data center full of MakerBots and you'd wire them up to the "buy now" button, and whenever you clicked "buy now," a MakerBot would print your stuff and then print a box around it and then print a FedEx label on it. It would show up in the mail. Obviously that didn't happen, and here we are 15 years later, and you don't buy anything on Amazon that's 3D printed. There's two big reasons. One is they're one pixel printers, so they're super slow, and that makes it expensive. And then the other part of it is that the input materials are expensive, so you've got these high quality filaments, plastic filaments and things that are expensive. At the end of the day, you're competing with injection molding, which is like the cheapest way of making anything on Earth. And so, it hasn't worked out. There's a couple of exceptions. So for example, with metals, 3d printing of metals has worked out pretty well for two reasons. One, they're higher value parts. So you're printing, you know, jet parts and rockets and stuff. But also the technique in the printers is it's a powder bed, so you have this bin of powder, you run over it with a binder, like glue, from an inkjet head or a laser or something to sinter it together, and then, you pick up your part and shake it off, and you've got this part that was printed in a bed of dust. It's actually a very elegant way of making a 3D printer, and it's faster, because they're more like layer at a time instead of pixel at a time. Anyway, so what Marvel Labs did is they adapted that style of printer, which is fast, but the input material is these used coffee grounds and what the effect of that is, is now they can print stuff out of coffee. They're making all kinds of stuff. Sinks and light fixtures and bicycles and things. And the parts come out of the machine. They're made of coffee and then they just powder coat them with paint or metalize them so they look like metal and you can't even tell that it's made of coffee. And so this whole thing works awesome, but the main reason that it's important , and the reason that we invested, is that it flips the economics. So now, these parts that Marvel Labs is making, they've reshored manufacturing, they manufacture stuff in the U. S., they do it fully automated. And the parts are cheaper than doing it in Asia. That's what's exciting to me. They're also printing with seaweed. They're printing with sawdust. All the technologies they invented to make it work are about, printing with biomass in general. They're kind of the kingpin. Now we can get this whole vision together of producing things on demand in 3D printers in the U. S. Ash: It's interesting because several things, right? One is, like you said, it's not just, the on demand. All of our strategic risk starts to change, right? Think of what happens when, we get to a point where we're having another pandemic or, I don't know, they go after Taiwan. Supply chain changes if you're suddenly local, right? As long as we can get enough coffee into the system, we have enough of our own source material. Pablos: Ha, Ha, ha, ha. As a matter of national security, Americans are being asked to drink more coffee. Ash: It's a national security imperative that you get a frappuccino. Pablos: Well, I found out China just surpassed the U. S. as having the most Starbucks locations. Ash: China did. Frightening. I mean, Japan, Starbucks, whole different story. I was just looking at the botanical Starbucks in Japan, Starbucks is its own, own different conversation. But I was going to say that when you think about all of this, the implications for logistics, and one thing I wasn't sure on, on the way that they produced, what was their binding material? Because I know they're, one of the things they were talking about was biodegradability. Pablos: Marvel Labs has invented a variety of different binders. One of them is entirely sugar based. They use it with seaweed and they can make these biodegradable parts. Which is really cool, and then they have some top secret binders they invented that are super cool and they're not ready to announce them yet, but it's awesome. Ash: I saw some of the pieces. Pablos: Yeah. Oh, that's right. Ash: I got to actually play around with it. I, I think what's amazing to me is that the idea that you can cut production time. I don't know if it was an experiment or if they still do it, but remember there was Amazon Now. Where like they had little trucks going around and, and they had like USB cables or like whatever you needed, like that minute. Pablos: circulating your neighborhood With, that was loaded with the things that they predicted, were going to be bought. Ash: Yeah, 100%. That's what it was, right? They predicted that, everyone in Palo Alto needs like an extra USB cable. And they had one and you could get it like one hour delivery. Pablos: But that truck could just have a 3D printer in the back. Ash: That's exactly it. Right? Like imagine, how big are these things? How big are the printers? Pablos: The printers are, I'd say like 80 percent of the printer is the print bed by volume. So, if you have a printer the size of a refrigerator, 20 percent of it is gantry and other crap. And that's pretty typical of 3D printers, I guess you could say. And at least in a powder bed style printer. And the rest of the volume is printable. So, these printers are actually quite large. And one of the nice things about a powder bed printer is that you could just print a whole bunch of parts at once. You just fill up the bed with parts because they're just floating in powder because the powder is like the support material as well. It makes it easy to do big batches of stuff. If you're printing coffee mugs, you can print it and you got a fridge size printer. You can print, a couple hundred mugs or whatever all at the same time. And then, they just come out of there. I'd say 3D printing's future, over the next 10 years or so will be really focused on figuring out how to make multi material printers. There's a little bit of work on that now, especially trying to be able to do conductive materials. It'd be great to be able to print something like a game controller or a pair of headphones or something, have some of the wires printed in it. Ash: Maybe you have the recycled aluminum just like get blasted and powderized. I know of a magma plant coming up that might be able to... Pablos: Can we make a magma, printer? Ash: You take the aluminum, you feed it into the magma god and it comes out powderized. Pablos: Well, most aluminum comes from Iceland anyway. Aluminum is essentially made of electricity and they have access to cheap, clean electricity, Ash: That's the, the, secret, right? So we have infinite power and then they're just producing the conductive dust. One of the things I was thinking is like, how do you market this, right? Because we have to get a behavioral change on consumption. It's so easy to go with fast fAsh:ion, fast goods. We're addicted, I don't know if you've ever seen Wish? Pablos: Oh, uh, I know what it is, but I've seen Temu. I signed up for Temu. I ordered some shit before I found out it was obviously Chinese spyware app. And I um, I, bought some shit Temu cause it was so cheap. They're like paying you to take this stuff. And then it was like worse than infomercial products. Like I got these things and they're the cheapest possible things. And they had used like trick photography. I bought this bottle of, a cleaning product, I have it right here. I'm looking at it. It's this bottle called Foam Cleaner. I'm like, oh cool, I'll use that to clean the shower. I don't know what, kind of bug eye lens they must've used to photograph this thing. But when it showed up, the bottle itself is literally a 60 milliliter bottle, which is, that's like the size of, it's like a large bottle of nail polish, Ash: It's like, It's like, not even a perfume bottle. Pablos: And then it's got the full size spray head that you'd have on a bottle of Windex or something on it. So this whole thing, it looks like a joke. Nobody would ever do this. I've never seen a bottle this small with this big, like the spray head by volume is bigger than the bottle. Ash: So basically you've got a bobblehead cleaner. That's what you're saying. Bobblehead but foam cleaner. That's it. That's it. We can market it. Pablos: Yeah. I mean, I'm afraid to spray it because you know, like if I pull that trigger more than three times, the bottle will be empty. Ash: I'm sure it's not a neurotoxin or anything. Pablos: Okay. But anyway, the point being. Yeah, it's Temu and Wish and all this bullshit. I don't know about consumer behavior change. You would know more than me. What are the odds that we're ever gonna be in a world where people buy less shit? Ash: It's not that we buy less. I'm trying to figure out if we can shift them, right? Think about it. At one point, we were all obsessed around Gore Tex, it was like the magic, right? We had just left our class on osmosis and we were like, wow, it's like osmosis in a fabric, we were excited. Pablos: Maybe explain how Gore Tex works. Ash: Gore Tex's whole idea was about breathability, where the pores on the fabric were supposed to for air to go out, but water not to come in. Pablos: Which works because... Ash: It's surface tension allows the droplets to hold more together, so they're bigger than the water vapor molecules going out, right? So, so the molecular sizes are different. So you can create this sort of barrier. Now there's 50 versions of this to Sunday. But, Gore Tex was, was something which became a brand name, right? I don't know if it was before Intel Inside, but it was kind of the same concept, right? Saw a little label on Gore Tex. Pablos: It's like the Dolby of outerwear. Ash: It is. It was the Dolby of Outerwear. So I think somehow we've got to build that kind of reputational or brand concept, For example, if it's the seaweed and sugar and everything nice, right? Pablos: Okay. I see. Full circle brand where it's like "buy as much of this shit as you want. Whenever you're done we're just gonna turn it into the next shit you're gonna buy." Ash: it's not just recyclable... Pablos: It's like infinitely recyclable. Recycling is a is a joke. Ash: And the amount of energy and stuff that it takes is is sort of crazy, on that as well, right? So that's that's one of the, the sort of big, big problems that that happens with it. And I think one of the challenges is that we've got to figure out a way. That, something like what we're talking about in terms of, this new product, this new mechanism, this new process can be Gore Tex'd. Or Dolby'd, and a little bit more than like this is recyclable. I think we're kind of over it, right? Like we've seen the little symbol, we don't even know what's going on anymore. I know that in most countries they have like, at least like five bins. I think most Americans can't figure out like. What's up? There's a blue box. Pablos: You could imagine a version of this where, ultimately everything is just made of, some atoms, right? They have to come from somewhere. And then the energy it costs to, move them around and stick them together. So. You know, if you sort of just take that approach, you could say, okay, this stuff is made of this much joules and, this many atoms, like you could basically measure everything that way. Then you could say like, all right, well, the total cost of ownership in a given product could be added up that way. The cost of like mining all the shit, the cost of transporting around the world, the cost of, burning stuff to make it, whatever it takes. If you added that up for any object, it would probably be staggering. In the long run, you would, you, what you would like to do is track things that way and then be able to say, okay, this is kind of a full circle product, like an apple is probably like the closest you get maybe to a product that is low impact, it grows, we there, there's some energy cost in transporting it from a farm to your mouth, and then you eat it, you throw out a quarter of it as biomass. Ash: When you say an Apple, not your iPhone. Pablos: Oh yeah, I'm talking about like an actual physical apple. The kind you can eat. Yeah. Not an phone. Granny Smith, not a Macintosh. Ash: But maybe that's the score, right? Pablos: I think your Intel inside becomes... Ash: is it net negative? Is it net positive? Pablos: It's net negative or it's like close to the threshold of about an apple instead of being, at the threshold of like about a Tesla. Ash: That may be the interesting way to do it? So maybe a dynamic symbol is the way to think of it, right? So instead of the old Intel Inside or Dolby Atmos or whatever's going on, or Gore Tex, maybe it's about the level. Is there a number? Is there a score? Lasered in or 3D printed into the object itself or, or anything that you look at, it just tells you that this has a small number or a small something that people can understand that's better or higher or whatever. Pablos: Energy star. Ash: I look at something like calories. Like years and years ago, we all started getting obsessed and that definitely the generation that grew up with cereal boxes, who had nothing better to read. And we didn't have a iPhone to scroll. We read cereal boxes. We knew more about niacin and potassium in your cornflakes than any human should ever know. Pablos: It's true. I read a lot of cereal boxes. Ash: That's what you'd read. You read, you'd read the cereal box. When they changed the USDA standard for what you can see inside, the bigger format I remember that was like a big change on the packaging design. That was something where we could see the calories and then we realized, per standard serving size or whatever it was. And I think that at some point, the same thing has to happen, right? Each object that we consume or buy, can have that. There's actually a company. That we're looking at, called Love, like seriously called love.com. Uh, uh, I won't go into much more about that, but they're actually trying to change this, like specifically change this idea. They're trying to build an Amazon. First of all, they have love.com. I sort of tossed out the idea that it's powered by love. And that way, it can have a score, each thing you're buying. They curate what's allowed to be sold on there. So it's like an Amazon, but like, we're going to get rid of Pablos: So all you need is love. Love is all you need? Ash: It's true. That's their eventual goal is to go head to head with Amazon. A billionaire multi time, entrepreneur who's kicking this off. What's interesting, though, is I think people will start to recognize this. Pablos: Yeah, you could do some big branding campaign around, certified green or whatever, but it seems so like all these things are so gameable. I mean like calories, even like, I understand this as a kid, but now that I know what a calorie is like... Ash: It's totally gameable. Pablos: Oh my god, that's a totally fake thing that we made up that's, like, barely a measure of anything. Ash: That's why I picked it. I was going to say that with good numbers come good evil, right? Are you drinking a 12 ounce can of Coke? Was it like eight ounces? What did they do? It's interesting how it became a complete nonsense number? It mattered. We learned later that maybe the mix matters, and it wasn't about the sodium. And there's a lot of little bits that didn't matter. The question becomes, can you build something genuinely? There's another company, we invested in, Dollar Donation Club. And what's interesting about them is, when Seth, who's the founder, said, "Hey, I'm going to see if we could create the world's first super philanthropist." The idea that if we all gave a dollar a month, technically it's billions of dollars. You can make a lot of changes. He said," where am I going to give the money? I don't want to be another money place. I want to be something where I can see the impact." So he built a giant impact map of things he wanted to do. And he said, "okay, I want to know exactly how many kilos of microplastic are removed for my donation." Like, I don't care that I donate $1, $2. I was like, I'm willing to go and take out a kilo. Well, it turned out he can only get to like, I forget what the number is like 11 or 20 charities. It took that long and that his professional teams, like when they vet out what the charity really does. Pablos: Yeah. Ash: Almost no one qualified. So I think this is the unfortunate thing that's going to happen, right? So if our coffee friends bring it full circle, if Marvel can really like just crush it. Like they can demonstrate there's an actual true cost reduction I'm talking about from Guangzhou to, Columbus. By the time it gets there, like what actually happened and then the return leg, right? Like what happens on the back if, if that's actually a real score. That we can defend. Maybe that's what Marvel has to do. Pablos: The way it should be done probably is kind of like, consumer reports. There ought to be, like, life cycle metrics made for, the product coming outta Marvel Labs versus its competitor that came from Guangzhou. Here's your Samsung versus iPhone versus, Nokia or whatever and somebody does the research and figures out; this is the mining footprint; this is the shipping cost. This is how much, energy was burned. The factory is running off of a coal plant versus a nuclear reactor or whatever. Ash: Like Energy Star, but like it actually makes sense as opposed to Energy Star. Pablos: Yeah, and that could be given a score in joules that just ranks these things against each other. Ash: But we're talking about three ideas here, right? So that one idea is to get somebody to come out there and say, look, fundamentally, product life cycle measurement is something someone should go build, like someone should, whether it's independent of Marvel or not, somebody should do it. And then different manufacturers or, or whether it's a 3D printer of type company or someone else should go in and say, look, let's show you why we are the lowest score, the highest score, whatever the, whichever one's considered the better thing. And then we have to create education and marketing on that, to say, Hey, if you're not doing this, you, you are literally creating damage. Pablos: There must be initiatives like this that we don't know about. An interesting thing to consider is an iPhone is made of whatever, 2000 components. Some of them are like screws that Apple sourced and didn't manufacture. Where was the metal for the screws mined? Where's the factory for the screws? How far are the screws traveling to get to the iPhone factory? All that kind of stuff. And so you would, eventually if this were fully played out, when you design an iPhone and CAD, it would just tell you, where your screws are coming from. We already have the environmental impact score for those screws. Pick the ones that have the lower score. Ash: So this is like an SAP thing. So go back to, Fast moving consumer goods. So in the FMCG world, one of the things that's really interesting is something called, smart label and smart label is interesting because it said, Hey, like ingredients don't cut it. I want to know like really what's going on, it goes really deep, you can dive into the label, but where did you source it? Like, is it really honey from here or what was going on? I think Nestle, I think some of the biggest players all support it. Procter and Gamble, all these guys are on smart, smart label. Now that's interesting because you're almost already there, for those guys, you're pretty close, but that's for food. Hopefully that's mostly biodegradable. Otherwise we have other problems in life. Pablos: Yeah, that's interesting. Maybe that could be extended so that all the, the ingredients of my, headphones... Ash: Exactly. Could you extend that construct? I actually think back to another company, from years ago, it is one of my patents, from a while back. it was a company called, Black Duck Software. You were talking about, as you're sitting there with your CAD, I was thinking of, open source. Remember it was like, ""are you using something that's gonna infect the rest of your project?" When you're coding in Eclipse or something and you're like, oh, let me just grab this little... Pablos: You accidentally scoop up some GPL library... Ash: Yeah, it's an LGPL or something. It happened to Fidelity. Their entire mortgage calculator, their entire mortgage algorithm had to be open sourced because they used a website plug in. So, they eventually invested in the company. Obviously, they invested in us. But what was good is that, when you, were able to sit down and look at the project, it would tell you immediately, like, if you put this in there, you will like, have to open source your print driver. Pablos: All that should just be in CAD. A lot of CAD software has a plug in to tell you how much it's going to cost to machine that part that you made based on the design. And it could easily tell you how much material it's going to take and how much material cost there's going to be. But you could extend on that and say, you chose these screws. Here's how much they're going to cost. Here's what the lead times are. All that's in SAP already. And then it tells you, this is the environmental footprint of the screws you chose. Ash: And now you can tie that into some exchanges or B2B sourcing companies and just say, okay, give me a scenario. I want to automatically reduce my carbon or my, my total footprint. Where else could I source, right? So maybe instead of titanium screws, I have to manufacture for this new titanium iPhone from like some Russian mine where the titanium lives. Pablos: be seven Web3 companies trying to do this already. Ash: I think what they miss. And this is something that I think is an interesting part of the journey, right? That you and I also take is it sometimes great technology and great back end stuff doesn't hit the front. The only reason calories don't matter today because we woke up and realized that somebody paid off the cardiologists to get us to eat margarine and told us that sugar was, okay and fat was terrible. That was programming, right? That was maybe we need some good programming. I mean, we got programmed the wrong way. Maybe we need to program people. To see the right thing. And I don't know that we could be seen as altruistic or that we're necessarily not, not commercially motivated. I think that there's some way that today because of information and speed of information, I think we can create some level of transparency, like you said. And then we can turn around and say, back in the day, I couldn't tell you where my, millet was coming from for the food. Today we can, Smart Label will tell you literally where that food comes from. I think we could do something fun, fun with that. Someone should go do that. Pablos: Yeah. Someone should go do that, which is, one of the main points of doing this podcast is that hopefully we'll come up with ideas that somebody else should go do.

Coming up in this episode * We do a little upgrade * Firefox fixes a tooltip * The History of W, V, X and CDE * How it went * And a new old desktop to explore 0:00 Cold Open 1:42 Lemmy's Upgraded! 10:56 A 22 Year Old Bug 15:50 Install Firefox Correctly 22:22 CDE History: Intro 24:04 CDE History: X 27:33 CDE History: OPEN LOOK 29:25 CDE History: COSE 31:28 CDE History: CDE & Others 34:24 CDE History: The Opening 36:14 CDE History: The Releases 43:02 How'd CDE Go? 1:16:00 Next Time 1:21:29 Stinger Watch the video! (https://youtu.be/-tycNQ-Ey9Q) https://youtu.be/-tycNQ-Ey9Q Banter The LUS Lemmy instance (https://lemmy.linuxuserspace.show) got an update (https://github.com/LemmyNet/lemmy-ansible/releases/tag/1.2.0). The ansible repo switched to tagged releases. There were ⚠️breaking changes⚠️ that needed to be prepared for (https://github.com/LemmyNet/lemmy-ansible/blob/main/README.md#upgrading). One of the issues Dan had is likely fixed now. (https://github.com/LemmyNet/lemmy-ansible/commit/300a261b2a346dd6489f5eb43d6af632633f4059) The Bug (https://arstechnica.com/gadgets/2023/10/22-year-old-firefox-tooltip-bug-fixed-in-a-few-lines-offering-hope-to-us-all/) that's old enough to drink and drive, but hopefully not at the same time! Dan installed Firefox (https://support.mozilla.org/en-US/kb/install-firefox-linux#w_install-firefox-from-mozilla-builds) from the .tar.gz download. Spoiler - it updates just fine because my user is the owner in the /opt directory. Announcements This program was made possible by: * The letters W, V, X, C, D and E *

Come to FOSSY 2023! Show Notes: FOSSY 2023 will happen next week in Portland, OR, USA. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom by following Conservancy on on Twitter and and FaiF on Twitter. We are working on setting up a group chat again, too! Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Come to FOSSY 2023! Show Notes: FOSSY 2023 will happen next week in Portland, OR, USA. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Cet épisode marathon sera découpé en deux morceaux pour éviter à vos oreilles une écoute marathon. Dans cet épisode on y parle Brian Goetz, Bian Goetz, Brian Goetz, usages des threads virtuels, OpenAPI, Kubernetes, KNative, copilot et Tekton. La deuxième partie couvrira des sujets d'architecture et de loi société et organisation ainsi que les conférences à venir. Enregistré le 8 juillet 2022 Téléchargement de l'épisode LesCastCodeurs-Episode–281.mp3 News Langages Peut-être une nouvelle syntaxe spécifique aux Records Java pour tordre le cou aux builders Brian Goetz discute de l'idée d'avoir une syntaxe spécifique pour les records pour facilement créer un record dérivé, potentiellement avec des valeurs par défaut, mais en paramétrant certains champs Point shadowPos = shape.position() with { x = 0 } Cela évite de créer la notion de paramètre par défaut dans les constructeurs ou les méthodes Il y a l'article Data Oriented Programming de Brian Goetz, sur InfoQ projet Amber amène des changements qui combinés permet de faire du data oriented programming en Java et pas que du OOP OO combine état et comportement (code) OO est super utile pour défendre des limites (programme large en des limites plus petites et plus gérable) mais on s'oriente vers des applications plus petites (microservices) data oriented programming: modélise data immuable et le code de la logique métier est séparée records -> data en tant que classe, sealed classes -> définir des choix, pattern matching -> raisonne sur des data polymorphiques algebraic data: hiérarchie de sealed classes dont les feuilles sont des records: nommées, immuable, testable (pas de code) Un nouveau JEP pour intégrer une Classfile API Le JDK inclut déjà des forks de ASM, de BCEL, et d'autres APIs internes, pour manipuler / produire / lire le bytecode Mais l'idée ici c'est que le JDK vienne avec sa propre API officielle, et qui soit plus sympa à utiliser aussi que le pattern visiteur de ASM par exemple La version d'ASM intégrée était toujours en retard d'une version (problème de poule et d'oeuf, car ASM doit supporter la dernière version de Java, mais Java n+1 n'est pas encore sorti) Lilian nous montre à quoi va ressembler les Record Patterns de JEP 405 Apache Groovy et les virtual threads, et aussi Groovy et le Deep Learning Paul King, qui dirige actuellement le PMC de Apache Groovy, a partagé récemment plusieurs articles sur le blog d'Apache sur des intégrations intéressantes avec Groovy Groovy et sa librairie GPars pour la programmation concurrente et parallèle s'intègre facilement avec les Virtual Threads de JEP 425 / JDK 19 https://blogs.apache.org/groovy/entry/gpars-meets-virtual-threads Groovy avec Apache Wayang et Apache Spark pour classifier des Whiskey par clusterisation KMeans https://blogs.apache.org/groovy/entry/using-groovy-with-apache-wayang Et aussi Groovy avec différentes librairies de Deep Learning pour la classification https://blogs.apache.org/groovy/entry/classifying-iris-flowers-with-deep Le jargon (en anglais) de la programmation fonctionnelle, si vous avez rêvé d'avoir sous la main la définition de foncteur, de monoïde, et j'en passe avec des exemples en JavaScript des pointeurs vers des librairies fonctionnelles en JavaScript des traductions dans d'autres langues et d'autres langages de programmation Librairies Spring Boot 2.7 SpringBoot 2.7 Spring GraphQL 1.0 Support pour Podman Gestion de dépendance et auto configuration pour Cache2k nouvelle annotations pour Elasticsearch et CouchBase dernière versions avant SpringBoot 3 qui changera plus de choses. Recommande de migrer une version a la fois. Support pour 2.5 à fini (upstream) Quarkus 2.10.0 Travaux préliminaires sur les threads virtuels de Loom Support non-blocking pour GraphQL Prise en charge des Kubernetes service binding pour les clients SQL réactifs CacheKeyGenerator pour l'extension de cache quarkus-bootstrap-maven-plugin déprécié et remplacé par quarkus-extension-maven-plugin (uniquement utile pour les développeurs d'extensions Quarkus) Nouveaux guides: Using Stork with Kubernetes OpenId Connect Client Reference Guide Using Podman with Quarkus Les différences entre OpenAPI 2 et 3 Introduction de la notion de lien pour créer des relations entre Response et Operations, pratique pour faire des APIs hypermédia La structure du document OpenAPI a été -un peu simplifiée, en combinant par exemple basePath et schemes, ou en rassemblant les securityDefinitions Des améliorations sur les security schemes, autour de OAuth et OpenID Plus de clarté dans la négociation de contenu et les cookies La section des exemples de Request / Response devrait aider les outils qui génèrent par exemple des SDK automatiquement à partir de la description OpenAPI Un support étendu de JSON Schema Introduction d'une notion de Callback, importante pour les APIs asynchrones, en particulier les WebHooks je me demande si ils ont l'intention d'embrasser AsyncAPI ou su la partie asynchrone d'OpenAPI 3 a pour objectif de faire de la competition Infrastructure N'utilisez pas Kubernetes tout de suite ! Kubernetes, c'est bien, mais c'est un gros marteau. Est-ce que vous avez des gros clous à enfoncer ? Ne commencez peut-être pas avec l'artillerie lourde de Kubernetes. Commencez plutôt avec des solutions managées genre serverless, ce sera plus simple, et au fur et à mesure si votre infrastructure a besoin de grossir et dépasse les fonctionnalités des solutions managées, à ce moment là seulement évaluer si Kubernetes peut répondre à votre besoin Choisir Kubernetes, c'est aussi avoir la taille de l'équipe qui va bien avec, et il faut des profils DevOps, SRE, etc, pour gérer un cluster K8S L'auteur suggère grosso modo que ça dépend de l'ordre de magnitude de la taille de l'équipe : avec quelques personnes, préférez des solutions type Google App Engine ou AWS App Runner, avec une dizaine de personne peut-être du Google Cloud Run ou AWS Fargate, avec moins d'une centaine là pourquoi pas du Kubernetes managé comme Google Kubernetes Engine, et si vous dépassez mille, alors peut-être vos propres clusters managés par vos soins et hébergés par vos soins sur votre infra ca impose d'utiliser les services du cloud provider? Parce que la vie ce n'est pas que du code maison. C'est la mode de dire de pas utiliser K8S : https://www.jeremybrown.tech/8-kubernetes-is-a-red-flag-signalling-premature-optimisation/ (mais bon, vu le nombre de fois où il est pas utilisé à b Knative Eventing Devlivery methods on peut faire de la delviery simple 1–1 sans garantie on peut faire de la delivery complexe et persistante en introduisant la notion de channel qui decouple la source de la destination. on peut repondre a la reception d'un message et pousser la réponse dans un second channel mais ca devient compliquer a gérer quand on rajoute des souscripteurs il y a la notiuon de broker qui definit: des flitres, un channel (automatique) et la capacité de répondre les triggers sont un abonnement non pas a un channel mais a un type d'évènement spécifique Cloud AWS is Windows and Kube is Linux pourquoi utilisez Kube qui etait pas stablewa lors qu'AWS offre tout AWS forcé d'offrir EKS MAis pourri Lockin AWSIAM Pourquoi AWS serait le windows economies d'echelles de faire chez soi kube devient rentable une certaine taille de l'organisation besoin alternative a AWS (bus factor) on voit le Kube distro modele arriver Google data center Paris Outillage IntelliJ IDEA 2022.5 EAP 5 amène des nouveautés Frameworks and Technologies Spring 6 and Spring Boot 3 Support for new declarative HTTP Clients in Spring 6 URL completion and navigation for Spring Cloud Gateway routes Experimental GraalVM Native Debugger for Java Code insight improvements for JVM microservices test and mock frameworks Code insight improvements for Spring Shell Improved support for JAX-RS endpoints Support for WebSockets endpoints in HTTP Client Support for GraphQL endpoints in the HTTP Client UI/UX improvements for the HTTP Client Improved navigation between Protobuf and Java sources Kubernetes and Docker Intercept Kubernetes service requests with Telepresence integration Upload local Docker image to Minikube and other connections Docker auto-connection at IDE restart Docker connection options for different docker daemons GitHub copilot est disponible pour tous (les developpeurs) 40% du code écrit est généré par copilot en python (ca calme) gratuit pour les étudiants et les développeurs OSS Revue de Redmonk décrit copilot comme une extension d'intelligence ou auto complete mais qui « comprend » le code autour premiere fois pas une boite de cette taille et à cette échelle l'avantage de copilot en terme de productivité, de qualité de code, de sécurité et de légalité En gros, c'est encore à voir. Mais la qualité impressionne les gens qui l'ont testé ; sécurité pas de retour d'un côté ou de l'autre sauf que les développeurs humains ne sont pas des lumières de sécurité :D GitHub pense que GitHub n'est pas responsable de la violation de code vue que ce sont des machines et des algorithmes qui transforment: cela a l'air d'etre le consensus des avocats GitHub dit qu'on est responsable du code qu'on écrit avec copilot Et implicitement GitHub dit que la licensure du code « source » ne se propage pas au code generé. Et là, c'est pas clair et de la responsibilité de l'utilisateur, mais la encore les avocats sont plutot ok moralement c'est probablement pas ok mais bon et il y a débat autour des licenses copyleft notamment LGPL 1% du temps, code copié verbatim de > 150 caractères Question sur le code non open source sur lequel GitHub Copilot s'appuie mais en gros le marcher s'en fout un peu des licences Risque de reputation de Microsoft la question c'est quand / si les gens seront prêt à accepter cet usage Gradle publie sa roadmap Historiquement, la société Gradle Inc ne publiait pas vraiment de roadmap officielle Outre les tickets que l'on pouvait voir dans Github, cette fois ci, une “roadmap board” est visible et disponible pour tout le monde, et pas seulement pour les clients Tekton est groovy (mais non, il n'utilise pas Groovy !) Un grand tutoriel sur Tekton Une brève histoire de CI/CD (avec un contraste avec Groovy utilisé dans Jenkins) Un aperçu des grands concepts de Tekton, avec ses tâches et ses pipelines (Task, TaskRun, Pipeline, PipelineRun) Comment installer Tekton Les outils CLI Un exemple concret d'utilisation Sortie de Vim 9, surtout avec VimScript 9 des changements incompatibles entre VimScript 8.2 et 9 font qu'il était nécessaire de passer à une version majeure mais l'ancienne version du langage reste supportée pour compatibilité avec la nouvelle, les utilisateurs peuvent s'attendre à des performances x10 voire x100 ! le langage devient pré-compilé, au lieu d'être interprété ligne par ligne l'idée était d'avoir un langage plus proche de ce qu'on trouve dans JavaScript, TypeScript ou Java Conférences De la part de Youen Cette année Codeurs en Seine, c'est le 17 novembre et le cfp est ouvert N'hésitez pas à amener un peu de JVM dans l'appel à orateur. (ca commence à se faire rare). Pour rappel : codeurs en seine c'est 1000 personnes autour des métiers du développement dans une des plus grande salle de Rouen, le kindarena. Nous contacter Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Faire un crowdcast ou une crowdquestion Contactez-nous via twitter https://twitter.com/lescastcodeurs sur le groupe Google https://groups.google.com/group/lescastcodeurs ou sur le site web https://lescastcodeurs.com/

Karen and Bradley discuss two other DMCA exemptions filed by Software Freedom Conservancy during the 2020/2021 Triennial Rulemaking Process at the copyright office: one for wireless router firmwares and one for privacy research. Show Notes: Segment 0 (00:39) Supporters of Conservancy can join this mailing list to hear and see live recordings of every show! Segment 1 (06:30) Conservancy filed a DMCA exemption request for wireless routers, and updated it with their long comment on the issue. NPR's Planet Money had a show that discussed how recycling plastic in the USA was somewhat of a large con game funded by the plastics industry. Both audio a transcript is available. (19:32, 20:44) Segment 2 (29:10) Bradley and Karen discuss the third exemption request that Conservancy filed, for research to find privacy flaws, and updated it with a long comment on the issue. Karen and Bradley noted that individuals can file reply comments before the deadline of Wednesday 10 March 2021 at 23:59 US/Eastern. Note that the “neutral comment” requirement appears to no longer be listed; the 2021-03-10 (47:20) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Software Freedom Conservancy filed multiple exemptions in the USA Copyright Office Triennial Rulemaking Process under the Digital Millennium Copyright Act (DMCA). In this episode, Karen and Bradley explore the details of Conservancy's filing to request permission to circumvent technological restriction measures in order to investigate infringement of other people's copyright, which is a necessary part of investigations of alleged violations of the GPL and other copyleft licenses. Show Notes: Segment 0 (00:39) Bradley claims that you'll now love the audcast more than ever (02:51) Conservancy filed many exemptions as part of the currently ongoing triennial DMCA Process. (02:50) Segment 1 (04:22) Everyone in the Free Software community wishes the USA's Digital Millennium Copyright Act didn't exist. (05:24) Bradley is currently doing research going to the year 1790 that shows the foundations of the copyright act, but Karen points out that Bradley isn't a professional copyright historian (yet). He points out he is an amateur copyright historian (05:45) DMCA is the USA's implementation of the WIPO Copyright Treaty (WCT), but is more a restrictive copyright act than the WCT requires. (06:50) Bradley mentioned that the three videos from the Copyright Office, which are linked to from Conservancy's blog post on the subject that, while they are Copyright Office propaganda, that are helpful to explain the DMCA (10:57): A Legal Overview of § 1201 (PDF slides only). The Triennial Rulemaking Process for §1201 (PDF slides only). Streamlined Petitions for Renewed Exemptions (PDF slides only). Conservancy filed the most exemption requests in the 2020/2021 Rulemaking Process (21:25) Segment 2 (28:07) Conservancy filed an exemption request and a “Long Form” comment in support of it that was labeled “Class 16: Computer Programs &—; Copyright License Investigation” by the Copyright Office (29:00) Bradley mentioned that people can get arrested just for giving talks under the DMCA, referring to Dmitry Sklyarov. Adobe simply called the FBI and got him arrested under DMCA. (38:50) Segment 3 (34:36) If you are a Conservancy Supporter as well as being a FaiFCast listener, you can join this mailing list to receive announcements of live recordings and attend them through Conservancy's Big Blue Button (BBB) server. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

The first live podcast of Free as in Freedom, hosted at SeaGL 2019 in November 2019. Hear questions from the studio audience and answers from Bradley and Karen. Show Notes: Segment 0 (00:38) Producer Dan speaks on mic to introduce that this is a live show. Segment 1 (01:17) This is a live show from SeaGL 2019, a community-organized FaiP (02:15) Carol Smith from Microsoft asked about being a charity in the USA under recent tax changes regarding tax deduction and, and asked about Conservancy's annual fundraiser which had completed by the time this show was released. (04:53) Deb took a photo during the show (07:30) A questioner asked about the so-called “ethical but-non-FOSS licenses”. Bradley gave an answer that is supplemented well by this blog post (10:15) and Karen mentioned at CopyleftConf 2020 there was a discussion about this. (15:15) The follow up question was also related to these topics (15:44). Eric Hopper asked about how Conservancy decides when a project joins, and what factors Conservancy considers in projects joining (18:14) A written questioner asked how to handle schools requiring proprietary software as part of their coursework. (22:00) Michael Dexter asked about Karen's teaching at Columbia Law School. (27:25) A written questioner asked about copyleft-next's sunset clause. (29:22) Karen mentioned “Copyleft, All wrongs reversed” as it appeared on n June 1976 on Tiny BASIC, which inspired the term copyleft to mean what it does today. (30:45) Karen spoke about the issues of copyright and trademark regarding Disney, that is supplemented by this blog post. (32:52) Carol Smith asked what Karen and Bradley thought were Conservancy's and/or FOSS' biggest achievements in the last decade. (35:20) Karen mentioned Outreachy was a major success. (37:08) A questioner asked about using the CASE Act to help in GPL enforcement. Bradley discussed how it might ultimately introduce problems similar to arbitration clauses. (41:42) Since the podcast was recorded, the CASE Act has also passed the Senate, but does not seem to have been signed by the President. (47:30) Bradley noted that Mako Hill has pointed out that FOSS has not been involved in lobbying enough. (48:10) A questioner in the audience asked about the Mozilla Corporation structure would allow Mozilla to do lobbying for FOSS. (50:57) Karen explained the Mozilla corporate legal structure (51:35). A questioner in the audience asked about Mako Hill's keynote and how individuals can help further the cause of software freedom. (54:53) Michael Dexter asked if software patents are still as much of a threat as they once were. (1:01:30) Carol asked about the supreme court hearing the Oracle v. Google case (1:09:04) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Karen and Bradley discuss the end to Microsoft's e-book platform and generally the dangers and disasters that Digital Restrictions Management (DRM) cause for software users and developers. Show Notes: Karen and Bradley discuss the end to Microsoft's e-book platform and generally the dangers and disasters that Digital Restrictions Management (DRM) cause for software users and developers. Segment 0 (00:35) Bradley mentioned that Microsoft ended their e-book platform. He said this was “last month” but we ended up releasing this show late, so it was in August 2019 (01:31). Bradley mentioned the analog hole. (09:50) Karen discussed the exception process under DMCA, which Conservancy participated in regarding “Smart” TVs. (12:30) Bradley mentioned this historical burning of the Library of Alexandria as a Roman weapon, comparing it to DRM. (15:07) Bradley talked about how Netflix and Microsoft used Silverlight initially as the method of DRM, and that Microsoft was a leader in the entertainment industry in providing DRM (20:00) Segment 1 (26:31) Bradley and Karen discuss how DRM and other lock-down of devices, including medical devices, are creating problems in society generally. Karen noted that the role of for-profit companies is not to safeguard the public interest. (41:10) Bradley mentioned you can turn off DRM on the Google Play store for your book (as the publisher). (43:04) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen enjoy and discuss Molly De Blanc's keynote at the first annual CopyleftConf, entitled The Margins of Software Freedom, followed by an exclusive interview with Molly! Show Notes: Segment 0 (00:37) Bradley mentioned (without the title) the film, When a Stranger Calls, which is indeed a real movie, not a TV movie, and was from the late 1970s — although Bradley saw it on TV sometime in the 1980s. (02:15) Segment 1 (04:11) A recording of Molly De Blanc's keynote at the first annual (2019) CopyleftConf, entitled entitled The Margins of Software Freedom. Slides for Molly's talk are available on her gitlab account. Segment 2 (20:11) Bradley and Karen talk about the keynote and set up the interview. Segment 3 (23:56) Extended interview with Molly from on site at CopyleftConf 2019! Segment 4 (34:06) Bradley and Karen discuss what ideas Molly's interview got them thinking about. Bradley wrote a blog post about Delta's anti-union marketing. (40:50) Molly De Blanc is now an employee at the GNOME Foundation and President of the Open Source Initiative (52:53) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss two additional permissions that can be used to “backport” the GPLv3 Termination provisions to GPLv2 — the Kernel Enforcement Statement Additional Permission, and the Red Hat Cooperation Commitment. A blog post on Conservancy's site summarizes the discussion on this show. Show Notes: Segment 0 (00:35) Bradley mentioned irregardless is not actually a word, but it does appear to be slang, which dates back to 1795! (03:23) The additional permission system was codified as a formal part of GPLv3, but are generally more informal under GPLv2. (05:24) Karen explained what the Principles of Community-Oriented GPL Enforcement. (07:49) Karen mentioned that Daleks terminate! (08:51) Segment 1 (13:04) Bradley mentioned the inbound=outbound FOSS licensing contributor assent system (18:15) Segment 2 (26:10) Karen and Bradley discuss the term “non-defensive” and what it means. Bradley mentioned the Twin Peaks lawsuit as a non-hypothetical case where the RHCC would not apply where GPL enforcement was used by Red Hat itself as a retaliation tactic. (29:23) The Kernel Enforcement Statement and the RHCC are available online. Segment 3 (38:40) The next episode of will be an interview with Molly De Blanc and recording of her keynote at CopyleftConf 2019 Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the details of the completion of the lawsuit (which Conservancy supported) between Christoph Hellwig and VMware in Germany. Show Notes: Segment 0 (00:37) Bradley mentioned the episode of Red Dwarf, White Hole, where the characters are speaking too slowly or two quickly due to time differentials. (01:30) Bradley explained that the Hellwig vs. VMware suit in Germany has concluded. (03:30) German is a civil law legal system. (05:15) Christoph Hellwig announced on his website that he has decided not to appeal. (07:18) Bradley did a technical analysis how much of Christoph's code appeared in the infringing VMware product. (07:50) Till Jaeger was Christoph's lawyer; Till was also the lawyer for Harald Welte's (currently defunct) gpl-violations.org project. (09:04) Segment 1 (09:26) “Trolling” refers to being a non-practicing entity. Patrick McHardy is specifically a practicing entity, since he upstreamed a lot of code in Linux. (09:50) Bradley was thinking of the patent troll, Intellectual Ventures. (10:40) Bradley that the Eastern district of Texas hears many patent cases in the USA. (10:50) Bradley mentioned a This American Life, Episode 411, which discussed patents. Show hosts/producers Laura Sydell and Alex Blumberg visit one of those “empty-but-not” office buildings in the Eastern District of Texas. (11:18) Bradley and Karen wrote about Patrick McHardy's behavior back in July 2016 — Conservancy was the first to talk about it publicly. Bradley sought to prevent the “compliance industrial complex” from using knowledge of Patrick's behavior to unduly scare people. (13:10) Conservancy (with FSF) also published the Principles of Community-Oriented GPL Enforcement (15:10) The rest of the Netfilter team, except for Patrick McHardy, endorsed the Principles. (16:30) The VMware suit started 2015-03-05, and began before Patrick McHardy started his problematic behavior. While the VMware suit was working its way through the court, McHardy had filed many inappropriate lawsuits. (18:30) German court decisions are very rarely published, but thanks to hard work by everyone involved, the appeal decision, and the lower Court's decision (the latter of which was also translated into English.) (27:30) Segment 2 (33:01) In the next episode, Karen will discuss the Kernel Enforcement Statement Additional Permission, and the Red Hat “Cooperation Commitment”. (35:40) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss and critique the new initiative by the Linux Foundation called CommunityBridge. The podcast includes various analysis that expands upon their blog post about Linux Foundation's CommunityBridge. Show Notes: Segment 0 (00:36) Conservancy helped Free Software Foundation and GNOME Foundation begin fiscal sponsorship work. (07:50) Conservancy has always been very coordinated with Software in the Public Interest, which is a FOSS fiscal sponsor that predates Conservancy. (08:26) Conservancy helped NumFocus get started as a fiscal sponsor by providing advice. (08:53) The above are all 501(c)(3) charities, but there are also 501(c)(6) fiscal sponsors, such as Linux Foundation and Eclipse Foundation. (10:00) Bradley mentioned that projects that are forks can end up in different fiscal sponsors, such as Hudson being in Eclipse Foundation, and Jenkins being associated with a Linux Foundation sub-org. (10:30) Bradley mentioned that any project — be it SourceForge, GitHub, or Community Bridge — that attempts to convince FOSS developers to use proprietary software for their projects is immediately suspect (12:00) Open Collective, a for-profit company seeking to do fiscal sponsorship (but attempting to release their code for it) is likely under the worst “competitive” threat from this initiative. (19:50) Segment 1 (21:23) Projects that use CommunityBridge are required to act in the common business interest of the Linux Foundation members. (27:30) Board of Directors seats at the Linux Foundation are for sale, according to their by-laws. (28:50) Bradley advises that you should not put anything copylefted into CommunityBridge — given Linux Foundation's position on copyleft and citing the ArduPilot/DroneCode example. (29:50) CommunityBridge appears to only allow governance based on the “benevolent dictator for life model” (31:40), at least with regard to who controls the money (34:30) Bradley mentioned the LWN article about Community Bridge. (33:22) Segment 2 (36:54) Karen mentioned that CommunityBridge also purports to address diversity and security issues for FOSS projects. (37:00) Bradley mentioned the code hosted on k.sfconservancy.org and also the Reimbursenator project that PSU students wrote. (42:00) Segment 3 (42:44) Bradley and Karen discuss (or, possibly don't) discuss what's coming up on the next episode. Fact of the matter is that this announcement wasn't written yet when we recorded this episode and we weren't sure if 0x65 would be released before or after that announcement was released. We'll be discussing that topic on 0x66. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen interview their own producer, Dan Lynch, on site at Copyleft Conf 2019. Show Notes: Segment 0 (00:46) Karen now teaches teaches a course at Columbia University. (03:40) In addition to being the producer of Free as in Freedom, Dan Lynch was the host of Rat Hole Radio, the co-host of Linux Outlaws, and currently co-hosts Hollywood Outlaws. (04:30) Segment 1 (5:19) Dan helps co-organize Oggcamp which is having its tenth-anniversary event on Saturday 19 October 2019. (08:00) Bradley mentioned the phrase from IT Crowd quote: Did you see that ludicrous display last night? (11:08) Dan talked about The Manchester Ship Canal. (13:16) Dan promoted Hollywood Outlaws where he and his co-host Fab talk about Bosch. (23:18) Dan promoted his own podcast about comics called Tales of the Unattested. (23:27) Dan Lynch has a personal website, which has his blog. (23:55) Bradley referenced the phrase You are no Jack Kennedy which was stated by Bentsen on Wednesday 5 October 1988 during the VP debate between Quayle and Bentsen for the 1988 USA Presidential campaign. Details and background of this are explained by NBC in this story. (26:30) Segment 2 (28:23) Bradley and Karen briefly dissect the interview with Dan. Segment 3 (32:22) Karen and Bradley mention that they'll discuss the Linux Foundation initiative, “Community Bridge” in the next episode. If you want a preview Bradley and Karen's thoughts, you can read their blog post about Linux Foundation's “Community Bridge” initiative. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

In their final installment regarding their joint keynote at FOSDEM 2019, entitled: Can Anyone Live in Full Software Freedom Today?: Confessions of Activists Who Try But Fail to Avoid Proprietary Software, you listeners can hear the final product — a recording of the actual FOSDEM keynote. Afterwards, Karen and Bradley compare notes on what went wrong and what went right (but mostly what went wrong) during the talk. Show Notes: Segment 0 (00:00:35) Bradley and Karen talk logistics of how the talk is embedded in the audio. Segment 1 (00:04:14) The audio in this segment taken directly from the video of Karen and Bradley's FOSDEM 2019 opening keynote, entitled Can Anyone Live in Full Software Freedom Today? Confessions of Activists Who Try But Fail to Avoid Proprietary Software, which was given . If you'd rather watch the video, you can do so via FSODEM's video site in either webm format or in mp4 format. Segment 2 (00:46:01) Karen mentioned “time shifting”, which was permitted for the public, despite accusations of copyright infringement, in the Betamax case. (55:10) Segment 3 (01:05:31) Karen and Bradley mention that the next episode will be an interview with Dan Lynch recorded at CopyleftConf 2019. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen have the last pre-talk installment of discussing the preparation for their joint keynote at FOSDEM 2019, entitled: Can Anyone Live in Full Software Freedom Today?: Confessions of Activists Who Try But Fail to Avoid Proprietary Software. This episode is the third of three episodes where Bradley and Karen record their preparation conversations for this keynote address. In this particular episode, they discuss the issue of letting others use proprietary software on your behalf, the problem of relying too much on that, and then finish up discussing with how they'll include this material into the final talk. Show Notes: Segment 0 (00:34) Karen discussed the idea of a shabbos goy, and the analogy between that and allowing other people use proprietary on your behalf. (02:58) Bradley and Karen discussed that it is equally abhorrent to ask someone else to use proprietary software for you as it is to use yourself, since someone's software freedom is compromised in any event (06:58) Bradley mentioned that he had previously applied to serve on the USA's Internal Revenue Service (IRS)'s Electronic Tax Administration Advisory Committee (ETAAC). Bradley mentioned how sadly the IRS typically accepts people from proprietary software companies like Intuit but has to his knowledge never accepted anyone involved in FOSS software for IRS form preparation (10:02) Bradley mentioned the Free Software PDF fill-in tools evince and flpsed (12:24) Karen stated that Conservancy's policy is that: We care so much about software freedom that we would rather use proprietary software than have someone else lose their software freedom. (15:20) Karen mentioned that her Linux Conf Australia 2019, Right to Not Broadcast, which you can view online. (22:18) Segment 1 (23:15) Bradley mentioned the A-Team line, “I love it when a plan comes together”. (23:23) Bradley and Karen generally discuss the final plans for incorporating this material into the keynote Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen continue the process of preparing their joint keynote at FOSDEM 2019, entitled: Can Anyone Live in Full Software Freedom Today?: Confessions of Activists Who Try But Fail to Avoid Proprietary Software. This episode is the second of three episodes where Bradley and Karen record their preparation conversations for this keynote address. In this particular episode, they discuss the golden age in history when they used very little proprietary software, and then discuss the beginning of their personal Dark Ages of using some proprietary software. Show Notes: Segment 0 (00:35) Bradley mentioned The Who's destruction of their instruments and his discomfort with it in relation to computers. (06:10) Bradley and Karen mentioned their long-time use of the HTC Dream (07:30) Bradley mentioned that he helped start the Replicant project, but his primary contribution was its name. (08:24) Segment 1 (12:34) Karen mentioned the pinball machine that she owns. (12:50) Bradley mentioned the Dead Kennedys album, Give Me Convenience or Give Me Death. (25:10) Karen and Bradley discuss proprietary Javascript. (28:20) This is the screen you get if you attempt to use Google maps without Javascript. (28:45) Karen was wrong about this image no longer appearing. The image linked to here is from the day before our FOSDEM keynote was delivered. (29:55) Bradley and Karen recorded this episode while on site at LinuxConf Australia 2019. They had dinner the night this was recorded at a restaurant called, Dux Dine in Christchurch, NZ. There were, in fact, ducks dining at Dux Dine. (35:07) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen pull back the curtain and begin the process of preparing their joint keynote at FOSDEM 2019, entitled: Can Anyone Live in Full Software Freedom Today?: Confessions of Activists Who Try But Fail to Avoid Proprietary Software. This episode is the first of multiple episodes where Bradley and Karen record their preparation conversations for this keynote address. Show Notes: Segment 0 (00:36) Bradley and Karen discuss the plan to do prep for their FOSDEM keynote “on air” as part of FaiF broadcasts. Segment 1 (07:13) Bradley read out the abstract from Bradley and Karen's keynote, Can Anyone Live in Full Software Freedom Today? Confessions of Activists Who Try But Fail to Avoid Proprietary Software at FOSDEM 2019. (circa 10:00) This started for Bradley with the HTC Dream, and Karen's struggle started with her heart device (10:42) Bradley and Karen discussed how they plan to organize their FOSDEM 2019 joint keynote. Bradley mentioned that if Karen and Bradley recorded an episode of the two of them reading Lorem Ipsum that listeners would likely still listen. Karen disagreed. (33:05) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen return, as promised, in 2018 (just barely)! They discuss the many non-FOSS and otherwise software-freedom-unfriendly licenses that have been promulgated in 2018. Show Notes: Segment 0 (00:36) Bradley and Karen discuss ideas for what to do with the oggcast going forward. Segment 2 (07:49) Bradley mentioned the field of endeavor restriction in Open Source Defintion. (09:20) Bradley mentioned how badly Amazon treats its workers who pack boxes, which was widely reported this month (10:22). Bradley referenced that someone changed attempted to change a license on a project to prohibit use by USA border protection agents. This was the Lerna project, and Bradley wrote a blog post about it earlier this year. (12:14) Bradley mentioned the controversy about the new MongoDB license, the SS Public License, which Bradley also wrote a blog post about earlier this year (14:09) karen reports that many people at the Sustain OSS Conference were surprised that sustaining the idelogy of software freedom was something that people value. (27:10) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

We talk about our recent trip to FOSDEM, we discuss the pros and cons of permissive licensing, cover the installation of OpenBSD on a dedibox with full-disk encryption, the new Lumina guide repository, and we explain ZFS vs. OpenZFS. This episode was brought to you by Headlines [FOSDEM Trip report] Your BSDNow hosts were both at FOSDEM in Brussels, Belgium over the weekend. On the friday before FOSDEM, we held a FreeBSD devsummit (3rd consecutive year), sponsored by the FreeBSD Foundation and organized by Benedict (with the help from Kristof Provost, who did it in previous years but could not make it this year). We had 21 people attend, a good mixture of FreeBSD committers (mostly ports) and guests. After introductions, we collected topics and discussed various topics, including a new plan for a future FreeBSD release roadmap (more frequent releases, so that features from HEAD can be tried out earlier in RELEASES). The devsummit concluded with a nice dinner in a nearby restaurant. On Saturday, first day of FOSDEM, we set up the FreeBSD Foundation table with flyers, stickers, FreeBSD Journal print editions, and a small RPI 3 demo system that Deb Goodkin brought. Our table was located next to the Illumos table like last year. This allowed us to continue the good relationship that we have with the Illumos people and Allan helped a little bit getting bhyve to run on Illumos with UEFI. Meanwhile, our table was visited by a lot of people who would ask questions about FreeBSD, take info material, or talk about their use cases. We were busy refilling the table throughout the day and luckily, we had many helpers at the table. Some items we had ran out in the early afternoon, an indicator of how popular they were. Saturday also featured a BSD devroom (https://twitter.com/fosdembsd), organized by Rodrigo Osorio. You can find the list of talks and the recordings on the BSD Devroom schedule (https://fosdem.org/2018/schedule/track/bsd/). The room was very crowded and popular. Deb Goodkin gave the opening talk with an overview of what the Foundation is doing to change the world. Other speakers from various BSD projects presented their talks after that with a range of topics. Among them, Allan gave his talk about ZFS: Advanced Integration (https://fosdem.org/2018/schedule/event/zfs_advanced_integration/), while Benedict presented his Reflections on Teaching a Unix Class With FreeBSD (https://fosdem.org/2018/schedule/event/reflections_on_reaching_unix_class_with_freebsd/). Sunday was just as busy on the FreeBSD table as Saturday and we finally ran out of stickers and some other goodies. We were happy with the results of the two days. Some very interesting conversations at the table about FreeBSD took place, some of which we're going to follow up afterwards. Check out the FOSDEM schedule as many talk recordings are already available, and especially the ones from the BSD devroom if you could not attend the conference. We would like to thank everyone who attended the FreeBSD devsummit, who helped out at the FreeBSD table and organized the BSD devroom. Also, thanks to all the speakers, organizers, and helping hands making FOSDEM another success this year. *** NetBSD kernel wscons IOCTL vulnerable bug class (http://blog.infosectcbr.com.au/2018/01/netbsd-kernel-wscons-ioctl-vulnerable.html) I discovered this bug class during the InfoSect public code review session we ran looking specifically at the NetBSD kernel. I found a couple of these bugs and then after the session was complete, I went back and realised the same bug was scattered in other drivers. In total, 17 instances of this vulnerability and its variants were discovered. In all fairness, I came across this bug class during my kernel audits in 2002 and most instances were patched. It just seems there are more bugs now in NetBSD while OpenBSD and FreeBSD have practically eliminated them. See slide 41 in http://www.blackhat.com/presentations/bh-usa-03/bh-us-03-cesare.pdf (http://www.blackhat.com/presentations/bh-usa-03/bh-us-03-cesare.pdf) for exactly the same bug (class) 16 years ago. The format of the this blog post is as follows: Introduction Example of the Bug Class How to Fix How to Detect Automatically with Coccinelle More Bugs Conclusion These source files had bugs ./dev/tc/tfb.c ./dev/ic/bt485.c ./dev/pci/radeonfb.c ./dev/ic/sti.c ./dev/sbus/tcx.c ./dev/tc/mfb.c ./dev/tc/sfb.c ./dev/tc/stic.c ./dev/tc/cfb.c ./dev/tc/xcfb.c ./dev/tc/sfbplus.c ./arch/arm/allwinner/awin_debe.c ./arch/arm/iomd/vidcvideo.c ./arch/pmax/ibus/pm.c ./dev/ic/igfsb.c ./dev/ic/bt463.c ./arch/luna68k/dev/lunafb.c Reporting of the bugs was easy. In less than a week from reporting the specific instances of each bug, patches were committed into the mainline kernel. Thanks to Luke Mewburn from NetBSD for coming to the code review session at InfoSect and coordinating with the NetBSD security team. The patches to fix these issues are in NetBSD: https://mail-index.netbsd.org/source-changes/2018/01/24/msg091428.html (https://mail-index.netbsd.org/source-changes/2018/01/24/msg091428.html) "Permissive licensing is wrong!” – Is it? (https://eerielinux.wordpress.com/2017/11/25/permissive-licensing-is-wrong-is-it-1-2/) A few weeks ago I've been attacked by some GNU zealots on a German tech site after speaking in favor of permissive licenses. Unfortunately a discussion was not possible there because that would require the will to actually communicate instead of simply accusing the other side of vile motives. Since I actually do care about this topic and a reader asked for a post about it in comments a while ago, here we go. This first part tries to sum up the most important things around the topic. I deliberately aim for an objective overview that tries not to be one-sided. The second part will then contain my points in defence of permissive licensing. Why license software at all? Licenses exist for reasons of protection. If you're the author/inventor of some software, a story or whatever product, you get to decide what to do with it. You can keep it for yourself or you can give it away. If you decide for the latter, you have to decide who may use it and in which way(s). In case you intend to give it to a (potentially) large group of people, you may not want to be asked for permission to xyz by everybody. That's when you decide to write a license which states what you are allowing and explicitly disallowing. Most of the well-known commercial licenses focus on what you're not allowed to do (usually things like copying, disassembling, etc.). Open source licenses on the other hand are meant to grant the user rights (e.g. the right to distribute) while reserving some rights or only giving permission under certain conditions – and they usually make you claim responsibility for using the software. For these reasons licenses can actually be a good thing! If you got an unlicensed piece of code, you're not legally allowed to do anything with it without getting the author's permission first. And even if you got that permission, your project would be risky, since the author can withdraw it later. A proper license protects both parties. The author doesn't get his mail account full of email asking for permission, he's save from legal trouble if his code breaks anything for you and at the same time you have legal certainty when you decide to put the code to long-term use. Permissive vs. Copyleft (in a nutshell) In short terms, permissive licensing usually goes like this: “Here you are, have fun. Oh, and don't sue me if it does something else than what you expect!” Yes, it's that easy and there's little to dispute over. Copyleft on the other side sounds like this (if you ask somebody in favor of Copyleft): “Sure, you can use it, it's free. Just keep it free, ok?”. Also quite simple. And not too bad, eh? Other people however read the same thing like this: “Yes, you're free to use it. Just read these ten pages of legalese and be dead certain that you comply. If you got something wrong, we will absolutely make you regret it.” The GNU Public license (GPL) The most popular copyleft license in use is the GPL (in various versions) (https://www.gnu.org/licenses/gpl.html). It got more and more complex with each version – and to be fair, it had to, because it was necessary to react to new threats and loop holes that were found later. The GNU project states that they are committed to protect what they call the four freedoms of free software: the freedom to use the software for any purpose the freedom to change the software to suit your needs the freedom to share the software with your friends and neighbors the freedom to share the changes you make These are freedoms that every supporter of open source software should be able to agree with. So what's the deal with all the hostility and fighting between the two camps? Let's take a look at a permissive license, too. The BSD license Unlike the GPL, the BSD family of licenses begun with a rather simple license that span four rules (“original BSD license”). It was later revised and reduced to three (“modified BSD license”). And the modern BSD license that e.g. FreeBSD uses is even just two (“simplified BSD license”). Did you read the GPLv3 that I linked to above? If you are using GPL'd code you really should. In case you don't feel like reading all of it, at least take a look and grasp how long that text is. Now compare it to the complete modern BSD license (https://opensource.org/licenses/bsd-license.php). What's the problem? There are essentially two problems that cause all the trouble. The first one is the question of what should be subject to the freedom that we're talking about. And closely related, the second one is where that freedom needs to end. Ironically both camps claim that freedom is the one important thing and it must not be restricted. The GPL is meant to protect the freedom of the software and enforces the availability of the source code, hence limiting the freedom of actual persons. BSD on the other hand is meant to protect the freedom of human beings who should be able to use the software as they see fit – even if that means closing down former open source code! The GNU camp taunts permissive licenses as being “lax” for not providing the protection that they want. The other camp points out that the GPL is a complex monster and that it is virulent in nature: Since it's very strict in a lot of areas, it's incompatible with many other licenses. This makes it complicated to mix GPL and non-GPL code and in the cases where it's legally possible, the GPL's terms will take precedence and necessarily be in effect for the whole combined work. Who's right? That totally depends on what you want to achieve. There are pros and cons to both – and in fact we're only looking at the big picture here. There's also e.g. the Apache license which is often deemed as kind of middle ground. Then you may want to consider the difference between weak (e.g. LGPL) as well as strong copyleft (GPL). Licensing is a potentially huge topic. But let's keep it simple here because the exact details are actually not necessary to understand the essence of our topic. In the next post I'll present my stance on why permissive licensing is a good thing and copyleft is more problematic than many people may think. “Permissive licensing is wrong?” – No it's not! (https://eerielinux.wordpress.com/2018/01/25/permissive-licensing-is-wrong-no-its-not-2-2/) The previous post gave a short introduction into the topic of software licenses, focusing on the GPL vs. BSD discussion. This one is basically my response to some typical arguments I've seen from people who seem to loathe permissive licensing. I'll write this in dialog style, hoping that this makes it a little lighter to read. Roundup Install OpenBSD on dedibox with full-disk encryption (https://poolp.org/posts/2018-01-29/install-openbsd-on-dedibox-with-full-disk-encryption/) TL;DR: I run several "dedibox" servers at online.net, all powered by OpenBSD. OpenBSD is not officially supported so you have to work-around. Running full-disk encrypted OpenBSD there is a piece of cake. As a bonus, my first steps within a brand new booted machine ;-) Step #0: choosing your server OpenBSD is not officially supported, I can't guarantee that this will work for you on any kind of server online.net provides, however I've been running https://poolp.org on OpenBSD there since 2008, only switching machines as they were getting a bit old and new offers came up. Currently, I'm running two SC 2016 (SATA) and one XC 2016 (SSD) boxes, all three running OpenBSD reliably ever since I installed them. Recently I've been willing to reinstall the XC one after I did some experiments that turned it into a FrankenBSD, so this was the right occasion to document how I do it for future references. I wrote an article similar to this a few years ago relying on qemu to install to the disk, since then online.net provided access to a virtual serial console accessed within the browser, making it much more convenient to install without the qemu indirection which hid the NIC devices and disks duid and required tricks. The method I currently use is a mix and adaptation from the techniques described in https://www.2f30.org/guides/openbsd-dedibox.html to boot the installer, and the technique described in https://geekyschmidt.com/2011/01/19/configuring-openbsd-softraid-fo-encryption.html to setup the crypto slice. Step #1: boot to rescue mode Step #2: boot to the installer Step #3: prepare softraid Step #4: reboot to encrypted OpenBSD system Bonus: further tightening your system enable doas disable the root account update system with syspatch add my ssh public key to my ~/.ssh/authorized_keys disable password authentication within ssh reboot so you boot on a brand new up-to-date system with latest stable kernel VOILA ! January 2018 Development Projects Update (https://www.freebsdfoundation.org/blog/january-2018-development-projects-update/) Spectre and Meltdown in FreeBSD Issues affecting most CPUs used in servers, desktops, laptops, and mobile devices are in the news. These hardware vulnerabilities, known by the code-names “Meltdown” and “Spectre”, allow malicious programs to read data to which they should not have access. This potentially includes credentials, cryptographic material, or other secrets. They were originally identified by a researcher from Google's Project Zero, and were also independently discovered by researchers and academics from Cyberus Technology, Graz University of Technology, the University of Pennsylvania, the University of Maryland, Rambus, the University of Adelaide and Data61. These vulnerabilities affect many CPU architectures supported by FreeBSD, but the 64-bit x86 family of processors from Intel and AMD are the most widely used, and are a high priority for software changes to mitigate the effects of Meltdown and Spectre. In particular, the Meltdown issue affects Intel CPUs and may be used to extract secret data from the running kernel, and therefore, is the most important issue to address. The FreeBSD Foundation collaborates with Intel, and under this relationship participated in a briefing to understand the details of these issues and plan the mitigations to be applied to the x86 architectures supported by FreeBSD. We also made arrangements to have FreeBSD's security officer join me in the briefing. It is through the generous support of the Foundation's donors that we are able to dedicate resources to focus on these issues on demand as they arise. Foundation staff member Konstantin (Kostik) Belousov is an expert on FreeBSD's Virtual Memory (VM) system as well as low-level x86 details, and is developing the x86 kernel mitigations for FreeBSD. The mitigation for Meltdown is known as Page Table Isolation (PTI). Kostik created a PTI implementation which was initially committed in mid-January and is available in the FreeBSD-CURRENT development repository. This is the same approach used by the Linux kernel to mitigate Meltdown. One of the drawbacks of the PTI mitigation is that it incurs a performance regression. Kostik recently reworked FreeBSD's use of Process-Context Identifiers (PCID) in order to regain some of the performance loss incurred by PTI. This change is also now available in FreeBSD-CURRENT. The issue known as Spectre comes in two variants, and variant 2 is the more troubling and pressing one. It may be mitigated in one of two ways: by using a technique called “retpoline” in the compiler, or by making use of a CPU feature introduced in a processor microcode update. Both options are under active development. Kostik's change to implement the CPU-based mitigation is currently in review. Unfortunately, it introduces a significant performance penalty and alternatives are preferred, if available. For most cases, the compiler-based retpoline mitigation is likely to be the chosen mitigation. Having switched to the Clang compiler for the base system and most of the ports collection some years ago, FreeBSD is well-positioned to deploy Clang-based mitigations. FreeBSD developer Dimitry Andric is spearheading the update of Clang/LLVM in FreeBSD to version 6.0 in anticipation of its official release; FreeBSD-CURRENT now includes an interim snapshot. I have been assisting with the import, particularly with respect to LLVM's lld linker, and will support the integration of retpoline. This support is expected to be merged into FreeBSD in the coming weeks. The Foundation's co-op students have also participated in the response to these vulnerabilities. Mitchell Horne developed the patch to control the PTI mitigation default setting, while Arshan Khanifar benchmarked the performance impact of the in-progress mitigation patches. In addition, Arshan and Mitchell each developed changes to FreeBSD's tool chain to support the full set of mitigations that will be applied. These mitigations will continue be tested, benchmarked, and refined in FreeBSD-CURRENT before being merged into stable branches and then being made available as updates to FreeBSD releases. Details on the timing of these merges and releases will be shared as they become available. I would like to acknowledge all of those in the FreeBSD community who have participated in FreeBSD's response to Meltdown and Spectre, for testing, reviewing, and coordinating x86 mitigations, for developing mitigations for other processor architectures and for the Bhyve hypervisor, and for working on the toolchain-based mitigations. Guides: Getting Started & Lumina Theme Submissions (https://lumina-desktop.org/guides-getting-started-lumina-themes/) I am pleased to announce the beginning of a new sub-series of blog posts for the Lumina project: Guides! The TrueOS/Lumina projects want to support our users as they use Lumina or experiment with TrueOS. To that end, we've recently set up a central repository for our users to share instructions or other “how-to” guides with each other! Project developers and contributors will also submit guides to the repository on occasion, but the overall goal is to provide a simple hub for instructions written by any Lumina or TrueOS user. This will make it easier for users to not only find a “how-to” for some procedure, but also a very easy way to “give back” to the community by writing simple instructions or more detailed guides. Guides Repository Our first guide to get the whole thing started was created by the TrueOS Linebacker (https://discourse.trueos.org/t/introducing-the-trueos-linebacker/991) (with technical assistance from our own q5sys). In this guide, Terry Tate will walk you through the steps necessary to submit new wallpaper images to the Lumina Themes collection. This procedure is fully documented with screenshots every step of the way, walking you through a simple procedure that only requires a web browser and a Github account! Guide: Lumina Themes Submissions (https://github.com/trueos/guides/blob/master/lumina-themes-submissions/readme.md) The end result of this guide was that Terry Tate was able to submit this cool new “Lunar-4K” wallpaper to the “lumina-nature” collection. TrueOS Community Guides (https://github.com/trueos/guides/tree/master) ZFS vs. OpenZFS (by Michael Dexter) (https://www.ixsystems.com/blog/zfs-vs-openzfs/) You've probably heard us say a mix of “ZFS” and “OpenZFS” and an explanation is long-overdue. Our Senior Analyst clears up what ZFS and OpenZFS refer to and how they differ. I admit that we geeks tend to get caught up in the nuts and bolts of enterprise storage and overlook the more obvious questions that users might have. You've probably noticed that this blog and the FreeNAS blog refer to “ZFS” and “OpenZFS” seemingly at random when talking about the amazing file system at the heart of FreeNAS and every storage product that iXsystems sells. I will do my best to clarify what exactly these two terms refer to. From its inception, “ZFS” has referred to the “Zettabyte File System” developed at Sun Microsystems and published under the CDDL Open Source license in 2005 as part of the OpenSolaris operating system. ZFS was revolutionary for completely decoupling the file system from specialized storage hardware and even a specific computer platform. The portable nature and advanced features of ZFS led FreeBSD, Linux, and even Apple developers to start porting ZFS to their operating systems and by 2008, FreeBSD shipped with ZFS in the 7.0 release. For the first time, ZFS empowered users of any budget with enterprise-class scalability and data integrity and management features like checksumming, compression and snapshotting, and those features remain unrivaled at any price to this day. On any ZFS platform, administrators use the zpool and zfs utilities to configure and manage their storage devices and file systems respectively. Both commands employ a user-friendly syntax such as‘zfs create mypool/mydataset' and I welcome you to watch the appropriately-titled webinar “Why we love ZFS & you should too” or try a completely-graphical ZFS experience with FreeNAS. Yes, ZFS is really as good as people say it is. After enjoying nearly a decade of refinement by a growing group of developers around the world, ZFS became the property of database vendor Oracle, which ceased public development of both ZFS and OpenSolaris in 2010. Disappointed but undeterred, a group of OpenSolaris users and developers forked the last public release of OpenSolaris as the Illumos project. To this day, Illumos represents the official upstream home of the Open Source OpenSolaris technologies, including ZFS. The Illumos project enjoys healthy vendor and user participation but the portable nature and compelling features of ZFS soon produced far more ZFS users than Illumos users around the world. While most if not all users of Illumos and its derivatives are ZFS users, the majority of ZFS users are not Illumos users, thanks significantly in part to FreeNAS which uses the FreeBSD operating system. This imbalance plus several successful ZFS Day events led ZFS co-founder Matt Ahrens and a group of ZFS developers to announce the OpenZFS project, which would remain a part of the Illumos code base but would be free to coordinate development efforts and events around their favorite file system. ZFS Day has grown into the two-day OpenZFS Developer Summit and is stronger than ever, a testament to the passion and dedication of the OpenZFS community. Oracle has steadily continued to develop its own proprietary branch of ZFS and Matt Ahrens points out that over 50% of the original OpenSolaris ZFS code has been replaced in OpenZFS with community contributions. This means that there are, sadly, two politically and technologically-incompatible branches of “ZFS” but fortunately, OpenZFS is orders of magnitude more popular thanks to its open nature. The two projects should be referred to as “Oracle ZFS” and “OpenZFS” to distinguish them as development efforts, but the user still types the ‘zfs' command, which on FreeBSD relies on the ‘zfs.ko' kernel module. My impression is that the terms of the CDDL license under which the OpenZFS branch of ZFS is published protects its users from any patent and trademark risks. Hopefully, this all helps you distinguish the OpenZFS project from the ZFS technology. Beastie Bits Explaining Shell (https://explainshell.com/) OPNsense® 18.1 Released (https://opnsense.org/opnsense-18-1-released/) “SSH Mastery 2/e” copyedits back (https://blather.michaelwlucas.com/archives/3104) Sponsoring a Scam (https://blather.michaelwlucas.com/archives/3106) Thursday, February 8, 2018 - Come to Netflix to talk about FreeBSD (https://www.meetup.com/BAFUG-Bay-Area-FreeBSD-User-Group/events/246623825/) BSD User Group meeting in Stockholm: March 22, 17:30 - 21:00 (https://www.meetup.com/BSD-Users-Stockholm/events/247552279/) FreeBSD Flavoured talks from Linux.conf.au: You can't unit test C, right? (https://www.youtube.com/watch?v=z-uWt5wVVkU) and A Brief History of I/O (https://www.youtube.com/watch?v=qAhZEI_6lbc) EuroBSDcon 2018 website is up (https://2018.eurobsdcon.org/) Full day bhyvecon Tokyo, Japan, March 9, 2018 (http://bhyvecon.org/) *** Feedback/Questions Thomas - freebsd installer improvements (http://dpaste.com/3G2F7RC#wrap) Mohammad - FreeBSD 11 installation from a read only rescue disk (http://dpaste.com/0HGK3FQ#wrap) Stan - Follow up on guide you covered (http://dpaste.com/2S169SH#wrap) Jalal - couple questions (http://dpaste.com/35N8QXP#wrap)

Bradley and Karen discuss Conservancy's ContractPatch Initiative that will help Free Software developers negotiate their agreements with employers. Show Notes: Segment 0 (00:38) Software Freedom Conservancy has two blog posts and a mailing list to discuss the Contract Patch initiative (02:40). Bradley searched for the NPR story he mentioned but just couldn't find it, but he did fine a similar one covering terms of service agreements (08:30) Karen mentioned the the Outreachy Project of Conservancy. (09:30) The Google Map API ToS states that you have to pay for it after a certain amount of usage (17:30) Bradley mentioned the book, What Color Is Your Parachute? (24:30) The “put it in writing” commercials from AT&T and MCI. (46:44) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss Conservancy's conference trips and presentations during the first half of 2016. Show Notes: Segment 0 (00:38) Bradley attended and spoke at FOSDEM 2016 and LinuxConf Australia 2016 (03:10) Bradley and Karen co-coordinated the FOSDEM 2016 Legal and Policy Issues DevRoom (04:43) Tom Marble did an interview-format discussion with Richard M. Stallman at FOSDEM 2016 (04:55) Bradley gave two talks at FOSDEM 2016, Copyleft For the Next Decade: A Comprehensive Plan for the GPL and A Beautiful Build: Releasing Linux Source Correctly (06:40) Richard Fontana gave a talk at FOSDEM 2016 entitled Open source foundations: threat or menace? (08:15) The Doge take on FOSDEM 2016 Legal and Policy Issues DevRoom was Much politics. Many peoples. (11:00) There was a Conservancy Supporter event at the Novotel Grand Place in Brussels at FOSDEM 2016. (14:00) Bradley gave a talk at LCA 2016. (15:20) Karen gave the closing keynote at LibrePlanet 2016, entitled Companies, free software, and you . (16:54) Karen Sandler gave a talk at the Linux Foundation's Embedded Linux Conference 2016 entitled Tales of Enforcement (27:00) Karen gave a talk at

Bradley and Karen give a basic introduction of copyright licensing of Open Source and Free Software. Show Notes: Segment 0 (00:35) Bradley mentioned the phrase “fixed in a tangible medium” which appears in the USA copyright law. (03:10) Bradley mentioned the Sherman Antitrust act. (04:05) Bradley mentioned the card game Pit (04:15) Bradley jokingly quoted Mit Romney's famous gaffe, “Corporations are people, my friend.” (04:44) Bradley read Title 17, the USA Copyright act many times. (06:50) Bradley mentioned the court case, UNIX System Laboratories, Inc. v. Berkeley Software Design, Inc., which resulted in releasing the parts of BSD that could be Free Software. (12:27) Bradley mentioned the FSF's Free Software Definition (13:11) Bradley mentioned OSI's Open Source Definition (13:16) Apparently, the problem of categorization is called Categorization in Philosophy. (14:30) The issue of Open Source not being trademarked is discussed in this essay by Richard Stallman. (15:44) The basic categorizations of types of FLOSS licenses are copyleft and non-copyleft. Karen suggests reading GPLv2 and GPLv3. (39:31) Bradley made a crude drawing of the spectrum of licenses. (40:20) Bradley mentioned the The Principles of Community-Oriented GPL Enforcement (55:40) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the plan for restarting Free as in Freedom and plans for episodes to come. Show Notes: Segment 0 (00:36) Bradley said in the before time — in the long long ago, which is a reference to the South Park parody of the ST:TOS episode, Miri (01:30) Bradley mentioned when Karen Sandler left the GNOME Foundation and took over Bradley's old job as Executive Director of Conservancy. (02:20) Karen mentioned that Bradley used to be Executive Director of the Free Software Foundation, a position now held by John Sullivan. (03:25) Dan blogged about his illness, details of scheduling surgery, which he occurred successfully. (10:28) Karen mentioned the Conservancy Supporter program discussed in detail on Episode 0x57. (12:40) Bradley mentioned the short lived Jon Masters Linux Kernel Mailing List Summary Podcast. (14:45) Karen and Bradley discussed Video Killed the Radio Star by the Buggles, and Bradley attempted to mention this version which he likes better. (17:36) Bradley mentioned Kantian Ethics (20:05) Bradley mentioned the Portlanda skit, Rent it Out from S04E02 (20:24) Karen mentioned WellDeserved: A Marketplace for Privilege (20:38) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss Conservancy's Debian Copyright Aggregation project. (Note: While it was released just after DebConf16, this episode was recorded well before DebConf16; the discussions about DebConf refer to DebConf15.) Show Notes: Segment 0 (00:38) Note: While it was released just after DebConf16, this episode was recorded well before DebConf16; the discussions about DebConf refer to DebConf15. Bradley mentioned his talk at DebConf. This was recorded before DebConf 16, so Bradley is talking about DebConf 15, which was summarized in this blog post and his keynote from DebConf15. A video of that talk is available. (02:00) Bradley mentioned this bug about the copyright notice on the Debian website (07:47) Ian Jackson asked about bequeathing copyright at Bradley's talk. (15:45) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Free as in Freedom host Christopher Allan Webber interviews Karen Sandler and Bradley Kuhn about their work on copyleft and at Software Freedom Conservancy. You can become a Supporter of this work! Show Notes: Bradley mentioned Cygnus Solutions, ultimately acquired by Red Hat, which was an early for-profit supporter of copylefted projects. Bradley and Karen discussed the VMware lawsuit. Chris Webber wrote this blog post in response to a Shane Curcuru, who is VP of Brand Management at the Apache Software Foundation, anti-copyleft talk at OSCON 2015. Shane's talk is consistent with Apache Software Foundation's historical and recent anti-copyleft positions (12:23) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the VMware lawsuit that Software Freedom Conservancy is funding. Show Notes: Bradley and Karen discuss the lawsuit that Christoph Hellwig filed. (07:37) Karen mentioned her LibrePlanet keynote about the VMware lawsuit. (21:30) Bradley's talk at LinuxConf Australia 2015, Considering The Future of Copyleft, is available online. (22:04) Bradley mentioned the discussion on pump.io about NPR fundraisers. (24:23) Bradley mentioned a Debian 8 release party at LinuxFest Northwest, which Microsoft didn't invite him to, since he wasn't willing to give Microsoft his contact info for marketing purposes. (29:16) Karen and Bradley promoted the Conservancy supporter program (31:40) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen interview Nick Coghlan, who works onn development and test infrastructure for Red Hat and is heavily involved with the Python community. Show Notes: Segment 0 (00:00:35) Bradley and Karen interviewed Nick Coghlan who works for Red Hat and contributes to various Open Source and Free Software projects such as Python. Nick discussed his work on the infrastructure team at Red Hat, and his advocacy of Kallithea for use for the CPython project. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen interview Carol Smith, Programs and Open Source Community Manager of Google Summer of Code about the program and its policies and procedures. Show Notes: Segment 0 (00:00:35) Bradley encourages those who attend FOSDEM 2015 to attend sign up to attend the Supporter Night Event on 30 January 2015 in Brussels, Belgium. Segment 1 (00:50:11) More Show notes for this one coming soon! Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss what plagiarism is (or isn't) and how it interacts with copyleft licenses. Show Notes: Segment 0 (00:00:37) Please donate to to send Dan to a conference. There's a progress bar on faif.us now. You can also donate to support Software Freedom Conservancy, where Bradley and Karen work, by becoming a supporter. Karen mentioned her blog post about the supporter program. (00:08:30) Bradley mentioned his blog post about the supporter program as well. (00:09:30) Segment 1 (00:16:16) Bradley and Karen pick up on a topic original discussed in Segment 1 of FaiF 0x02. (00:16:50) Bradley discussed the Laurie Stearns' article from the California Law Review, entitled Copy Wrong: Plagiarism, Process, Property, and the Law (00:23:50) Bradley mentioned The GNOME Foundation Copyright Assignment Guidelines that he co-authored. (00:28:05) Bradley mentioned the Doris Kearns Goodwin Plagiarism controversy, and how it would have been simply redressed if the material she reused had been copylefted. (00:29:26) Karen mentioned that Flickr made different policies for CC-BY-SA'd works when selling printed versions. (32:30) Bradley mentioned that even software freedom advocates just comply with the copyleft licenses and don't work collaboratively, particularly during hostile forks, using Conservancy's Kallithea project as an example. (00:35:25) Bradley reiterated a point he made in FaiF 0x08, where he discussed that Linus Torvalds switched to GPL for Linux because he realized non-commercial restrictions weren't appropriate. (00:37:50) Bradley mentioned the hostile fork of GCC called egcs. The H-Online years later wrote a long article that discussed the egcs fork egcs fork. (00:39:46) Bradley mentioned that plagiarism is ultimately about attribution, and modern DVCS systems makes attribution easy and renders plagiarism impossible (if DVCS logs are accurate). (00:44:15) Bradley mentioned that he continually has learned the lesson that if you let your employer keep copyright, you lose everything you had when you switch employers (if the work isn't copylefted). (00:47:00) Bradley discussed the methods of attribution required in GPLv3. (00:50:05) Bradley mentioned that copyright notices are the primary method of attribution in copyleft licenses, and even non-copyleft ones too. (00:53:19) Karen discussed the attribution requirements in text of CC-BY-SA 4.0. (00:53:49) Bradley wants to do a whole FaiF show about how CC-BY-SA may not be a true copyleft since it has no source code requirement (00:54:40) Bradley mentioned the “fake name” that film directors use when they wish to disavow a work they aren't happy with. The name is, in fact, Alan Smithee, and indeed the 1984 film Dune lists Smithee as a director even though David Lynch is known publicly to be the director. (00:58:40) Bradley mentioned the unfair accusations against Red Hat when they stopped publishing their internal Linux Git repository and instead released a more standard ChangeLog. (01:05:30) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen play and discuss Stefano Zacchiroli's talk entitled Legal issues from a radical community angle that he gave 12:00 European/Central time on Sunday 2 February 2014 at FOSDEM 2014. Show Notes: Segment 0 (00:00:35) Karen and Bradley introduce the talk. Segment 1 (00:02:38) Stefano Zacchiroli's talk entitled Legal issues from a radical community angle . You can watch the video instead of listening to our audio and/or follow along with Zach's slides. Segment 2 (00:53:17) Please note: Bradley and Karen recorded these comments before the init system coupling referendum completed, which is why Karen and Bradley don't discuss it. However, their comments about the Debian democratic process are highly relevant to the recent vote. Also, Bradley discussed his views on that specific issue as a guest co-host on Linux Outlaws, Episode 368. Bradley and Karen discussed SPI as Debian's fiscal sponsor and used a few terms like grantor/grantee (01:01:20) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen play and discuss Pam Chestek's talk entitled Why Licenses Requiring Use of Trademarks are Non-Free that she gave on Sunday 2 February 2014 at FOSDEM 2014. Show Notes: Segment 0 (00:00:34) You can donate now to send Producer Dan Lynch to a Free Software conference. Donations will be made to Conservancy and any proceeds raised beyond the amount needed to send Dan to a conference will support Conservancy generally. (05:30) Dan will of course need to follow Conservancy's travel policy since Conservancy will fund his travel. (06:50) Bradley discussed the backstory on the Groupon attempt to steal GNOME's name. GNOME Foundation had to go public to raise funds to fight Groupon (10:05) Segment 1 (00:13:26) Pam Chestek gives a talk entitled Why Licenses Requiring Use of Trademarks are Non-Free. You can watch the video instead of listening to our audio and follow along with Pam's slides. Segment 2 (01:00:37) Bradley mentioned Pam's talk from the previous year, which was played on 0x3C. (01:01:32) Bradley mentioned that GPLv3§7 allows for removal of additional restrictions that abuse that clause of GPLv3. (01:04:24) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Karen and Bradley interview Richard M. Stallman on the occasion of the 30th Anniversary of the GNU Project. Note: Episode 0x5B was released out of sequence, but they are in the order of release date on faif.us (rather than numerical order by episode number). Show Notes: Segment 0 (00:34) Note: Episode 0x5B was released out of sequence, but they are in the order of release date on faif.us (rather than numerical order by episode number). Bradley and Karen introduce the interview. Segment 1 (01:20) This segment is an interview with Richard M. Stallman on the occasion of GNU's thirtieth anniversary. RMS mentioned the LibreJS project. (26:10) Segment 2 (33:58) Bradley and Karen discuss the interview. Bradley mis-rememered, RMS said he would start on Thanksgiving in the original announcement (38.40). Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Karen and Bradley announce Conservancy's DMCA filing and Conservancy and FSF's joint launch of the copyleft.org project, and then discuss Eileen Evans' FOSDEM 2014 talk, entitled Licensing Models and Building an Open Source Community. Show Notes: Segment 0 (00:36) Conservancy file a DMCA petition regarding so-called “Smart TVs”. (02:00) Bradley mentioned the magic marker that was as circumvention technique under DMCA. Here's an amusing joke press release about the issue. (03:10) There isn't much documentation online of Bruce Perens live DMCA violation, but this article appears to be the main one on the subject, and there is also this interview (06:46). Bradley and Karen talked about the joint FSF/Conservancy copyleft.org announcement. (09:10) Bradley first pulled together the materials for copyleft.org for FSF's CLE seminars, particularly the one in March 2014. (10:00) Karen noted that Conservancy donated the time to write up a pristine example of good complete, corresponding source code for a GPL'd product. (11:30) Bradley discussed the incorrect GPLv2§2(a) violation accusations that some made against Red Hat regarding its changes to its publication of RHEL's Linux fork. (12:00) Karen and Bradley encouraged listeners to submit talk proposals for the FOSDEM 2015 Legal and Policy Issues DevRoom (15:03) Segment 1 (19:38) This is a recording of Eileen Evans' FOSDEM 2014 talk, entitled Licensing Models and Building an Open Source Community. If you'd rather watch the video, which includes the slides from her talk, it's available on FOSDEM's site. Segment 2 (46:40) Bradley and Karen discuss Eileen's talk. Bradley mentioned the OpenStack CLA fight, which was covered in a panel discussion on FaiF 0x4B. (56:16) Karen mentioned the 501(c)(6) issues that OpenStack Foundation has faced, which were discussed already on FaiF 0x4E. (56:34) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Note: Episode 0x5A was released out of sequence, but they are in the order of release date on faif.us (rather than numerical order). Karen and Bradley discuss connections between the so-called “Gamergate” controversy and how it relates to the Free Software community and a few obvious legal issues. Show Notes: Segment 0 (00:37) Karen asked if Bradley had heard of the Gamergate situation. (01:30) Matthew Garrett wrote a blog post regarding this topic entitled Actions have consequences (or: why I'm not fixing Intel's bugs any more) (10:23) Mathew was attacked on LKML about this blog post (10:50) Lennart Poettering also wrote an essay recently about aggression and attacking people in Free Software communities. (12:12) Karen mentioned the harassment Kathy Sierra faced in the late 2000s. (13:00) Bradley called out Linux Foundation to ask why they tacitly support the bad behavior by its employees and others in the Linux Project (14:35, 31:10) Bradley mentioned that Antti Aumo in his LinuxCon Europe 2011 keynote, said that a great thing about the Internet of Things is that you can put a lock on your fridge when the wife's on a diet. (16:32) Bradley mentioned the Eddie Murphy's Saturday Night Live skit, White Like Me, which according to the transcript, originally aired on 1984-12-15 on SNL. (24:45) Bradley mentioned FaiF 0x13, which discussed torts and why they're important. (29:50) Bradley wrote a blog post about Bradley mentioned his blog post about John Oliver's discussion of the Miss America Pageant (43:30) Bradley suggested that Intel should have instead given the Gamasutra money to Society of Women Engineers Scholarship fund. (45:30) Karen mentioned the statement Intel published a statement regarding the situation. (47:10) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss and criticize comments made by Linus Torvalds at his Q&A during DebConf 2014 in Portland, OR on 29 August 2014. Show Notes: Segment 0 (00:37) Bradley and Karen discuss the Q&A with Linus Torvalds at DebConf 2014 in Portland, OR on 29 August 2014. (01:09) Segment 1 (04:30) Ryan Lortie asked about an offensive public statement Linus Torvalds made on 6 July 2012. (05:04) Bradley mentioned that Linus Torvalds argued Red Hat was kowtowing to Microsoft using offensive language. (07:57) Karen mentioned that Linus called GNOME an unholy mess. (19:05) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the key differences between 501(c)(3) and 501(c)(6) organizations in the USA, and discuss recent refusals by the IRS to grant such statuses to Open Source and Free Software orgs. Show Notes: Segment 0 (00:34) Bradley mentioned the 501(c)(3) vs. 501(c)(6) difference came up on FaiF 0x41. (03:35) Bradley mentioned that in 501(c)(3) status from the IRS is based on receiving some status governed by §170(b)(1)(A) of the tax code. (Most Free Software charities, such as Conservancy, are classifed as non-profit charities under §170(b)(1)(A)(vi).) (05:10) Bradley mentioned this issue had been discussed on FLOSS Foundations' mailing list (05:50) Bradley discussed that at the OSCON 2013 tutorial, Community Foundations 101, most of the 501(c)(6) representatives who spoke argued incorrectly that the differences between 501(c)(3)'s and 501(c)(6)'s were not substantive. (10:50) Karen referenced how the TV show Silicon Valley parodies the irony of for-profit software companies claiming they make the world a better place. (11:58) Bradley mentioned he was inspired by Michael Moore in his work on Free Software. (15:02) Bradley mentioned Karen's talk called Identity Crisis (15:21) Karen mentioned that open source was on the list of items the IRS gave additional scrutiny. (16:51) Bradley mentioned a blog post by Jim Nelson where Yorba's rejection was discussed; Yorba's 501(c)(3) application was previously discussed on was discussed on 0x1C, and covered in many other places. (17:46) Karen wrote a blog post about why she isn't worried for Conservancy's 501(c)(3) status at this time. (18:30) Bradley mentioned that IRS decisions don't make precedent, and if there's a dispute, it would go to USA Tax Court (19:00) Mozilla Foundation's odd hybrid for-profit/non-profit model was audited by the IRS, and Mozilla Foundation settled with the IRS. (20:22) Open Stack Foundation was initially denied 501(c)(6) status, as reported on Mark McLoughlin's blog. (25:10) Bradley promised links to both Yorba's 501(c)(3) denial letter from the IRS and Open Stack Foundation's 501(c)(6) denial letter from the IRS. (The response to the IRS from OpenStack, written by DLA Piper, OpenStack Foundation's law firm, is also available, too. (27:15) Bradley and Karen discussed Board of Directors meetings in FaiF 0x45: I'm Board (31:40) Bradley mentioned the How fresh stays fresh campaign, which includes the Nature's Pause Button television commercials by the American Frozen Food Institute, which is a 501(c)(6) organization. It's FY 2012 Form 990 is the most recent on available. Bradley also mentioned the Beef: It's What's For Dinner advertisting campaign that has existed for decades in the USA, which is sponsored by the National Cattlemen's Beef Association, Inc. which is a 501(c)(6) as well. It's FY 2012 Form 990 is the most recent on available. (35:40) Bradley further mentioned the Pork: the other white meat advertising campaign, which has also existed for decades but is now called the Pork: Be Inspired campaign, seems a bit more dubious in its non-profit existence. It appears to be funded by the National Pork Board Foundation, which is ostensibly a 501(c)(3) but has no assets, revnue nor expenses, and appears to be a front for an org called the America's Pork Producers / Pork Checkoff, which appears to be some quasi-govermental agency related to pork (in other words, it's pork for pork). More research would probably be needed to figure out better what's going on here with regard to non-profit status, but it seems that unlike the Beef ads, which are clearly funded by a 501(c)(6), this campaign is funded by a separate legislation, presumably unrelated to §501(c). There is, BTW, also, a 501(c)(5) called the National Pork Producers Council, which appears to be where the big money is (— not surprisingly — 501(c)(4)'s and 501(c)(5)'s often make 501(c)(6)'s and 501(c)(3)'s look tiny by comparison). (36:13) Segment 1 (39:43) Conservancy and OSI jointly announced a working group on IRS applications and denials. (40:49) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Karen Sandler interviews Lennart Poettering and Alan Day during the GNOME Asia Summit 2013. Bradley and Karen comment on this interview. Show Notes: Segment 0 (00:38) Bradley and Karen introduce Karen's interview with Lennart Poettering and Alan Day. Segment 1 (02:06) Karen interviews Lennart Poettering and Alan Day about Lennart's Sandboxed Applications for GNOME talk at GNOME Asia Summit 2013. Segment 1 (35:24) Bradley mentioned his comment during the GPLv3 process regarding the Ty Coon issue. (41:20) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the talk, Copyleft vs. Permissive vs. Contributor License Agreements: A Veteran's Perspective by Simo Sorce given at FOSDEM 2013 on Sunday 3 February 2013. Show Notes: Segment 0 (00:00:38) Bradley and Karen introduce Simo's talk. Segment 1 (00:03:02) The slides from Simo's talk are available, if you want to follow along Segment 2 (00:59:50) Bradley menitoned his blog post about CLA's on Conservancy's website. (01:00:10) Segment 3 (01:10:22) Bradley and Karen are still trying to decide what to do about the FOSDEM 2014 talks. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen host a panel discussion on CLAs with Van Lindberg and Richard Fontana. Show Notes: Segment 0 (00:38) Bradley and Karen introduce the panel discussion. Segment 1 (01:28) The panel guests are Van Lindberg and Richard Fontana. Van quoted from the Apache Corporate CLA. (40:55) Segment 2 (48:17) Bradley and Karen wrap up the discussion. Bradley mentioned the AKG C1000S which we use to record the oggcast. (50:40) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss Contributor Licensing Agreements, which pulls material from Bradley's blog posts on the subject. Show Notes: Segment 0 (00:36) Bradley mentioned FSF's copyright assignment process. (05:50) Bradley mentioned RMS' essay regarding what you should do if a company asks you to assign copyright on Free Software. (14:00) Open Stack is reconsidering their CLA. Bradley mentioned again that goofy Eclipse contributor poster. (27:22) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the talk, Why the free software phone doesn't exist by Aaron Williamson given at FOSDEM 2013 on Sunday 3 February 2013. Show Notes: Segment 0 (00:37) Bradley and Karen introduce the talk. Segment 1 (04:06) Aaron's slides area available. Segment 2 (56:41) Bradley mentioned dakota imaging where he used to work. (1:02:15) dacotag imaging Karen mentioned Aaron's OSCON 2010 talk (but we incorrectly said it was 2009). (1:04:35) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the talk, copyleft-next: an Introduction by Richard Fontana given at FOSDEM 2013 on Sunday 3 February 2013. Show Notes: Segment 0 (00:37) Bradley and Karen introduce the talk. Segment 1 (05:37) The slides Fontana's talk on copyleft-next are available. Segment 2 (01:06:51) Bradley mentioned the issue of Noam Chomsky's points on concision (01:13:23). Bradley mentioned the anti-GPL keynote by Tom Preseton-Werner of Github at OSCON 2013. (01:14:53) Bradley and Karen discussed the Harvey Birdman Rule. (1:27:45) Bradey mentioned a comment he posted about CHR-governed policy meetings. (01:29:00) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss why software freedom as a political, social and moral issue is important to each of them personally. Show Notes: Segment 0 (00:36) Bradley mentioned that he used to frequently give talks on why software freedom is important to him. There are available on FSF's Audio/Video website three different recordings of that talk, usually titled Software Freedom and the GNU Generation. (01:28) Bradley's first distribution was SLS. (18:20) Bradley mentioned that OpenStack was denied 501(c)(6) trade association status by the IRS. (37:56) Karen mentioned the Cooper Union law suit. (48:40) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the talk, Legally Cementing Licences in Legislation: Two Law Merchant Models for Free Software Licences by Maureen O'Sullivan given at FOSDEM 2013 on Sunday 3 February 2013. Show Notes: Segment 0 (00:00:37) Bradley mentioned the Planet money t-shirt story (03:04) Bradley mentioned he buys Union made sweat pants (04:42) Segment 1 (00:06:48) Bradley and Karen introduce the talk. Segment 2 (00:07:20) This segment is the talk, Legally Cementing Licences in Legislation: Two Law Merchant Models for Free Software Licences by Maureen O'Sullivan given at FOSDEM 2013 on Sunday 3 February 2013. You can follow along with the slides. Segment 3 (00:50:55) Bradley mentioned a talk he gave on 2005-03-12 at UC Irvine to a workshop of academics meeting about the research area of Computing Communities. Bradley still has some email archives regarding this, but can't find any online link to the workshop (URLs in the emails are all dead) or a recording of his talk. (58:52). As Bradley mentioned, ESR self-identifies as a gun nut. (01:00:19) Bradley mentioned FaiF 0x3A, which had Gabriel Holloway's talk (01:03:27) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss the details, what to worry about, and what the usual duties are when serving on a Board of Directors for a USA non-profit. The discussion is primarily about 501(c)(3) organizations, but at the end they spend some time discussing 501(c)(6) organizations as well. Show Notes: Segment 0 (00:00:44) An image of Alfie chewing on the antler (01:22) Karen is running for the GNOME Foundation Board of Directors. (05:15) Bradley once criticized the CNRI OPEN SOURCE LICENSE AGREEMENT (used for parts of Python), because it is governed by the laws of a place that doesn't exist. (06:48) Bradley mentioned a Planet Money episode that talked about it's “too easy” to incorporate in Delaware (23:50) Segment 1 (00:32:25) Bradley and Karen discuss various additional things about being on a Board of Directors, including why and how you might be able to serve on one. Bradley and Karen discuss the requirements for getting on a 501(c)(6) Board like Linux Foundation (55:30) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).