Current changes to the 1Hive discord server, and some ideas.

Current changes to the 1Hive Discord server and some ideas

It has come to our attention that the huge influx of users has caused the 1hive discord server to be rather chaotic and unorganized. This is noticeable from repetitive questions being asked in the wrong channels, to bot commands being used outside of the bot-commands channel. Please note that everything is still subject to change, based on feedback. This is still a work in progress.

Motivation
An improved structure will lead to a clear, concise, and clutter-free Discord server, allowing for improved user experience; Information will be easier to find, which will lead to new users being able to achieve their goal quicker. Channels will be used as intended, and bot commands will not be issued all over the place. The goal is to continuously moderate the channels, and stay open to changes if the community wishes so.

Role changes

Seed :seedling:
The original Bee role has been replaced with the Seed role. The Seed role will be the new role for the founders of the 1Hive community. The idea stems from the ‘seed’ group being the group of people who helped plant the seeds for the 1Hive community.

Verified :heavy_check_mark: :
Members with the Verified role will have no special privileges other than access to some channels that are otherwise hidden, such as the channels part of the Bees section. (More on that below)

Fauna :cat:
A new role has been created known as the :cat: fauna role. The role has been created to discuss community moderation, support, and culture. The members of the fauna, are the moderators of the 1Hive discord and manage the server. The role has been created to discuss community moderation, support, and culture. Mall intent, and other actions considered bannable, are handled by fauna moderators with the help of ‘Carl’, a discord moderation bot. The reason for using a moderation bot is transparency - it is much better to use a bot to do the actual banning and kicking, where the Fauna members just have the power to make the bot do so.

Bee :honeybee:
we are currently experimenting with a new trusted role Bee. This role is given to users who have contributed to 1Hive. In the future this role might possibly mint more cred than the regular Verified role. Either 0.75x or 1x. Still to be discussed.

Keeper :honey_pot:
The Keeper role is assigned to users who hold at least 1 Honey (HNY) in their accounts. Having a Keeper role unlocks the Keeper channel.

Self assignable roles :sunflower: :hibiscus: :tulip: :sun_with_face: :honeybee:
Self assignable roles have been added for access to the Swarms channels. Through the :wave: #welcome channel, users are able to choose which swarm they want to join; This is done by reacting to the emoji related to the swarm. This should not be confused with the channels found in the Bees channels. The purpose of the Swarms channels is for contributors to discuss.

Changes to the structure

The most important structural changes will be outlined in this section.

Information channels
The default channels are pretty straight forward and don’t change much. Our main idea here is to create a sort of channel hierarchy to prevent noise in the channels further down in the list, that are more topic-specific.

  • :wave: Welcome - Asks user to perform a basic task that grants access to the rest of the discord, helps prevent bots
  • :mega: Announcements
  • :eyes: Info - Quick and easily accessible information related to 1hive.

Open channels
The #intros channel has been removed, as we want to engage users more into discourse, and have them introduce themselves on there. Furthermore, the use of a welcome message for each newly joined user was redundant.

  • :four_leaf_clover: General
  • :ear_of_rice: Honeycomb - A new channel for users to discuss farming-related topics.
  • :bug: Onboarding - This is tentative because ideally onboarding will be automated after which it’s essentially part of the Bot Commands channel.
  • :frog: Memes
  • :honey_pot: Honey
  • :robot: Bot commands

Bees channels
Note: requires no self assigning, and is open to all members that are Verified

  • :white_check_mark: Check-in
  • :sunflower: Gardens
  • :hibiscus: Flora
  • :tulip: Tulip
  • :sun_with_face: Celeste
  • :honeybee: Buzz
  • :butterfly: Morphosis
  • :white_flower: Pollen
  • :ear_of_rice: Dev
  • :rainbow: Design
  • :earth_africa: Terra - Dedicated to translating 1hive projects, documentation and resources
  • :last_quarter_moon_with_face: Luna - This swarm is focused on modeling 1hive using cadCAD and supporting the community with computer-aided governance.

Support channels
The support channels have been reworked. For now, three main channels will be used.

  • :cloud_with_lightning_and_rain: Help
  • :cloud_with_lightning_and_rain: Help-es (Help in Spanish, as we noticed we have had an influx of Spanish speaking users.)
  • :beetle: Bug report
  • :+1: Feedback

