|
|
Subscribe / Log in / New account

Debian discusses Discourse

Debian discusses Discourse

Posted Apr 18, 2020 6:54 UTC (Sat) by NYKevin (subscriber, #129325)
In reply to: Debian discusses Discourse by pizza
Parent article: Debian discusses Discourse

> I'm glad you have something that is "good enough" for your purposes, but without a decent MUA and a workflow I've refined over many, many years, I'd have been long overwhelmed by the sheer volume of communication traffic I need to stay on top of and meaningfully respond to, much of it highly technical in nature.

I receive a large volume of email as well. I found that prioritizing emails with my own address in the To: and CC: lines, and one or two carefully chosen lists, was sufficient, and nearly all of my other filters are just quality-of-life "skip the inbox" filters. I've got several thousand unread emails in my inbox at any given time, and I'm not too concerned about reading most of them, because I already read all of the messages that I actually need to care about. The rest, I just let float by into the ether, occasionally plucking one from the stream of detritus if the subject line looks interesting. I'm sure this sounds horrifying and uncivilized to some readers, but I read all the email I need to read, and I don't read the rest. Isn't that what a filtering strategy is meant to accomplish?

> Yes, there was a learning curve for this stuff, and maintaining it takes some time and effort, but in return, I gain efficiencies that pay for themselves many, many times over in the form of (much!) higher personal productivity.

I'm well aware of this general concept; I have a highly tricked out zshrc and a moderately tricked out vimrc. I just don't see much point in extending that effort to email when the only benefit is making the number next to my inbox folder smaller (as opposed to, say, allowing me to execute commands or edit text with fewer keystrokes, which directly increases my productivity).

> It was not my intent to call all forums crappy, just that Discourse with those "engagement" features turned off amounts to little more than a relatively crappy example of a forum, with an even crappier implementation of a mailing list tacked onto it. In other words, turn those features off, and there are better forums, and much better mailing lists.

That's certainly fair, and I'm not sufficiently experienced with forum software to comment here. My concern, however, is that nobody is discussing any forum-like alternatives as far as I can see from limited skimming of the Debian discussion (as I mentioned above, there's a laundry list of reasons why these discussions are hard to read as a non-participant, so I may have missed something). And it's likely that many of the same arguments you and others are making against Discourse would translate to most other forum software packages as well (none of them are going to support POP3 or SMTP, for example, so you won't be hooking your MUA up to the forum).

As a result, I fear the "older" open source and free software communities may reject forums altogether, and wall themselves off into an aging and disfavored protocol. SMTP already requires numerous weird extensions to the RFC just to make it slightly harder to send spam, and its encryption story has never made much sense in comparison to HTTPS. Meanwhile, web-based technologies get more powerful and modern every year. Meanwhile, the "younger" open source (mostly) communities will embrace GitHub et al. and refuse to even have mailing lists, which creates a worst-of-both-worlds scenario wherein Debian developers (and anyone else in the "distro" space) have to constantly context-switch between their MUAs and their browsers to interact with each other and upstreams respectively. There's also a serious risk of email ceasing to effectively federate, as more and more anti-spam measures are piled on top of a system that was never designed for a global, trustless internet. I don't think this is happening any time soon, but nobody appears to be planning for it at all.

There are problems with web-based tech, too. Federation is usually poor to nonexistent (unless you count dumb hyperlinking), many sites are bloated beyond all reason, the web is increasingly a Chrome/Chromium monoculture, and it's not clear that anyone actually cares about any of these problems enough to do something about them. However, if all of the people who most strongly object to those issues simply avoid using the web entirely, then the web will continue to develop without their input, and things will get worse.


to post comments

Debian discusses Discourse

Posted Apr 18, 2020 13:01 UTC (Sat) by pizza (subscriber, #46) [Link] (2 responses)

> (as I mentioned above, there's a laundry list of reasons why these discussions are hard to read as a non-participant, so I may have missed something).

It's worth noting that what makes this hard is that you were a _non-participant_, not because it took place via email versus Discourse or some other forum. How do you ensure you don't miss something important, without reading the whole thing? (Important to _you_, not what others involved might think is important. Because, especially when discussing technical things, the details matter)

> And it's likely that many of the same arguments you and others are making against Discourse would translate to most other forum software packages as well (none of them are going to support POP3 or SMTP, for example, so you won't be hooking your MUA up to the forum).

This is one of the points I tried to make earlier. I've participated in forums where the admins went through great lengths to make email users have a first-class experience in the discussions. Technically, it worked great, but for any given message, you could *always* tell who wrote it via email and who wrote it via the web site -- not just from superficial details like quoting style or the typical length of the response, but the depth of what was said as well -- the difference between the cultures was quite stark. It quickly became clear that folks who did most of the actual development work overwhelmingly preferred email, and the mass of non-[code-]contributing users overwhemingly preferred the forum.

Of course, looking just at the traffic/usage metrics the latter vastly outnumbered the former, leading naive outsiders to question why so much effort went into supporting those old fogeys who just didn't want to embrace modern things..

I've seen this pattern repeat itself many, many times over the years.

(Oh, and you don't need to make your forum directly speak POP3; that's what the recipients' email servers are for, and these days webapps that do any sort of email notifications nearly always directly speak SMTP)

> However, if all of the people who most strongly object to those issues simply avoid using the web entirely, then the web will continue to develop without their input, and things will get worse.

Until, of course, those developing those "modern" web thingeys with ever-more-"modern" tooling realize they still need an actual operating system running on actual hardware, at which point their heads explode when they encounter that _very_ different mentality and culture.

Systems administration used to be the ultimate example of "box of tools, make it do what you want" and a necessary rite of passage (or minimum threshold of competence to enter) but now, like so much else, it's just another platform API to interact with, handed down from up high on immutable [1] slabs of javascript.

[1] Immutable for the end user; the service provider can and will change it whenever they feel like it.

Debian discusses Discourse

Posted Apr 18, 2020 16:04 UTC (Sat) by NYKevin (subscriber, #129325) [Link] (1 responses)

> It's worth noting that what makes this hard is that you were a _non-participant_, not because it took place via email versus Discourse or some other forum.

I already rattled off a huge list of reasons why I disagree with this assertion. I will not repeat myself.

> How do you ensure you don't miss something important, without reading the whole thing?

Is this a trick question? I would read the whole thing. But that's a lot easier when it's in a forum than when it's in an email thread, as I explained.

> Until, of course, those developing those "modern" web thingeys with ever-more-"modern" tooling realize they still need an actual operating system running on actual hardware, at which point their heads explode when they encounter that _very_ different mentality and culture.

Pffft, they don't need to care about that. Just look at Chrome OS. Sure, someone has to develop Zircon etc., but the average web developer does not care.

> Systems administration used to be the ultimate example of "box of tools, make it do what you want" and a necessary rite of passage (or minimum threshold of competence to enter) but now, like so much else, it's just another platform API to interact with, handed down from up high on immutable [1] slabs of javascript.

This is a Good Thing, it means more people can contribute with less effort. Sure, they may be using a methodology, language, and layer of abstraction that is foreign to your experience, but they're still, y'know, developing software.

Debian discusses Discourse

Posted Apr 18, 2020 16:29 UTC (Sat) by pizza (subscriber, #46) [Link]

> Is this a trick question? I would read the whole thing. But that's a lot easier when it's in a forum than when it's in an email thread, as I explained.

Our experiences obviously differ, but the best interface I've personally used for staying on top of a large number of mailing lists is a nntp reader pointed at the gmane nntp gateway.

> Pffft, they don't need to care about that. Just look at Chrome OS. Sure, someone has to develop Zircon etc., but the average web developer does not care.

...Nor should they have to care.

However, it behoves those webdevs to be aware that they aren't the only fish in the pond, and their ability to generally not care is due to a great deal of effort on the part of many other folks who (usually) have pretty good reasons for doing things their own way.

> This is a Good Thing, it means more people can contribute with less effort. Sure, they may be using a methodology, language, and layer of abstraction that is foreign to your experience, but they're still, y'know, developing software.

"developing software" basically consists of bolting abstraction layers on top of abstraction layers, which is great until one of those buried middle layers inevitably leaks all over your shoes.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds