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

The Journey and Future of WeChall

Global Rank: 24
Totalscore: 390563
Posts: 263
Thanks: 215
UpVotes: 274
Registered: 18y 257d






Last Seen: 114d 50m
The User is Offline
The Journey and Future of WeChall
Google/translate2Thank You!5Good Post!0Bad Post! link
WeChall early days

When WeChall first appeared, it was a spark in a dark and scattered landscape. Challenge sites were everywhere, but each one was its own island, with no bridge connecting them. Then came WeChall - an innovation that stitched the fragmented world together. For the first time, hackers/challengers could carry their identity and reputation across platforms, measure themselves against a global scale, and feel part of something larger than any single site. It wasn’t just useful. It was elite.

Those early days carried an energy, a sense of discovery. Watching your linked accounts light up the scoreboard felt like belonging to a secret society. It was proof that someone out there understood what real challenge meant.

The Present: A Quiet Survivor

Today, WeChall is still here. Still growing, though slowly. The fire is smaller, but it hasn’t gone out. New challenge sites rise and fall in the rotten world of hype and disposability, yet WeChall remains - a steady veteran. It is less flashy than the newcomers, but more enduring. A gathering of the dedicated, those who remember why this all began.

But the game has changed. Competitors with sleek designs, corporate funding, and gamified platforms dominate attention. To many new learners, WeChall looks old-school. And maybe it is. But old-school carries weight.

The Future: Two Possible Paths

WeChall now stands at a crossroads.

Path One: Slow Decline
If development remains minimal, funding uncertain, and the user base stagnant, WeChall risks fading into obscurity. Competing platforms with bigger budgets and faster innovation could eventually overshadow it. Challenge sites come and go, and WeChall could one day disappear too. In this outcome, it becomes more of a nostalgic archive than an active hub - respected, but silent.

Path Two: Renewal and Growth
There’s another path - a brighter one. With the right support, WeChall could reinvent itself and spark the same excitement it did in its early days. By opening its doors to volunteers, setting up a clear framework for contributions, and securing donations or sponsorships, the platform could modernize, grow, and inspire again. New features, fresh integrations, and stronger community bonds could transform WeChall from a quiet veteran into a thriving hub once more. A shared sense of ownership and vision would help it thrive again.

Suggestions for a Stronger Future

1. Volunteer Framework: Define clear, more refined ways for contributors, so community members can step in with purpose.
2. Funding and Donations: Launch a structured donation system, or sponsorships to secure recurring support.
3. Community Building: Modernize the forums, add mentoring, or other features to make WeChall not just a tracker, but a living network.
4. Modernization: Refresh the site step by step - new integrations, deeper analytics, and even better UX.
5. Visibility Through Modern Tools: Use social networks (Facebook/Linkedin), modern chat platforms like Discord, and regular updates to amplify WeChall’s presence and attract a bigger audience - not just new challengers, but also educators, students, security professionals, event organizers, and even companies that could benefit from and contribute to the ecosystem.

WeChall began as a daring innovation. Today, it survives as a steady flame in a world where most projects burn out quickly. Tomorrow, it could either fade away or rise again as a beacon for those who seek real challenge, beyond the noise of a rotten world. The choice is not just with its creators - it is with the community it first helped unite.

The question is simple: will WeChall drift into memory, or will the elite rise once more to build its next chapter?
Last edited by quangntenemy - Sep 13, 2025 - 17:01:38
Global Rank: 198
Totalscore: 110647
Posts: 1795
Thanks: 1390
UpVotes: 961
Registered: 18y 258d




Last Seen: 64d 14h
The User is Offline
RE: The Journey and Future of WeChall
Google/translate0Thank You!1Good Post!0Bad Post! link
I would like some things:

1) Fav Challs in profiles + challenge list and metadata from the sites.

2) Split WC server2 (this one) into old for challenges and new for the rest of web (modernized, phpgdo).

3) The cert thingy... quang cert could be solve all fav challs from quang.

Thanks for your input.

- giz
The geeks shall inherit the properties and methods of object earth.
Global Rank: 24
Totalscore: 390563
Posts: 263
Thanks: 215
UpVotes: 274
Registered: 18y 257d






