enforcer48 cross-posted this post in Community Announce 3 years ago


Come to STEMGeeks: A Curator's Beckoning

in STEMGeeks3 years ago

         Looking to read about STEM-related topics with another token attached to it? STEMGeeks got you covered!

         The tribe picks up posts that have the tags science, technology, engineering, and math. It also looks at stem and stemgeeks as well, though the latter tends to be more for administrative posts.

         As the tribe's name suggests, the token for STEMGeeks is STEM. There is also a miner associated with the tribe with the ticker STEMM.

         This tribe hosted the first Hive Hackathon event last year. The @hiveonboard project by @roomservice was the grand prize winner.

What type of content do we want?

         Many people on Hive has the misconception that STEM content has to be like the academic articles. You know, with citations of peer-reviewed papers and whatnot. While we welcome such content, it is important to understand that it is not the only acceptable form.

         We love to see videos, DIY experiments/projects, or even sharing about things you've found. That is, if you add at least some original thought instead of copy/paste links.

         And for some, writing may not be your thing. In which case, we welcome good collections of STEM-related photos. If you are digital artist, show us the process of how you created your masterpiece. There can be many different ways to show your enthusiasm for STEM.

What if you aren't a content creator?

         At STEMGeeks, we support meaningful engagements between authors and audience alike. The curators reward comments as long as they are do not seem like placeholders to fish for votes. This way, people won't feel compelled to create content for the sake of creating.

         If you don't feel like interacting with anyone, you are free to only cast your votes and/or staking STEM miners. Funds on Hive such as @brofund and @discohedge also distribute them through dividends.

         In short, you don't have to be a content creator or social person to earn STEM.

What type of content do we not want?

         It's tempting to categorize crypto posts under the technology umbrella. However, we do not accept content focused on the price movements or market conditions. TAs are also not what we are looking for in terms of content.

         We discourage daily reports and stats posts as they are. Often, these are repetitive even when they relate to STEM. We already have the community owner account, @stemgeeks, that make tribe announcements.

         Talking about the tribe is fine, but we don't want them to become too prevalent. Bottom line is, if you have to think too long about why your post is STEM-related, it might likely not be.

So, why use the STEMGeeks' front end?

         In your journey through the tribe, you may discover other communities of interests. One of my favorite examples is the Architecture and Design community.

         Posting via STEMGeeks will send your post to appear under the STEMGeeks community. Furthermore, it also allows you to keep 100% of your author rewards in STEM. Currently, there is a 50% penalty on author rewards for content posted not through our front end. The tribe burns author rewards from the said penalty, further reducing the supply.

         This is similar to the penalty that exists in other tribes such as LeoFinance and Neoxian City. This encourages users who want the STEM tokens to use our front end.

What are some features of the front end?

         You can see which author used STEMGeeks to post their content. There will be a small tribe symbol next to their post time stamp.

         Like other front ends, you can promote your post by sending some STEM tokens to @null. Make sure they are STEMGeeks links. Promoting your post may help you become more visible to those looking at STEM content. It's less competitive than front ends like PeakD where you'd be bidding against every tag.

         The curators are usually more willing to visit your posts when you choose to promote it. Promoted posts have blue highlights around them for easier identification.

         STEMGeeks has feature you could use to interact with the community on Discord. This is for those who may feel hesitant towards using a centralized service. Or, if you don't feel like getting a Discord account.

Moderation

         The rules are simple:

         As tribes evolved, we have moved away from downvoting as a mean to mitigate abuse. At STEMGeeks' inception, we opted for an anti-abuse account with massive STEM stake. This was due to limitation of the system and caused controversies for some. Even when the effect on HIVE payout was negligible, not everyone was appreciative. This was further complicated by the fact that we span across multiple tags. We don't own the STEM-related tags, we only adjusted STEM payouts.

         These days, we are capable of muting individual posts without muting the user. Sometimes, the content may not be what we are looking for. This gives us more flexibility and without the need to engage in downvoting content.

         For grievous offenses, we mute the user accounts from the tribe. A muted user can no longer earn STEM tokens via proof-of-brain or mining.

         Downvotes are now relics of the past in the tribe. It's only used for reward disagreement when our muting abilities are not affected.

Future directions?

         The second Hive Hackathon event is definitely on the table. We would love to encourage useful projects to the Hive ecosystem to debut.

         The ultimate goal of STEMGeeks is reaching out to educational institutions. This is an ambitious end goal that requires a lot of build up and improvements in the tribe. But, we will take it a step at a time.

         In the meantime, you can spend STEM in @dcitygame to obtain some scientists for your city.

Posted with STEMGeeks

Sort:  

pixresteemer_incognito_angel_mini.png
Bang, I did it again... I just rehived your post!
Week 48 of my contest just started...you can now check the winners of the previous week!
2