Organizational changes to Discord

Announcements
1

Hi,

We are announcing some organizational changes to Discord. The goal is to simplify the structure by cutting out the fat and moving some communications to the community forum to better retain the valuable information. We aim to keep Discord focused on real-time chat and community support.

The changes are separated into four stages.

Stage 1 will be implemented today.
Stage 2-4 have no ETA and depend on your feedback.

We are asking for feedback for the stages 2, 3, and 4 as some of the changes may be controversial.
We welcome all feedback. Post it in the Discord thread or reply to this topic.

Stage 1

  1. We are archiving org focused channels (#finances, #documentation, #translation, #community-meta, #project-managment). All of them have dedicated repositories, were barely used or are better served by our community forum.
  2. One Backer category channel is being archived and replaced with a community forum category to better serve the type of content being shared there.
  3. id-request is being moved to the Backer category. It has long been treated as a free service by people that can’t even take a second to look at the filename before asking the obvious.
  4. #programming and #code-review are being consolidated into a single #dev-chat channel. The channel will supplement the community forum Development category.
  5. #ui-ux is being renamed to #ui-ux-talk.
  6. #nsfw-favorite-female, #nsfw-favorite-male, and #nsfw-favorite-female-trans are being renamed to #female-showcase, #male-showcase and #trans-showcase respectively. #nsfw-favorite-male-trans is being removed completely as it has 0 posts since its creation.

Stage 2

Note
All proposed changes are not final and subject to change based on your feedback.

There are quite significant changes that simplifies Discord flow and encourages more structured conversations to take place on Discourse.

  • Support category removed.
  • #help and #bugs channels moved to Stash category.
  • #feedback archived.
  • #scenes archived.
  • #images archived.
  • #groups archived.
  • #galleries archived.
  • #performers archived.
  • #studios archived.
  • tags archived.

Stage 3

Note
All proposed changes are not final and subject to change based on your feedback.

These are probably the most controversial changes.

Archival of community contributions category. These channels are primarily used for support or showcase of new projects. But due to Discord real-time conversation style most of the important posts can be easily lost. With moving them to the community fourm we hope preserve all that knowlegde and resources.

  • #scrapers archived.
  • #plugins archived.
  • #theming archived.
  • #ai-projects-feed-the-machine archived.
  • #ai-recog-tagging archived.
  • #funscripts-and-handy archived.
  • #community-projects archived.

Stage 4

Note
All proposed changes are not final and subject to change based on your feedback.

Removal of StashDB category and archival of its channels. This will effectively move all StashDB related communications to the community forum StashDB category and StashDB General chat.

  • #stashdb-guidelines archived.
  • #ministry-of-truth archived.
  • #stashdb-invites archived.
6 Likes
3

Seems mostly reasonable, but there is definitely going to be pushback on Stages 3 & 4.

1 Like
4

I’m all for this. Looks as though nothing is being truly removed, just moved to a somewhere else

Moving more to the forums and off of Discord works well for me. As you sate, a real-time chat application isn’t the place to go for techical support as you either get help later and the response has been lost in the flurry of other people seeking assistance or your message is missed because it gets lost in the noise.

As someone who was disappointed by the loss of the Matrix bridge I accept that I’m definitely not going to fall in the bucket of “most people” but since this involves change I expect that there will be some pushback.

Keep up the good work regardless.

1 Like
6

Maybe it doesn’t much work like this in practice, and there’s probably better places to ID performers, but moving ID request to backers prevents non backers from answering requests thus lowering its utility. It also potentially lowers other submission quality because more people will not ID unlisted performers correctly.

Not sure that’s a solution to what seems like an ignorable problem. Seems like just problem creation.

7

There was a previous discussion here about moving ID request to a backers exclusive area. Looking over the recent history of the channel, there were no requests that were answered by non-backers. I can’t speak to how many requests led to better stashdb submissions, but I am skeptical that it would be a significant number.

My feeling is that this was a resource provided gratis mostly by backers to mostly non-backers, and not necessarily related to stashdb submissions. It makes sense to me to make it a backer perk. We can of course reassess after the dust settles.