A while ago, I started building a social media platform called VibeConnect. It was mostly a learning project. I was experimenting with authentication, posts, communities, profiles, and other social-media features while learning how everything worked. But VibeConnect had a lot of problems. Security wasn't strong enough, several important features were missing, there was no proper 2FA, media handling was incomplete, and many parts of the platform were still unfinished. Instead of trying to keep patching the same project, I decided to start again — this time with a much bigger goal. That's how CrowdWide started. Why I Started CrowdWide One thing I've noticed while building and sharing projects is that getting people to discover your work can be surprisingly difficult. When you post something on an existing social platform, larger accounts and established communities often already have a huge audience. That doesn't necessarily mean their content is better. It just means they already have momentum. As someone who builds projects while learning, I've experienced this myself. You can spend days or weeks working on something, share it online, and barely get any attention. Meanwhile, an established account can post something similar and immediately reach thousands of people. That made me think: What if a social platform gave newer creators and smaller communities a better opportunity to be discovered? That question eventually became CrowdWide. What Is CrowdWide? CrowdWide is a social platform I'm building around communities, creators, and discovery. The idea isn't to guarantee that every post becomes popular. Instead, I want community size to be less of a barrier to getting that initial exposure. CrowdWide is intended to support different kinds of creators and communities: Developers YouTubers Bloggers Artists Writers Project builders Personal blogs Article creators Online communities People documenting their learning journey The goal is to make discovery more accessible without removing the importance of good content. Experimenting With the Feed Algorithm One of the ideas I've been experimenting with is how the initial feed distribution works. My current experimental split is: 40% — new users and smaller/new communities 55% — established communities 5% — viral or trending content This isn't meant to be a permanent rule. It's an experiment. The important idea behind it is that community size shouldn't completely determine whether something gets seen. A post from a small community should have an opportunity to prove itself. If people interact with it positively, it can gain momentum and receive more distribution. So instead of: Big community → automatically gets more reach I'm trying to move toward: Initial opportunity → people respond → content earns more reach I'm still working out the exact algorithm, and I expect this part to change significantly as I get real usage data. What I've Built So Far CrowdWide has grown quite a lot from the original idea. Some of the things I've implemented include: Posts and Content Text posts Articles Polls Drafts Scheduled publishing Media uploads Alt text Hashtags Mentions Quote posts Linked post replies Content warnings Post editing and deletion Engagement Likes Comment likes Reactions Bookmarks Sharing Nested replies Threaded discussions AJAX interactions without full page reloads Communities Public and private communities Join requests Community roles Moderators Banned words Post approval Pinned posts Community guidelines Community feeds Profiles Profile banners Avatars Bios Links Followers and following Saved posts Activity Likes Comments Privacy controls Discovery I've also been working on the discovery side of the platform: Personalized feeds New-content discovery Viral posts Trending hashtags Recommended users Recommended communities Search filters RSS support An API for posts There is also an unanswered-post discovery filter so people can potentially find posts that haven't received a response yet. Security Has Been a Major Focus After working on VibeConnect, I realized how important it is to think about security early rather than treating it as something to add at the end. CrowdWide currently includes things such as: Email verification Password reset Login lockouts TOTP-based 2FA Recovery codes Session/device management CSRF protection Security headers Rate limiting Account suspension Reports and moderation queues Audit logs Data export and deletion I'm also trying to make security-related actions visible and understandable to users rather than hiding everything behind the scenes. Moderation Is Another Big Part A social platform isn't just about building features that let people post. You also need systems for dealing with abuse, spam, inappropriate content, and community-level moderation. CrowdWide already has reporting and moderation infrastructure, but there's still a lot I want to improve. Some of the things I'm working toward include: Moderation appeals Evidence attachments Temporary mutes Better CAPTCHA and abuse controls Stronger spam detection Better moderation tooling More comprehensive automated testing I want moderation to be useful without making communities feel overly controlled. What Still Needs to Be Done Despite having a large feature set already, CrowdWide isn't finished. Some of the major things still on my roadmap are: Browser push notifications Link previews Richer article editing Media captions and transcripts Moderation appeals Better spam detection More automated integration tests End-to-end signup and posting tests Structured logging Monitoring and alerts Backup and restore testing CI/CD Staging infrastructure Virus scanning for uploads API documentation More admin functionality And, of course, there are probably bugs I haven't discovered yet. The Testing Problem One of the hardest parts of building something like this isn't necessarily writing the code. It's testing it properly. There are a lot of interactions between different parts of a social platform. Also, I have created different roles like admin, moderator and user... by default you will have role user. To get role moderator just mail on the contact email developerpuneet2010@gmail.com and after verification you will get role moderator and you can access the panel but if you break the rules that role will be deleted For example: Account → Community → Post → Comment → Notification → Moderation A change in one area can unexpectedly affect another. Right now, I'm working toward having much stronger automated tests before opening the platform to more people. I'd rather discover problems during testing than after a public release. What's Next? My current plan is roughly: Finish the remaining core features Complete the admin and moderation systems Add more automated tests Perform manual testing Set up staging Get a few developers to test it Fix the issues they find Release a public beta Monitor the platform Continue improving it Eventually move toward a stable release I'm deliberately not trying to rush the public launch. A social platform needs to be reliable, secure, and reasonably polished before putting it in front of a larger audience. From a Learning Project to Something Bigger The biggest difference between VibeConnect and CrowdWide isn't just the number of features. It's how I'm approaching the project. VibeConnect was primarily about learning how to build a social platform. CrowdWide is about trying to solve a problem that I've personally experienced while building and sharing projects. I'm still learning a lot while developing it. There are plenty of things I don't know yet, and I'm sure the architecture and algorithms will change as the project grows. But that's part of the process. I'm building it, breaking things, fixing them, and learning along the way. Where CrowdWide Goes From Here I don't know exactly what CrowdWide will look like a year from now. The feed algorithm will probably change. Some features will probably be removed. New ones will probably appear. And I'm sure I'll rewrite parts of the code that I currently think are perfectly fine. 😅 For now, my goal is simple: Build the best version of the idea I can, test it properly, and see whether it actually helps smaller creators and communities get discovered. That's where CrowdWide is today. And this is just the beginning.