Live data from Hacker News

We Need to Save What Made Linux and FOSS Possible

linuxjournal.com

161–170 of 264 posts

Re: We Need to Save What Made Linux and FOSS Possible

#161

Earlier quoted context omitted.

Source?

«While we still use it heavily, IRC is an ongoing source of abuse and harassment for many of our colleagues and getting connected to this now-obscure forum is an unnecessary technical barrier for anyone finding their way to Mozilla via the web. Available interfaces really haven’t kept up with modern expectations, spambots and harassment are endemic to the platform, and in light of that it’s no coincidence that people…

Where's the part about Matrix?

Re: We Need to Save What Made Linux and FOSS Possible

#162

– We collaborate inside proprietary environments Why is that? Why have users chosen those environments? Assume they are rational beings, and get at the heart of it. Ask: "How can we address the actual user needs while supporting our goals?" – Many Linux and FOSS geeks today use Linux only professionally Same answer as above. – We're not modeling our values WHY? (Hint: "the use of nonfree" is not, and has never been a…

> Assume they are rational beings, and get at the heart of it.

Except: They aren't, so you won't get at the heart of it if you make that assumption.

People simply are extremely short-sighted. People choose the "convenient" proprietary solution for the same reason that they elect the "convenient" dictator or for the same reason that they choose the "convenient" SUV ... what all of those choices (and countless others) have in common is that long-term costs are simply ignored when making the decision.

It's actually just a lie that proprietary software is more convenient. What is true is that it (oftentimes) is more short-term-convenient, i.e., you will save some time/effort right now. But the pretty much universal goal of the proprietors of proprietary software, and in particular of proprietary platforms, is to use that short-term convenience (which they optimize for) to establish themselves in a position of power, which they then use in the long term to maximize the profit while inconveniencing those they have managed to gain power over in any way that promises profits.

The most pernicious form of that long-term inconvenience is the "invisible inconvenience", namely the inconvenience that results from hindering innovation by hindering competition: It's inconvenience that you never notice because the more convenient alternative simply never gets developed, so you never get to experience the difference between what you do have and what you could have.

Re: We Need to Save What Made Linux and FOSS Possible

#163

Earlier quoted context omitted.

«While we still use it heavily, IRC is an ongoing source of abuse and harassment for many of our colleagues and getting connected to this now-obscure forum is an unnecessary technical barrier for anyone finding their way to Mozilla via the web. Available interfaces really haven’t kept up with modern expectations, spambots and harassment are endemic to the platform, and in light of that it’s no coincidence that people…

Where's the part about Matrix?

Oh, I thought you just needed a source on the harassment claims. I do not believe there was an explicit rejection, however at the bottom of the blog post, we have...

* We are not rolling our own. Whether we host it ourselves or pay for a service, we’re getting something off the shelf that best meets our needs.

* We are evaluating products, not protocols.

* We aren’t picking an outlier; whatever stack we choose needs to be a modern, proven service that seems to have a solid provenance and a good life ahead of it. We’re not moving from one idiosyncratic outlier stack to another idiosyncratic outlier stack.

Given other language such as "modern expectations" in regard to interfaces and being "spoiled for good options" as well as Rust's move to Discord possibly setting a precedent within Mozilla, the posters in the HN thread above don't have a lot of hope Matrix will be selected even via Riot.

Re: We Need to Save What Made Linux and FOSS Possible

#164
post #160

Earlier quoted context omitted.

Forget IRC. You can do everything with Matrix :)

Kinda-sorta? Matrix is an incredibly centralized service masquerading as an easily self-hosted distributed service. The moment you try to get a non-technical user connected to a homeserver other than matrix.org, all hell starts to break loose. It's bad enough that both France (tchap) and Purism have created their own client forks to make on-boarding somewhat tolerable at the expense of really painful rebases against…

This is pretty disingenuous - we have spent loads of time making Riot work well with self-hosted servers (c.f. the current login & registration flows, which explicitly prompt you to select a server), and around 50% of the network are running their own servers. Our intention is to turn off the original matrix.org server once we have decentralised accounts and the network is healthy enough.

Re: We Need to Save What Made Linux and FOSS Possible

#165
post #117
post #36

Its more abjectly a moral failing of society that institutions have not aligned to enable free software proliferation. Software, and information in general, have been a prisoners dilemma for time immemorial. The optimization of utility is total freedom of information - but such a state of affairs means benefactors reap the labors of others and have no obligation to give anything in return. Copyright was fabricated to…

Free Software enthusiasts can't advocate against copyright, because it's the only thing that gives the GPL any meaning at all. In a copyright-free world, any company could make a proprietary GCC fork, lock its code up behind many layers of physical and digital security, make all its developers/employees sign NDAs and other legal agreements ensuring they don't leak any of the new code, et voila. Hardly sounds like a F…

My personal take on it is that in practice software liberation is more akin to the right to repair than to a need for intellectual property.

