None of this is true for discord. It isn't indexed by anything, even "servers" are walled gardens to each other mostly. Anything shared on discord will be lost to time in a decade or two. Nothing discovered or solved within $project's discord will possibly benefit anyone outside that project.
And sure, we already had that problem with IRC, but I think the text-only nature of it helped that anything a bit more involved moved to forums or mailing lists which again both were web accessible and searchable. And even then some projects did have logbots which just dumped text files into a web server.
I don’t have the time or energy to arse about with real time chat and micro-communities for every single thing. The claim is that they are inclusive but I find them rather cliquey and exclusive.
Personally, as someone who has watched the evolution of IRC and other types of communication channels, I would argue that unless a thread is archived to the open web, anything shared in a realtime chat channel is lost in hours if not days.
I think the best thing for this stuff is still a forum, like GitHub Discussions (or Issues), or just run your own message board.
That being said, Stallman (still?) uses mostly terminal based software, so that take is a bit biased.
The Linux terminal is fairly comfy and depending on the task, it can be vastly superior to graphical applications. The opposite can also be true for other tasks. It really depends on what someone wants to do with their computer.
It blows me away just how out of touch one otherwise-intelligent man can be.
FOSS often has severe usability issues compared to popular proprietary counterparts -- just look at any article here talking about trying to use Matrix or get friends/relatives to use it, it's basically always a big dumpster fire. Yet somehow you still have people recommending it.
I think the issue is less getting a designer interested, and more that it would be really hard to get consensus. Changing UX is more subjective AND intrusive compared to adding more features or improving performance. Changing the UI means changing people's existing flows, as opposed to a new feature that can just be one more button somewhere.
There are some exceptions, but the ones that care the most about market share either have a corporate backer that is profiting from the project (Microsoft, Chromium) or require large numbers for the project to be successful (Firefox, Fediverse).
Is this for the same reason that most Linux users don't care about free software (i.e. are happy running various proprietary blobs on Linux, Windows games in Wine etc.)
i.e. as far as I can tell most users of free software don't care about the free software aspect very much.
Talked to a Linux user about this last night and he seemed to think the "free" part means "no cost"... Sad!
I'm not saying that it's strictly worse or the same as with FOSS software. Just a different tradeoff.
The tolerance of inconvenience is a practical argument. If you have non-free dependencies, the most likely scenario is that sooner or later the dependency will kill support for the project and you have no legal recourse. Eg, if a project uses Discord, at some point it will have to move away to some other technology/protocol. If it uses git, the project won't ever have to move away from git. Those predictions can be made purely from analysing the license.
Since a move is inevitable, it really should make more sense to use FOSS protocols and clients from the get go. People don't though, and I don't pretend to understand the reasons. But what I can confidently say that Discord is going to become inhospitable for the project eventually.
People are talking about Discord like Freenode didn't crap on everyone recently
Meanwhile, sure, feel free to use an OSS solution then realize nobody cares
And that is the upside of OSS. When Freenode caused people trouble they all just walked calmly to a new server. Case closed. Little of value was lost.
But yes, I do think that free software ideals discourage supporting those platforms - however some may support them to give their users at least some freedom, eg when they are forced to use the platforms due to some work policy.
Ultimately, a huge hacker culture built on proprietary tools might lead to more freedoms, both political and technical, than a tiny hacker community built on other tools. The size and political influence of a larger community matters.
I suppose the real problem of using proprietary tools for a larger community is the marginalized people. Like, if Discord didn't allow people from a certain country. It's a tradeoff between having as large a community as possible and making sure you include everyone, even those with uncommon circumstances. That's a tradeoff that gets made in many situation I think.
My stance is that it is okay to use proprietary platforms as long as it does not negatively impact the users not willing to use them, i.e. all channels must be bridged to non-Discord, so that it does not "partition the community" in any way. Discord-specific features should be avoided to not affect the usability of users on Matrix. So far it works well and I get to basically have the cake and eat it too.
At the time (still?) it seemed impossible to bridge Discord channels (which are viewed very much as 'create as you please') to Matrix rooms without painfully doing it one-by-one via a config file and managing/creating both on each side (Matrix really seems stuck on the idea of preferring its 'one room' model and has not really embraced channels in the Discord sense.) Discord had also just gotten forums with no way to bridge them.
Additionally, our Matrix rooms were seeing a good amount of spam that Discord was not, which would then get relayed to Discord via the bridge and would require moderating in both sides.
Finally, our strongest Matrix advocates firmly disliked the idea of a bridge because it meant their Matrix messages would go to the proprietary Discord company.
In the end, we let them run side-by-side for a little while then the Matrix quickly died.
> In the end, we let them run side-by-side for a little while then the Matrix quickly died.
The Stallman mentality is a plague.
I don't like / trust that stuff either but it's often necessary and easy enough to run in a container (e.g.: Docker/Podman, LXC, Guix Shell) or VM (e.g.: Vagrant, QEMU/libvirt).
I actually run most of my software dev stuff that way these days because all these tools are routinely pulling hundreds of deps from the internet that are doing who knows what in their build systems.
https://github.com/spantaleev/matrix-docker-ansible-deploy
Personally I've never seen any significant amount of spam on Matrix.
This amount of altruism is rare. More likely it's just the desire to be acknowledged by others. It's ok, but it's also worth reflecting on why you need that, as the process of freeing yourself from that can make you happier.
Also quantity <> quality; Discord users often are the people who have been trapped down the slope of least friction and that are ok with "being the product".
For instance if I were the head of browser or desktop environment project I’d want to hear from as wide of an audience as I feasibly can because otherwise there’s almost certainly issues (usability, compatibility, bugs, etc) that I’m not privy to because they aren’t encountered often in small more technical samples of users.
Yes, this is the problem. The article suggests: try to fix it.
I've never actually had a question answered (rarely even addressed) within some chat-like timeframe anyway, then after some days or a week or so I forget all about it or couldn't find it again scrolling up if I wanted to.
People always talk about search engines not indexing it harming discovering, but another aspect of that is that you can't tell if the 'server' is completely dead until you make an account or log in and join it. Then potentially you just see a flood of people joining, maybe one or two asked a question, and there's just no other activity.
But my main issue I think is just that I can't keep up with the chat for so many different 'servers' and their channels, so why does it make sense for it to be chat anyway? Something like Reddit makes much more sense to me, where there's a bit of a sense of what's current, but not to the same extent.
If someone would just clone discord/slack and make it so people could stand up a server in minutes and manage it with near zero effort, and the UI/UX pretty much copied what users find familiar it would probably take off. Don't make it distributed, just apply enough cryptography to secure the client-server communication. Yeah, users will need to trust their admins and it won't be perfect security, most users don't need that.
Make it easy to run fully public and indexed/searchable servers, make it similarly easy to run servers that weren't fully public and indexed and required logins and kept everything private, let the users decide instead of the developers.
If your chat protocol cares too much about perfect forward security against hostile admins and attacks by the FBI while supporting a distributed protocol then you're likely producing something that is too complicated to use for 99% of the happy slack/discord users who don't care about that. The challenge for FOSS developers is to recognize that most people don't care about what they deeply care about and that they're not smart enough to solve the iron triangle of security. And that is when they're not self-sabotaging their product by looking at the way that e.g. slack and discord let you easily edit your comments and declaring yourself philosophically opposed to that.
What if whatever you are making runs against a popular alternative? How are you going to convince the Discord people to switch from that thing to your thing? They are Discord people: they are programmed to seek whatever large numbers of other people are using, which is why you have to resort to Discord to reach them.
If your intent is to have your code reach the maximum amount of people to benefit them, and you want your project to benefit from networks effects.. then GitHub and Discord, the two proprietary platforms used by the largest portion of people for modern OSS project development, are basically a non-choice. Every other option results in far less people discovering and interacting with your project, by orders of magnitude.
In a project I run, we forced everyone into Matrix as much as possible and refused to operate a Discord for over a year. Once we relented, and decided 'we would run both' - over 95% of people in under a month stopped participating in the Matrix channels and instead went to Discord. The number of people in the community grew orders of magnitude larger, in a shorter time period, as well - even with us pushing it less on our docs/etc.
It sucks. Wish it wasn't true - but that's where people are.