Hey folks - Got an Ops update for all of you.
In the past three weeks, we’ve seen a 25% increase in server members, from 8,000 to over 10,000.
While this is fantastic, many of them are left overwhelmed with the number of Discord channels, as I’m sure many of us are as well.
Looking at the categories we have:
- Welcome (Level 0)
- BanklessDAO in Bites
- Community Call
- General (Level 1)
- Member Perks
- Cross Guild Collab
- Project Planning
- Analytics Guild
- Audiovisual Guild
- Design Guild
- Developers Guild
- Education Guild
- Legal Guild
- Marketing Guild
- Ops Guild
- Research Guild
- Translators Guild
- Treasury Guild
- Writers Guild
Holy shit. The proposed solution here is to gate all of the guilds behind roles and consolidate projects and cross-guild collab.
This mechanism would gate almost all guild channels behind that guild’s role, which members can select from
- If you do NOT have a guild tag, only two channels are available:
- If you DO have the guild tag, all channels under that particular guild category are available.
- Furthermore, a singular
firehosetag will unlock ALL channels to bypass the Discord tag gating
WARNING:warning: This does introduce one potential problem: If you tag a member in a guild channel when they don’t have view permissions for that channel, they will not receive the notification. The expectation here is that L2 members and maybe active L1 members will opt to use the
Firehose tag to receive all notifications, at which point we will emphasize muting and collapsing categories to minimize noise. Gating is meant for less active/specialized members, of which there are many.
There’s very little distinction between project planning and cross guild collab right now. Furthermore, there are many project planning channels that need to be pruned into archive.
But WAIT! Many of these projects do not belong in the planning category. You would be correct. This leads nicely to the next segment: Project Categories!
Over the past week or so, we’ve seen a number of new categories pop up in the bottom of Discord:
Notice how all of these categories are projects? Turns out that once projects gain enough traction, a single channel is no longer sufficient. To facilitate better coordination, the heuristic here is that if it is funded for a significant amount and has the “feel” of a long-term project, it should have its own category with its own start-here page and role select.
WARNING:warning: Naturally this will create more channels. But similar to
#guild-select and role gating, we will apply the same rules to projects. There will be a
#project-select category that will unlock the remainder of the channels within a project category.
The following projects are requested to create their own categories at the BOTTOM of Discord:
- Bounty Board - @Icedcool @Bpetes
- First Quest - @angyts @Behold
- Website - @Katarina @MrPackman @livethelifetv
- Bankless Loans - @livethelifetv
In creating a category, please include (at minimum):
If it makes sense to add additional roles within the project, Angyts has created a nice guide.
Once these channels are up, ops guild will create a
#project-select channel and gate the category (save for the