Last Seen: 114d 50m
The User is Offline
RE: The Journey and Future of WeChall
Google/translate1Thank You!3Good Post!0Bad Post! link
The path looks sharp, gizmore. Fav lists, split, certs - solid steel.

But don't forget the fire needs more fuel. Without widening the circle, the signal stays faint.

Time to draw fresh minds into the fold.
Global Rank: 16
Totalscore: 462313
Posts: 8
Thanks: 8
UpVotes: 10
Registered: 13y 321d









Last Seen: 113d 15h
The User is Offline
RE: The Journey and Future of WeChall
Google/translate2Thank You!2Good Post!1Bad Post! link
Proposal: Integrating Learning Paths into WeChall — From Practice to Mastery

Overview

WeChall has long been a hub connecting diverse challenge sites and tracking progress across them. However, its current structure focuses primarily on the what of learning (challenges) rather than the how (guided progression). To foster renewal and long-term engagement, WeChall can evolve from a challenge aggregator into a learning and mastery platform — one that teaches, guides, and then tests.

Concept: Learning Paths

Learning Paths would be curated, structured sequences that guide users through a topic — such as cryptography, web exploitation, or reverse engineering — combining educational material with practical challenges.

Each path would include at least:

1. Concept Modules: Concise, well-structured textual lessons introducing key theory, examples, and resources.
2. Challenge Integration: At the end of each module, learners are directed to relevant challenges — either hosted on WeChall or linked to external partner sites (e.g., “Now that you understand SQL Injection basics, try Challenge ABC on Site XYZ”).

Benefits

1. Bridges Learning and Application: Learners gain context and confidence before tackling challenges.
2. Strengthens Ecosystem Links: By referencing challenges from other sites, WeChall becomes a gateway and guide, not just a scoreboard.
3. Encourages Contribution: Volunteers can create or refine learning paths, sharing expertise while keeping WeChall’s knowledge base current.
4. Increases Engagement and Retention: Users will stay longer, progress further, and share more — creating a virtuous cycle of growth.

Implementation Possibilities

1. Launch with a few pilot paths (e.g., Cryptography Basics, Intro to Web Security).
2. Allow community-driven submissions and peer review for new paths.
3. Explore partnerships with challenge sites to formally align paths and cross-link progress.
Global Rank: 8858
Totalscore: 952
Posts: 4
Thanks: 6
UpVotes: 10
Registered: 364d 21h
Last Seen: 312d 13h
The User is Offline
RE: The Journey and Future of WeChall
Google/translate3Thank You!7Good Post!0Bad Post! link
I am completely new. It takes getting used to. But its fantastic site! Honestly.

I think if more people knew about it, it would be bigger.