We currently have both a draconian IP regime and woefully inadequate right to repair, but fixing the latter does absolve free software from needing the former to function.

Re: We Need to Save What Made Linux and FOSS Possible

#166
post #117

Earlier quoted context omitted.

Free Software enthusiasts can't advocate against copyright, because it's the only thing that gives the GPL any meaning at all. In a copyright-free world, any company could make a proprietary GCC fork, lock its code up behind many layers of physical and digital security, make all its developers/employees sign NDAs and other legal agreements ensuring they don't leak any of the new code, et voila. Hardly sounds like a F…

> Free Software enthusiasts can't advocate against copyright You're right that we can't advocate for just eliminating copyright, without shooting ourselves in the foot. However, eliminating copyright, combined with, say, an obligation of software companies to disclose the source code of their "products" to their customers, or, less intrusively, with making the type of NDAs you describe illegal, would work.

More generally it comes back to the right to repair. We operate in this perverse economy where we lack a meaningful right to repair in the digital age because understanding on the subject is so scarce, but I personally believe in a strong consumer right to repair, and in a post-IP world that would include a requirement to disclose source of software - in practical terms, so the owner of the tractor can fix bugs in the tractors computer, but in general so anyone purchasing software - or just goods of any kind - should have the right to understand what it is and how it works.

Its one of the defined software freedoms of the FSF, after all, and its fundamentally why software freedom is advocated for, but it absolutely doesn't need copyright to be enshrined in law.

Re: We Need to Save What Made Linux and FOSS Possible

#167
post #49
post #27

Earlier quoted context omitted.

This is such a close minded view of the world that the only way to monetize software is to violate software freedoms to do so. The valuable good in exchange is the developers time, not the code itself - nation states have constructed a goliath IP apparatus to impair the natural capacity to instantly and infinitely replicate information. But its wholly fictional and fabricated - its just an outdated paradigm from the…

> This is such a close minded view of the world that the only way to monetize software is to violate software freedoms to do so. Ok, I don't even agree with your definition of freedoms , but I'll bite anyway. Do you have an example of a different approach? RedHat? Selling services, FOSS is just a by-product. Mozilla? Yes, though its position is very unique, and they are the only ones who really have incentives aligne…

Many popular programs are now seeing continuous paid development by patronage including Godot, Krita, Blender, GIMP, and OBS.

It is unsettling that they all get this success on a proprietary middle man that siphons a portion of the money in the form of Patreon, but the principle is absolutely applicable to development in general. Right now its regular people paying to have software they want to use developed - game engines, art tools, etc - but nothing should stop a culture shift from getting both corporations and private developers to start paying in a similar way for libraries and infrastructure given the means to correlate the added value in doing so.

Re: We Need to Save What Made Linux and FOSS Possible

#168
post #100

Earlier quoted context omitted.

> "It's not as good as this other (proprietary) software, but it's free" won't cut it. Except that it has to cut it in order for a free software movement to exist, because otherwise free software is starved by a chicken-and-egg problem where developers don't use free software because it's inferior, and free software never improves because developers don't use it. In other words, being willing to use technically infer…

That argument is not holding any water. First, free software doesn't improve "because developers use it". It improves because developers work on it. Blaming the users for that problem is not helping at all, except with a vague sense of moral superiority. Second, people use tools (e.g. software) to achieve things. "Making the engine of free software run" is not on that list of things for the vast majority of people, s…

[deleted]

Re: We Need to Save What Made Linux and FOSS Possible

#169
post #64
post #45

Earlier quoted context omitted.

> Because they don't give a rat's ass about the freedom aspect of free software. It's attitudes like this that make people really not care about FOSS. Yelling at people because they're not using IRC instead of slack isn't a good way to convince anyone.

When IRC looks like this https://quasseldroid.info/assets/images/phone.png or this https://blog.irccloud.com/static/2018-05-14-slack-integratio... and people still complain about IRC’s UI or usability, then what more can we IRC devs do?

IRC had its problems but I’d still rather be able to control my ui rather than have a bloated web browser running all day.

Re: We Need to Save What Made Linux and FOSS Possible

#170

– We collaborate inside proprietary environments Why is that? Why have users chosen those environments? Assume they are rational beings, and get at the heart of it. Ask: "How can we address the actual user needs while supporting our goals?" – Many Linux and FOSS geeks today use Linux only professionally Same answer as above. – We're not modeling our values WHY? (Hint: "the use of nonfree" is not, and has never been a…

An excellent point. FOSS has long been great at underlying tech, freedom, and openness, and terrible at UI/UX and ease-of-use. That's been true for a long time and still seems to be true today. The reasons for this are much-debated and well-known, yet the underlying challenge persists.

Because companies that build consumer product spend tons of money on usability testing and people to work on the ui who are not developers. There just are not that many of these people working on oss projects. What ends up happening is features are just jammed in wherever a developer thinks they are convenient and you end up with an image editor that’s about as fun to use as the software your company has you filling out your timesheets on.
Post reply on HN