Swarm channels
As mentioned before: This should not be confused with the channels found in the Bees channels. The purpose of the Swarms channels is for contributors to discuss. Right now these are limited to the following roles:

  • :sunflower: Gardens ⏣
  • :hibiscus: Flora ⏣
  • :tulip: Tulip ⏣
  • :sun_with_face: Celeste ⏣
  • :honeybee: Buzz ⏣
  • :white_flower: Pollen ⏣

(⏣) indicating that this is a contributor channel

Keepers channel
The keepers channel will be unlocked for users who own at least 1 Honey (HNY). The keepers channel only consists of one channel, known as :honey_pot: #keepers. Users with the Keeper role can discuss in this channel.

Cross-pollination

  • :eagle: Aragon
  • :octopus: Metagame
  • :high_brightness: BrightID
  • :herb: token-engineering

Social rooms

  • :coffee: Cafe
  • :flamingo: Lounge
  • :apple: Library

This is it for now, feedback is always welcome :slight_smile:

12 Likes

Some suggestions were made in this thread: Suggestions for the 1Hive Discord

Great, those are wonderful improvements, and so quickly after my proposals earlier today :wink:
I will check them and will let you know any additional ideas if any.

@onbjerg, how do I join the Fauna team?

1 Like

ps: it would be good to have a condensed version of this post as a pinned message in the main channels, it will save a lot of redundant questions.

1 Like

We havent really discussed yet how we will assign the Fauna role for members. For now we are keeping a close look on how everyone is contributing in the server :slight_smile:

Thanks for putting this together @Rayne. One question, the bee channels are open to all members who are ‘Verified’. Does this mean BrightID verified? Was able to get into #gardens, #tulips, #flora, #celeste, #buzz channels by following the instructions on the welcome thread (clicking channel emojis). However, I can’t seem to figure out how to get into the other channels such as #pollen, #dev, #design, etc. Are those actually keeper channels (1 HNY required)?

1 Like

@s_ben You need to be Bright ID verified and additionally need to !verify yourself for the discord server by typing that command in the #bot channel (though I think it works in the other top channels as well).

It works better if you wave a wand at the screen at the same time.

3 Likes

Hey Seth, this does indeed mean it requires brightid verification. If this is too much of a hassle give us (perhaps @lkngtn or @befitsandpiper) a shout on discord and we can work something out.

2 Likes

Thanks for the follow-up @Harry, @Jasper. Was able to get in. Documented the confusion I had on discord in case it helps :point_down:

hey @Harry, got in! Was confused before, as I was already BrightID verified and connected to 1Hive. was busy so just skimmed the bot instructions and gave up, thinking it was a problem on the backend. went through the process again this morning, read all the way through the steps, realized there were additional steps (scanning the code, typing !me), did them and it worked. can now see #pollen, #dev, etc.

3 Likes

@s_ben Thanks for highlighting something I wanted to point out that is still not really clear (as exhibited by your comments) to everyone.

  1. BrightID verification generally which pretty much is required to access faucet, get discord roles and to earn pollen.
  2. The steps to connect your verified brightID to discord (so you basically have the discord as one of the apps connected in BrightID)
  3. Being BrightID verified and connected to the faucet basically gets you the 1Hive app in BrightID application
  4. The steps to get connected to 1Hive instance of sourceCred so they can earn pollen.
  5. Using !join and having 1HNY in your associated wallet to get the Honey role in discord in addition to the ‘verified’ role.

In the loosest sense I think the term ‘verify’ or ‘verified’ without some other descriptor delineating differences between:

  • the process to be verified for what, and the most critical for a user
  • how can they confirm that they are successfully verified for 1 of the above things.

I think the biggest confusion and issues that crop up in these is the order with which they are done because different things happen if one isn’t BrightID verified first for most of these.

Example: Someone will connect their wallet with faucet and not be BrightID verified will see a message there along the lines of ‘waiting to be verfied’ which I have not checked but should say "waiting for you to be BrightID verified’ and will NOT allow the user to connect to the faucet. Now if someone was already BrightID verfied the faucet will just give them a BrightID QR code so they then get the 1Hive App connected to BrightID and can then access the faucet. The user confirmation of this step is either by seeing faucet button and/or a 1Hive app icon in their BrightID app or not.

