Status: Under Development 🚧

I've been building social media platforms for a while now. CrowdWide is the one where I'm trying to take everything I learned from my earlier projects and turn it into something I actually believe could solve a problem.

Where the Idea Came From

Before CrowdWide, I built another social media website called VibeConnect.

At that time, I was still learning. I built a lot of the project while learning web development, security, databases, and everything else involved in making a real web application.

Eventually, I realized that VibeConnect had a lot of gaps. Security wasn't where it needed to be, there was no proper 2FA system, encryption and secure storage needed significant improvement, media storage wasn't properly designed, and there were many features that were simply missing.

It was an important project for me, though, because I learned a lot from building it—and even more from seeing what I had done wrong.

The Problem That Led to CrowdWide

While I was learning and building projects, I also wanted people to actually see what I was creating.

I would post projects and content on existing social platforms, hoping that people would discover them.

But I kept noticing something: large accounts and established communities already had a huge advantage.

If someone already had a large following, their content had a much easier time getting attention. If you were new, getting that first audience was much harder.

And this isn't only a social-media problem. The same pattern exists for new YouTubers, bloggers, artists, writers, developers, and other content creators.

Someone who started years ago has had years to build an audience. Someone starting today has to somehow compete for attention with people who already have one.

That made me think:

What if I built a platform where being new didn't automatically mean being invisible?

That question eventually became CrowdWide.

What Is CrowdWide?

CrowdWide is a social media platform centered around communities and discovery.

Users can create profiles, create and join communities, publish posts and articles, interact with other users, follow people, discover content, and build their own audience.

But the main idea behind CrowdWide isn't simply to build another social network.

The goal is to create a system where new people and new communities have a genuine opportunity to be discovered.

CrowdWide can be used for many different types of content and communities:

  • Content creators
  • Personal blogs
  • Articles and writing
  • Artists
  • Developers
  • Project journeys
  • Learning communities
  • Hobbies and interests
  • New online communities

The Algorithm Idea

One of the biggest parts of CrowdWide is the recommendation and discovery system.

I don't want the system to simply say:

"This community already has millions of members, so show it to everyone."

Instead, I'm experimenting with a distribution model that intentionally creates room for different types of content.

  • 40% — New and growing communities: content from new users and smaller/newer communities gets dedicated discovery space.
  • 55% — Established communities: content from larger and established communities continues to receive substantial distribution based on relevance and engagement.
  • 5% — Viral/trending content: content that is gaining significant momentum can be surfaced regardless of the size of the community it comes from.

These percentages are not intended to be a permanent fixed formula. They're the starting point for an algorithm that I want to test and improve with real usage.

Popularity Isn't Everything

There's an important distinction I want CrowdWide to make: popularity and momentum are not the same thing.

Imagine a community with only 200 members. One of its posts suddenly receives unusually strong engagement from the people who see it.

That should be a signal that the content may deserve more exposure.

The fact that the community has only 200 members shouldn't automatically prevent it from competing with a community that has 200,000 members.

In other words:

Community size should influence the system, but it shouldn't be the entire system.

Where CrowdWide Is Right Now

CrowdWide is currently under active development.

At this point, the project has gone far beyond a simple social-media prototype.

The current system includes:

  • Posts, articles, polls, drafts and scheduled publishing
  • Media uploads and alt text
  • Hashtags, mentions, quote posts and linked replies
  • Likes, reactions, bookmarks and sharing
  • Nested comments and threaded discussions
  • Public and private communities
  • Community roles and moderators
  • Join requests and post approval
  • Community guidelines and moderation tools
  • Profiles with banners, avatars, bios and links
  • Followers and following
  • Saved posts, activity, likes and comments
  • Email verification and password recovery
  • TOTP-based 2FA and recovery codes
  • Session and device management
  • CSRF protection, security headers and rate limiting
  • Reports, moderation queues and audit logs
  • Account suspension and data export/deletion
  • Direct and group messaging infrastructure
  • Notification preferences and security notifications
  • Personalized feeds and discovery feeds
  • Viral/new content discovery
  • Trending hashtags and search filters
  • Mute and block controls
  • Content warnings
  • Production database indexes and health checks
  • Scheduled publication processing

There is still plenty left to build, but the underlying structure is now starting to look like a real platform rather than just a learning project.

Security Became a Major Focus

One of the biggest differences between VibeConnect and CrowdWide is what I learned about security.

I don't want to repeat the same mistakes from my earlier project.

CrowdWide already has features such as:

  • Email verification
  • Password reset
  • Login lockouts
  • TOTP 2FA
  • Recovery codes
  • Session/device management
  • CSRF protection
  • Security headers
  • Rate limiting
  • Moderation systems
  • Audit logging
  • Account suspension
  • Data export and deletion

Security isn't something I want to add at the very end. It needs to be part of the platform from the beginning.

What's Still Missing?

CrowdWide isn't ready for a stable public release yet.

Some of the major remaining work includes:

  • Browser push notifications
  • Better link previews and article editing
  • Media captions and transcripts
  • Moderation appeals
  • Evidence attachments
  • Temporary moderation actions
  • CAPTCHA and stronger abuse prevention
  • Automated route and permission testing
  • End-to-end signup and posting tests
  • Structured logging and monitoring
  • Backup and restore testing
  • CI and staging infrastructure
  • Virus scanning for uploads
  • Complete admin functionality
  • More reliable group chat
  • Safety/security emails for important account actions

And most importantly, I need to test the entire platform properly.

The Testing Problem

One challenge I'm currently facing is that I'm building most of this without a dedicated testing team or a group of developers constantly using the platform.

That's a major problem for a social platform.

I can test whether a feature works for me, but that doesn't mean it works correctly for everyone.

A real user will click things differently, enter unexpected data, find confusing interfaces, discover edge cases, and break things I never thought about.

That's why I don't want to rush CrowdWide into a public launch just because the website looks good.

The Road to Release

My current plan is:

  1. Finish the remaining core features.
  2. Complete the admin and moderation systems.
  3. Run extensive automated and manual testing.
  4. Prepare staging and production infrastructure.
  5. Get developers and testers to use the platform.
  6. Fix the problems discovered during testing.
  7. Run a public test/beta phase.
  8. Monitor the platform and collect feedback.
  9. Make the necessary changes.
  10. Prepare the first stable release.

I would rather release CrowdWide later and have a solid foundation than release it early with broken functionality and security problems.

What I Want CrowdWide to Become

I don't expect CrowdWide to instantly compete with the biggest social platforms.

That's not the point.

I want to build a platform where someone can join today with zero followers, create something genuinely interesting, and still have a reasonable chance of being discovered.

I want communities to be able to grow from a few people into something much larger.

I want creators to be able to build an audience without needing an audience first.

And I want the recommendation system to reward what people actually find interesting—not simply what is already popular.

Still Building 🚧

CrowdWide is nowhere near finished.

There are bugs to find, features to finish, infrastructure to build, and probably a lot of things I haven't even thought about yet.

But compared with where I started with VibeConnect, I now have a much better understanding of what it takes to build a real platform—not just the UI, but security, moderation, reliability, privacy, scalability, discovery, and the experience of the people who will actually use it.

CrowdWide started from a simple frustration: why is it so difficult for something new to get noticed?

Now I'm trying to turn that frustration into a product.

CrowdWide is still being built. And this is only the beginning. 🚀