Clarifying a few points about CoderLegion
We’ve recently come across some public claims about our platform that don’t accurately reflect how things work. For transparency, here are the facts:
• Origin & development timeline — The CoderLegion project has been under active development since 2020. However, the current domain and infrastructure were set up later, after an earlier version of the platform and rebranding from a previous domain. The “2020” value in our metadata/schema is legacy data and was unintentionally carried over due to a configuration issue, and we are updating it to accurately reflect our public-facing timeline
• Platform availability — A recent downtime was caused by planned updates and infrastructure changes. The site is fully operational.
• Ads & monetization — We are continuously exploring sustainable ways to support the platform while keeping it accessible. The platform previously did not include ads, but we now offer an ad-free experience for Pro users. The “ad-free” note on the About page was not updated, but has been updated to reflect this change.
• Users: CoderLegion currently has 4,100+ registered users. The figures cited in external posts appear to use different definitions of activity (e.g., daily writers vs monthly activity), which does not match our internal metrics or dashboard data.
• Domain status clarification — The claim that the CoderLegion domain is blocked from renewal or nearing expiry is incorrect. The domain is active and has been renewed successfully. Any references to “clientRenewProhibited” do not reflect the current registrar status.
• The issues mentioned in the authentication flows have been identified as a bug on our side. Our development team is actively working on fixing and improving the verification logic for both password reset and account deletion flows to ensure proper authentication checks are enforced. We take these reports seriously and are updating the system accordingly.
• CoderLegion is active and fully operational. There are no continuity or access risks requiring users to export content. We maintain and renew all infrastructure to ensure uninterrupted access.
• Other technical issues - we are continously listening to any issues faced by users and fixing it for better experience.
We welcome the use of public verification tools such as WHOIS, HTTP inspection, and source code review. However, some conclusions in the analysis are based on interpretation without full system context. We are actively improving consistency across our metadata and infrastructure to ensure clearer public information going forward.
We’re building CoderLegion in the open, and we welcome feedback—but it’s important that discussions are based on accurate information.
If anyone has questions, feel free to reach out directly.
— Team CoderLegion
