Home Creators Posts Import Register Favorites Logout

Content

The only way for our project to move forward is to build our own modification and distribution platform on top of the foundation built into all commercial browsers. With a commercial operation focused on scaling this client to millions of web users.

We’ve had something like this operational on Windows for months, but when it comes to macOS and Linux, we’re perpetually fucked. Too much of what we do is OS-dependent, especially when we try to replicate what OBS does under the hood at a low level to improve recording/composing performance... While we’re trying to build with Mac support in mind, maintaining the whole thing cross-platform could take a lot of resources, and we still need to test whether the Windows version even has any interest in the community.

This will require a downloadable mod manager to keep both the mods and the browser up to date. The process is streamlined and will be improved over time as we scale. I’m hesitant to make it open source, even if we’re able to sell data and services rather than features, not only because of potential competition (including from LLMs trained on that code), but also because malware could use our project as a foundation. We’ve already lost the ability to modify the browser’s internals because of malicious actors. The Chromium team generally assumes that if a PC is compromised, it’s not their problem, but the people working on Chrome actually care about threat response. I really don’t know how to approach this.

There’s a reason Chrome has 265,277 extensions but none of them are the REAL ones. Our project will be such, but I’m pessimistic overall. I don’t understand why I’m doing this.

None of this makes any sense, but I can’t stall the client’s progress over a Stockholm; this psychological trap has already cost us ~18 months and god knows how much.

Like for example this is a string from a translation file.

"remove_extension": "Please remove the extension that alters the service functionality or use a different browser.",

Use a different browser? Like… what?

Were they supposed to ban Google Chrome or something?

My brain is breaking over how stupid this whole thing is. All we had to do was talk and part ways on good terms. We've stolen the biggest Omegle extension and thought keeping that community in-house was an act of loyalty during critical time. Who the fuck decided that a DDoS attack was a good response to that? I couldn’t even react to it under such pressure.

I took the summer off, hoping to gather my thoughts and that a good season might lift the mood in the server’s camp, but nothing changed. It’s still radio silence and an angry young man screaming at the clouds. At least my brain is more operational now. No amount of good-faith gestures will ever change anything; we wasted 2025 for nothing.

Now we have to take over the web because our client will either fail or become something that changes the niche forever—a generational shift in which the server and client never understand each other. We’ll capture the web and create a commercially doomed web Omegle clone for our users with 1,000 people online, while our actions have led to OmeTV currently having 500,000 Xiaomis/pixels and monetizing them through Google Play. YEEHAW!

It’s not that we can’t do something or that we’re incapable of doing it quickly; it’s about the psychological barrier of putting something at risk after I personally sacrificed Omegle.com’s niche for it, despite having a real opportunity to save it. It’s not about the ban. I don’t think any modifications to such P2P chats should exist, and if I did think otherwhise, no ban could ever have stopped me. We were making a niche tool for content creation in the first place; it was never supposed to have a lot of users. I don’t know how to stop this thought from burning in my head. I thought time would help, but the feeling of being misunderstood hasn’t gone away.

What I’m confident about is that nobody wants this. But I have to sail this ship somewhere. This time, it’s Windows, and maybe Mac later.

Files

Comments

No comments found for this post.