Right now off the top of my head I do not have a set of terms to define these nicely.

I do know when we ever say ‘verified’ and mean ‘BrightID verified’ we should say that.
I also think we need to talk about confirmation. So when a user gets verified in some way they should be able to get a ‘confirmation’ they are verified for something. So if I was going to use a bot to do some of these functions I might have.

!confirm BrightID
!confirm Pollen
!confirm wallet
!confirm discord
!confirm discourse

Where bot results on say
!confirm BrightID

example 1: (not confirmed)
!confirm BrightID
RogueTwo - not BrightID verified - with link to BrightID meet + BrightID discord.
RogueTwo - BrightID verified

!confirm discord
RogueTwo - discord BrightID verified and confirmed
RogueTwo - discord verified and confirmed with following roles. Honey(more than 1HNY in wallet), Verified BrightID verified, Flora
RogueTwo - discord user Pollen verified and confirmed

etc.
The general
!confirm command without parameters could give a general report of everything, BrightID, faucet, discord, discourse, github, pollen

I am not married to any of the names/details here other than the terms should be pretty clear and well delineate between the differences. Also if the role is NOT verified there should be a link to help on how to become verified and to confirm this.

6 Likes

Excellent. Also be aware that many people that just come in the discord server and see 5 others type !verify or !join, often they will blindly copy it and do the same.

So in a perfect world, in the end every command should either generate a success (with confirmation) or a fail (with confirmation and pointers on what to do).

maybe for newbies it will be good to detail the purpose of some channel like

  • :sunflower: Gardens
  • :hibiscus: Flora
  • :tulip: Tulip
  • :sun_with_face: Celeste
  • :honeybee: Buzz
  • :butterfly: Morphosis
  • :white_flower: Pollen

for understand what is it talking about and how they can help and participate ?

1 Like

Read the message in the welcome channel, this information is already given.

1 Like

Hello ~

Something I notice , the name of the channels are miss leading sometimes . like the names in them self does not explain what they are .

Example ~ On boarding ~ you must know alot things before you know what for ~ .

Also general and honey ~ what different about them . I mean a bit not clear …

I hope the idea is clear ~~~

^.^/

1 Like

Hi All,

i’m new here discovering this promising “startup”, still asking is it serious or rather game play for children?!? Please tell me:
1/ That complex, confusing, unclear verification/approval process - is it intended to be difficult for new users to get in? Should users show enough effort to get qualified “bee”?
— if so, wouldn’t it be better to prove users through exams of project, forum&discord rules etc? Process which educates them and increases the knowledge of all?
2/ If this is not intended, then there is a huge lack of structure and clear information and clarification. And this applies in any case.
— I got verified, but i still don’t know why that was so important? Why BrightID, what is the value of that? Why click&paste in discord and studying and searching and finally know nothing why i need to do so? Eg. many links invites “join our discord”, when i joined, i was not able to write in any channel - ???

I miss some more implicit and strong support/FAQ page, information are this and that, pieces of the process here and there, ideas here and there, and the CORE realy unclear overall.

Can you leave an answer on these lines please?

(I understand, this all could be under construction - in such case i can help maybe…)

Hi, there is lots of documentation on all of this, especially on discord. To use honeyswap you don’t need to be verified, you only need to be verified if you want to use the faucet. Please refer to the information in the #welcome channel in discord to guide you further.

Hi Jasper,
thank you for your guide. I realize, that i did not read everything 100 % carefully.
But thats just what i’m pointing out. I read and spend quite lot of time and finaly, bored of a lot of unstructured (or unusually structured) information, i didn’t catch some important basics.

Eg. I use to look for FAQ and Support page when new. But FAQ here
is not FAQ at all. This is only one of many examples.

Yes you are correct and we are well aware of this. The project has grown enormously past weeks and some aspects are still catching up.

We are restructuring everything at the moment, to make it clearer and to remove redundancy. Any input is welcome, so if you have any specific ideas, let us know.

This is a community project and the community = us :blush:

I would be delighted to offer some improvement ideas. However, i need to discover thoroughly this site first before i can say anything helpful. Thank you for your reaction