Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
How can an SE refugee help fix encoding problems?
"Scoring System for Trust Level Requirements" by Mithrandir24601 states that at some point, interaction with the site will be gated behind trust levels, as described in "User Privileges" on the GitHub wiki. One thing that struck me as odd coming from Stack Exchange is that users who don't yet have a positively scored question or answer cannot suggest edits to others' questions or answers, despite the need for edits to clean up errors with the UTF-8 character encoding. (See "Character set conversion(?) failure during initial import from SE" by aCVn.) Another is a vague hint that some sites won't even let newly registered users ask questions, which I see as one big Catch-22. (See "How do I ask a question?" in Codidact FAQ.)
I have an account, and I've linked it to my Stack Exchange account, but my questions and answers from Worldbuilding SE were imported with zero votes here. This means I start at square one with zero trust with which to upvote others' questions and answers on Scientific Speculation. Nor can I tell whether my account is actually allowed to do anything because unavailable actions aren't actually hidden. (See "Post action links that cannot be used should be hidden" by aCVn.)
Will there be some way for Stack Exchange refugees to draw attention to their old imported questions in order to gain enough trust to suggest edits to others' imported questions? Or should they look for questions asked here that they can answer here before trying to help in other ways?
1 answer
tl,dr: You need'nt worry about this yet.
When we started this project, it was decided, that we wouldn't want a single "reputation" number, but rather finer more specific numbers, such as for example something like "edit helpfulness reate", and a broad concept of "trust levels".
However, for some reasons, we then later decided, to use an existing software (QPixel) by one of our contributors and to set it up for some communities needing a new home asap. We'd develop our "core" software in our chosen tech stack (C#, ASP.NET), but we'd also improve the qpixel software to have the same features as core should eventually have in MVP.
This process is not yet finished. So you'll still see things, which we will change, but which haven't changed yet. Reputation vs Trust Levels is one of these things.
We currently still use reputation, and everyone with a registered account can suggest edits.
This is bound to change at some point in the future, but there will be measurements to allow for new users and new communities to be actually able to gain these privileges.
0 comment threads
1 comment thread