Thanks for the suggestion. I think there is a small but important technical misunderstanding here that is worth clarifying.

WebRTC by itself is not a “free live streaming” solution. It is simply a real-time communication technology. The actual cost depends entirely on how the stream is hosted and scaled.

For example,

Let’s say you have 1 broadcaster streaming at 720p (around 3–4 Mbps) and 100 concurrent viewers.

In this case, the broadcaster sends roughly 4 Mbps to the server, but the server needs to deliver about 400 Mbps continuously to viewers. Over a month, this easily turns into 130–150 TB of outbound traffic.

To handle this properly with WebRTC, you need more than just WebRTC support:

- an SFU media server (mediasoup, Janus, LiveKit, etc.)
- TURN services for NAT and firewall cases
- strong outbound bandwidth
- ongoing monitoring and maintenance

In real production environments, a setup like this usually costs somewhere between 300 and 800 USD per month, depending on traffic and infrastructure. As the audience grows, the cost grows with it.

So while there may be no Agora subscription, the expense does not disappear. It simply shifts to servers, bandwidth, and operational responsibility. For many admins, self-hosted WebRTC becomes more expensive and less stable at scale.

Most scripts that advertise “free WebRTC live streaming” either limit usage to 1:1 calls, or provide demo-level implementations that are not designed for real traffic.

This product focuses on stability and scalability in real-world usage, rather than marketing a “free” solution that introduces hidden costs later on. I prefer to be transparent about that.

Ok thank you for explanation

Thanks for suggestion

Just a quick note: your item support period ended on July 14, 2025. To continue receiving support, you’ll need to renew/extend your support via Envato.

Thank you for your understanding.

Has an update with Brazilian Portuguese already bI left you a question in the ticket. een released or not?

No, it will be published in the next update. Your ticket was answered about 12 hours ago.

Thank you, amorphaticode. I’m always moving forward for the dizzy family.

Yes : https://prnt.sc/SZm9MAb9UVoj all platform content adult only used https://www.ageverif.com free

Thank you for that. I’ll look into it and try to include it in the update.

thank

Aha… Good to hear. Thank you for the prompt answer!

Just bought it

Thank you for your purchase, and welcome to the Dizzy family If you need any help during installation or later on, feel free to reach out via the support system. I’ll be happy to help.

Good updaye mean ! for Agency landing page add choice register Become Agency or Creator

Good updaye mean ! for Agency landing page add choice register Become Agency or Creator

Thank you. I will do it in future updates.

Thanks for your question.

Dizzy runs on standard hosting environments and does not require a high-end server to get started.

Base requirements: (pdo, curl, mbstring, openssl, gd, etc.) – HTTPS support

- PHP 8.0+ (8.1 recommended)
- MySQL 5.7+ or MariaDB 10.3+
- Apache or Nginx
- Common PHP extensions enabled

About video & Reels uploads: For best results and automatic video optimization, FFmpeg is recommended. When available, FFmpeg is used to:

- Normalize video formats
- Handle Reels aspect ratios
- Ensure consistent resolutions
- Generate thumbnails

Many VPS providers already include FFmpeg, and it can be added easily if needed. The system adapts to your hosting setup, and small communities can start without complexity.

For live streaming and higher traffic, a VPS is recommended for optimal performance.

It would be really interesting to add a Media section on the creator’s profile, where users can find exclusive content sold individually, with the price and the package details (for example: 1 video + 3 photos, etc.).

Dizzy already does this. It places the user’s profile URL on the images. It also writes what users have purchased during the purchase stage, just as you said. For example, if there is only text in the post they want to purchase and no image or video, it is displayed as https://ibb.co/NgdST1t6 https://ibb.co/BJ3ZFGs

Your suggestions regarding the agency feature are on my to-do list. I am truly grateful for your suggestions.

good job!

Thank you for your feedback, I appreciate you taking the time to share your experience.

Regarding the live video issue: As already discussed and verified multiple times, the live streaming system itself is working correctly in the current release. This has been confirmed on the public demo and across multiple test environments and devices. When the same feature works on the demo but not on a specific installation, this indicates an environment-level or browser permission issue rather than a core software bug. There is no confirmed or reproducible camera/microphone blocking issue affecting the general user base.

• HTTPS is correctly enabled
• Browser permissions are granted
• Agora keys are configured properly

Environment-specific investigations and file-level analysis are handled within active support, as documented in the support policy.

Regarding the night style for communities: Thank you for pointing this out. UI consistency between light and dark modes is important, and community pages are actively being reviewed as part of ongoing UI improvements. Visual refinements and theme consistency adjustments are handled through regular updates.

I appreciate constructive feedback, and any verified, general issues affecting all users are always addressed through official releases.

You’re very welcome.

The new language “Brazilian Portuguese” has been added to the next update.

nice

Thanks for the suggestion.

I understand what you mean by presets like beauty, low CPU, weak laptop, night or daylight modes.

Dizzy uses Agora and LiveKit for live camera streaming, so the video comes directly from the browser via WebRTC. Because of this, OBS-style heavy GPU filters are not applied on the server side.

