Discord server

[diomed]

Communities usually have Discord server nowadays where developers gather and talk about issues, exchange ideas and answer help questions. This should be made.

[nobkd]

Related: #1 (reply in thread)

[tipiirai]

@MichaelYuhe @nobkd @diomed it's up!

https://discord.gg/8dStsD6N

I want to keep this semi-closed initially. I want to focus on coding and don't want to drown into support requests.

[diomed]

@kon-pas please join

[misaw-kun]

so is the invite expired or limited to fewer folks as i read above ?

[nobkd]

@misaw-kun

I created a new invite, that does not expire.
I think that is alright: https://discord.gg/5RVfhKMwVB

@tipiirai, feel free to delete this comment, if you are not comfortable with it.

[tipiirai]

Cool. Jumping in.

[tipiirai]

Is it just me, but I find Discord slow, heavy, and bloated.

[goblinfactory]

@tipiirai imo discord is an abomination, worse than marquee.
I sometimes literally have a mini panic attack when i'm forced to use discord. It's the sole reason I took so long to properly get into using cloudflare tech. The search is almost non existent, and the WAAY TOO SMALL results pane that can't be resized, plus an endless suit of usability problems genetically designed to maximize stress for even the mildest of semi-adh personalities.

imo, valid alternatives are

• slack
  (without paying, just let old conversations fall off the search) i.e. use slack to prepare and discuss an issue before adding it to the issue backlog means that when the messages fall off the slack chat search, they'll have been summarised (without distracting comments) and the important stuff will remain forever in github issues, or ...forever as great new features or bugs that never come back in later releases ;D
• gitter
• Discourse
  I actually used gitter for konsole (my open source project) because it was less mental overhead. slack requires you run a big heavyweight "app" on your machine.

Having observed many teams, I think that slack is better suited for private closely collaborating teams, and gitter appears to be better for more random people communicating, rather than actually collaborating. i.e. maybe use gitter for the anon people using the product, and use slack for the key people actually doing all the work that need to have private conversations?

All that being said, I'll use whatever is setup.

[nobkd]

I also feel this problem with discord, but I haven't used any of the other tools listed here, so I can't provide any more ideas.

(Side note: I've seen some people use matrix (clients) as chat backend for this, but I don't know how it went for them)

[tipiirai]

@nobkd Nue has a small/private Slack group. If you want to join that please send me your email address to tipiirai @ gmail com

[nobkd]

Thank you, I just sent you my mail a few seconds ago

[goblinfactory]

@tipiirai Actually, sorry to backtrack on me saying I'm ok with anything that is chosen, but the mini "panic attack/stress moments" induced by having to use Discord's search is actually a real thing for me; if we moved these types of discussions there, I would have to severely limit my future involvement. (sorry, that's not meant as me trying to pressurise one option or the other.) I honestly believe the friction of having to create public messages here in github issues is tremendously valuable to you, the owner, and therefore the project's future liklihood of success, in that it creates a valuable constructive friction acting as a necessary filter. The "issue discussion threads" eventually dissapear, i.e. they dont accumlulate and cause a lot of noise; because each issue is triaged and eventually closed.

I would like to suggest simply parking the discussion around discord et al until there burden of not having something exceeds the benefits of keeping everything simple. We will all probably know when we're starting to approach that and a more natural time to revisit this issue might be foreseeable.

[tipiirai]

I'm thinking of keeping the Slack community for a small group of super actives before 1.0 is officially out and stable. I don't want a flood of feedback via public Discord or similar before that.