I’m writing this topic based on some concerns brought to me by other participants in combination with things that I’ve personally noticed. My goal is simply to bring the topic up for community discussion. I recognize that there may not be an immediately obvious solution, but I figure our community would value having stuff like this documented and brought to light so we can all think about it together.
I’ve noticed that the Announcement Channel in our Discord has some interesting impacts on the Cred of specific participants. The Announcement channel is a space that is super loosely defined, especially when it comes to crediquette (how we as participants engage with the current Cred mechanisms) and I think that’s creating some unintentionally inaccurate or obscured Cred-flows.
There are two major Cred inconsistencies that I’ve noticed with the Announcements Channel:
Lead Announcments
In the Announcement Channel there has been one announcement related to a person being elevated to Lead status, and a ton of emojis were added which flows a huge amount of Cred to both the person who made the announcement and the lead who was spotlighted. However, we haven’t repeated this announcement process with any of the folks elevated to lead status since then.
I don’t think this is out of any kind of favoritism but simply a lack of Cred literacy, lack of defined crediquette, and lack of defined process around when and what to post in the Announcements Channel.
I think that the amount of Cred flowed to the one lead who was announced isn’t bad. In fact, I can see it acting as a Cred-correction because there is so much that all leads do behind the scenes which our technology can’t see yet. Having that Announcement Channel bump evens that out, even if in a better world we’d just be tracking all the contributions of value instead of making up for lost contributions. However, if we feel that’s true for one lead, then why would it not be true for all leads?
Should all new leads be given a spotlight in the Announcements Channel, or should we find a different way of correcting for those as-of-yet untracked lead contributions?
Cred for Posting Announcements
Another thought re: Cred and the Announcements Channel is that anyone who makes an announcement gets a lot of Cred emojis because of the announcement’s visibility and wide-spread relevance.
For example, I didn’t come up with the idea of taking December off. I deeply agreed with it, helped encourage it, helped advocate for income stability which inspired the Grain boost, and I took the time to write up the announcement in Discord and Discourse. However, the Cred I’ll get from having been the person to share the announcement on both platforms is inaccurate because I was not the sole or even most instrumental person in us taking the month off.
I deserve some of the Cred, but certainly not all of it.
When I got props-ed for that idea/announcement in the Discord Props Channel (which flowed me even more Cred for this idea that was not originally mine), I took that opportunity to spread the Cred to Dandelion; pointing out how they originally came up with the idea in a props of my own. This is a work-around that I was able to spontaneously create, but it’s by no means a commonly expected or defined crediquette move.
My overall point is that our crediquette, Cred-flow literacy, and guidelines for use of the Announcements channel are all under-developed and I see it creating strange Cred-flows.
Some actions we could take:
- Accept that the Announcements Channel is flawed and make up for it with how we interact. Creating some crediquette-based Announcement Channel guidelines that are well communicated and commonly understood to mitigate the uneven way it’s flowing Cred right now.
- Turn off Cred minting for the Announcements channel all together and ensure that important correction-Cred flows around via other methods.
Feel free to share other perspectives or solutions. My intention is simply to surface this discrepancy that I and others have noticed in an effort to live up to our values of Accuracy and Transparency.