I like that its this oldschool. I actually probably rather love it! Why? Because its about the promise of fast web browser due to almost zero overhead of client-side JS. Its rare but as a pentester and normal human I just like it, its rare, but its fully functional concept that did not get obsolete in my mind.
Global Rank: 374
Totalscore: 66437
Posts: 274
Thanks: 258
UpVotes: 278
Registered: 15y 319d
space`s Avatar
The User is Offline
RE: The Journey and Future of WeChall
Google/translate1Thank You!1Good Post!0Bad Post! link
I also love the oldschool style and that there is not much Javascript involved.

Quote from quangntenemy
Sep 13, 2025 - 16:56:18

1. Volunteer Framework: Define clear, more refined ways for contributors, so community members can step in with purpose.


Everybody is invited to make Pull Request to the underlaying GWF (Gizmore Website Framework): https://github.com/gizmore/gwf3.

Quote from quangntenemy
Sep 13, 2025 - 16:56:18

3. Community Building: Modernize the forums, add mentoring, or other features to make WeChall not just a tracker, but a living network.


What do you mean concrete? In which way should the forum be modernized?

Quote from quangntenemy
Sep 13, 2025 - 16:56:18

4. Modernization: Refresh the site step by step - new integrations, deeper analytics, and even better UX.

As said, I like the oldschool style, but am open for more UX and UI improvements.
If anybody has concrete suggestions (or want to generate some with AI) e.g. for styling of the buttons, better fitting colors for some elements, functionality, shortcut icons, etc. please post them.
Some things can be achieved with little effort.
For example, I today created a Pull Request to add a copy button to source-code blocks: https://github.com/gizmore/gwf3/pull/147.
Contact only via c3BhY2VAd2VjaGFsbC5uZXQ= or PM...
Windows can be secure... but only if you don't use it Happy
Global Rank: 537
Totalscore: 48734
Posts: 6
Thanks: 6
UpVotes: 6
Registered: 357d 2h


Last Seen: 129d 2h
The User is Offline
RE: The Journey and Future of WeChall
Google/translate1Thank You!1Good Post!0Bad Post! link
My two cents as a newbie...
I also like the oldschool look, but this could have a more modern look, without sacrificing the oldschool look.
Some things you could do to draw in (some) more money for the servers : make a distinction between free and paying users. I would make subscription fairly cheap (like 5-10 euros a year) so that more people will be inclined to subscribe. Paying users could have some advantages : more stats, maybe more chall sites to aggregate (if you say free users can have 5 sites, but paying will be unlimited,...).
Also make it more visible if a certain user added a challenge himself or if he has a 100% on a site... Check out Project-euler, who has lots of 'awards' for user completing certain goals.
The forum over here is not that straightforward for me, looks a bit messy (but that could be just me).
Adding a discord channel could certainly improve the influx of new users, as would visibility on social media (even though myself i do not engage in social media much). Also here you add an 'award' to people for posting on x,bsky,fb,snap or whatever else exists...

Also maybe proactively reach out to existing chall sites...to draw more people in.

First thing you need to do is putting together a team who will be responsible for this. Not that they should do all the work, but that they could coordinate, while everyone is invited to give their ideas and moreover to help implement the new stuff. That could be the original founders of this website, but could include other people too with bright ideas
Global Rank: 24
Totalscore: 390563
Posts: 263
Thanks: 215
UpVotes: 274
Registered: 18y 257d






Last Seen: 114d 50m
The User is Offline
RE: The Journey and Future of WeChall
Google/translate1Thank You!1Good Post!0Bad Post! link
Quote from space
Mar 15, 2026 - 21:57:15

I also love the oldschool style and that there is not much Javascript involved.

Quote from quangntenemy
Sep 13, 2025 - 16:56:18

1. Volunteer Framework: Define clear, more refined ways for contributors, so community members can step in with purpose.


Everybody is invited to make Pull Request to the underlaying GWF (Gizmore Website Framework): https://github.com/gizmore/gwf3.

Quote from quangntenemy
Sep 13, 2025 - 16:56:18

3. Community Building: Modernize the forums, add mentoring, or other features to make WeChall not just a tracker, but a living network.


What do you mean concrete? In which way should the forum be modernized?

Quote from quangntenemy
Sep 13, 2025 - 16:56:18

4. Modernization: Refresh the site step by step - new integrations, deeper analytics, and even better UX.

As said, I like the oldschool style, but am open for more UX and UI improvements.
If anybody has concrete suggestions (or want to generate some with AI) e.g. for styling of the buttons, better fitting colors for some elements, functionality, shortcut icons, etc. please post them.
Some things can be achieved with little effort.
For example, I today created a Pull Request to add a copy button to source-code blocks: https://github.com/gizmore/gwf3/pull/147.


Great to see more ideas coming!

I agree the old-school style is a strength. But there’s still plenty of room for improvement without losing that identity.

Regarding your points:

1. Volunteer Framework
It’s great that contributions are already open through the GWF repository.
What I meant is making that path more visible and motivating. Something beyond “solve challenges” - more like “help build something meaningful for everyone”

A public roadmap would also help a lot. If people can see what’s coming next - including small tasks, not just big features - they can contribute in small parts.

2. Forum / Site Modernization
Not a full redesign - more like subtle evolution. For example:
- Better Unicode support
- Reactions beyond just “like” (love, haha, etc.)
- Lightweight emoji support in posts
- Improved mobile readability

Small changes like these can make the platform feel more alive without changing its core.
klinsten, 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 1458 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.