That said, a preset approach is possible in a more practical way, for example by adjusting resolution, frame rate, bitrate, and performance-related parameters. This allows modes such as low CPU or weaker device presets, as well as simple lighting-focused profiles, without putting extra load on the system.

I’m keeping this in mind for future updates and evaluating what can be added in a stable and reliable way across different devices and browsers.

Thank you for sharing the idea.

Thank you very much for the kind words, I truly appreciate it.

The update was already close to completion and most of the groundwork had been prepared, I was in the final testing and verification phase. However, after seeing your OBS suggestion, I wanted to include it right away and deliver something even more valuable.

Please feel free to share your feedback, ideas, or improvement suggestions regarding the OBS integration. I’m actively collecting input, and I’d be happy to incorporate your recommendations and enhancements into the very next update.

Thanks again for the support and motivation.

Hi,

I will send you a message from codecanyon contact about more OBS overlay improvement that will makes more interesting as other platform here already playing nice for few years

Hi, I’ve received and reviewed your message, thank you for sharing your OBS overlay improvement ideas.

I’ve gone through the details you sent. Enhancements that strengthen the OBS integration and improve the overall experience are planned to be evaluated and included in an upcoming update.

Thanks again for your valuable input and continued interest.

Hi, I’d like to clarify this once more in a clear and factual way.

In addition, update frequency is not a matter of speculation. It is transparently visible in the ChangeLog, with exact approval dates provided by Envato. Anyone can objectively verify how regularly the product is maintained.

Regarding your claim about sales: product performance cannot be reduced to a single narrative or assumption. Public comments, personal interpretations, or third-party claims do not reflect actual sales data, which is tracked internally and does not support the statement you’ve made.

It’s also important to note that the latest update was approved today, and this comment was posted within minutes of that approval. That alone demonstrates ongoing development and active support.

All of your questions have already been answered clearly and repeatedly. At this point, continuing to frame the same topic in a confrontational or misleading way does not add value to the discussion and is unfair to the work being done.

If potential buyers wish to evaluate the product, they can do so based on:

- the live demo
- the documented features
- the public ChangeLog
- and the official FAQ

That information is complete, transparent, and up to date.

Thank you.

Yes, a mobile app is planned for the platform.

However, due to the size and complexity of the system, this is not something that can be delivered immediately. The platform includes many advanced features, and delivering a stable, production-ready mobile application requires careful planning and development time.

At this stage, I am more likely to use React Native rather than Flutter, as it allows better alignment with the existing web architecture and offers strong long-term maintainability for both Android and iOS.

Once the core platform features are fully stabilized and matured, mobile application development will be considered as the next step. Updates will be shared transparently as the roadmap progresses.

do u have any roadmap, please share

I understand the interest in a roadmap, however I’m not able to share a public roadmap at this stage.

The platform includes a large number of advanced and tightly integrated features, and for architectural and performance reasons, the mobile app will not replicate the full web experience. Certain functionalities will remain web-dependent by design.

What I can confirm at this point is that the planned mobile app will focus on core user interactions such as:

- Visiting user profiles
- Likes and basic engagement
- Content sharing

For real-time features such as chat and live streaming, the plan is to develop a separate, dedicated application, as these require a different technical approach to ensure scalability and stability.

Beyond this scope, I’m not able to share additional details at the moment. Any confirmed developments will be communicated transparently when they are ready.

If you are currently using v2.21 or another much older version and the latest release is v5.3.x, unfortunately there is no safe one-click or direct incremental update path available.

Why a sequential version-by-version update is not recommended for very old releases

• Between v2.x and v5.3.x, there have been 55+ individual updates.
• Each update includes its own updateSQL.sql, covering different scopes such as:
  • bug fixes
  • database schema changes
  • new tables
  • removed or modified columns
  • logic and feature updates
• Applying dozens of incremental updates sequentially on a very old installation greatly increases the risk of:
  • missing or duplicated SQL changes
  • database schema inconsistencies
  • conflicts between legacy and current application logic
• For this reason, a long sequential update chain is not considered a reliable or safe approach for production websites with real data.

Recommended and supported approach for very old versions

If your website is actively used and contains real data, the safest method is:

1. Create a new empty database.
2. Import the full SQL file of the latest version (v5.3.x).
   This ensures the database structure is 100% correct.
3. From your old database, selectively migrate only the required data such as users, posts, subscriptions, payments, etc.
   Please do not blindly import everything.
4. Upload only the latest version files.
5. Update connect.php with the new database credentials.
6. Carefully merge the uploads/ directory:
   • Keep all user-uploaded files
   • Add any new folders introduced in recent versions
   • Do not overwrite existing user content

Important warning

This process must be handled carefully. Missing a required table or dataset during migration may result in errors or unexpected behavior later. Always take full backups before starting.

• Testing the process on a staging installation first, or
• Using professional paid support for a controlled and safe migration

This is currently the only reliable way to move from very old versions to the latest release without data corruption or structural issues.