4 ms·
My point is slightly different. You're focusing on fees, and open source being an industry in itself. Quoting from the linked comment: > This lack of awareness
by TeMPOraL 3y ago
My point is slightly different. You're focusing on fees, and open source being an industry in itself. Quoting from the linked comment:
> This lack of awareness hampers [open source community's] ability to participate effectively in the marketplace, including financial transactions to sustain itself.
Thing is, a large part of that community doesn't want to "participate effectively in the marketplace". The community started as a way to refuse playing the market game. Good or bad, visionary or naive, this was the OG culture, and remains potent in a subset of the larger OSS world.
> While I agree that small fees can serve as proof of identity—verifying that the software indeed comes from the claimed source, which seems to be one main intent of signatures—I don’t understand why these fees have to be exorbitant.
Again, I don't think the price is the problem, nor even that there is a fee. The problem is that "verifying that the software indeed comes from the claimed source" is done by requiring the software to be developed or controlled by a specific legal entity, and requiring that entity to establish trust via business relationships with the network of companies centered around major software corporations. It's forcing the entire OSS ecosystem (or at least the parts that directly, or transitively, target proprietary platforms) to commercialize.
Now, while I'm strongly biased against what I consider "security disempowering users and sucking out all the fun from computing", I'm not going to argue that this is entirely 100% bad, or that software devs have right to remain anonymous. Maybe, long-term, it's the only way forward. But right now, it feels like being colonized. "Yes, nice stuff you're making there, our citizens love it, and we've made some good money on it too. But from now on, you're no longer welcome on this land, unless you accept citizenship and become legible to our bureaucracy."
- keepamovin 3y agoThanks for your comprehensive response. I consider these topics deeply important, and worthy of a lot of consideration. I sensed we had a disagreement but likely tried to side step that to avoid any conflict, because I don’t really want to engage in that online. I’m glad to see I was right with my instinct and thank you for elaborating further just what any disagreement might be there! :) Please allow me some time to read, understand and consider what you said and maybe I’ll get back to you!
- TeMPOraL 3y agoThanks :). To be clear, I think what you wrote is true as well - it's a part of a larger picture. In my replies, I want to point at another part of that same picture, one I saw is not talked about at all in this thread, and which I believe may be more relevant to this case (because let's be honest, $629 for a project this widely used is peanuts, so it can't be the whole issue).
- keepamovin 3y agoBut maybe it is the issue. The guy is asking for money. He's not mounting a refusal of the whole system of signing. Everything in his announcement is about finding ways to accommodate himself to the new situation of having a certificate after a previous sponsor churned. His hesitation is clear, but a certificate there would cost $629 (tax excluded) for a single year, and his ask for sponsors is also very clear, and follows immediately: If your organization requires a signed installer then please consider sponsoring us with a code signing certificate. Please reach out to @dlemstra for questions or in case of a sponsorship. I understand the points you are making, but instead I think in this case it is not I who is missing the larger picture, but you--missing the larger picture, and one painted clearly in the text of the GitHub announcement this thread is about. However, in your other less relevant comment above, you raise interesting points which I want to address! While not as relevant to the specific case at hand, they are interesting and deep! Let's dive in over there! :)
- mike_hearn 3y agoYou can get certificates for individuals, not only companies.
- keepamovin 3y agoYour idealism and enthusiasm for this is charming! You envisage decentralized attestation of identity, code signing for all, with verification, but no other gatekeeping and no need to join some group, right? Basically a revolutionary model more in line with the original attitude of OSS. It's a cool idea, I hope you pursue it! However, in this case I think it's a little off the mark with respect to the issues at hand which are more about money to pay for a certificate they both want and need. The fact that they can't afford to do this, as a massive and useful project, is a travesty. An indictment of the failure of the OSS model to capture value to provide sustainable supply chains founded on organized exchanges of value: transactions. I get the anti-corporate idealism in your post, and it makes sense! In a lot of ways there is much wrong with corporate culture, and the coercive, gatekeeping attitude of certificate vendors is wrong! Like a cartel, as I said. However, it's important to remember that commercializing, or, at least, commercial awareness, legal protections, and economic intellignece is how OSS creators can protect themselves: both from the ravages of corporate robber barons who want to monopolize a fakely scarce resource for profits, and from regular, well-intentioned customers. Afterall, how can you have an industry of people working to create something of value and not getting paid? It doesn't work. I think you miss the big picture here, not me. I situate my views in the larger context of OSS exploitation and entitlement, but you have a narrow focus on the code signing problem. Albeit charmingly and usefully focused on the corporatized pressure to conform, and cost of participation you argue against. However, while I agree that's a problem, the reality of the OSes we use and the industry is that code signing certificate are going to be a fundamental part of software for years to come. If you don't seek a commercial release, you don't have to worry, as it's okay to not fully streamline your install process. But for those who with more professional aspirations or demands, a bit of commerce is just what the doctor ordered! :) And the issue of exploitation of OSS extends far beyond code signing. So you may as well figure out how to commercialize, is what I'm saying. Because commercial awareness is how you can protect yourself. It may not seem important, and indeed it isn't if you don't have a market. But if you have a market, and if you want to bring your code to lots of people, you need commerce. Otherwise it's just exploitation and entitlement. Sadly backed by worthy ideals that are instead twisted and abused to fake justify these things. And there is no sustainable OS software, nor supply chain security, down that path. While the shadow of capitalism indeed has a long dark tail, and your skepticism of commercialization is understandable, it doesn't have to be all doom and gloom. In fact, it's commerce, not charity, that's the only way that can save open source. Thank you for your comment! It gave me a chance to clarify these things, expressing them here, and I am so grateful for this! :) PLease work on your decentralized code signing, it sounds really cool!