Toxicity not working in messenger

All of a sudden I found this error on my site.

I am not sure if this is related to the new version 14-RC2 or not. I didn't update to the new RC2 version, and I have "autoupdate OFF, but the force update, even if some files will be modified" ON. So, I am not sure if that is related or not

attached is the error.log file,

Will appreciate any help?

In permissions app, I set to allow standard members to edit and delete talks, but it looks like they can also edit and delete talks that someone else created. Is this right or is this only on my site. I need to let people only edit and delete their own talks.

I want the mobile app to look exactly like my una site (artificer theme). Is it good practice to just have a blank webview app, so when the person opens the app it only shows the mobile verson of my site as of they are opening it in the chrome web browser? Or should I use UNA's mobile app? Also, is flutter good or should it be something else?

The update went perfectly fine, no visible errors... Great job, thanks guys!👍

Criticism of the UNA development team. Addressing Excessive Notifications and Emails

Users with email and push notifications enabled are often overwhelmed by alerts. For example, if a user uploads an album of 50 photos and has 1,000 subscribers, the platform would need to generate 50,000 on-site notifications, 50,000 push notifications, and 50,000 emails—clearly excessive. Now, imagine the numbers for 10,000, 100,000, or even 1,000,000 subscribers. If a subscriber follows 1,000 friends and each friend posts an album of 10 photos, how many notifications will that user receive daily?

UNA profits from selling cloud services, so they may not prioritize optimizing this. They will collect their fees from entrepreneurs. But if you’re planning to use the UNA script to build a community, think carefully about these implications.

1. Do you realize the costs involved?
2. Is this really worth it?
3. How many users will you lose?
4. How many people will you frustrate?
5. What’s the point?
6. Who benefits from this overload? This is very clear, UNA Cloud services!
7. Your website will definitely be banned by any email provider.

Is anyone on the UNA team thinking about this? It appears NOT. Or maybe YES, maybe they did this for more profit. I don't know if they really don't care, or maybe they don't realize the implications, or maybe they did it on purpose. Instead of focusing on simply packaging a product to sell, UNA needs to address the potential risks here. With a billion users, where is this notification model headed? Without careful planning, the volume of notifications would eventually become unsustainable, leading to skyrocketing operational costs and risking platform viability.

Enhancing User Experience with Album-Level Alerts

To improve user experience, especially during large batch uploads, sending a single notification for the entire album rather than individual notifications for each image is far more practical. This issue commonly arises when multiple images are uploaded at once, resulting in an overload of notifications that clutters user feeds.

Recommended Solution: Batch Notifications at the Album Level

The best approach is to implement a notification that summarizes the entire upload. For instance, a single alert could state, “User X uploaded 50 photos to [Album Name],” giving a concise overview without overwhelming the user. This approach offers several advantages:

• Clarity: Users can immediately understand that an album has been updated with multiple pictures, instead of having to sift through hundreds of individual alerts.
• Less Intrusive: A single summary notification reduces notification fatigue, improving the user experience.
• Better Engagement: Users are more likely to engage with an album update when they perceive it as a collective event rather than an endless stream of uploads.

Implementation Options

Consider the following strategies:

1. Batching Notifications: Consolidate notifications at the backend. Once an album upload is complete, the system sends a single, consolidated notification.
2. Frequency Controls: Allow users to toggle notification settings for individual or batch updates, for users who want more granular notifications.

In summary, album-level notifications for large uploads not only reduce the number of notifications and emails but also provide an efficient, streamlined approach that enhances usability and engagement.

Scalability Concerns for Future Growth

If anyone plans to make money with this platform, take a moment to do the financial math. You’ll see that this script is poorly designed and simply burns through money without delivering sustainable value. It appears that the UNA team has learned nothing from Dolphin’s challenges. So, entrepreneurs, take note—UNA is nothing more than a money pit. Investing in this script could lead to nothing but bankruptcy.

The moral of this discussion is that building a successful community requires a focus on user experience and sustainability. While platforms like UNA may offer interesting services, excessive notifications can overwhelm users, increase operational costs, and ultimately harm community engagement. Entrepreneurs should critically assess the implications of their choices and prioritize effective communication strategies, such as batching notifications, to ensure the long-term viability of their platforms. Ignoring these factors could lead to frustration among users and potential financial failure. In essence, thoughtful planning and user-centric design are key to fostering a thriving online community.

Personal thoughts about Boonex.

Would I do business with this script? Yes, I would only sell cloud services to those who aspire to have a social network. There are plenty of dreamers in this world. However, I’m fully aware of how poorly designed it is, so I wouldn’t use it for business purposes. For now, I’m just experimenting and testing it personally to explore its limitations and potential.

• If the UNA team doesn't prioritize building a viable script instead of merely selling cloud services, this script will never evolve. It will only drain people's wallets and frustrate many users. If UNA continues down this path, I genuinely believe it’s evident that this script has no future.
• I haven’t seen any positive changes since the UNA team took over Dolphin. Dolphin support has stopped. The migration script doesn’t work from Dolphin to UNA and many years have already passed ,and UNA is a poorly functioning platform and all modules have become poorer in functions.. It’s like a car that consumes 100 liters per 100 kilometers, creaking at every joint and making noise for no reason and lose parts while driving it on the road.. So where is the evolution?
• If UNA decides to change its name tomorrow and subsequently abandons the UNA platform in favor of another rebranding, similar to what they did with DOLPHIN, all the investments made here will be in vain. Until I have the ability to migrate my sites from DOLPHIN to UNA, I find it difficult to justify further investment in UNA. In my last test, I managed to migrate only users and articles, photos, videos, avatars, and other content are still not migrating.

I have invested over 30,000 euros in the development of my DOLPHIN sites, only to discover that there is now no support available for them. I have purchased licenses and modules without any return, and my expenditures on advertising and time have ultimately been in vain. Given the current chaos surrounding notifications, I find myself quite frustrated; I would much rather enjoy a cup of coffee and watch a good movie.