Username: 
Password: 
Restrict session to IP 
Online within 1d

WeChall Certificates – A Strategic Upgrade

1 2
Global Rank: 1
Totalscore: 759246
Posts: 11
Thanks: 7
UpVotes: 6
Registered: 13y 218d
rayaseiren`s Avatar








Last Seen: 114d 1h
The User is Offline
RE: WeChall Certificates – A Strategic Upgrade
Google/translate1Thank You!1Good Post!0Bad Post! link
I really like this idea, and I think WeChall has a very unique chance to make certificates more meaningful than a simple points-based badge.

What makes WeChall special, in my opinion, is not only the score itself, but the fact that it connects achievements across many different challenge sites. It also reflects long-term dedication, category diversity, and the experience of gradually climbing through the challenge ecosystem.

So maybe a WeChall certificate could focus on things that only WeChall can really represent: multi-site achievements, long-term progress, curated category paths, and possibly some kind of mentor or admin verification for higher-level certificates.

I also think it would be important to respect the alias culture of the community. Certificates could use the nickname by default, with an optional real-name field for people who want to use them professionally. A public verification link connected to the WeChall profile would help make the certificate trustworthy without forcing users to reveal more than they want.

In that sense, a WeChall certificate would not just be proof of points, but proof of a real journey across many different challenge worlds. I think that would fit WeChall’s identity very well.
1 2
quangntenemy, TheHiveMind, Z, balicocat, Ge0, arraez, jcquinterov, hophuocthinh, alfamen2, burhanudinn123, Ben_Dover, stephanduran89, braddie0, fpombal, csuquvq have subscribed to this thread and receive emails on new posts.
1 people are watching the thread at the moment.
This thread has been viewed 11448 times.

PHP Fatal Error(1): Constant E_STRICT is deprecated since 8.4, the error level was removed in www/protected/config.php line 6


Backtrace starts in [unknown file] line ?. GWF_Debug::shutdown_function() core/inc/util/GWF_Debug.php line 109. GWF_Debug::error_handler().... core/inc/util/GWF_Debug.php line 180.